User guide

C-105
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Performance Management Collection and Parsing Problems
C.11.1.3 PM Collection Fails for the Node - Logfile Shows "Card not discovered"
This can happen when the card is not in the active state.
Check the node_info table - echo "select card_not_discovered from node_info where
node_id=<node_id> and slot=<slot>" | dbaccess
If the card_not_discovered is set to 1 means, card is not discovered
Check the card table - echo "select fc_state, fc_type, slot from card where node_id = <node-id> and slot
= <slot-num> " | dbaccess.
The fc_state of the card must be 3
Defect Information—Collect the following information for further analysis:
pmcollector.log, output of - echo "select fc_state, fc_type, slot from card where node_id =
<node-id> and slot = <slot-num> " | dbaccess.
Related key index entries
pmcollector
Workaround—If the card is not in fc_state 3, lookup troubleshooting for EM module.
C.11.1.4 PM Collection Fails for the Node - Logfile Shows "Time not synchronized"
This can happen when the timestamp between the Cisco MGM and the Collector is not synchronized or
the timestamp between collector and node is not synchronized.
Check the sync_info table - echo "select offset from sync_info where sync_node_id=<node_id>" |
dbaccess
Check the time on the Cisco MGM/Collector and on the node and make sure the offset got from above
query is the difference of time in seconds.
In case of feeders, check the time difference between Cisco MGM and the routing node of the feeder.
Defect Information—Collect the following information for further analysis:
pmcollector.log
Related key index entries
pmcollector
Workaround—Set the time on the Cisco MGM/Collector and the node to the same timestamp.
C.11.1.5 PM Collection Fails for the Node - Logfile Shows "Snmp failed"
This can happen due snmp failure due to wrong community string or due to timeout.
Check the node_info table to check the get_str, set_str and make sure they are the one on the node. Check
the snmp community strings on the node using the 'dspsnmp'.
check the log files for more detailed error, grep "snmp" scm*, if it is timeout error, change the timeout
setting and retry setting in /opt/svplus/config/pmcollector.conf