DO NOT SHARE THESE DOCS WITH CUSTOMERS!
This is an LA release that will only be provided to a select number of PLM-sanctioned customers (PDFs only). Contact PLM for details.
To recover from the default indices, refer to Recovering from Default Indices in 1:1 HA SBC SWe, if applicable.
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 the HA pair is 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.
Figure 2: Install SBC Application
The signature file of the SBC package verifies the integrity of the package contents before proceeding with the SBC installation.
Enter the System Configuration details.
Select Peer Hostname and enter peer hostname.
For more information, refer to System Name and Hostname Naming Conventions.
Figure 3: System Configuration Pane
Choose the Active option for Server Role to designate the Active server as the one you are configuring.
Click Start Installation.
Figure 4: 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
Log on to EMA platform. The new SBC application version displays on the Monitoring → Dashboard → System and Software Info.
Figure 6: Displaying New SBC App Version
Verify the system status using Administration → System Administration → Platform Management menu.
Figure 7: Verifying System Status
From the EMA, install the SBC licenses required in order to use SBC application and its features. See Node-Locked Licensing 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.
Figure 8: Configuring Standby Server
Once the installation is completed, verify the system status for both "Active" and "Standby" servers using Monitoring → Dashboard → System and Software Info menu.
Figure 9: Verifying System Status for Active Server
Figure 10: Verifying System Status for Standby Server
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 the HA pair is 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.
Select the Package Name to install and then click Install Software.
Figure 11: Selecting SBC Package
The Install Software pane expands and displays the Install Version, Management Ports (configured in post-OS installation) and System Configuration details.
Figure 12: Install SBC Application
The signature file of the SBC package verifies the integrity of the package contents before proceeding with the SBC installation.
Enter the System Configuration details.
Select Peer Hostname and enter peer hostname.
For more information, refer to System Name and Hostname Naming Conventions.
Figure 13: System Configuration Pane
Choose the Active option for Server Role to designate the Active server as the one you are configuring.
Click Start Installation.
Figure 14: 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.
Figure 15: Installation Steps
Log on to EMA platform. The new SBC application version displays on the Monitoring → Dashboard → System and Software Info.
Figure 16: Displaying New SBC App Version
Verify the system status using Administration → System Administration → Platform Management menu.
Figure 17: Verifying System Status
From the EMA, install the SBC licenses required in order to use the SBC application and its features. See Node-Locked Licensing 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.
Figure 18: Configuring Standby Server
Once the installation is completed, verify the system status for both "Active" and "Standby" servers using Monitoring → Dashboard → System and Software Info menu.
Figure 19: Verifying System Status for Active Server
Figure 20: Verifying System Status for Standby Server