NMC-RX 7.3.x User Guide, Vol. 2 > Using the Provisioning Service > Starting the NMC-RX Provisioning Service

Starting the NMC-RX Provisioning Service

The NMC-RX Provisioning Service (PVS) provides an optional programmatic application programming interface (API) for integration with the NMC-RX Element Management System application.

The NMC-RX database acts as a repository of information for use by both NMC-RX client GUIs and clients that are accessing the NMC-RX application through the provisioning interface. You must install NMC-RX Element Management System software before you can run NMC-RX Provisioning Service.

Starting the Provisioning Service

NMC-RX Provisioning Service is a separately licensed NMC-RX component. To start the Provisioning Service, you must run the following four components:

• NMC-RX Database Service
• CORBA Naming Service
• NMC-RX Provisioning RMI Service
• NMC-RX Provisioning CORBA Bridge Service

Three of the services—NMC-RX Database, CORBA Naming, and NMC-RX Provisioning RMI—are located in the pvsSampleScripts directory. For information about starting the NMC-RX Database Service, see Chapter 2, Installing and Running the NMC-RX Application in the NMC-RX User Guide, Vol. 1.

To start NMC-RX Provisioning Service:

1. (Optional—This step is an alternative to performing steps 2 through 7 and is available only on Solaris.)
   Run the allpvs script with or without console windows.

1. Run allpvs start.

The four services (NMC-RX Database, CORBA Naming, NMC-RX Provisioning RMI, and NMC-RX Provisioning CORBA Bridge) start automatically without individual console windows.

1. Run allpvs start console.

The four services (NMC-RX Database, CORBA Naming, NMC-RX Provisioning RMI, and NMC-RX Provisioning CORBA Bridge) start automatically. Each service has its own console window, which lets you monitor each process.

2. Start the NMC-RX database.
3. To start the CORBA Naming Service, run either naming or naming start console.

An ins.ior file is generated and copied to the filename JuniperERXNameService.ior, which is located in the pvs directory.

4. To start the NMC-RX Provisioning RMI Service, run the nmcPvsRmiService script.

The RMI Service is ready when you see the following message:

EmsSessionsFactory binded to JUNIPER_NMCRX_TMF814_EMSSESSIONFACTORY_8284

From the PVS.rc file in the NMCRX_HOME directory, you can edit the name, "JUNIPER_NMCRX_TMF814_EMSESSIONFACTORY_8384." There are four lines in this file:

provisioning_server_port=8384

provisioning_server_emsname=JUNIPER_NMCRX

provisioning_server_log_enabled=true

provisioning_server_session_checking_time_interval=180000

 NOTE: The NMC-RX Provisioning Service CORBA Service uses the name "JUNIPER_NMCRX_TMF814_EMSSESSIONFACTORY_8384" to find the entry reference for the RMI Service. The entry reference is the name that the CORBA client (NMS client) program uses to find the CORBA reference from the CORBA Naming Service.



 

5. To start the NMC-RX Provisioning Service CORBA Bridge Service, run the nmcPvsCorbaBridgeService script.

The NMC-RX Provisioning Service software is ready for use by network management system (NMS) clients.

Sample PVS Scripts

Juniper Networks uses CORBA freeware Distributed Object Group (DOG) for development and testing. We ship the DOG CORBA freeware package Version 2.6 with our NMC-RX Provisioning Service (PVS) installer. We offer sample scripts to start NMC-RX Provisioning Service based on this CORBA package. You can use a different CORBA package; however, you must recompile CorbaApi.java, which is in the PVS directory.

NOTE: If a service is already running, it does not start again.

The pvsSampleScript directory contains the following sample scripts:

• naming—Starts the DOG CORBA Naming Service; it uses port 2001. When this service starts, it generates an ins.ior file and copies it to ../pvs/JuniperERXNameService.ior file for use in starting the CORBA Bridge Service. Because this relative path is used, be sure to start the sample script from this directory, unless you choose to modify the script.
• nmcPvsRmiService—Starts the Remote Method Invocation (RMI) Service.
• nmcPvsCorbaBridgeService—Starts the CORBA Bridge Service. If you do not designate a port number, the system assigns a port number. If you want to designate a specific port number (for example, port 12345), modify the nmcPvsCorbaBridgeService script by adding option -OAPort=12345.
• nmcPvsTestUtility—Starts the NMC-RX Provisioning Service test utility. For additional information about this utility, see Testing the NMC-RX Provisioning Service.
• allpvs (Solaris only)—Starts all services at one time in the correct order (NMC-RX Database, Naming Service, RmiService, and CORBA Bridge Service).

For more information about the scripts, use the help option.

NOTE: The help feature and all of the options (for example, start, start console, and so on) exist only on Solaris.

