You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

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 

Unable to show "metadata-from": No such page "_space_variables"
 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

Unable to show "metadata-from": No such page "_space_variables"
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:

  1. Enter the command:
    service sbx stop
  2. After the services are stopped, execute:
    service drbd stop
  3. Check the status of DRBD by executing:
    service drbd status
  4. Check the service status by executing:
    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.

     

    Selecting SBC Package


    The Install Software pane expands and displays the Install Version, Management Ports (configured in post-OS installation) and System Configuration details.

    Install SBC Application

    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.

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

      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.

     

    Start Installation

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

    1. Perform pre-install checks.

      Pre-Install Checks

    2. Extract the package contents.

      Extracting Package Contents

    3. Install SBC service.

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

      Initialize SBC Service

    5. Update Host Name

      Updating Host Name

    6. Reboot system.

      Reboot

  7. Log on to EMA platform. The new SBC application version displays on the Monitoring > Dashboard > System and Software Info.

    Displaying New SBC App Version

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

    Verifying System Status

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

     

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

  10. Repeat steps 2 through 8 to install the

    Unable to show "metadata-from": No such page "_space_variables"
     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.

    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.

    Verifying System Status for Active Server

    Verifying System Status for Standby Server

 Continue to Installing Securelink on Virtual Machine

  • No labels