Table Of Contents
12.1 What is Cisco MGM GateWay/CORBA?
12.1.1 Viewing the Cisco MGM GateWay/CORBA Properties Pane
12.1.2 Viewing the Cisco MGM GateWay/CORBA Client Configuration Table
12.2 Using a Static CORBA Listener Port on the Cisco MGM Server
12.3 Configuring the CORBA Timeout
Managing CORBA Interfaces
This chapter contains the following information:
•What is Cisco MGM GateWay/CORBA?
•Using a Static CORBA Listener Port on the Cisco MGM Server
•Configuring the CORBA Timeout
Note Cisco MGM GateWay/CORBA is only mentioned briefly here. For more information about Cisco MGM GateWay/CORBA, including how to enable username and password encryption, set the heartbeat event, and create OSS clients, refer to the Cisco Media Gateway Manager 5.0 GateWay/CORBA User Guide and Programmer Manual.
12.1 What is Cisco MGM GateWay/CORBA?
Cisco MGM GateWay is an architectural component that provides northbound EMS-to-NMS interface mediation. Cisco MGM GateWay allows service providers to integrate Cisco MGM with their OSSs by using open standard interfaces.
Note Cisco offers the CORBA (sold separately) option for Cisco MGM GateWay.
The Cisco MGM GateWay/CORBA option is a CORBA-based interface that provides higher-layer management systems with fault, and inventory information for each NE that Cisco MGM manages. The Cisco MGM GateWay/CORBA option is based on the TeleManagement Forum (TMF) standards for the NMS-to-EMS interface. Cisco MGM GateWay/CORBA supports up to eight simultaneous sessions with higher-layer management systems.
Note For more information about Cisco MGM GateWay/CORBA, including how to enable username and password encryption, set the Cisco MGM GateWay/CORBA heartbeat event, and create OSS clients for Cisco MGM GateWay/CORBA, refer to the Cisco Media Gateway Manager GateWay/CORBA User Guide and Programmer Manual.
Figure 12-1 illustrates the Cisco MGM GateWay/CORBA communications architecture within a service provider's OSS environment.
Figure 12-1 Cisco MGM GateWay/CORBA Communications Architecture
Cisco MGM GateWay/CORBA is based on the following TMF standards:
•TMF513 v2.0 (October 2001): Multi-Technology Network Management Business Agreement
•TMF608 v2.0 (October 2001): Multi-Technology Network Management Information Agreement
•TMF814 v2.0 (October 2001): Multi-Technology Network Management Solution Set
12.1.1 Viewing the Cisco MGM GateWay/CORBA Properties Pane
Use the GateWay/CORBA Service Properties pane to stop, start, or configure Cisco MGM GateWay/CORBA service parameters. To view the Cisco MGM GateWay/CORBA Properties pane, from the Domain Explorer window, choose Administration > Control Panel, then choose GateWay/CORBA Service from the hierarchy pane at left. The pane contains two tabs, Global and OSS Clients.
12.1.1.1 Global Tab
Use the Global tab to start and stop Cisco MGM GateWay/CORBA service.
12.1.1.2 OSS Clients Tab
Use the OSS Clients tab to view current Operations Support System (OSS) client configuration information or to add a new OSS client. The OSS Clients tab is not displayed if the Service Status is Not Installed.
12.1.2 Viewing the Cisco MGM GateWay/CORBA Client Configuration Table
The Cisco MGM GateWay/CORBA Client Configuration Table displays information about Operations Support System (OSS) CORBA client properties. To view the Cisco MGM GateWay/CORBA Client Configuration table, from the Domain Explorer window, choose Administration > Control Panel, then choose Administration > Cisco MGM GW/CORBA Client Configuration Table.
12.2 Using a Static CORBA Listener Port on the Cisco MGM Server
To use a static CORBA listener port on the Cisco MGM server, proceed as follows.
Step 1 Log into the Cisco MGM server workstation as the root user.
Step 2 Change the directory to /opt/CiscoMGMServer/bin.
Note The default directory /opt/CiscoMGMServer may have been changed during installation of the Cisco MGM server.
Step 3 Edit the jne454.sh file by inserting a new line before the -Xbootclasspath line:
-Dong.orb.iioplistenerport=Port Number \
For example, if the port number is 5555, enter:
-Dong.orb.iioplistenerport=5555 \Step 4 Start the Cisco MGM server.
12.3 Configuring the CORBA Timeout
The CORBA timeout determines the number of seconds that the Cisco MGM server has to process a CORBA call and return it to the Cisco MGM client. If the Cisco MGM server does not return a response in time, CORBA automatically times out.
Step 1 Open the ems-client.cfg file.
By default, the ems-client.cfg file is located in the C:\Cisco\MediaGatewayManagerClient\config directory for Windows platforms and in the /opt/CiscoMGMClient/config directory for Sun Solaris platforms.
Step 2 Set the CORBA_Call_Timeout_Seconds parameter to the desired value. The default timeout is 120 seconds; the recommended range is 120 to 300 seconds.
Note If the NE is busy or if the Cisco MGM server is processing many requests, you might need to increase the CORBA timeout parameter accordingly.
Step 3 Save and close the ems-client.cfg file.