In this section:

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.

Note

To recover from the default indices, refer to MOP to Recover from Default Indices in Standalone SBC SWe, if applicable.

The following procedure describes how to install the SBC SWe application as a standalone configuration:

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 click Install Software.


    Note

    The figures shown in this procedure are intended as examples of the user interface and might not match the presented images exactly.

    Selecting SBC Package

     
    The Install Software section 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 Standalone in the HA Configuration field.

    2. Select System Name field and enter the system name.

    3. Select Local Hostnameand enter local hostname.

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

      Installation Configuration Screen

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

  5. Click Start Installation.

    Starting the 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 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

      Rebooting the System

       

  7. Log on to EMA. 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 the SBC application and its features. See Node-Locked Licensing for guidance.


 Continue to Installing Securelink on Virtual Machine