SNA Link/iX Node Managers Guide (30291-90009)
Table Of Contents
- 1 SNA Links Overview
- 2 SNA Node and Link Configuration
- 3 Logging Configuration
- 4 SNA Node Startup and Shutdown
- 5 SNA Link Troubleshooting
- 6 MPE Commands
- 7 SNA Link Installation Information
- A Messages
- SDLC Link Startup Error Messages
- SDLC Link Driver Error Messages
- SNACONTROL Error Messages
- SNA Transport Error Messages
- SNA Transport Logging Messages
- SDLC Link Shutdown Error Messages
- X.25 Link Failure Error Codes
- X.25 Link Module Configurator Error Codes
- X.25 Link QLLC Internal Error Codes
- NetView Alerts Error Messages
- Network Dump Manager Error Messages
- LAN Error Messages
- B Netview Alerts

Appendix A 189
Messages
SDLC Link Driver Error Messages
ACTION: If this problem occurs repeatedly, call your Hewlett-Packard
support contact.
1051 MESSAGE: Request received when hardware in bad state.
CAUSE: The hardware was not ready to process a request message that
required hardware participation.
ACTION: Retry the request at a later time. If the problem continues, call
your Hewlett-Packard support contact.
1052 MESSAGE: Not enough TARs available to process request.
CAUSE: The driver could not obtain enough context storage to begin
processing a request, so the request was rejected. Unexpected use of
incorrect port subqueues might have created excessive pending
hardware activity.
ACTION: Write down the error information displayed on the console,
submit an SR, and call your Hewlett-Packard support contact.
1053 MESSAGE: Request received in invalid state.
CAUSE: The driver received a sequencing message at the wrong time.
This was a startup, shutdown, or dump control message that arrived
out of sequence.
ACTION: Write down the error information displayed on the console,
submit an SR, and call your Hewlett-Packard support contact.
1054 MESSAGE: Unimplemented request received.
CAUSE: The driver recognized a request message but the feature it
requested is not applicable to that driver. The message descriptor was
known but the message or its subfunction codes are not implemented.
ACTION: Call your Hewlett-Packard support contact and explain what
you were trying to do.
1055 MESSAGE: One or more do_bind config addresses is zero (0).
CAUSE: The path to the hardware might not be configured correctly.
ACTION: Use NMMGR or the configuration file critical summary to
ensure that the configured Physical Path is correct for the slot the PSI
is in.
CAUSE: The physical path to the hardware might be faulty, or a
previously undetected hardware failure might have occurred since
system startup.
ACTION: Write down the error information displayed on the console,
submit an SR, and call your Hewlett-Packard support contact.
1056 MESSAGE: Critical configuration message data is incorrect.
CAUSE: The configuration buffer that was passed to the driver during
startup was not correctly formatted for the driver it was sent to. That