SNA Transport Logging Messages
MPE documents | |
 Complete PDF | |
| Table of Contents | |
| Index |
| MESSAGE: PathInfoUnit |
| Level:
CAUSE: This message is used to print a Path Information Unit (PIU) as part of a logging message. ACTION: None. |
| MESSAGE: Activation/Deactivation protocol violation |
| Level:
CAUSE: The remote system has violated protocol in the activation/deactivation of a session. The erroneous Path Information Unit (PIU) is discarded. ACTION: Call your Hewlett-Packard support contact. |
| MESSAGE: Attempt to close link failed on node NodeName |
| Level:
CAUSE: SNA Transport received an error result code when trying to close the link. ACTION: Call your Hewlett-Packard support contact. |
| MESSAGE: Attempt to establish PU type 2.1 connection failed on node NodeName |
| Level:
CAUSE: The remote node did not respond to the XID poll. ACTION: Ensure that the remote node is active (VARIED ON). Also, make sure the remote MAC address, LSAP, and DSAP configured on the local MPE/iX system matches the remote system configuration. |
| MESSAGE: Attempt to open link failed on node NodeName |
| Level:
CAUSE: SNA Transport received an error result code when trying to open the link. ACTION: Call your Hewlett-Packard support contact. |
| MESSAGE: Close user granted on node NodeName |
| Level:
CAUSE: A request to close an LU user has been granted. ACTION: None; this is a normal event. |
| MESSAGE: Error code = ErrorNum |
| Level:
CAUSE: This accompanies the packet discard logging messages, indicating the reason for the discard. ACTION: None. |
| MESSAGE: Host beginning activation of node NodeName |
| Level:
CAUSE: SNA Transport received the ACTivate Physical Unit (ACTPU) request for the indicated node. ACTION: None; this is a normal event. |
| MESSAGE: HP IS PRIMARY LU LUName |
| Level:
CAUSE: This is part of the OpenUser/CloseUser logging messages. It indicates that the user is a primary LU, capable of issuing a BIND request. ACTION: None; this is a normal event. |
| MESSAGE: HP IS SECONDARY LU LUName |
| Level:
CAUSE: This is part of the OpenUser/CloseUser logging messages. It indicates that the user is a secondary LU, capable of only receiving a BIND request. ACTION: None; this is a normal event. |
| MESSAGE: INTERNAL ERROR ErrorNum IN NODE NodeName |
| Level:
CAUSE: The indicated SNA node has recognized a critical error. This event is serious and causes the node to shut down. ACTION: Call your Hewlett-Packard support contact, and please report the ErrorNum. |
| MESSAGE: IPR received correctly |
| Level:
CAUSE: SNA Transport received and processed the Isolated Pacing Response (IPR) and is discarding it when finished. ACTION: None; this is a normal event. |
| MESSAGE: Link activated for node NodeName |
| Level:
CAUSE: Link activation has completed successfully. ACTION: None; this is a normal event. |
| MESSAGE: Link connect failure on node NodeName |
| Level:
CAUSE: SNA Transport was unable to connect with the WAN module configurator. ACTION: Call your Hewlett-Packard support contact. |
| MESSAGE: Link disconnect failure on node NodeName |
| Level:
CAUSE: SNA Transport received a bad response to a link disconnect request. ACTION: Call your Hewlett-Packard support contact. |
| MESSAGE: Link failure, recovery in progress on node NodeName |
| Level:
CAUSE: A recoverable link failure has occurred on the indicated node. ACTION: Call your Hewlett-Packard support contact. |
| MESSAGE: Link failure, shutting down the node NodeName |
| Level:
CAUSE: An irrecoverable link error has occurred on the indicated node. ACTION: Call your Hewlett-Packard support contact. |
| MESSAGE: LUNAME IS LUName |
| Level:
CAUSE: This message is printed for error codes that do not yet have accompanying diagnostic messages. ACTION: None; this is a normal event. |
| MESSAGE: Max Data size greater than LLC frame size on node NodeName |
| Level:
CAUSE: The value specified in the MAX DATA field of the SNA Node PU Data screen is too big. This value must be at least 36 less than the BUFFER SIZE specified in the NS Link Token Ring Data screen. ACTION: Use NMMGR to change the value of the MAX DATA filed in the SNA Node PU Data screen or the value of the BUFFER SIZE in the NS Link Token Ring Data screen. |
| MESSAGE: Module ModuleNum rcvd unrecognized msg on node NodeName |
| Level:
CAUSE: The indicated SNA Transport module has received a port message it does not recognize. ACTION: Call your Hewlett-Packard support contact. |
| MESSAGE: NETVIEW — Sending an alert on node NodeName |
| Level:
CAUSE: SNA Transport sent an alert to NetView. ACTION: Write down the circumstances and report them to your HP e3000 system operator. |
| MESSAGE: NETVIEW ALERT — Dial a bad phone number on node NodeName |
| Level:
CAUSE: SNA Transport received an error from the SDLC link driver because it tried to dial with an invalid phone number. ACTION: Use NMMGR or the configuration file critical summary to verify that the configured Phone Number is correct. |
| MESSAGE: NETVIEW ALERT — Dial not completed on node NodeName |
| Level:
CAUSE: The automatic calling unit (ACU) is not turned on. ACTION: Ensure that the ACU is turned on. CAUSE: SNA Transport received an error from the SDLC link driver because it received a busy signal or no answer at all from the remote system. ACTION: This should be a temporary problem. Wait a few minutes and then try re-dialing. |
| MESSAGE: NETVIEW ALERT — Inoperative dialing device on node NodeName |
| Level:
CAUSE: SNA Transport received an error from the SDLC link driver because it detected that the automatic calling unit (ACU) is not on or that the cable is missing. ACTION: Ensure that the ACU is on and functional, and that the cable is connected correctly. |
| MESSAGE: NETVIEW ALERT — Link Failure on node NodeName |
| Level:
CAUSE: SNA Transport received an error from the SDLC link driver because it detected a link failure. ACTION: Call your Hewlett-Packard support contact. |
| MESSAGE: NETVIEW ALERT — WAN driver detected an error on node NodeName |
| Level:
CAUSE: SNA Transport received an error from the SDLC link driver because it detected an internal error. ACTION: Call your Hewlett-Packard support contact. |
| MESSAGE: (NO DIAGNOSTIC MESSAGE IN CATALOG) |
| Level:
CAUSE: This message is printed for error codes that do not yet have accompanying diagnostic messages. ACTION: None; this is a normal event. |
| MESSAGE: Node NodeName all sessions closed — beginning shutdown |
| Level:
CAUSE: SNA Transport has finished shutting down all sessions on the indicated node and is about to begin node clean up and link shutdown. ACTION: None; this is a normal event. |
| MESSAGE: Node NodeName ready for activation by host |
| Level:
CAUSE: SNA Transport has completed initialization and link activation, and is now awaiting activation of the PU by the remote system. ACTION: None; this is a normal event. Note that if you are using a manual-dial modem, you can begin to dial after this message is displayed. |
| MESSAGE: Node NodeName shut down completed |
| Level:
CAUSE: Node shutdown has completed successfully. The indicated node is no longer active. ACTION: None; this is a normal event. |
| MESSAGE: Node shutdown in progress |
| Level:
CAUSE: SNA Transport is discarding a Path Information Unit (PIU) received during the node shutdown. ACTION: None; this is a normal event. |
| MESSAGE: Open user granted on node NodeName |
| Level:
CAUSE: A request to open an LU user has been granted. ACTION: None; this is a normal event. |
| MESSAGE: Pacing req not allowed in current state |
| Level:
CAUSE: The remote system has sent consecutive pacing requests, with no response to the initial request. ACTION: Call your Hewlett-Packard support contact. |
| MESSAGE: PACKET DISCARDED ON NODE NodeName BY MODULE ModuleNum |
| Level:
CAUSE: A shutdown is occurring, and the module is cleaning up before termination. ACTION: None; this is a normal event. CAUSE: An error has been detected by SNA Transport and the erroneous packet has been discarded. The error code and diagnostic message indicate the reason for the discard. ACTION: Call your Hewlett-Packard support contact. |
| MESSAGE: PACKET REJECTED ON NODE NodeName BY MODULE ModuleNum |
| Level:
CAUSE: An error was detected in the received request. So, a negative response (a packet reject) is sent by SNA Transport. ACTION: Call your Hewlett-Packard support contact. CAUSE: The node is shutting down. ACTION: None; this is a normal event. CAUSE: The remote system is configured to send a welcome screen immediately after receiving the ACTivate Logical Unit (ACTLU) response. When this is the case, the welcome screen is rejected with sense 1003. ACTION: None; this is a normal event. The welcome screen is retransmitted by the remote system when the LU-LU session is established. |
| MESSAGE: PU type 2.1 XID3 (negotiable) exchange protocol error on node NodeName |
| Level:
CAUSE: SNA Transport detected an XID3 protocol violation. This may cause the MPE/iX SNA node to shut down. ACTION: Submit node trace, SNA/Transport version, NMCONFIG.PUB.SYS, and a console logging list to the Hewlett-Packard support contact. |
| MESSAGE: PU type 2.1 XID3 (T2P1) exchange protocol error on node NodeName |
| Level:
CAUSE: SNA Transport detected an XID3 protocol violation. This may cause the MPE/iX SNA node to shut down. ACTION: Submit node trace, SNA/Transport version, NMCONFIG.PUB.SYS, and a console logging list to the Hewlett-Packard support contact. |
| MESSAGE: Received invalid negative response |
| Level:
CAUSE: SNA Transport received an erroneous negative response. ACTION: Call your Hewlett-Packard support contact. |
| MESSAGE: Received Non-Activation XID3 on node NodeName |
| Level:
CAUSE: SNA Transport received an unsupported non-activation XID3. ACTION: None. SNA Transport will ignore the non-activation XID3 and continue to process as normal. |
| MESSAGE: Received PIU with invalid FID type |
| Level:
CAUSE: SNA Transport received a Path Information Unit (PIU) with a Format IDentifier (FID) other than 2. ACTION: Call your Hewlett-Packard support contact. |
| MESSAGE: Received PIU with invalid LFSID |
| Level:
CAUSE: SNA Transport has received a Path Information Unit (PIU) with an invalid session ID. ACTION: Call your Hewlett-Packard support contact. |
| MESSAGE: Received PIU with invalid RH |
| Level:
CAUSE: SNA Transport received a Path Information Unit (PIU) whose Request/Response Header (RH) is not of the supported format. ACTION: Call your Hewlett-Packard support contact. |
| MESSAGE: Received PIU with invalid TH |
| Level:
CAUSE: SNA Transport received a Path Information Unit (PIU) whose Transmission Header (TH) is not of the supported format. ACTION: Call your Hewlett-Packard support contact. |
| MESSAGE: Received too long RU |
| Level:
CAUSE: SNA Transport received a Path Information Unit (PIU) whose Request/Response Unit (RU) is longer than the maximum RU size specified in the BIND. ACTION: Call your Hewlett-Packard support contact. |
| MESSAGE: Received too short RU |
| Level:
CAUSE: SNA Transport received a Path Information Unit (PIU) shorter than the sum of the length of the Request/Response Header (RH) plus Transmission Header (TH); that is, no Request/Response Unit (RU) exists. ACTION: Call your Hewlett-Packard support contact. |
| MESSAGE: Received unexpected expedited response |
| Level:
CAUSE: SNA Transport received an expedited response when no expedited request has been sent. ACTION: Call your Hewlett-Packard support contact. |
| MESSAGE: Received unexpected IPR |
| Level:
CAUSE: SNA Transport received an Isolated Pacing Response (IPR) when "send pacing" was not specified in the BIND. ACTION: Call your Hewlett-Packard support contact. |
| MESSAGE: Received unexpected pacing response |
| Level:
CAUSE: SNA Transport received a pacing response when no request was sent. ACTION: Call your Hewlett-Packard support contact. |
| MESSAGE: Received unexpected response |
| Level:
CAUSE: SNA Transport received a response for which no corresponding request exists. ACTION: Call your Hewlett-Packard support contact. |
| MESSAGE: Received unexpected RQR response |
| Level:
CAUSE: SNA Transport received a ReQuest Recovery (RQR) response when no expedited request has been sent. ACTION: Call your Hewlett-Packard support contact. |
| MESSAGE: Received XID3 with format error on node NodeName |
| Level:
CAUSE: SNA Transport received an XID3 with illegal format. ACTION: The remote host does not conform to the XID3 exchange protocol. Submit an CR along with an SNA node trace, SNA/Transport version, NMCONFIG.PUB.SYS, a console logging list, and time and date of error to the Hewlett-Packard support contact. |
| MESSAGE: Remote node did not support PU type 2.1 on node NodeName |
| Level:
CAUSE: The remote node is not a PU type 2.1 node. ACTION: Ask the remote system administrator to reconfigure the system to support PU type 2.1. |
| MESSAGE: Request not allowed in current state |
| Level:
CAUSE: SNA Transport has received an unexpected request. ACTION: Call your Hewlett-Packard support contact. |
| MESSAGE: SDI connect reply failure on node NodeName |
| Level:
CAUSE: SNA Transport cannot establish 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 connect request failure on node NodeName |
| Level:
CAUSE: SNA Transport cannot establish 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 disconnect reply failure on node NodeName |
| Level:
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 disconnect request failure on node NodeName |
| Level:
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 rendezvous reply failure on node NodeName |
| Level:
CAUSE: SNA Transport cannot establish 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 rendezvous request failure on node NodeName |
| Level:
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 |
| Level:
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 |
| Level:
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 |
| Level:
CAUSE: SNA Transport detected a missing segment or received segments out of order. ACTION: Call your Hewlett-Packard support contact. |
| MESSAGE: Sense code = SenseCode |
| Level:
CAUSE: This accompanies the packet reject logging messages, indicating the reason for the reject. ACTION: None. |
| MESSAGE: Session not open |
| Level:
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 |
| Level:
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. |
| MESSAGE: Session terminated on node NodeName |
| Level:
CAUSE: The indicated session received and processed a DeACTivate Physical Unit (DACTPU), DeACTivate Logical Unit (DACTLU), or UNBIND, as applicable. ACTION: None; this is a normal event. |
| MESSAGE: Shutdown type = Internal error |
| Level:
CAUSE: This is part of the logging messages "Node NodeName all sessions closed — beginning shutdown" and "Node NodeName shut down completed" (each message is described earlier in this listing). This message indicates the type of shutdown (caused by an internal error) that is in progress. ACTION: None. |
| MESSAGE: Shutdown type = Kill |
| Level:
CAUSE: This is part of the logging messages "Node NodeName all sessions closed — beginning shutdown" and "Node NodeName shut down completed" (each message is described earlier in this listing). This message indicates the type of shutdown (kill) that is in progress. ACTION: None. |
| MESSAGE: Shutdown type = Link failure norecovery |
| Level:
CAUSE: This is part of the logging messages "Node NodeName all sessions closed — beginning shutdown" and "Node NodeName shut down completed" (each message is described earlier in this listing). This message indicates the type of shutdown (caused by a nonrecoverable link failure) that is in progress. ACTION: None. |
| MESSAGE: Shutdown type = Link failure recovery |
| Level:
CAUSE: This is part of the logging messages "Node NodeName all sessions closed — beginning shutdown" and "Node NodeName shut down completed" (each message is described earlier in this listing). This message indicates the type of shutdown (caused by a recoverable link failure) that is in progress. ACTION: None. |
| MESSAGE: Shutdown type = Protocol |
| Level:
CAUSE: This is part of the logging messages "Node NodeName all sessions closed — beginning shutdown" and "Node NodeName shut down completed" (each message is described earlier in this listing). This message indicates the type of shutdown (protocol) that is in progress. ACTION: None. |
| MESSAGE: Shutdown type = Quiesce |
| Level:
CAUSE: This is part of the logging messages "Node NodeName all sessions closed — beginning shutdown" and "Node NodeName shut down completed" (each message is described earlier in this listing). This message indicates the type of shutdown (quiesce) that is in progress. ACTION: None. |
| MESSAGE: SIDH = SessIDHi, SIDL = SessIDLo, ODAI OAFDAFAssgnInd |
| Level:
CAUSE: This is part of the OpenUser/CloseUser logging messages. It uniquely identifies the session. ACTION: None; this is a normal event. |
| MESSAGE: SNA PACKET REJECTED ON NODE NodeName BY MODULE ModuleNum |
| Level:
CAUSE: A packet intended for the LU-LU session was sent on the LU-SSCP session. The LU-LU session is not available, since no SNA service has opened the session yet. So, the packet was rejected. ACTION: Call your Hewlett-Packard support contact. CAUSE: The remote system is configured to send a welcome screen immediately after receiving the ACTivate Logical Unit (ACTLU) response. When this is the case, the welcome screen is rejected with sense 1003. ACTION: None; this is a normal event. The welcome screen is retransmitted by the remote system when the LU-LU session is established. |
| MESSAGE: SNA Transport received exception event from LLC on node NodeName |
| Level:
CAUSE: An exception event caused the token ring LLC level to shut down. ACTION: Software internal error. Submit node trace, SNA/Transport version, NMCONFIG.PUB.SYS, and console logging list to the Hewlett-Packard support contact. |
| MESSAGE: SOCKERR nnn |
| Level:
CAUSE: This is part of the logging message "subsystem = SubsysID, procedure = ProcNum, error num = ErrorNum" when the ProcNum is -1 (the message is described later in this listing). ACTION: Look in the NS 3000/XL Error Messages Reference Manual for the message with the number corresponding to nnn. |
| MESSAGE: Subsystem = SubsysID, Error Code = ErrorCode |
| Level:
CAUSE: This is associated with the "INTERNAL ERROR ErrorNum IN NODE NodeName" logging message (the message is described earlier in this listing). ACTION: Write down the SubsysID and ErrorCode, and call your Hewlett-Packard support contact. |
| MESSAGE: Subsystem = SubsysID, procedure = ProcNum, error num = ErrorNum |
| Level:
CAUSE: This is part of the logging message for link errors (including errors that occur when trying to open or close the link). ACTION: Write down the indicated values and call your Hewlett-Packard support contact. Note that, (1) depending on the ErrorNum, you might have to look at a message with the corresponding number in "X.25 Link Failure Error Codes" later in this appendix; and (2) depending on the ProcNum, you might have to look at a message with the corresponding number in "X.25 Link QLLC Internal Error Codes" later in this appendix. |
|
SNA Transport Error Messages |
SDLC Link Shutdown Error Messages |