If a switchover is triggered on the SBC SWe platform due to any of the following reasons, a media outage of 20 seconds occurs for the stable calls:
The SBC SWe is deployed in a redundant High Availability (HA) configuration whereby a standby virtual machine (VM) protects the active VM. The HA configuration shares the data between the VMs which protect each other in a 1-1 redundancy model.
It is recommended that HA pair needs to be installed on two different physical hosts. For more information on setting up logical connections HA nodes, refer to Setting Up Logical Connection between High Availability Nodes.
The following procedure describes how to install the SBC application software on HA system (both active and standby VM).
If any mistakes occur during the installation, you must reinstall the application. Before re-installing, execute the following commands from the console to check the application status and the DRBD status:
service sbx stop
service drbd stop
service drbd status
service sbx status
drbd not loaded
If the above output displays, it is safe to continue with the installation.
If you are using a wide-area or low-bandwidth connection, the time delay over the network may be long enough to cause the virtual machine to start auto-repeat. This can manifest in unintended repeated keystrokes when typing in a remote console. If you experience this issue, refer to the VMware Knowledge Base for a solution.
Launch the EMA. Refer to Logging on to EMA in Platform Mode for guidance.
Navigate to Administration > System Administration > Software Install/Upgrade tab. The Packages screen displays.
The Install Software pane expands and displays the Install Version, Management Ports (configured in post-OS installation) and System Configuration details.
Enter the System Configuration details.
Select Peer Hostname and enter peer hostname.
Choose Active option for Server Role to designate the Active server as the one you are configuring.
Click Start Installation.
The installation process starts and displays the installation status on the Installation Log section.
Perform pre-install checks.
Extract the package contents.
Install SBC service.
The installation checks whether ConnexIP OS version is compatible with the SBC application. If the OS upgrade is required, it performs the OS upgrade first and reboots the server. Once it is rebooted, login into the EMA again to continue with the SBC application.
Initialize SBC service.
Update Host Name
Reboot system.
Log on to EMA platform. The new SBC application version displays on the Monitoring > Dashboard > System and Software Info.
Verify the system status using Administration > System Administration > Platform Management menu.
From the EMA, install the SBC licenses required in order to use SBC application and its features. See Managing SBC Node-Locked Licenses for HW and SWe SBCs for guidance.
Continue upgrading the standby server once all the status is up and running.
Repeat steps 2 through 8 to install the SBX application on the Standby peer, but with the following changes to steps 4c to 4e:
Step 4c. Enter Standby server name in Local Hostname field, which is typically the System Name with a letter b appended to the end.
Step 4d. Enter Active server name for Peer Hostname field, which is typically the System Name with a letter a appended to the end.
Step 4e. Choose the "Standby" option for Server Role to designate the Standby server as the one you are configuring.
You must use the same System Name and TIPC NETID for both active and standby servers.
Once the installation is completed, verify the system status for both "Active" and "Standby" servers using Monitoring> Dashboard> System and Software Info menu.