Cisco Systems 78-16845-01 appendix Performance Management Collection and Parsing Problems, 117

Appendix J Troubleshooting

J.10.10 Performance Management Collection and Parsing Problems

J.10.9.2.10 Miscellaneous Issues or Problems in Diagnostics Center

If you encounter any other issues or problems, contact the CTM engineers with the defect information.

Step 1 Check whether a similar operation can be performed successfully through the CLI.

Defect Information—Collect the following information for further analysis:

•Describe the operation during which the problem/issue was encountered.

•DCServer.log and cmsvr.log files from /opt/svplus/log directory.

•Screen snapshots.

•CLI dump of this operation if applicable.

Possible alternative workaround—None.

J.10.10 Performance Management Collection and Parsing Problems

PM collection is done on the entire node and statistics files are uploaded from all applicable cards on that node.

The Stats Parser parses these statistics files and stores the stats data in the database.

J.10.10.1 PM Collection Issues

This section includes the following information:

•J.10.10.1.1 pmcollector—Generic Troubleshooting, page J-117

•J.10.10.1.2 PM Collection Fails for the Node—Log File Shows "Node not discovered", page J-118

•J.10.10.1.3 PM Collection Fails for the Node—Log File Shows "Card not discovered", page J-118

•J.10.10.1.4 PM Collection Fails for the Node—Log File Shows "Time not synchronized", page J-119

•J.10.10.1.5 PM Collection Fails for the Node—Log File Shows "Snmp failed", page J-119

•J.10.10.1.6 PM Collection Fails for the Node—Log File Shows "Ftp failed", page J-120

•J.10.10.1.7 PM Collection Fails for the Node—Log File 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", page J-120

J.10.10.1.1 pmcollector—Generic Troubleshooting

When performing generic troubleshooting, always do the following:

•Verify that the pmcollector process is running by executing the psg pmcollector command and checking for a result.

•Make sure the stats files are in the /opt/svplus/purge directory of CTM. Check for all stats files; there should not be any missing file, and there should be no files accumulated in the /opt/svplus/spool directory.

•Check the file_err_log table for any file collection failure.

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