SDLC Alert Local Logging

Before SNA Server attempts to build and send an SDLC Link Alert, information about the outage that caused the alert is logged in a log file that can be viewed using the Windows NT Event Viewer. Message 182 will always be logged, as follows:

182I:  Connection failure, code = (outagecode)
Cause Data                          = hh...hh
Link Role                           = hh
Remote Node Type                    = hh

The Outage Code (outagecode) is also reported on a 23 message. For a complete list of these codes, the conditions they represent, and the specific Link Alerts on which they are used, see the next section.

Cause Data is a list of the failure causes from the Failure causes subvector in the alert. Link Role and Remote Node type are as described in the Link Connection Subsystem Configuration Data subvector in the alert.

A connection failure can be due to a station outage, rather than a link outage. If it is due to a station outage — which can be recognized by outage code values of X'80' or higher — then message 183, formatted as follows, will also be logged:

183I:
Detailed diagnostic data for station (stationaddress):
SBSY   CFTX   CFRX   V(S)   V(R)   N(R)   OSFC   T1CT
hh     hhhh   hhhh   hh     hh     hh     hh     hhhh

The value (stationaddress) is the station address as given in the Detail qualifier subvector in the alert.

The other fields are all data from the Link Station Data subvector, as follows:

Field

Description

SBSY

Link station state: 80 or 40

(local or remote station sending RNR)

CFTX

Last SDLC control field sent

CRX

Last SDLC control field received

V(S)

N(S) count

V(R)

N(R) count

N(R)

Last received N(R)

OSFC

Outstanding frame count

T1CT

Reply timer expiration count


Identifying Alerts from Local Logs Only

When only the local log of an alert is available, you can still obtain the information that would have been supplied on the alert. To do this, check the outage code given on the 182 message against the following list to find the alert that uses this outage code, and then check the alert data in "SDLC Failure Alerts" earlier in this chapter. Some Outage Codes are used for more than one alert; in these cases, you can find the appropriate alert by comparing the failure causes codes given on the 182 message with those given in the alert data.

SDLC Outage Codes

Outage code

Condition

Alert description/ID

11

DSR failure

1000 : 83BB6EC8

12

CTS failure

3300 : 0231CF0A

14

DCD failure

1000 : C3BB504A

15

Connection terminated by host

2100 : D635CA1 :

24

Nonproductive receive retry exceeded

3300 : C458E284

25

Idle timeout retry exceeded

3300 : 0E2DDF11

29

Connection problem

3300 : 0AECC2

2D

Abnormal response

1000 : 70A15CB0

2E

Write timeout retry exceeded

1000 : 61D02E7B

80

DM received

3300 : BD84C4C9

81

Disconnect retry limit

3300 : 32A37F1B

82

Contact retry limit

3300 : 32A37F1B

83

Poll retry limit

3300 : 32A37F1B

84

No response retry limit

3300 : 32A37F1B

85

Remote busy retry limit

3300 : 66D6DA74

86

FRMR received

2100 : A472BC48

2100 : B3B7D723

2100 : B776CA94

2100 : BA35EC4D

2100 : BEF4F1FA

87

Invalid frame received

2100 : 1103D152

2100 : 15C2CCE5

2100 : 1C40F78B

2100 : 5F7624FD

88, 89

RIM or RD received

2100 : 29BF0032