J-93
Cisco Transport Manager Release 6.0 User Guide
78-16845-01
Appendix J Troubleshooting
J.10.8 Connection Ma nagement Problems
J.10.8.3.8 Cmsvr—Connection Diagnostic Issues
The cmsvr processes validates and services the connections provisioning requests from the CM GUI.
During an add, modify, or delete connection request, the request is forwarded to the cmgrd process
through an ILOG (IPC) request. If the request is for connection diagnostics such as testdelay or testconn
(except conntrace), cmsvr sends it to the snmpcomm process for forwarding to the switch.
J.10.8.3.9 TestConn or TestDelay Failed with Switch Error
Connection diagnostics (testdelay/testcon/up/down/reroute) fail with one of the following error
messages:
•TestDelay failed with Switch error
•TestConn failed with Switch error
Step 1 Query the connection information from the user_connection table for that connection. If possible,
execute the testdelay/testcon diagnostics for the same connection from ConnProxy (Service Agent) and
verify the results.
Step 2 Query the connection information from the switch CLI and verify the connection status (dspcon or
dspchan).
Step 3 Execute the testdelay/testcon diagnostics from the switch CLI and verify that the results match what was
reported in CTM (tstdelay, tstconn).
Defect Information—Do the following:
•Capture selnd output
•Copy all the cmsvr logs from the /opt/svplus/logs directory
•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 testdelay/testconn diagnostics on the same connection
Possible alternative workaround—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
testdelay/testconn diagnostics.
Note The testcon is not applicable for single-end SPVC connections and on AXSM card types.
Note The connection status should be Clear or Fail for the testdelay/testcon diagnostics to be executed,
otherwise the test will be blocked from cmsvr.
Note The testconn/testdelay diagnostics cannot be done on RP- to-RPM connections.
Note The testdelay diagnostic is not applicable for voice and data connections.