User guide
C-76
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Connection Management Problems
C.9.3.5 Cannot Add Connection Between -byte Port Header and -byte Port Header for chan type NIW
and NIW-replace
During a connection addition between two FRSM_12 ports, the cmsvr checks to see if the port headers
are the same (4-byte or 2-byte) for both the end points. An error is thrown if they are not. "Cannnot add
Connection between 4 byte port header to 2 byte port header for chan type NIW or NIW-replace."
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, in the directory /opt/svplus/log.
Possible alternative workaround—None
C.9.3.6 Unsupported Service Type - General node-slot-port-version
During a Connection addition the cmsvr checks the node/slot/port versions to ensure that the service type
is supported on that version of the node/card/port.
Step 1 Make sure that the said version of the node/slot or port support that service type from Cisco MGM.
Step 2 Check the ConnGroupService.mib as an additional check for the versions and the supported parameters.
Defect Information—Collect the cmsvr logs, in the directory /opt/svplus/log.
Possible alternative workaround—None
C.9.3.7 End Point Not Present in One of the Connection Tables During Modify
When a connection modification is attempted and an error window on the screen states "Connection []
not found in database"
Step 1 Verify that a row (entry) exists for the connection in the user_connection. A query in the form
%> 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 look in the corresponding connection table (connection - for FR, atm_connection for atm
segments, cesm_connection for cesm segments, rpm_connection for rpm segments and voice_conn for
vism segments) to see if the connection exists there.
Step 3 If it doesn't look in the dbkr_temp table for an entry for that connection.
Defect Information—The following log files need to be collected:
Collect the cmsvr, sdbroker and corresponding em logs, in the directory /opt/svplus/log.
Collect the 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 synchup to complete