Skip to end of metadata
Go to start of metadata

This section describes the Replica ePSX installation procedure on SBC 5000 series platform.

 

On this page:

This procedure assumes that the correct BMC, BIOS firmware and ConnexIP OS versions are installed on active and standby SBC server, and that the installation package is downloaded and pre-staged on the server or local machine.

The ePSX is not supported on SBC 5100 due to the hard drive size limitation.

Prior to installing ePSX, ensure its management network addresses belong to the same subnet as the corresponding SBC interfaces. The default route for ePSX is assigned the same gateway address as the gateway for the SBC mgt0 address, and it must be compatible with the ePSX mgt0 address. Pay particular attention to the network prefixes, subnet masks and IP addresses themselves.

Procedure

 

If the OS and/or SBC application are already installed and at correct versions, skip the associated steps.

Upload Files to Active and Standby Server

  1. Download the SBC and ePSX application package from SalesForce to your local PC or server.
  2. Validate the SBC md5 checksum using the checksum calculator. See Validating MD5Sum with 'Checksums Calculator' for guidance.
  3. Launch the Platform Manager. See Logging into Platform Manager for guidance.
  4. Click Upload Files > SFTP Upload tab. A security warning is displayed before running the application.

    Figure : SFTP Upload Screen

    Note

    Your computer must be installed with the latest Java version to run the SFTP application.

  5. Accept the risk and click run to start the SFTP application.

    Figure : Running SFTP Application

  6. Login into the SFTP client using sftpadmin/sftpadmin credentials.

    Figure : SFTP Credentials

  7. Select the sbc-V04.00.02-R000.x86_64.tar.gz, sbc-V04.00.02-R000.x86_64.md5, sbc-V04.00.02-R000.x86_64.signature and ePSX-V09.01.01R000.ova file located in your PC or server.

     

    Figure : SFTP Upload Tab

  8. Click Upload. This will start uploading the file into /opt/sonus/external.

    The File Transfer takes few minutes to complete. Wait for the upload to complete and click Done before proceeding to next step.

    Figure : Uploading Files

    Install Active SBC Server

     

  9. Click SW Install tab. The Install SBC Application screen displays. Select the SBC application version to install and click Next.

    Figure : Install SBC Application

    Once the user clicks on the Software Install tab, the Platform Manager extracts the package contents. The signature file verifies the integrity of the package contents before proceeding with the SBC installation.
  10. Select System Name field and enter the system name (using all uppercase letters). For example, WFDSBC01 where:
    - WFD represents the physical location
    - SBC represents the machine designation
    - 01 represents the number which SBC represents at this particular location.

    The system name must be identical for both the active and standby servers.

  11. Select Local Hostname and enter local hostname. The Local Hostname is typically the system name with a letter 'a' appended to the end. For example, WFDSBC01a is the local hostname derived from the System Name of "WFDSBC01". (The System Name should be all uppercase).

    The special character “_” (underscore) is not allowed in the Local Hostname. For more information, see System Name and Hostname Conventions.
  12. Select Peer Hostname and enter peer hostname.The Peer Hostname is typically the system name with a letter "b" appended to the end. For example, WFDSBC01b is the peer hostname derived from the System Name of "WFDSBC01". (The System Name should be all uppercase).

    The special character “_” (underscore) is not allowed in the Peer Hostname. For more information, see System Name and Hostname Conventions.
  13. Choose Active option for Server Role to designate the Active server as the one you are configuring.
  14. Select Personality field and choose Install embedded PSX (ePSX) option.

    Figure : Configuration Information Screen

  15. Select NTP Server IP field and enter the NTP server IP address. This field is also configured through BMC configuration screen.
  16. Select NTP Server Time zone field and enter the NTP Time zone. Click Next to continue.
  17. Confirm the installation process by providing your user credentials. Click Install.

    Figure : Confirm Install Screen


    The installation process starts and displays the installation status on the SBC Install Log screen.

    Figure : Viewing Installation Status

    The SBC installation checks whether ConnexIP OS upgrade needs to be performed or not (see example below). If the OS upgrade is required, it performs the OS upgrade process first and reboots the server. Once it reboots, login into the Platform Manager to continue with the SBC installation.

    Figure : Verifying ConnexIP OS Version

  18. Allow the SBC installation to complete. The SBC System Reboot required message appears on the screen.This reboots the SBC system.

    Figure : Rebooting SBC System

  19. Login again into the Platform Manager. By default, the main screen appears.

    Figure : Platform Manager Main Screen

     
  20. Verify the Installation in SW Install > SBC Install Log tab. The Install Done message appears.

    Figure : Active Server Installation Complete

  21. Once the SBC installation is successfully completed on the active server, continue installing SBC application on the standby server.

    Install Standby SBC Server

  22. Click SW Install tab. The Install SBC Application screen displays. Select the SBC application version to install and click Next.

    Figure : Install SBC Application

    Once the user clicks on the Software Install tab, the Platform Manager extracts the package contents. The signature file verifies the integrity of the package contents before proceeding with the SBC installation.
  23. Select System Name field and enter the system name (using all uppercase letters). For example, WFDSBC01 where:
    - WFD represents the physical location
    - SBC represents the machine designation
    - 01 represents the number which SBC represents at this particular location.

    The system name must be identical for both the active and standby servers.

  24. Repeat step 12 through 14 with the following changes:
    - Enter Standby server name in Local Hostname field, which is typically the System Name with a letter “b” appended to the end.
    - Enter Active server name for Peer Hostname field, which is typically the System Name with a letter “a” appended to the end.
    - Choose Standby option for Server Role to designate the Standby server as the one you are configuring.

  25. Select Personality field and choose Install embedded PSX (ePSX) option.

    Figure : Configuring Standby SBC

  26. Select NTP Server IP field and enter the NTP server IP address. This field is also configured through BMC configuration screen.
  27. Select NTP Server Time zone field and enter the NTP Time zone. Click Next to continue.
  28. Confirm the installation process by providing your user credentials. Click Install.

    Figure : Confirm Install Screen


    The installation process starts and displays the installation status on the SBC Install Log screen.

    Figure : Viewing Installation Status

    The SBC installation checks whether ConnexIP OS upgrade needs to be performed or not (see example screenshot below). If the OS upgrade is required, it performs the OS upgrade process first and reboots the server. Once it is rebooted, login into the Platform Manager to continue with the SBC installation.

    Figure : Verifying ConnexIP OS Version

  29. Allow the SBC installation to complete. The SBC System Reboot required message appears on the screen.This reboots the SBC system.

    Figure : Rebooting SBC System

  30. Login again into the Platform Manager. By default, the main screen appears.

    Figure : Platform Manager Main Screen

  31. Verify the Installation in SW Install > SBC Install Log tab. The Install Done message appears.

    Figure : SBC Installation Complete on Standby Server



  32. Once the SBC installation is successfully completed on the standby server, continue installing ePSX application on the active server.

    Install Active ePSX

    Replica ePSX installation triggers an initial download of database content from external PSX Master. Perform the Installation during maintenance window to avoid additional load on PSX Master.

  33. Select SW Install > Install ePSX Application tab on active SBC server. Select the ePSX version to Install and click Next.

     

    Figure : Selecting ePSX Installation Package

    The ePSX application package is unpacked and validated before starting the configuration (see figure below).

    Figure : ePSX Package Validation

  34. Select the ePSX Configuration Type and click Apply. The configuration screen displays:

    1. Standalone ePSX

    2. Replica ePSX

      For ePSX slave configuration, select Replica ePSX option (see figure below).

      Figure : Selecting ePSX Slave

  35. The configuration data fields are launched below. Enter the configuration data.

    (info)  Use the scroll bar to view additional configuration fields.

    Figure : Configuration Fields



  36. Select Mgt port 0 IP field and enter the IP address.
  37. Select Mgt port 0 prefix field and enter the IP prefix.
  38. Select Mgt port 1 IP field and enter the IP address.
  39. Select Mgt port 1 prefix field and enter the IP prefix.

    Figure : Management Port Configuration

     
  40. Select ePSX System Name and VM Host Name field and enter the system name and hostname of Virtual Machine application.

    The system name must be same for both ePSX Active and Standby VM.

    Figure : Configuring VM Hostname

    The management IP addresses mentioned here are new IP addresses for ePSX. Do not use the IP addresses used for SBC management.

  41. Select the Master DB system name field under ePSX replica and enter the name of external PSX.
    1. Select the Master DB system IP field and enter the IP address of external PSX.

      Figure : Master DB System Information

      The listener.ora file on the master PSX must be defined with a IP address instead of hostname.
      #Filename: Listener.ora
      #
      LISTENER=
            (ADDRESS_LIST =
                  (ADDRESS= (PROTOCOL=IPC)(KEY=SSDB))
                  (ADDRESS= (PROTOCOL=IPC)(KEY=PNPKEY))
                  (ADDRESS= (PROTOCOL=TCP)(Host = 10.12.15.114) (Port =1521)(IP = FIRST)
            )

  42. Once all information is entered, click Install. The ePSX installation proceeds.

    Figure : ePSX Installation Status

  43. Allow the ePSX installation to complete. The ePSX INSTALL is DONE message appears on the screen. Click OK to continue.

    Figure : ePSX Install Complete

  44. Once ePSX installation completes, SBC server restarts. Wait for the SBC server to come up before proceeding.

  45. Verify that the SBC application is up and running.

    Figure : SBC Application Status

  46. From the EMA, install the POL-BASE license in order to use ePSX application.

  47. Verify the SBC and ePSX status in Platform Manager screen. The SBC status is UP(Active) and ePSX application is Active (ePSX icon turns green) on the active SBC server.

    Figure : SBC Status on Software Versions Tab

    Install Standby ePSX

  48. Install the Standby ePSX after the ePSX is running on the active SBC. Repeat Step 34 through Step 47 to install the ePSX application on the standby server with the following change in Step 41:
    - Enter Standby hostname in VM Hostname field, which is typically the System Name with a letter “b” appended to the end.
  49. Verify the SBC and ePSX status in Platform Manager screen. The SBC status is UP (Standby) and ePSX application is Active (ePSX icon turns green) on the standby SBC server.

    Figure : Verifying Standby SBC Status

  50. Verify both servers are up and running using CLI command "show table vmApplication ePSX status":

    show table vmApplication ePSX status
    admin@WFDSBC01a> show table vmApplication ePSX status
                                                                              PACKAGE       INSTALLED     	INTERNAL IP
     CE NAME    STATE   REASON OS VERSION                       APP VERSION   VERSION       CONFIGURATION 	ADDRESS
     --------------------------------------------------------------------------------------------------------------------------------
     WFDSBC01a  running na     Linux_2.6.32-279.11.1.el6.x86_64 V09.01.01R000 V09.01.01R000 replicaEPSX     169.254.77.2
     WFDSBC01b  running na     Linux_2.6.32-279.11.1.el6.x86_64 V09.01.01R000 V09.01.01R000 replicaEPSX     169.254.77.2
  51. Create a default route for Management mgt1 using the following CLI command:

    admin@WFDSBC01a> configure
    admin@WFDSBC01a% set vmApplication ePSX mgmtStaticRoute <SBC_Hostname> 0.0.0.0 0 <Gateway_IP_Address> mgt1 preference 11
  52. Follow the instructions to configure the SBC to use external PSX. See Configuring SBC to Use External PSX.

    When you are configuring the external PSX server as a remote server, use the internal VM IP address 169.254.77.2.

    The ePSX licenses must be pushed from EMS after ePSX installation is completed. This is required for ePSX to accept calls.