J-59
Cisco Transport Manager Release 6.0 User Guide
78-16845-01
Appendix J Troubleshooting
J.10.5 Configuration Center, Chassis View, Diagn ostics Center, and Statistics Report Problems
Step 6 If duplicate nodes are not present in the NMServer cache, open a new GUI and verify whether the node
is shown in it.
Defect Information—Collect the following information for further analysis:
•CMSCclient.log file under /opt/svplus/log. For PC Client, collect CMSCclient.log file under
D:\Documents and Settings\<username>\log.
•Node data from node table for that specific node.
•ILMITopoc.log and topod.log, if there are duplicate nodes in the database.
Possible alternative workaround—None.
J.10.5.4 Network Element Discovery Issues
This section includes the following information:
•J.10.5.4.1 All the Cards Under a Node Are Missing, page J-59
•J.10.5.4.2 Configuration Center, Chassis View, Diagnostics Center, or Statistics Report Does Not
Show a Card, Line, or Port for a Node, page J-60
•J.10.5.4.3 Card, Line, or Port Information Is Incorrect on Configuration Center, Chassis View,
Diagnostics Center, or Statistics Report, page J-60
•J.10.5.4.4 Configuration Center, Chassis View, Diagnostics Center, or Statistics Report Shows a
Card, Line, or Port that Is Not Present in a Node, page J-61

J.10.5.4.1 All the Cards Under a Node Are Missing

No cards are shown under a node in the Configuration Center, Chassis View, Diagnostics Center, or
Statistics Report.
Step 1 Check whether the node is synced up. This can be done by using the command selnd on the CTM CLI.
Step 2 If the node has not synched up, wait for it to do so.
Step 3 If the node has synced up, check whether cards are populated in the card table. If the card table is empty,
collect the EM logs. See J.10.4 Equipment Management Problems, page J-40 for more information.
Step 4 Check whether NMServer has cards in its cache. This can be done by using the command nmControl
on the CTM CLI.
Step 5 If cards are not present in the NMServer cache, collect the logs.
Step 6 If cards are present in the NMServer cache, use nmClient and verify whether getChildren for node's FDN
returns the cards in the nmClient.<pid>.dump file.
Step 7 If cards are present in the NMServer cache, open a new GUI and verify whether the cards are shown in it.
Defect Information—Collect the following information for further analysis:
•topod.log, ILMITopoc.log, and NMServer.log
•nmControl.dump
•CMSCclient.log