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:
- (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.
The four services (NMC-RX Database, CORBA Naming, NMC-RX Provisioning RMI, and NMC-RX Provisioning CORBA Bridge) start automatically without individual console windows.
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.
- Start the NMC-RX database.
- 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.
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
- 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:
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
<NMC-RX-HOME>/pvsSampleScripts/nmcPvsTestUtility
The PVS Test Utility window opens.
- Specify your NMC-RX username and password in the PVS Login area.
- (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.
- (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.
- 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 44 lists each test performed, the failure criteria for each test, and the potential output text for each test.