Appendix J Troubleshooting
J.10.10 Performance Management Collection and Parsing Problems
•Check the collsvr_err_log table for any failure during start/stop collection.
•Check the coll_err_log table for entire collection server errors.
•Check '/opt/svplus/cache/scm/scmcollout.log' for a completed stats file request.
•Check '/opt/svplus/cache/scm/scmcollin.log' to verify whether or not stats file has been completed.
•Check '/opt/svplus/cache/scm/scmcollout.log' for stats file collection errors.
J.10.10.1.2 PM Collection Fails for the
This can happen when the node is not in mode 3.
Step 1 Check the node_info table by executing the following command:
echo "select node_not_discovered from node_info where node_id=<node_id> and slot=<slot>" dbaccess
If node_not_discovered is set to 1, it means that the node has not been discovered.
Step 2 Check the state of the node by executing the following command:
echo "select (*) from node where
Step 3 Check the mode of the node in the output: the mode must be 3.
Defect
•pmcollector.log, output of selnd or output of:
echo "select (*) from node where node_name =
•Related key index entries
•pmcollector
Possible alternative
J.10.10.1.3 PM Collection Fails for the
This can happen when the card is not in the Active state.
Step 1 Check the node_info table by executing the following command:
echo "select card_not_discovered from node_info where node_id=<node_id> and slot=<slot>" dbaccess
If card_not_discovered is set to 1, it means that the card has not been discovered.
Step 2 Check the card table by executing the following command:
echo "select fc_state, fc_type, slot from card where node_id =
The fc_state of the card must be 3.
Defect
•Pmcollector.log, output of:
| Cisco Transport Manager Release 6.0 User Guide |
|