The SBC SWe Edge (on-premises and virtual machine-based version only) fully supports High Availability (HA) with mid-call failover. This document provides information on upgrading a standalone (SA) Node-Locked Licensed (NLL) SWe Edge to an HA NLL SWe Edge. It covers two distinct scenarios:

  • The SBC SWe Edge is connected to a Ribbon Application Management Platform (RAMP) for management and monitoring.
  • The SBC SWe Edge is not connected to RAMP.
Note

You must purchase a license to upgrade your SA NLL SWe Edge to an HA NLL SWe Edge. For more information on HA licenses, refer to:

Upgrading an SA Node-Locked Licensed SWe Edge to an HA Node-Locked Licensed SWe Edge

The NLL licensing method is where an installed license file locks sessions and features to a specific SBC node, identified through its hardware serial number or Virtual Machine Universal Unique Identifier (UUID). Upgrading an SA NLL SWe Edge to an HA NLL SWe Edge allows you to use HA functionality on the SBC SWe Edge that provides on-site support for increased stability with two instances of SBC Edge, where a Standby SBC mirrors and instigates call-takeover during any Active SBC failure.  

For SA SWe Edge, you use only one SWe Edge ID to generate the NLL. For HA, you use the SWe Edge ID of both the Active and the Standby instances to generate the NLL. Due to the different ways of generating an NLL for an SA node and an HA pair, if you managed your SA SWe Edge through RAMP, you must deregister and remove the SA from RAMP. 

For more information on HA functionality on the SBC SWe Edge, refer to Deploying High Availability on the SBC SWe Edge.

The following provides information on upgrading an SA NLL SWe Edge to an HA NLL SWe Edge in two scenarios:


Prerequisites 

  • One SBC SWe Edge instance ESXi, KVM, or Hyper-V host with: 

    • a minimum of four vCPUs with a memory of 4 GB

    • all five network interfaces (mgt0, pkt0, pkt1, pkt2, pkt3) mapped through network configuration

      Of the five network interfaces, you must leave one available to convert to HA. For more information on the network interfaces, refer to High Availability Interface.

       

    • Release 12.0.0 or above installed on the system.

  • Peer instance HA IP addresses and an associated Netmask. 

  • Access to Ribbon Application Management Platform (RAMP) version 23.06 or later. For more information on RAMP, refer to About RAMP and How to Access RAMP.