Appendix J Troubleshooting
J.10.5 Configuration Center, Chassis View, Diagnostics Center, and Statistics Report Problems
Possible alternative workarounds:
1.Open a new GUI and a new Configuration Center, Chassis View, Diagnostics Center, or Statistics Report.
2.Use nmControl and perform "Resync Node," specifying the node ID.
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
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 synced up, wait for it to do so.
Step 3 If the node has synced up partially, check whether the card, line, or port is populated in the database. Refer to the Cisco Transport Manager Release 6.0 Database Schema.
Step 4 If the entry is not populated in the database, see J.10.4 Equipment Management Problems, page
Step 5 If the entry is present in the database, check the NMServer cache. This can be done by using the command nmControl on the CTM CLI. Check the nmControl.<pid>.dump
Step 6 If the element is not present in the NMServer cache, use nmClient and verify whether getChildren for FDN returns the entities in the nmClient.<pid>.dump file.
Step 7 If the element is present in the NMServer cache, open a new GUI and verify whether the missing elements are shown in it.
Defect
•topod.log, ILMITopoc.log, and NMServer.log
•nmControl.dump
•CMSCclient.log
Possible alternative workarounds:
1.Open a new GUI and a new Configuration Center, Chassis View, Diagnostics Center, or Statistics Report.
2.Use nmControl and perform "Resync Node," specifying the node ID.
J.10.5.4.3 Card, Line, or Port Information Is Incorrect on Configuration Center, Chassis View, Diagnostics Center, or Statistics Report
The entity information of an element shows incorrectly on 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 synced up, then wait for it to do so.
Step 3 Check whether the card, line, or port is populated in the database. Refer to the Cisco Transport Manager Release 6.0 Database Schema.
Step 4 If the entry in the database matches the GUI, see J.10.4 Equipment Management Problems, page
Step 5 If the entry doesn't match the database, check the NMServer cache. This can be done by using the command nmControl on the CTM CLI. Check the nmControl.<pid>.dump.
Cisco Transport Manager Release 6.0 User Guide
|
|
| |
|
|
