User guide

C-21
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Equipment Management Problems
The following is the flow of events which are involved in OOEMC coldstart sync up process:
1. Topo process discovers a node in the network. The process will change the node mode in node DB
table to -1. Then it notifies OOEMC component for the discovery. Then OOEMC will change the
node mode from -1 to 1 after the component starts managing the node.
2. When NTS component is able to register with the node, it sends link up message to the OOEMC
which manages the node. The OOEMC component will change the node mode from 1 to 2 to signify
the start of node sync up.
3. The OOEMC component sends SNMP bulk file creation request to the switch. If the request is
allowed, the switch will send trap 60901 to the Cisco MGM to signify the start of bulk file creation.
When bulk file creation is completed on the switch, the switch will send trap 60902 to the
Cisco MGM. After Cisco MGM has received this trap, it will start the FTP of the config upload files.
4. f the upload and parsing of all config files have completed without error, the OOEMC will change
the node mode from 2 to 3. If the upload or parsing of config upload for any service module on the
switch, the node sync up will complete partially and the OOEMC will change the node mode from
2 to 4 at the end of the node sync up process. If the error occurs on the shelf generic card file
(CARD_01_CC.CF) or pnni file (PNNI_01_CC_CF), the OOEMC will change the node mode from
2 to 5 to signify node sync up failure.
C.5.1.2 Network Setup and Configuration Required for OOEMC Sync Up Process
There are network setup and Cisco MGM configuration prerequisite required by EM before it can start
sync up process. On the switch, the following is the check list for trap manger and trap IP setup:
Use CLI "dsptrapmgr" to check that the Cisco MGM IP has been added to the trap manager. If you find
that your Cisco MGM IP is not registered with the switch, add the Cisco MGM IP to the trap manager
by typing the CLI "addtrapmgr cwm_ip 2500" where 2500 in the command is the port number and
cwm_ip is the IP address of your Cisco MGM machine. You may need to delete other IP from the trap
manager list if the list has been full. If the list is not full, the registration will take place automatically
if the Cisco MGM is configured to manage the node.
The trap IP should have been configured on the switch properly. Whenever you configure the switch to
use whatever IP (atm0 IP or lnPci0 IP) of the switch as primary IP, the topology component of
Cisco MGM should use that IP for node discovery. You can display the primary and secondary IP
information of the switch by typing CLI "dspndparms". To configure primary and secondary IP, you can
enter "cnfndparms" and the CLI will prompt you for options. After you have set up the primary and
secondary IP, you should also configure the primary IP as trap IP on the switch by entering CLI
"cnftrapip configured_IP" where configured_IP is the IP that you have chosen to use as primary IP in
CLI "cnfndparms".
On the Cisco MGM, the following is a list of configurable parameters in the file
/opt/svplus/config/emd.conf of your Cisco MGM machine that you should set up for proper problem
logging:
"OODebug" : For debugging purpose, this parameter should be set to level 6 or above, e.g. the log level
statement in emd.conf should be "OODebug Level 6".
"OOKeep" : For debugging purpose, this parameter should be set to a value depending on how many log
files you want to keep, e.g. the statement in emd.conf should be "OOKeep 100 OOEMC log files per
oochild"
Sometimes, a different network environment requires other parameters in the same files to be tuned for
correct functioning of Cisco MGM.