SNA Link/iX Node Managers Guide (30291-90507)

236 AppendixA
Messages
SNA Transport Logging Messages
MESSAGE: SDI rendezvous request failure on node NodeName
CAUSE: The value specified in Local SSAP field in the SNA Node Token
Ring Link screen is being used by another node.
ACTION: Use NMMGR or the configuration file critical summary to
check that the Local SSAP value of the node is not the same as any
currently
active SNA node. Otherwise, submit a node trace,
SNA/Transport version, NMCONFIG.PUB.SYS, and a list of console
logging to the Hewlett-Packard support contact.
MESSAGE: SDI separate reply failure on node
NodeName
CAUSE: SNA Transport cannot disconnect the LLC link connection.
ACTION: Software internal error. Submit node trace, SNA/Transport
version, NMCONFIG.PUB.SYS, and console logging list to the
Hewlett-Packard support contact.
MESSAGE: SDI separate request failure on node NodeName
CAUSE: SNA Transport cannot disconnect the LLC link connection.
ACTION: Software internal error. Submit node trace, SNA/Transport
version, NMCONFIG.PUB.SYS, and console logging list to the
Hewlett-Packard support contact.
MESSAGE: Segmentation error
CAUSE: SNA Transport detected a missing segment or received
segments out of order.
ACTION: Call your Hewlett-Packard support contact.
MESSAGE: Sense code =
SenseCode
CAUSE: This accompanies the packet reject logging messages,
indicating the reason for the reject.
ACTION: None.
MESSAGE: Session not open
CAUSE: SNA Transport received a deactivation response on a session
that is no longer open.
ACTION: Call your Hewlett-Packard support contact.
MESSAGE: Session started on node
NodeName
CAUSE: The indicated session received and processed an ACTivate
Physical Unit (ACTPU), ACTivate Logical Unit (ACTLU), or BIND, as
applicable.
ACTION: None; this is a normal event.