Page History

Info
title Note
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
0 product2

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

Spacevars
0 product

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

Info
title 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: Enter the command: service sbx stop After the services are stopped, executerun: service drbd stop Check the status of DRBD by executingentering: service drbd status 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
title 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.
   Include PageScreenshot_disclaimerScreenshot_disclaimer Caption0
   
   Figure 1: Selecting SBC Package
   Image Modified

   
   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 Modified

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

      0

      Info
      title Note
      For more information, refer to System Name and Hostname Naming Conventions.
      Caption

      Figure

      1

      3: System Configuration Pane
      Image Modified

   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 4: Start Installation
   Image Modified

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

   1. Perform pre-install checks.
      

      Caption0Figure1Pre-Install Checks

      Image Removed

   2. Extract the package contents.

      Caption0Figure1Extracting Package Contents

      Image Removed

   3. Install SBC service.

      Caption0Figure1Installing SBC Service
      Note

      Image Removed
      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

      0	Figure
      1	Initialize SBC Service

      Image Removed

   5. Update Host Name

      Caption0Figure1Updating

      Host Name

      Image Removed

   6. Reboot system.caption
      0Figure
      Figure 5: Installation Steps1Reboot
      Image Modified
      
      

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

   caption

   
   

   0Figure

   
   

   1

   Figure 6: Displaying New SBC App Version
   Image Modified

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

   Caption0

   
   
   Figure

   1

   7: Verifying System Status
   Image Modified

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
   title Note
   Continue upgrading the standby server once all the status is up and running.

   
   

10. Repeat steps 2 through 8 to install the

    Spacevars
    0 prodkey

     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.

    0

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

    
    Figure

    1

    8: Configuring Standby Server
    Image Modified

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.

    caption

    
    

    0Figure

    
    

    1 Caption0

    Figure 9: Verifying System Status for Active Server
    Image Modified

    
    

    Figure

    1

    10: Verifying System Status for Standby Server
    Image Modified
    

    
    

Noprint
Panel bgColor transparent borderWidth 2  Continue to Installing Securelink on Virtual Machine

Pagebreak

Include Page
media_outage_Swe media_outage_Swe

The 

Spacevars
0 product2

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

Spacevars
0 product

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

Info
title 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: Enter the command: service sbx stop After the services are stopped, executerun: service drbd stop Check the status of DRBD by executingentering: service drbd status 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
title 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.

   
   Include PageScreenshot_disclaimer

   
   
   Figure 11: 

   Screenshot_disclaimer Caption0Figure1

   Selecting SBC Package
   Image Modified

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

   caption

   
   

   0Figure1

   
   Figure 12: Install SBC Application
   Image Modified

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

      0

      Info
      title Note
      For more information, refer to System Name and Hostname Naming Conventions.
      Caption

      
      Figure

      1System

      13: System Configuration Pane
      Image Modified
      

      
      

   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 Modified
   
   

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

   1. Perform pre-install checks.
      

      Caption

      0	Figure
      1	Pre-Install Checks

      Image Removed

   2. Extract the package contents.

      Caption

      0	Figure
      1	Extracting Package Contents

      Image Removed

   3. Install SBC service.

      Caption

      0	Figure
      1	Installing SBC Service

      Image Removed

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

      Caption0Figure

      1Initialize SBC Service

      Image Removed

   5. Update Host Name

      Caption0Figure1Updating

      Host Name

      Image Removed

   6. Reboot system.

      Caption0

      Reboot

      Figure

      1

      15: Installation Steps

      
      Image Modified
      

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

   caption

   
   

   0Figure

   
   

   1Displaying

   Figure 16: Displaying New SBC App Version
   Image Modified
   
   

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

   Caption0

   
   
   Figure

   1Verifying

   17: Verifying System Status
   Image Modified

   
   

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
   title Note
   Continue upgrading the standby server once all the status is up and running.

   
   

10. Repeat steps 2 through 8 to install the

    Spacevars
    0 prodkey

     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.

    0

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

    
    Figure

    1Configuring

    18: Configuring Standby Server
    Image Modified

    
    

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 Modified
    

    Caption0Figure1Verifying

    Figure 20: Verifying System Status for Standby Server
    Image Modified
    

    
    

Noprint
Panel bgColor transparent borderWidth 2  Continue to Installing Securelink on Virtual Machine

pagebreak