User guide

C-106
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Performance Management Collection and Parsing Problems
Defect Information—Collect the following information for further analysis:
• pmcollector.log
• Related key index entries
• pmcollector, manual snmp results
Workaround—If the community strings are different on Cisco MGM and node, lookup troubleshooting
for Topology module
C.11.1.6 PM Collection Fails for the Node - Logfile Shows "Ftp failed"
This could happen for various reasons, generally because of wrong user/password or due to timeout.
Check the node_info table to check the node_id, node_name, ipaddress and make sure they are the
correct one.
Check the type of ip routing used while starting collection and for that ip routing check if the ip address
is reachable/valid.
Check the ftp_user_name and ftp_user_passwd in the coll_info table and the ftp_user_name and
ftp_user_passwd in the node_info table of stratacom database are matching and are valid.
Defect Information—Collect the following information for further analysis:
• pmcollector.log, dump of coll_info table, dump of node_info table of stratacom.
• Related key index entries
• pmcollector
Workaround—Use the atm or lan ip which is reachable.
C.11.1.7 PM Collection Fails for the Node - Logfile Shows "Polling failed and wait for major retry" or
"Major retry failed and wait for critical retry" or "Critical retry failed and wait for history retry" or
"History retry failed and wait for next retry" or "No more retry"
This could happen for various reasons, mainly due to ftp/tftp failures.
Check the node reachable[pingable] with nw_ip_address or lan_ip_address.
If only the nw_ip_address is reachable and the lan_ip_address is unreachable, then make sure the 'IP
Routing' for stats collection is using the 'In Band'.
If only the lan_ip_address is reachable and the nw_ip_address is not reachable, then make sure the 'IP
Routing' for stats collection is using the 'Out of Band'.
Use 'dspifip' command to check the lan_ip_address and nw_ip_address
Check the pmcollector.log, whether we are using the correct ip_address or not for stats collection.
Check for the existence of connections on the slot, for which, we are collecting the stats. Also check for
the stats Flag. Use command 'sumDBShow' or 'sfmDBShow' on the node.
Check the ftp_user_name and ftp_user_passwd in the coll_info table and the ftp_user_name and
ftp_user_passwd in the node_info table of stratacom database are matching and are valid.