In this section:

The NSM Server Window

The Network Services Manager (NSM) Server application on SDA establishes a communication link to the NSM to handle all Service Management Interface (SMI) messages between SDA and the NSM.

The NSM Server is configured in the SDA System Manager GUI. The following figure shows the NSM Server window.

SDA NSM Server window

The Toolbar

The following figure shows the 5129 Protocol Interface window toolbar with the following icons:

NSM Server window toolbar

You can perform the following tasks by clicking on the toolbar icons:

  • Refresh - refresh the connection status information in the window.
  • Update - modify the IP Address, Port, Username, Password, and Status of an individual NSM Server connection.

NSM Service Management Interface Controller (SMIC) Support on SDA

The NSM Server establishes the Service Management Interface (SMI) communication link to the NSM to handle all SMI message traffic. The NSM Server polls the NSM to establish and maintain an SMI communication link between SDA and the NSM.

The following components are required to establish a connection between the NSM Server and the SDA database:

  • NSM Server running the SMI protocol converter to interface with the SDA database.
  • flx5129 handling of all SQL commands received from SDA and sends responses back to the NSM Server.

Internal communication between the NSM Server and the flx5129 application on SDA is permitted using DSC exchange.

To interface with the SDA database, the NSM Server converts all SMI messages received from the NSM to an SQL database command format.

The following summarizes limitations of SMIC:

  • The SMI NP database supports the following services: MNP, CLASS, LIDB, WSMS, CNAM.

  • The SMI NP database only supports RN service provisioning.

  • The SMI NP database maintains the same LRN and MNP Service RN with same values.

 DPC/SSN provisioning is not supported on SDA and provisioning requests are rejected.

Perform the following steps to add the NSM Server to SDA.

To add an NSM Server to SDA

  1. Add the following lines to /opt/FLXsm/java/server/htdocs/guiconf/ApplicationCatalog.cat:
     

    NSMServer=NSM Interface,NSM Interface

       

  2. Add the following lines to /opt/FLXsm/Security/etc/SmCmd:
     

    NSMStatus,NSMServer,                      1
NSMConfig,NSMServer,                      2
GuiNSMServer,NSMServer,                   1

       

  3. Add the following lines to /opt/FLXsm/java/server/htdocs/guiconf/Launcher.cfg:
     

    //Making entries for  NSMServer
ConfigProviderLeaf,REMOTE ACCESS=NSMServer,ala.sm.nsm.launcher.NSMProvider
NSMServer=NSM Server|blue-down-triangle.gif|greenball.gif

         

  4. Create a directory for the NSM apps.
     

    # mkdir /opt/FLXsm/NSMPS

          

  5. Upload the java security files (including alaNSM.jar):
     

    # scp tools/SM/stage/jar/*.jar root@10.91.1.4://opt/FLXsm/java/server/htdocs/codebase/

       

  6. Upload the Moss binary with the NSM license shortcut.

  7. Add the alaNSM.jar file to /opt/FLXsm/java/server/htdocs/flexgui.html.

  8. Copy the ApplicationPartNumber.class file to /opt/sigflex/flexSysMgr_12_1_0_nb20130313/bin/FLXsm/java/server/htdocs/ala/sm/nsm.

  9. Upload the NSM.cfg file to /opt/sigflex/current/bin/FLXsm/java/server/htdocs/NSMConfig.

  • No labels