Cisco Systems 78-16845-01 appendix Appendix J Troubleshooting Equipment Management Problems

Appendix J Troubleshooting

J.10.4 Equipment Management Problems

J.10.4.6 CTM Database Is Inconsistent with Switch Data After Successful Coldstart (CTM Server Stop/Start) or Periodic Resync

After a successful node resynchronization triggered by the periodic resync, the CTM database is found to be inconsistent with the switch data.

Step 1 Collect the ooemc log files and all config upload files for the node. The ooemc implements a node-based cache. You can dump and save the cache.

Step 2 Get the process ID of the ooemc process that manages the node.

Step 3 Save the config upload files and ooemc log files.

Defect information—Collect the ooemc and config upload files from the /opt/svplus/log directory.

Possible alternative workaround: Manually resync the node. If the problem persists, perform a coldstart. If the problem is still not resolved, collect the log files and report the problem.

J.10.4.7 CTM CM GUI Shows Incomplete Connections After Successful Node Resync and Dbroker Sync-Up

CTM shows that some of connections are incomplete after the node resync process and dbroker synchronization process.

Step 1 Determine which ooemc process manages the node. The ooemc will manage the connection segment in the CTM database, which terminates on the MGX. Find the child ID of the ooemc process that manages your node. The purpose of finding the child ID of the ooemc process is to find the correct ooemc log files for inspection. The debugging process for this issue mainly focuses on log file inspection.

Step 2 After you have identified the ooemc log files, grep NotifyDataBroker from the files to see some log message examples before you modify your grep format. This will help you more efficiently grep the pair of log messages that correspond to the local and remote ends of one endpoint (primary endpoint or secondary endpoint) of a connection segment. In other words, each end (either primary end or secondary end) of a connection segment managed by ooemc should be logged with one pair of messages, one for local end and one for remote end. This pair of messages corresponds to one atm_connection segment entry in the database. Verify the information that ooemc sends to dbroker. Dbroker will refer to these messages from ooemc and construct a user_connection database entry. CTM Connection Management (CM) GUI displays connection information based on the user_connection database entry. Whether or not the connection is displayed as complete or incomplete depends on the information in the user_connection database entry. It is important to verify that ooemc sent the correct information to dbroker. Also verify that the segment database entries are populated correctly.

Step 3 If the correct number of messages have been forwarded to dbroker and the data in the messages is correct, but the user_connection database entry still contains invalid data, see J.10.13.2 Data Inconsistency, page J-129for more debugging information, or contact the dbroker development engineer (DE) for further investigation. If the problem is due to wrong data populated in segment database entries, then the EM DE should look at the problem.

Defect information:

•Collect ooemc and dbroker log files from the /opt/svplus/log directory.

Cisco Transport Manager Release 6.0 User Guide

J-46 78-16845-01