User guide

C-40
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Configuration Center, Chassis View, Diagnostic Center and Statistics Report Problems
Step 3 If duplicate nodes do not exist in database, then check the cache of NMServer using nmControl (Option
3).
Step 4 Check the CMSCclient.log for the node.
Step 5 Using nmClient, use getTopology option to retrieve the node information and verify whether it matches
with database and the GUI.
Step 6 If duplicate nodes is not present in NMServer cache, Open a New GUI and verify whether the node is
shown in the new GUI.
Defect Information—Collect the following information for further analysis:
Collect CMSCclient.log file under /opt/svplus/log. For PC Client, collect CMSCclient.log file under
D:\Documents and Settings\<username>\log.
Collect node data from node table for that specific node.
Collect ILMITopoc.log, topod.log need to be collected if there are duplicate nodes in database.
Possible alternative workaround—None
C.6.4 Network Element Discovery Issues
This section includes the following information:
C.6.4.1 All the Cards Under a Node Are Missing
C.6.4.2 Configuration Center, Chassis View, Diagnostic Center or Statistics Report GUIs Do Not
Show a Card/Line/Port for a Node
C.6.4.3 Card/Line/Port Information Incorrect on Configuration Center, Chassis View, Diagnostic
Center or Statistics Report GUIs
C.6.4.4 Configuration Center, Chassis View, Diagnostic Center or Statistics Report GUI Shows a
Card/Line/Port That Is Not Present in a Node
C.6.4.1 All the Cards Under a Node Are Missing
No Cards are shown under a node in the Configuration Center, Chassis View, Diagnostic Center or
Statistics Report GUIs.
Step 1 Check whether the node is synced up.
This can be done by using the command selnd on the Cisco MGM CLI.
Step 2 If the node has not synced up, then wait for the node to sync-up.
Step 3 If the node has synced up, then check whether cards are populated in the card table. If the Card table is
empty, Collect the EM logs. See C.5 Equipment Management Problems.
Step 4 Check whether NMServer has cards in it's cache.
This can be done by using the command nmControl (Option 4) on the Cisco MGM CLI.
Step 5 If cards are not present in NMServer cache, collect the logs.
Step 6 If cards are present in NMServer cache, use nmClient and verify whether getChildren for node's FDN,
returns the cards in the nmClient.<pid>.dump file.