User guide

C-77
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Connection Management Problems
C.9.3.8 Cmsvr—Connection Diagnostics Issues
The cmsvr processes validates and services the Connection provisioning requests from the CM GUI.
If the request is for connection addition, modification, deletion or connection trace, the request is
forwarded to cmgrd process through ILOG(IPC) request. If the request is for connection diagnostics like
testdelay, testconn etc. (except conntrace), cmsvr sends to snmpcomm process for forwarding to switch.
C.9.3.9 TestConn or TestDelay Failed With Switch Error
Connection diagnostics(testdelay/testcon/up/down/reroute) failures 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 ,
dspchan etc.)
Execute the testdelay/testcon diagnostics from switch CLI and verify the results matches with what was
reported in Cisco MGM(tstdelay, tstconn)
Defect Information
1. Capture selnd output
2. Copy all the cmsvr logs from /opt/svplus/logs directory
3. Capture the user_connection table query output from Cisco MGM DB for the given end point (if the
request is not an addition request)
4. Capture the switch CLI output for the testdelay/testconn diagnostics on the same connection
Possible alternative workaround—
1. 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 etc.). After the
connection comes up and is in clear state, rerun the testdelay/testconn diagnostics again.
2. Note that testcon is not applicable for single-end SPVC connections and on AXSM card types
3. Note that the connection status should be clear or fail for the testdelay/testcon diagnostics to be
executed, otherwise the test will be blocked from cmsvr
4. Note that testconn/testdelay diagnostics cannot be done on RPM to RPM connections
5. Note that testdelay diagnostics is not applicable for VOICE and DATA connections
6. Note that for any connection if the local end of the connection does not support that particular
diagnostics, cmsvr will verify if the diagnostics can be executed from the remote end. If the
diagnostics is not supported by both the end points of a connection, an appropriate error message
will be given to the user.