Appendix J Troubleshooting

J.10.5 Configuration Center, Chassis View, Diagnostics Center, and Statistics Report Problems

Configuration—Dumps the configuration data to the dump file.

nmClient—This utility is used to isolate an issue between client and server. It is used to query the NMServer the same way as the Configuration Center, Chassis View, Diagnostics Center, or Statistics Report GUI queries the server. Output is redirected to /opt/svplus/log/nmClient.log. Cache dumps are redirected to /opt/svplus/log/nmClient.dump.

You must perform the Register Client operation before performing any other operations. When you are finished using the client, perform the Unregister Client operation.

Register Client—Registers with the server.

Update Filter—Updates the subscription/filter with the server passing the FDN.

Unregister Client—Unregisters with the server.

Get Topology—Gets the topology information of networks and nodes.

Get Children—Gets the list of children for a particular object in the tree.

Get CwmInfo—Gets the CTM sync-up state information.

Get ManagedObject—Gets the detailed information about an object in the tree.

Subscribe for all events—Subscribes to all updates on the server.

Unsubscribe for all event—Unsubscribes from all updates on the server.

The GUI client's log files (CMSCclient.log) are saved under log directories; for example, in Windows, D:Documents and Settings\<username>\log\, or in Unix: /opt/svplus/log.

J.10.5.2 Basic Issues

This section includes the following information:

J.10.5.2.1 Configuration Center, Chassis View, Diagnostics Center, or Statistics Report Does Not Show Any Nodes, page J-55

J.10.5.2.2 Configuration Center, Chassis View, Diagnostics Center, or Statistics Report Is Unable to Connect to Server, page J-56

J.10.5.2.3 Configuration Center, Chassis View, Diagnostics Center, or Statistics Report Does Not Show a Newly Added Node, page J-56

J.10.5.2.1 Configuration Center, Chassis View, Diagnostics Center, or Statistics Report Does Not Show Any Nodes

Step 1 Check whether the nodes are discovered. See J.10.2.1 No Nodes Are Discovered, page J-34.

Step 2 Check whether NMServer has the nodes and trunks in its cache. This can be done by using the command nmControl in the CTM CLI.

Step 3 If the nodes are in the NMServer cache, open a new GUI and verify whether the nodes are shown in it.

Defect Information—Collect the following information for further analysis:

topod.log, ILMITopoc.log, NMServer.log

nmControl.dump

CMSCclient.log

Cisco Transport Manager Release 6.0 User Guide

 

78-16845-01

J-55

 

Page 55
Image 55
Cisco Systems 78-16845-01 appendix Basic Issues