user manual

J-61

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 6 Use nmClient and verify whether getChildren for FDN returns the correct information for the element

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 Information—Collect the following information for further analysis:

• 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.4 Configuration Center, Chassis View, Diagnostics Center, or Statistics Report Shows a Card, Line, or Port that Is Not

Present in a Node

An extra card, line, or port element is shown 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 element is present in the database but does not match what is shown in the GUI, see

J.10.4 Equipment Management Problems, page J-40.

Step 5 If element is not 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 Use nmClient and verify whether getChildren for FDN returns the element in the nmClient.<pid>.dump

file.

Step 7 If element is not present in the NMServer cache, open a new GUI and verify whether the extra element

is shown in it.