Cisco Systems 78-16845-01 appendix Connection Up/Down/Reroute Failed, Connection Trace Failures

Appendix J Troubleshooting

J.10.8 Connection Management Problems

Note For any connection, if the local end of the connection does not support that particular diagnostic, cmsvr will verify if the diagnostic can be executed from the remote end. If the diagnostic is not supported by both endpoints of a connection, an appropriate error message will be given.

J.10.8.3.10 Connection Up/Down/Reroute Failed

Connection up/down/reroute diagnostic failed with a switch error.

Step 1 Query the connection information from the user_connection table for that connection.

Step 2 Query the connection information from the switch CLI and verify the connection status (dspcon or dspchan).

Step 3 Execute the up/down/reroute diagnostic from the switch CLI and verify that the results match what was reported in CTM (upcon, dncon, rrtcon).

Defect Information—Do the following:

•Capture selnd output

•Copy all the cmsvr logs from the /opt/svplus/logs directory

•Capture the user_connection table query output from the CTM database for the given endpoint (if the request is not an addition request)

•Switch CLI output for the up/down/reroute diagnostics on the same connection

Possible alternative workaround:

a.Check the status of the connection and clear any alarms due to line/port issues (adding loopback, correcting the physical cable issues by verifying the physical port connections and so on). After the connection comes up and is in the Clear state, rerun the up/down/reroute diagnostics.

b.Verify the connection status to find out if the connection is already down when trying to do a down operation, or the connection is already up when trying to do an up operation.

Note The connection reroute might take the connection to the Fail state for a while.

J.10.8.3.11 Connection Trace Failures

Step 1 Make sure the connection is not in the Fail state. Connection trace does not work on failed connections; in addition, CTM does not block this request.

Step 2 Query the connection information from the user_connection table for that connection.

Step 3 Query the connection information from the switch CLI and verify the connection status (dspcon or dspchan).

Step 4 Execute the connection trace diagnostics from switch CLI and verify that the results match what was reported in CTM (conntrc, dsptrcbuffer).

Defect Information—Do the following:

Cisco Transport Manager Release 6.0 User Guide

J-94 78-16845-01