Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c86e9b2550016ec54396b5000a, userName='null'}
JIRAIDAUTHSBX-129446
REV5UserResourceIdentifier{userKey=8a00a0c86e9b2550016ec54396b5000a, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a0c86e9b2550016ec54396b5000a, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a0c86e9b2550016ec54396b5000a, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a0c86e9b2550016ec54396b5000a, userName='null'}


Info
titleNote

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

Anchor
BackToTop
BackToTop

After installing the SBC OS on the KVM instance, you must install the standalone SBC SWe application.

To install the standalone SBC SWe application:

  1. Launch EMA in platform mode. For more information on Platform mode login, see refer to EMA Platform Mode - Login Window.


  2. Select Administration → System Administration → Software Install/Upgrade tab.
    The Packages screen displays:

    Include Page
    _Screenshot_disclaimer
    _Screenshot_disclaimer
  3. Select Package Name to install and click Install Software.
    The Install Software section expands and displays the Install Version, Management Ports (configured in post-OS installation) and System Configuration information:

    Info
    titleNote

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


  4. Perform the steps to configure the system information:
    1. Select Standalone in the HA Configuration field.
    2. Enter a system name in the System Name field.

    3. Enter a local hostname in the Local Hostname field.

      Info

      For more information, see System Name and Hostname Conventions.


    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.
    The installation process starts and displays the installation status on the Installation Log section. After installing the application reboots and prompts you to login.
  6. The installation process starts and displays the installation status on the Installation Log section.

    1. Perform the pre-install checks:



    2. Extract the package contents:



    3. Install the SBC service:

      Info
      titleNote

      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 the SBC service:


    5. Update the Host Name:


    6. Reboot the system:


  7. Log on to the application in EMA mode. For more information on EMA mode login, see EMA Mode - Login Window.
    The System Status screen displays:

    Include Page
    _Screenshot_disclaimer
    _Screenshot_disclaimer

  8. Select Monitoring → Dashboard → System and Software Info.
    The System and Software Info screen displays:

    Verify the interface configuration set during installation.

  9. Select Administration → System Administration → Platform Management to verify the system status.


  10. Install the required SBC licenses to use SBC application. For more information on licensing SBC, see Managing SBC Licenses for guidance.