J-92
Cisco Transport Manager Release 6.0 User Guide
78-16845-01
AppendixJ Troubleshooting
J.10.8 Connection Management Problems
Step 1 Determine what port header was used while creating the port in question. Then use ports with matching
port headers to create the connection.
Defect Information—Collect the cmsvr logs from the /opt/svplus/log directory.
Possible alternative workaround—None.
J.10.8.3.6 Unsupported Service Type—General node-slot-port-version
During a connection addition, the cmsvr checks the node, slot, and port versions to ensure that the
service type is supported on that version of the node, card, and port.
Step 1 Make sure that the version of the node, slot, or port supports that service type from CTM.
Step 2 Check the ConnGroupService.mib as an additional check for the versions and the supported parameters.
Defect Information—Collect the cmsvr logs from the /opt/svplus/log directory.
Possible alternative workaround—None.
J.10.8.3.7 Endpoint Is Not Present in One of the Connection Tables During a Modify Operation
When a connection modification is attempted, an error message is thrown:
"Connection [] not found in database."
Step 1 Verify that a row (entry) exists for the connection in the user_connection. Perform a query:
%> echo "select (*) from user_connection where l_node_id = A and l_slot = B and l_port = C
and l_subchnl_1 = D and l_subchnl_2 = E" | dbaccess stratacom
Step 2 If it does not exist, look in the corresponding connection table to see if the connection exists. Connection
entries are as follows:
connection for FR
atm_connection for atm segments
cesm_connection for cesm segments
rpm_connection for rpm segments
voice_conn for vism segments
Step 3 If it does not exist, look in the dbkr_temp table for an entry for that connection.
Defect Information—The following log files need to be collected:
Cmsvr, sdbroker and corresponding em logs, in the directory /opt/svplus/log.
Outputs of the database entries for the endpoints in the segment tables and user_connection table.
Possible alternative workaround—Resync the node or wait for sync-up to complete.