User guide

C-120
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Miscellaneous Problems
Defect Information: See C.15.2.1 Connection Inconsistency Between the Switch and GUI .
Possible alternative workaround—See C.15.2.1 Connection Inconsistency Between the Switch and GUI
Related key index entries: inconsistency, connection
C.15.2.3 Inconsistent Connection Secondary Status
The GUI display of 'Secondary Status' is from the 'Secondary_status' field of the user_connection table.
The field represents the worst condition of any of the segments in the connection. This field is a bit map
with each secondary status using 2 bits. The values of each status entry are
0 = unknown
1 = ok
2 = fail
The bit pattern is:
bits 1-2 local abit
bit 2,4 local ais
bit 5,6 local OAM
bit 7,8 local Conditioned
bit 9,10 remote abit
bit 11, 12 remote AIS
bit 13,14 remote OAM
bit 15, 16 remote Conditioned
Step 1 If the value is not what is expected, check the connection level databases for each segment to see if they
are correct. See C.15.2.1 Connection Inconsistency Between the Switch and GUI . The last message on
the segment in question is the important one.
Defect Information: See C.15.2.1 Connection Inconsistency Between the Switch and GUI .
Possible alternative workaround—See C.15.2.1 Connection Inconsistency Between the Switch and GUI
Related key index entries: inconsistency, connection
C.15.2.4 Incomplete Connections
A common issue is having 'to many' connections on a given card. This problem may be a result of
incomplete connections. For example, if a feeder segment of a three-segment connection has not been
processed by databroker, the incomplete connection would have an endpoint of a routing node, not the
missing feeder. There would appear to be 'to many' connections on the routing node. A connection can
be identified as incomplete if the 'state = 4' in the user_connection table
Step 1 Check the user_connection table for the number of segments and the inseg flags for the connection in
question.