Search

Page tree
Skip to end of metadata
Go to start of metadata

In this section:

The SDA installation is performed on the Sonus Signaling System.

Note

An SDA software installation is performed by Sonus professional services during initial SDA deployment.

Installing the SDA Software

Perform the steps outlined in the following procedures to install SDA on the Sonus Signaling System.

Note

Before installing or upgrading the SDA software on the Sonus Signaling System, it is recommend that you backup all SDA database tables installed on your system. Sonus professional services perform backup and restore operations on your system when installing new software or upgrading an existing SDA installation.

To install SDA on the Sonus Signaling System

  1. Log onto the MGMT CPU as root for the Sonus Signaling System requiring the SDA software.

  2. Verify the required SDA installation files are installed on the MGMT CPU.

    Command Example
    # ls -l
    
    total 116
    -r-xr-xr-x 1 root root 31148 Sep 14 08:39 INSTALL_flex.sh
    -rw------- 1 root root 20518 Aug 29 15:56 anaconda-ks.cfg
    -rw-r--r-- 1 root root 42663 Aug 29 15:55 install.log
    -rw-r--r-- 1 root root  8256 Aug 29 15:54 install.log.syslog
    
    # ls -l software/
    
    total 92788
    -r--r--r-- 1 root root 47116123 Sep 14 08:40 SDA_16_1_0_nb20170910.tgz

                   

  3. Execute the following command at the system prompt to install SDA.

    Command
     # ./INSTALL_flex.sh --no_usb --path .
    Command Output
    -----------------------------------------------------------------------------
    --- INSTALL_flex.sh script running on slot13_0...
    -----------------------------------------------------------------------------
    
    
    Checking base system software...
    Checking flex tarballs on USB key...
    Creating sigflex directories and directory pointers on MGMT CPUs...
    NOTE: /var/log/sigflex/flexDSS_current and /var/log/sigflex/flexSysMgr_current do not already exist on slot13_0. Treating this as a fresh install and placing tarballs in flexDSS_current and flexSysMgr_current directories.
    0
    0
    0
    0
    Copying the flex DSS tarball to the MGMT CPUs.
    Copying the flex System Manager tarball to the MGMT CPUs.
    
    --------------------------------------------------------------------------------
    The flex software tarballs have been stored on the MGMT CPUs in:
       /var/log/sigflex/flexDSS_current
       /var/log/sigflex/flexSysMgr_current
    
     Proceed to Flex Routing Configuration in the text menu.
    --------------------------------------------------------------------------------
    
    End of installation script.

             

  4. Enter startmenu at the system prompt to access the TextUI.

    Command
    # startmenu
    Command Output
    Main Menu
    Sonus Networks DSC 8000
     1 - System 
     2 - Enter Shell
     l - Logout
    Enter Selection:
    
    
    
    User: root Hostname: dsc8klab62.lab.ottawa.sonusnet.com  

             

  5. Select System and press Enter.

    Command Output
    System 
     1 - Date/Time
     2 - Software Revisions 
     b - Back
     l - Logout
    Enter Selection:
    
    
     
    User: root Hostname: dsc8klab62.lab.ottawa.sonusnet.com

               

  6. Select Software Revisions and press Enter.

    Command Output
    Software Revisions 
     1 - Pre Upgrade Check
     2 - Express Upgrade
     3 - CPU Versions
     4 - Switch Versions
     5 - IO Versions
     6 - Express Rollback
     7 - Servicepacks 
     8 - DSC DB
     9 - SS7 DB Apps
     b - Back
     l - Logout
    Enter Selection:
    
    
     
    User: root Hostname: dsc8klab62.lab.ottawa.sonusnet.com

             

  7. Select SS7 DB Apps and press Enter.

    Command Output
    SS7 DB Apps
     1 - Display SS7 DB Apps Status
     2 - SS7 DB Apps Configuration
     3 - SS7 DB Apps Network Configuration
     4 - SS7 DB Apps Upgrade
     b - Back
     l - Logout
    Enter Selection:
    
    
    
    User: root Hostname: dsc8klab62.lab.ottawa.sonusnet.com

                 

  8. Select SS7 DB Apps Configuration and press Enter.

    Command Output
    ---- SS7 DB APPS CONFIGURATION ----
    CURRENT SS7 DB APP software found on MGMT CPUs:
       flexSysMgr_16_1_0_nb20170910
       flexDSS_16_1_0_nb20170910
    
    
    APPLICATION CPU SS7DB STATUS:
    
    SLOT  SS7DB |  INSTALLED SS7DB    | CAPABILITY |HDD FREE SPACE |SS7DB PROCCESSES
     #     TYPE |-RELEASE--BUILD DATE-|-DSS-SYSMGR-|HD1(MB) HD2(MB)|RUNNING-STOPPED-
    ---------------------------------------------------------------------------------
    20       -- |   none    installed |  Y     Y   | 16428  228936 |
    21       -- |   none    installed |  Y     Y   | 16717  244198 |
    23       -- |   none    installed |  Y     N   | 16694    n/a |
    24       -- |   none    installed |  Y     N   | 14912    n/a |
    
    This is a FRESH INSTALL.
    
    4 CPUs meet the requirements for SS7 DB APP DSS cards.
    
    2 CPUs meet the requirements for SS7 DB APP System Mgr cards.
    
    
    Enter slot # of CPU to configure / re-configure, or <enter> to invoke changes:

                  

  9. Enter the slot number of the SDA SysMgr CPU and press Enter.

    Command Output
    20
    Enter action to perform on CPU in slot 20:
       d - configure CPU in slot 20 as a SS7 DB APP "DSS" node
       s - configure CPU in slot 20 as a SS7 DB APP "SYSTEM MANAGER" node
       <enter> to return to SS7 DB APP Configuration Menu.

            

  10. Select 's' to configure the slot as an SDA SysMgr node and press Enter.

    Command Output
    s
    Assigning slot 20 to be SYSMGR_1
    Slot 20 configured as SS7 DB APP System Manager.
    
    APPLICATION CPU SS7DB STATUS:
    
    SLOT  SS7DB |  INSTALLED SS7DB    | CAPABILITY |HDD FREE SPACE |SS7DB PROCCESSES
     #     TYPE |-RELEASE--BUILD DATE-|-DSS-SYSMGR-|HD1(MB) HD2(MB)|RUNNING-STOPPED-
    ---------------------------------------------------------------------------------
    20 SYSMGR_1 |   none    installed |  Y     Y   | 16428  228936 |  n/a      n/a
    21       -- |   none    installed |  Y     Y   | 16717  244198 |
    23       -- |   none    installed |  Y     N   | 16694    n/a |
    24       -- |   none    installed |  Y     N   | 14912    n/a |
    
    
    Enter slot # of CPU to configure / re-configure, or <enter> to invoke changes:

               

  11. Enter the slot number for the other SDA SysMgr CPU and press Enter.

    Command Output
    21
    Enter action to perform on CPU in slot 21:
       d - configure CPU in slot 21 as a SS7 DB APP "DSS" node
       s - configure CPU in slot 21 as a SS7 DB APP "SYSTEM MANAGER" node
       <enter> to return to SS7 DB APP Configuration Menu.

                

  12. Select 's' to configure the slot as an SDA SysMgr node and press Enter.

    Command Output
    s
    Assigning slot 21 to be SYSMGR_2
    Slot 21 configured as SS7 DB APP System Manager.
    
    APPLICATION CPU SS7DB STATUS:
    
    SLOT  SS7DB |  INSTALLED SS7DB    | CAPABILITY |HDD FREE SPACE |SS7DB PROCCESSES
     #     TYPE |-RELEASE--BUILD DATE-|-DSS-SYSMGR-|HD1(MB) HD2(MB)|RUNNING-STOPPED-
    ---------------------------------------------------------------------------------
    20 SYSMGR_1 |   none    installed |  Y     Y   | 16428  228936 |  n/a      n/a
    21 SYSMGR_2 |   none    installed |  Y     Y   | 16717  244198 |  n/a      n/a
    23       -- |   none    installed |  Y     N   | 16694    n/a |
    24       -- |   none    installed |  Y     N   | 14912    n/a |
    
    
    Enter slot # of CPU to configure / re-configure, or <enter> to invoke changes:

           

  13. Enter the slot number of the SS7 DB Application DSS node and press Enter.

    Command Output
    23
    Enter action to perform on CPU in slot 23:
       d - configure CPU in slot 23 as a SS7 DB APP "DSS" node
       <enter> to return to SS7 DB APP Configuration Menu.

           

  14. Select 'd' to configure the slot as a DSS node and press Enter.

    Command Output
    d
    Assigning slot 23 to be a DSS CPU.
    Slot 23 configured as DSS.
    
    APPLICATION CPU SS7DB STATUS:
    
    SLOT  SS7DB |  INSTALLED SS7DB    | CAPABILITY |HDD FREE SPACE |SS7DB PROCCESSES
     #     TYPE |-RELEASE--BUILD DATE-|-DSS-SYSMGR-|HD1(MB) HD2(MB)|RUNNING-STOPPED-
    ---------------------------------------------------------------------------------
    20 SYSMGR_1 |   none    installed |  Y     Y   | 16428  228936 |  n/a      n/a
    21 SYSMGR_2 |   none    installed |  Y     Y   | 16717  244198 |  n/a      n/a
    23      DSS |   none    installed |  Y     N   | 16694    n/a |  n/a       n/a
    24       -- |   none    installed |  Y     N   | 14912    n/a |
    
    
    Enter slot # of CPU to configure / re-configure, or <enter> to invoke changes:

                   

  15. Enter the slot number of the second SS7 DB Application DSS node and press Enter.

    Command Output
    24
    Enter action to perform on CPU in slot 24:
       d - configure CPU in slot 24 as a SS7 DB APP "DSS" node
       <enter> to return to SS7 DB APP Configuration Menu.

          

  16. Select 'd' to configure the slot as a DSS node and press Enter.

    Command Output
    d
    Assigning slot 24 to be a DSS CPU.
    Slot 24 configured as DSS.
    
    APPLICATION CPU SS7DB STATUS:
    
    SLOT  SS7DB |  INSTALLED SS7DB    | CAPABILITY |HDD FREE SPACE |SS7DB PROCCESSES
     #     TYPE |-RELEASE--BUILD DATE-|-DSS-SYSMGR-|HD1(MB) HD2(MB)|RUNNING-STOPPED-
    ---------------------------------------------------------------------------------
    20 SYSMGR_1 |   none    installed |  Y     Y   | 16428  228936 |  n/a      n/a
    21 SYSMGR_2 |   none    installed |  Y     Y   | 16717  244198 |  n/a      n/a
    23      DSS |   none    installed |  Y     N   | 16694    n/a |  n/a       n/a
    24      DSS |   none    installed |  Y     N   | 14912    n/a |  n/a       n/a
    
    
    Enter slot # of CPU to configure / re-configure, or <enter> to invoke changes:
    
  17. Press Enter.

    Configure SS7 DB APP on these CPUs? [y/n]:
  18. Enter 'y' to proceed with the SDA configuration on the CPUs and press Enter.

    Note

    The following command line only appears when Local licensing is used:

    Configure SDA to use Exact vs Best Match feature? [y/n]:
    Command Output
    y
    Generating /opt/sigflex/current/data/flex.cfg configuration file needed for SS7 DB APP
    flex.cfg configuration completed.
    
    licensing type: legacy
    ============== Installing System Manager s/w on slot 20 ==============
    mkdir: cannot create directory `/shared/core': File exists
    Pushing flexSysMgr_16_1_0_nb20170910.tgz tarball from MGMT CPU to slot 20
    Untarring flexSysMgr_16_1_0_nb20170910 tarball on CPU (slot 20) into "current"
    Setup softlink /opt/sigflex/current -> /opt/sigflex/flexSysMgr_16_1_0_nb20170910 on CPU (slot 20)
    
    Setting up various configuration files needed for SS7 DB APP on CPU (slot 20)
    Removing flexSysMgr_16_1_0_nb20170910.tgz tarball from slot 20
    ... Refreshing configuration on slot 20
    STOPPING SS7 DB APP processes on CPU (slot 20)
    ============== Installing System Manager s/w on slot 21 ==============
    mkdir: cannot create directory `/shared/core': File exists
    Pushing flexSysMgr_16_1_0_nb20170910.tgz tarball from MGMT CPU to slot 21
    Untarring flexSysMgr_16_1_0_nb20170910 tarball on CPU (slot 21) into "current"
    Setup softlink /opt/sigflex/current -> /opt/sigflex/flexSysMgr_16_1_0_nb20170910 on CPU (slot 21)
    
    Setting up various configuration files needed for SS7 DB APP on CPU (slot 21)
    Removing flexSysMgr_16_1_0_nb20170910.tgz tarball from slot 21
    ... Refreshing configuration on slot 21
    STOPPING SS7 DB APP processes on CPU (slot 21)
    ============== Installing DSS s/w on slot 23 ==============
    mkdir: cannot create directory `/shared/core': File exists
    Pushing flexDSS_16_1_0_nb20170910.tgz tarball from MGMT CPU to slot 23
    Untarring flexDSS_16_1_0_nb20170910 tarball on CPU (slot 23) into "current"
    Setup softlink /opt/sigflex/current -> /opt/sigflex/flexDSS_16_1_0_nb20170910 on CPU (slot 23)
    
    Setting up various configuration files needed for SS7 DB APP on CPU (slot 23)
    Removing flexDSS_16_1_0_nb20170910.tgz tarball from slot 23
    ... Refreshing configuration on slot 23
    STOPPING SS7 DB APP processes on CPU (slot 23)
    STARTING SS7 DB APP processes on CPU (slot 23)
    ============== Installing DSS s/w on slot 24 ==============
    mkdir: cannot create directory `/shared/core': File exists
    Pushing flexDSS_16_1_0_nb20170910.tgz tarball from MGMT CPU to slot 24
    Untarring flexDSS_16_1_0_nb20170910 tarball on CPU (slot 24) into "current"
    Setup softlink /opt/sigflex/current -> /opt/sigflex/flexDSS_16_1_0_nb20170910 on CPU (slot 24)
    
    Setting up various configuration files needed for SS7 DB APP on CPU (slot 24)
    Removing flexDSS_16_1_0_nb20170910.tgz tarball from slot 24
    ... Refreshing configuration on slot 24
    STOPPING SS7 DB APP processes on CPU (slot 24)
    STARTING SS7 DB APP processes on CPU (slot 24)
    Setting up Disk Mirroring between SS7 DB APP Sys Mgrs on slot 20 and its peer, slot 21. This may take several minutes...
    Installing DRBD on slot20_0...
    
    Installing DRBD on slot21_0...
    Initializing DRBD on slot20_0...
    
    Created smroot user on CPU (slot 20)
    Created smroot user on CPU (slot 21)
    STARTING SS7 DB APP processes on CPU (slot 20)
    STARTING SS7 DB APP processes on CPU (slot 21)
    The disk mirroring on SysMgr cards MUST be completed before proceeding any further ...
    Please monitor the mirroring progress (from another xterm window) by checking the content of /proc/drbd or /opt/sigflex/current/drbd_setup.log on SysMgr Card slot 20
    Is Disk Mirroring completed (y=completed  n=failed)? (y/n):
    y
    Copying the schema/sri_schema_version file to /nfmd0a/fr/dbs/schema/sri_data_version
     0
    To complete the FLEX configuration, all flex cards need to be rebooted (confirm only after Disk Mirroring is completed).  Reboot now? (y/n):

             

  19. Enter 'y' to reboot the SDA CPUs and press Enter.

    Command Output
    y
    Rebooting all FLEX cards now...
    
    === REBOOTING Sysmgr 1:  slot 20 ===
    === REBOOTING Sysmgr 2:  slot 21 ===
    
    === REBOOTING DSS:  slot 23 ===
    
    
    === REBOOTING DSS:  slot 24 ===
    
    
    End of SS7 DB APP Configuration.
    
    
    Press <return> to continue.

               

  20. Press Enter to complete the SDA installation and return to the startmenu.