The following is a sample of the allpvs help:

Running Multiple PVS Services to One NMC-RX Database

You can name and run multiple uniquely named PVS Services to one NMC-RX database.

To run multiple uniquely named PVS Services to one NMC-RX database, follow these steps. Note that there must be one dedicated Provisioning Service for each CORBA client:

1. Start the Naming Service.
2. Modify the PVS.rc file by assigning a unique emsName and server port for the Provisioning Service.
3. Start the NMC RMI Service.
4. Start the NMC CORBA Service.
5. Start the PVS Test Utility, and confirm that the emsName (Provisioning Service) is up and functioning as expected. (See Testing the NMC-RX Provisioning Service.)
6. Modify the PVS.rc file again by assigning a different emsName and server port for the Provisioning Service.
7. Repeat step 3-5.

Testing the NMC-RX Provisioning Service

You can use the PVS test utility to test the NMC-RX Provisioning Service. This utility attempts to connect to the database, the RMI Service, and the CORBA server. After connecting, the utility attempts to exchange data over the CORBA bridge by viewing a specified node or all of the nodes.

Running the PVS Test Utility

To run the PVS test utility:

1. Start the nmcPvsTestUtility program from the following location:

<NMC-RX-HOME>/pvsSampleScripts/nmcPvsTestUtility

The PVS Test Utility window opens.

2. Enter the Element Management System (EMS) name and port.
3. Specify your NMC-RX username and password.
4. (Optional) Specify a primary IP address in the Device area for the device that you want to test.
   

   NOTE: If you do not specify a primary IP address, the PVS test utility lists all devices on the system.

   
   
5. (Optional) Specify a system contact in the Device area to change the system contact.
   

   NOTE: If you do not specify a system contact, the system contact on the device does not change.

   
   
6. Click Start.

The PVS Test Utility Status dialog box opens.

After the PVS test utility starts, you can cancel the test or close the dialog box at any time. When the PVS test utility is finished testing, you can close the dialog box.

Understanding PVS Test Utility Output

The PVS test utility performs a sequence of tests. These tests provide output based on the test results. Table 52 lists each test performed, the failure criteria for each test, and the potential output text for each test.

Table 52: PVS Test Utility Output 

Test	Procedure	Failure Criteria	Messages
Database	Gets database location and user information from local NMC-RX resource file; attempts to contact database	Database is not running at assigned location Database settings in NMC-RX resources are not correct Various other reasons	Initial status text: Connecting to DB at location: localhost. Final status text: Success: Connected to DB at location: localhost. Success: Connected to DB at location: ipAddress. Failure: Could not connect to DB at location: ipAddress. [Followed by exception message]
RMI Service	Gets PVS port number from Provisioning Service resources file; contacts RMI Service at local IP address	RMI Service is not running Various other reasons	Initial status text: Connecting to PVS RMI Service at location ipAddress:portNumber. Final status text: Success: Connected to PVS RMI Service at location ipAddress:portNumber. Failure: Could not connect to PVS RMI Service at location ipAddress:portNumber. [Followed by exception message]
IOR file	Searches for JuniperERXNameService.ior file in PVS subdirectory	Unable to find IOR file (indicates that Naming Service has never run)	Initial status text: Finding Naming Service file. Final status text: Success: Found d:path\filename.ior. Failure: Could not find d:\path\filename.ior. [Followed by exception message]
CORBA Bridge	Uses Naming Service to contact PVS	PVS CORBA Bridge is not functioning Naming Service is not running Various other reasons	Initial status text: Connecting to PVS CORBA Bridge. Final status text: Success: Connected to PVS CORBA Bridge. Failure: Could not connect to PVS CORBA Bridge. [Followed by exception message]
Nonempty IP Address field	Requests information about device associated with IP address that you provide	Unable to find specified device Naming Service is not running CORBA bridge is not running	Initial status text: Viewing device [ipAddress]. Final status text: Success: Viewed device [ipAddress]. Failure: Could not view information for device [ipAddress]. [Followed by exception message]
Empty IP address field	Requests information about all devices on system	Unable to list devices Naming Service is not running CORBA Bridge is not running	Initial status text: Listing devices. Successful status text: Success: No devices found. Successful status text: Success: ipAddress1 ipAddress2 ipAddress3 ipAddress4 Status text for failure: Failure: Could not list devices. [Followed by exception text]
Nonempty IP address and nonempty System Contact field	Sets the system contact for device to specified device	Unable to configure system contact value	Initial status text: Configuring System Contact for device [ipAddress] to [systemContactText]. Final status text: Success: System Contact information configured for device [ipAddress]. Failure: Could not configure System Contact Information.
Status	Indicates that all tests are complete	None	Status text: Testing complete.