J-132
Cisco Transport Manager Release 6.0 User Guide
78-16845-01
AppendixJ Troubleshooting
J.10.13 Miscellaneous Problems
The cache dump will be written to a file in /opt/svplus/log/sdbkrCache.dump. Verify if the connection
in question is correct in the cache.
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
as well as the segment tables for this connection. The specific node, slot, logical_port, vpi, and vci of
both ends of the connection in question is also useful. If a cache dump was done, include that also.
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>]. If the problem still exists, collect the defect information.
Related key index entries: inconsistency, connection, databroker
J.10.13.2.2 Inconsistent Connection Status
The GUI display of Status is from the state field of the user_connection table. The field represents the
worst condition of any of the segments in the connection. This field values are:
•1 = Clear
•2 = Fail
•3 = Down
•4 = Incomplete
•5 = Error
Step 1 If the value is not what is expected, check the connection level databases for each segment to see if they
are correct.The last message on the segment in question is the important one.
Step 2 If the status is incomplete it means that one of the segments of the connection is not in the
user_connection table, check the in_seg flags in the user_connection table entry for this connection.
Search the database and messages for the segment that has flag = 0.
If two primary endpoints each have the same secondary endpoint, then you have an errored connection.
The first connection established will have a status of Error and the second primary endpoint connected
to the secondary will have a status of Incomplete.
Defect Information—See J.10.13.2.1 Connection Inconsistency Between the Switch and GUI, page
J-129.
Possible alternative workaround—See J.10.13.2.1 Connection Inconsistency Between the Switch and
GUI, page J-129.
Related key index entries: inconsistency, connection
J.10.13.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