To verify the SDA installation

Note

Verify the status of the SDA software installation on all SDA CPU cards on the Sonus Signaling System.

  1. From an MGMT CPU, SSH to the primary system manager card and execute the status command.

    Command
    # ssh slot<slot # of the primary system manager>_0
    
    #/opt/sigflex/current/scripts/sigflexmgr status 
    Command Output
    Local is primary         
              sigflxsys  running       
                 flxsql  running
    flexServicesLicense  running 
           sigFlxOrbMgr  running        
                   sfsc  running        
                 TrcMgr  running
                 FwdMgr  running
            EventMgrSvr  running     
                 CmdLgr  running     
             SmIntruder  running            
                   Moss  running     
           SySecMgrSrvr  running           
                  Trcrt  running       
             5129Server  running         
              NSMServer  running
              ScrServer  running
        autoexec-script  running
             ScrSecIntf  running
       SmFlex5129Server  running      
            ScrFlexIntf  running 
        FlexRTGUIServer  running
    
  2. From an MGMT CPU, SSH to the standby system manager and execute the status command.

    Command
    # ssh slot<slot # of the standby system manager>_0
    
    # /opt/sigflex/current/scripts/sigflexmgr status
    Command Output
    Remote is primary  
              sigflxsys  running      
                 flxsql  stopped
    flexServicesLicense  stopped
           sigFlxOrbMgr  stopped        
                   sfsc  stopped      
                 TrcMgr  stopped   
                 FwdMgr  stopped
            EventMgrSvr  stopped   
                 CmdLgr  stopped 
             SmIntruder  stopped        
                   Moss  stopped 
           SySecMgrSrvr  stopped       
                  Trcrt  stopped    
             5129Server  stopped    
              NSMServer  stopped    
              ScrServer  stopped
        autoexec-script  stopped 
             ScrSecIntf  stopped
       SmFlex5129Server  stopped
            ScrFlexIntf  stopped
        FlexRTGUIServer  stopped
    

  3. From an MGMT CPU, SSH to the first DSS card and execute the status command.

    Command
    # ssh slot<slot # of the first DSS>_0
    
    #/opt/sigflex/current/scripts/sigflexdss status
    Command Output
     yj4flx  running
    mDaemon  running
  4. Repeat step 3 for all DSS cards.

Installing Services and Service Handlers

Following the installation of the SDA software, to complete the SDA deployment, installation of Services and Service Handlers is required.

Note

Installation of required Services and Service Handlers is provided by Sonus professional services during initial SDA deployment based on contractual agreement.

For more information on menu and toolbar options for accessing Services and Service Handlers in the SDA System Manager GUI, refer to the SDA System Manager User Guide.

  • No labels