Appendix J Troubleshooting
J.10.8 Connection Management Problems
•Capture selnd output
•Copy all the cmsvr logs from /opt/svplus/logs directory
•Copy all the cmgrd logs from /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 trace 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 fine in the Clear state, rerun the trace diagnostics.
b.Verify the connection status. If the connection status is Down, trace cannot be executed on the connection. If the connection status is failed, the trace result will probability be an empty string.
Note The connection trace cannot be executed on an incomplete, or DAX PNNI segment connections.
J.10.8.4 CMGRD
This section includes the following information:
•J.10.8.4.1 High-Level Connection Management Subsystem Architecture, page J-96
•J.10.8.4.2 Cmgrd—Sdbroker Errors, page J-97
•J.10.8.4.3 Cmgrd—Sdbroker Addition/Modification/Deletion Errors: Adding a Connection Results in "Fail to Communicate with sDatabroker" Error, page J-97
•J.10.8.4.4 Cmgrd—Sdbroker Addition, Modification, and Deletion Errors: Provisioning a Connection Results in "sDatabroker process busy. Please retry" Error, page J-97
•J.10.8.4.5 Cmgrd—Sdbroker Addition Errors: Adding a Connection Results in "CTM sync-up in progress" Error, page J-98
•J.10.8.4.6 Cmgrd—Sdbroker Addition Errors: Adding a Connection Results in "No more vpi/vci available for local trunk end" Error, page J-98
•J.10.8.4.7 Cmgrd—Sdbroker Addition Errors: Adding a Connection Results in "EndPoint Exists Local/Remote/Both end of the connection already exists." Error, page J-99
•J.10.8.4.8 Cmgrd—Sdbroker Modification/Deletion Errors: Modifying or Deleting a Connection Results in "sDatabroker Could not lock connection entry." Error, page J-100
•J.10.8.4.9 Cmgrd Errors, page J-100
•J.10.8.4.10 Cmgrd—Addition, Modification, and Deletion Errors: Provisioning a Connection Results in "Fail due to Switch Timeout" Error, page J-100
•J.10.8.4.11 Cmgrd—Addition, Modification, and Deletion Errors: Provisioning a Connection Results in “Agent not responding, request timed-out; or Fatal error, Snmpcomm is not running.” Error, page J-101
•J.10.8.4.12 Cmgrd—Addition, Modification, and Deletion Errors: Provisioning a Connection Results in "Outstanding request exists for same object." Error, page J-101
•J.10.8.4.13 Cmgrd—Addition/Modification/Deletion Errors: Provisioning a Connection Results in "Fatal error, IOSMGR is not running, may need to be manually started" Error, page J-102
Cisco Transport Manager Release 6.0 User Guide
