Versions Compared

Old Version 2

changes.mady.by.user Scoggins, Bruce

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

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

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


Info
titleNote

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

Include Page
_media_outage_Swe
_media_outage_Swe

The 

Spacevars
0product2
 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.

Info
titleNote

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

Spacevars
0product
application software on HA system (both active and standby VM).

Info
titleNote

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, executerun:
    service drbd stop
  3. Check the status of DRBD by executingentering:
    service drbd status
  4. Check the service status by executingentering:
    service sbx status

    The output should display:
    drbd not loaded

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


Note
titleKeystroke 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.
    include
    _Screenshot_disclaimer
    _Screenshot_disclaimer Caption0Figure 1: Selecting SBC Package
    Image RemovedImage Added


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

    Caption0



    Figure

    1

    2: Install SBC Application

    Image Removed

    Image Added

    Info
    titleNote

    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.

      caption
      Info
      titleNote

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

      0Figure
      1

      Figure 3: System Configuration Pane

      Image Removed

      Image Added

    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.

    Caption0Figure1

    Figure 4: Start Installation

    Image Removed

    Image Added

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

    1. Perform pre-install checks.

      Caption0Figure1

      Pre-Install Checks

      Image Removed

    2. Extract the package contents.

      Caption0

      Figure1Extracting Package Contents

      Image Removed

    3. Install SBC service.

      Caption
      0Figure
      1Installing SBC Service
      Image Removed

      Note
      Info
      title

      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.

      Caption
      0Figure
      1Initialize SBC Service
      Image Removed

    5. Update Host Name

      Caption0Figure1Updating

      Host Name

      Image Removed

    6. Reboot system. Caption0

      Figure 1RebootImage Removed5: Installation Steps
      Image Added

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

    Caption


    0Figure1

    Figure 6: Displaying New SBC App Version

    Image Removed

    Image Added

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

    Caption0



    Figure

    1

    7: Verifying System Status

    Image Removed

    Image Added

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

    Info
    titleNote

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


  10. Repeat steps 2 through 8 to install the

    Spacevars
    0prodkey
     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.

    Info
    titleNote

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

    Caption
    0Figure
    1


    Figure 8: Configuring Standby Server

    Image Removed

    Image Added

  11. Once the installation is completed, verify the system status for both "Active" and "Standby" servers using Monitoring> Dashboard> System Monitoring → Dashboard → System and Software Info menu.

    Caption0



    Figure

    1

    9: Verifying System Status for Active Server

    Image Removed

    Caption0

    Image Added

    Figure

    1

    10: Verifying System Status for Standby Server

    Image Removed

    Image Added


Noprint


Panel
bgColortransparent
borderWidth2

 Continue to Installing Securelink on Virtual Machine


Pagebreak

Include Page
_media_outage_Swe
_media_outage_Swe

The 

Spacevars
0product2
 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.

Info
titleNote

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

Spacevars
0product
application software on HA system (both active and standby VM).

Info
titleNote

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, executerun:
    service drbd stop
  3. Check the status of DRBD by executingentering:
    service drbd status
  4. Check the service status by executingentering:
    service sbx status

    The output should display:
    drbd not loaded

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


Info
titleNote

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.


    Include Page_Screenshot_disclaimer


    _Screenshot_disclaimer Caption


    0Figure1

    Figure 11: Selecting SBC Package

    Image Removed

    Image Added


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

    Caption0



    Figure

    1

    12: Install SBC Application

    Image Removed

    Image Added

    Info
    titleNote

    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.

      0
      Info
      titleNote

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

      Caption


      Figure

      1System

      13: System Configuration Pane

      Image Removed

      Image Added


    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.

    caption

    0Figure1

    Figure 14: Start Installation

    Image Removed

    Image Added

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

    1. Perform pre-install checks.

      Caption0Figure1

      Pre-Install Checks

      Image Removed

    2. Extract the package contents.

      Caption0

      Figure1Extracting Package Contents

      Image Removed

    3. Install SBC service.

      Caption
      0Figure
      1Installing SBC Service
      Image Removed

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

      Caption0Figure

      1Initialize SBC Service

      Image Removed

    5. Update Host Name

      Caption0Figure1Updating

      Host Name

      Image Removed

    6. Reboot system.

      Caption
      0Figure
      1Reboot

      Image Removed

      Figure 15: Installation Steps
      Image Added

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

    Caption



    Figure 16: Displaying

    0Figure1Displaying

    New SBC App Version

    Image Removed

    Image Added

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

    Caption0



    Figure

    1Verifying

    17: Verifying System Status

    Image Removed

    Image Added


  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.


    Info
    titleNote

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


  10. Repeat steps 2 through 8 to install the

    Spacevars
    0prodkey
     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.

    captionConfiguring
    Info
    titleNote

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

    0Figure
    1


    Figure 18: Configuring Standby Server

    Image Removed

    Image Added


  11. Once the installation is completed, verify the system status for both "Active" and "Standby" servers using Monitoring> Dashboard> Monitoring → Dashboard → System and Software Info menu.

    Caption0



    Figure

    1Verifying

    19: Verifying System Status for Active Server

    Image Removed

    Caption0

    Image Added

    Figure

    1Verifying

    20: Verifying System Status for Standby Server

    Image Removed

    Image Added


Noprint


Panel
bgColortransparent
borderWidth2

 Continue to Installing Securelink on Virtual Machine

pagebreak