Appendix J Troubleshooting
J.10.13 Miscellaneous Problems
•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 J.10.13.2.1 Connection Inconsistency Between the Switch and GUI, page J-129. The last message on the segment in question is the important one.
Defect Information—SeeJ.10.13.2.1 Connection Inconsistency Between the Switch and GUI, page J-129.
Possible alternative workaround—SeeJ.10.13.2.1 Connection Inconsistency Between the Switch and GUI, page J-129.
Related key index entries: inconsistency, connection
J.10.13.2.4 Incomplete Connections
A common issue is having too 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 the databroker, the incomplete connection will have an endpoint of a routing node, not the missing feeder. There will appear to be too many connections on the routing node. A connection can be identified as incomplete if the state is equal to four 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.
Step 2 Select num_segs, status, inseg_tbl_1, inseg_tbl_2, inseg_tbl_3 from user_connection where l_node_id = x and l_slot=y and l_port=z and l_subchnl_1 = v and l_subchnl_2 = w.
Defect Information—You need the logs of the processes on both sides of the interface on which the message was dropped. A dump of the specific user_connection table entry that is incorrect is also useful. The specific node, slot, logical_port, vpi, vci of both ends of the connection in question is also useful.
Possible alternative workarounds—If the problem is between the sdbroker cache and the database, a cache resync can be done. To do this execute the command /usr/usrs/svplus/tools/CacheResync [-t <time in seconds>].
Related key index entries: inconsistency, incomplete connection
| | Cisco Transport Manager Release 6.0 User Guide | | | |
| | |
| 78-16845-01 | | | J-133 | |
| | | |
