
Configuring DLSw Services
C-18 114063 Rev. A
Common DLSw Non-Problems
The DLSw log often contains debug event messages that report conditions about
proper network activity. These debug messages are not errors and should not be
treated or reported for further action. The DLSw non-problems include
• Unexpected protocol action
• TCP open error 29
• DLSw peers not reachable due to lack of a route
• Traffic going over SRB instead of DLSw path
• Resetting dynamic window algorithm
• Expecting SNRM prior to DLSw connection to host
Unexpected protocol action
An unexpected protocol action occurred multiple times. This condition indicates
that frames are being transmitted between two DLSw routers while an LLC
Disconnect Pending frame is processing. This condition clears itself and the
DLSw disconnect sequence finishes normally. The following sample log entries
show this condition:
# 36: 04/25/95 22:43:17 DEBUG SLOT 1 DLS Event Code: 16
State change in llc_disc_ind, conn = 30927f70, old state = 1,
new state = 11
# 38: 04/25/95 22:43:17 DEBUG SLOT 1 DLS Event Code: 36
Unexpected protocol action: state = 11, event = 10 conn = 30927f70
# 39: 04/25/95 22:43:17 DEBUG SLOT 1 DLS Event Code: 0
The previous event on slot 1 repeated 7 time(s). [Code 36]
# 40: 04/25/95 22:43:17 DEBUG SLOT 1 DLS Event Code: 45
SSP dl_halted frame rcvd in LLC, conn, state, flag: 30927f70, b,
0
TCP open error 29
The DLSw peer connections through TCP cannot be activated until the source
(local) IP interface becomes active. For example, Token Ring networks that take
longer to initialize may cause this error in the log. The TCP sessions establish
when the IP interface activates. For example:
Comentários a estes Manuais