OSI Troubleshooting Guide, May 1997

68 Chapter 2

Problem Solving

Common Logged Errors

Table 2-7 Subsystem TRANSPORT

NOTE Transport errors will have message IDs that begin with either 41xx or

40xx, depending on whether you are running over CLNS or CONS

respectively. The statements shown below apply as well to the 40xx

errors.

[5010]

S_DCNX_KO

This error is logged after the Session layer has successfully

established a connection, but is releasing the connection in some

error state. Examine the log or user application for other errors.

Error Description

[4103]

Protocol Error

Indicates a protocol error was detected at this layer. You should

verify that both sides are using correct combinations of Class,

Alternate Class, Flow Control and Expedited Data. If problem

persists, ensure that you have both Transport and Network layer

traces of the dialog, and contact your HP support representative.

[4108]

T_REJECT

Indicates that the Transport connection was not successfully

established. Examine the log for other errors (such as routing

problems, or network layer problems). If no other logged errors

appear, the problem may be that no process is listening at the

address you speciﬁed. Verify the remote address given as well as

what addresses are available at the remote.

[4113]

Routing

Indicates that CLNS was unable to determine the NSAP/ MAC

address translation for the destination Network Address given.

Possible problems are: mistyped address, remote is not up, remote

does not support ES/IS, the remote’s destination conﬁguration

(ots_dests) is incorrect.

[4115]

Processing

Error

This error usually appears in conjunction with a protocol error. It

may give more information about what was not liked with the PDU.

Error Description