user manual

J-58
Cisco Transport Manager Release 6.0 User Guide
78-16845-01
Appendix J Troubleshooting
J.10.5 Configuration Center, Chassis View, Diagnostics Center, and Statistics Report Problems
Step 3 Check the node in the NMServer's cache. This can be done by using the command nmControl in the
CTM CLI.
Step 4 Check the CMSCclient.log for the node/trunk. Verify whether a delete message was received for the
node.
Step 5 From nmClient, use the getTopology option to retrieve the node information and verify whether it
matches the database and GUI.
Step 6 If the node is 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:
• ILMITopoc.log, topod.log, and NMServer.log.
• Dump outputs of ILMITopoc, topod and NMServer. The dump can be captured by issuing a kill
-USR1 signal to the process.
• Output of the switch CLI, selnd, and dbnds.
J.10.5.3.4 Configuration Center, Chassis View, Diagnostics Center, or Statistics Report Shows Incorrect SyncState for a Node
Step 1 Check the node information in the database by querying the node table. This can be done by using the
command selnd on the CTM CLI. Check the status.
Step 2 Check the node in the NMServer's cache. This can be done by using the command nmControl on the
CTM CLI.
Step 3 Check the CMSCclient.log for the node. Verify whether the correct message was received for the node.
Step 4 From nmClient, use the getTopology option to retrieve the node information and verify whether it
matches the database and the GUI.
Defect Information—Collect the following information for further analysis:
• ILMITopoc.log, topod.log, and NMServer.log.
• Dump outputs of ILMITopoc, topod and NMServer. The dump can be captured by issuing a kill
-USR1 signal to the process.
• Output of the switch CLI, selnd, and dbnds.
J.10.5.3.5 Duplicate Nodes Are Displayed on the Configuration Center, Chassis View, Diagnostics Center, or Statistics Report
Step 1 Check whether the node table has duplicate node IDs.
The node table can be queried using the following command:
tballraker18% echo "select (*) from node where node_id=2 and slot=1" | dbaccess stratacom
Step 2 Check whether both nodes in the database have active=1. If both nodes are active then collect the logs.
Step 3 If duplicate nodes do not exist in the database, check the cache of NMServer using nmControl.
Step 4 Check the CMSCclient.log for the node.
Step 5 From nmClient, use the getTopology option to retrieve the node information and verify whether it
matches the database and the GUI.