Cisco Systems 78-16845-01 PM Collection Fails for the Node-Log File Shows Snmp failed, 119

Appendix J Troubleshooting

J.10.10 Performance Management Collection and Parsing Problems

echo "select fc_state, fc_type, slot from card where node_id = <node-id> and slot = <slot-num> " dbaccess

•Related key index entries

•Pmcollector

Possible alternative workaround—If the card is not in fc_state 3, look up troubleshooting for the EM module.

J.10.10.1.4 PM Collection Fails for the Node—Log File Shows "Time not synchronized"

This can happen when the time stamp between the CTM and the collector is not synchronized or the time stamp between the collector and the node is not synchronized.

Step 1 Check the sync_info table by executing the following command:

echo "select offset from sync_info where sync_node_id=<node_id>" dbaccess

Step 2 Check the time on the CTM/Collector and on the node and make sure the offset from the previous query is the difference of time in seconds.

Step 3 For feeders, check the time difference between CTM and the routing node of the feeder.

Defect Information—Collect the following information for further analysis:

•Pmcollector.log

•Related key index entries

•Pmcollector

Possible alternative workaround—Set the time on the CTM/Collector and the node to the same time stamp.

J.10.10.1.5 PM Collection Fails for the Node—Log File Shows "Snmp failed"

This can happen due to SNMP failure caused by an incorrect community string or a timeout.

Step 1 Check get_str and set_str in the node_info table and make sure they are the community strings on the node. Check the SNMP community strings on the node using the command dspsnmp.

Step 2 To check the log files for more details on the error, grep "snmp" scm*. If the error is a timeout error, change the timeout setting and retry the setting in /opt/svplus/config/pmcollector.conf.

Defect Information—Collect the following information for further analysis:

•Pmcollector.log

•Related key index entries

•Pmcollector, manual SNMP results

Possible alternative workaround—If the community strings are different on CTM and the node, look up troubleshooting for the Topology module.

	Cisco Transport Manager Release 6.0 User Guide
78-16845-01		J-119