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.

Note

To recover from the default indices, refer to Recovering from Default Indices in 1:1 HA SBC SWe, if applicable.


Note

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:

  • if there is process hang in the media handling application,
  • if media handling process is manually killed or because of the core dump.

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.

Note

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).

Note

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:

  1. Enter the command:
    service sbx stop
  2. After the services are stopped, run:
    service drbd stop
  3. Check the status of DRBD by entering:
    service drbd status
  4. Check the service status by entering:
    service sbx status

    The output should display:
    drbd not loaded

If the above output displays, it is safe to continue with the installation.

Keystroke Errors After OS 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.

Procedure

  1. Launch the EMA. Refer to Logging on to EMA in Platform Mode for guidance.

  2. Navigate to Administration → System Administration → Software Install/Upgrade tab. The Packages screen displays.

  3. Select the Package Name to install and then click Install Software.

    Figure 1: 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 2: Install SBC Application

    Note

    The signature file of the SBC package verifies the integrity of the package contents before proceeding with the SBC installation.

  4. Enter the System Configuration details.

    1. Select HA Pair in the HA Configuration field.
    2. Select System Name field and enter the system name.
    3. Select Local Hostname and enter local hostname.

    4. Select Peer Hostname and enter peer hostname.

      Note

      For more information, refer to System Name and Hostname Naming Conventions.

      Figure 3: System Configuration Pane

    5. Choose the Active option for Server Role to designate the Active server as the one you are configuring.

    6. Keep default Active Primary CE IP.
    7. Keep default Standby Primary CE IP.
    8. Keep default Inter CE Prefix. The inter CE prefix is the netmask of the network in which the Inter CE IPs are configured.
    9. Use default TIPC NETID value (1500) if no other SBC SWe running in the same subnet.
    10. Select NTP Server IP field and enter the NTP server IP address.
    11. Select NTP Server Time Zone field and enter the NTP time zone.

  5. Click Start Installation.

    Figure 4: Start Installation

  6. The installation process starts and displays the installation status on the Installation Log section.

    1. Perform pre-install checks.

    2. Extract the package contents.

    3. 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.

    4. Initialize SBC service.

    5. Update Host Name

    6. Reboot system.

      Figure 5: Installation Steps


  7. 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

  8. Verify the system status using Administration → System Administration → Platform Management menu.

    Figure 7: Verifying System Status

  9. From the EMA, install the SBC licenses required in order to use SBC application and its features. See Node-Locked Licensing for guidance.

    Note

    Continue upgrading the standby server once all the status is up and running.

  10. 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.

    Note

    You must use the same System Name and TIPC NETID for both active and standby servers.


    Figure 8: Configuring Standby Server

  11. 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

 Continue to Installing Securelink on Virtual Machine


Note

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:

  • if there is process hang in the media handling application,
  • if media handling process is manually killed or because of the core dump.

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.

Note

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).

Note

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:

  1. Enter the command:
    service sbx stop
  2. After the services are stopped, run:
    service drbd stop
  3. Check the status of DRBD by entering:
    service drbd status
  4. Check the service status by entering:
    service sbx status

    The output should display:
    drbd not loaded

If the above output displays, it is safe to continue with the installation.

Note

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.

Procedure

  1. Launch the EMA. Refer to Logging on to EMA in Platform Mode for guidance.

  2. Navigate to Administration → System Administration → Software Install/Upgrade tab. The Packages screen displays.

  3. 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

    Note

    The signature file of the SBC package verifies the integrity of the package contents before proceeding with the SBC installation.

  4. Enter the System Configuration details.

    1. Select HA Pair in the HA Configuration field.
    2. Select System Name field and enter the system name.
    3. Select Local Hostname and enter local hostname.

    4. Select Peer Hostname and enter peer hostname.

      Note

      For more information, refer to System Name and Hostname Naming Conventions.


      Figure 13: System Configuration Pane

    5. Choose the Active option for Server Role to designate the Active server as the one you are configuring.

    6. Keep default Active Primary CE IP.
    7. Keep default Standby Primary CE IP.
    8. Keep default Inter CE Prefix. The inter CE prefix is the netmask of the network in which the Inter CE IPs are configured.
    9. Use default TIPC NETID value (1500) if no other SBC SWe running in the same subnet.
    10. Select NTP Server IP field and enter the NTP server IP address.
    11. Select NTP Server Time Zone field and enter the NTP time zone.

  5. Click Start Installation.

    Figure 14: Start Installation


  6. The installation process starts and displays the installation status on the Installation Log section.

    1. Perform pre-install checks.

    2. Extract the package contents.

    3. Install SBC service.

      Note

      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.

    4. Initialize SBC service.

    5. Update Host Name

    6. Reboot system.

      Figure 15: Installation Steps

  7. 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


  8. Verify the system status using Administration → System Administration → Platform Management menu.

    Figure 17: Verifying System Status

  9. From the EMA, install the SBC licenses required in order to use the SBC application and its features. See Node-Locked Licensing for guidance.

    Note

    Continue upgrading the standby server once all the status is up and running.

  10. 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.

    Note

    You must use the same System Name and TIPC NETID for both active and standby servers.


    Figure 18: Configuring Standby Server

  11. 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

 Continue to Installing Securelink on Virtual Machine