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

178 AppendixA
Messages
SDLC Link Startup Error Messages
17 MESSAGE: Could not unfreeze the configuration data.
CAUSE: Memory problems are occurring.
ACTION: Write down the error information displayed on the console and
call your Hewlett-Packard support contact.
18 MESSAGE: Unable to obtain dump/diag ports.
CAUSE: The Diagnostic User Interface (DUI) software or the Network
Dump Process was not installed properly.
ACTION: Write down the error information displayed on the console and
call your Hewlett-Packard support contact.
19 MESSAGE: Could not create the auxiliary buffer pool.
CAUSE: An internal error has occurred.
ACTION: Write down the error information displayed on the console and
call your Hewlett-Packard support contact.
20 MESSAGE: Could not create or bind with the driver.
CAUSE: (
Status = C3 xx 00D8) The wrong path number is configured for
the installed PSI card.
ACTION: Use NMMGR to correct the Physical Path for the link.
CAUSE: (
Status = CD xx 00D5) The card for the configured path number
is bad.
ACTION: Use NMMGR or the configuration file critical summary to
check that the Physical Path configured for the link corresponds to a
good PSI card. To determine whether the PSI card is good, your
Hewlett-Packard support contact will have to run diagnostics on the
PSI.
CAUSE: (
Status = DA xx 00D5) No card is in the slot for the path number
configured for the link.
ACTION: Use NMMGR or the configuration file critical summary to
check the configured Physical Path for the link, and correct it if
necessary. Or, call your Hewlett-Packard support contact to install a
PSI card.
CAUSE: (
Status = E0 xx 00D5) The bus converter is not configured.
ACTION: Your local Hewlett-Packard support contact will have to check
the bus converter configuration in SYSGEN and reconfigure it, if
necessary (for Series 950 only).
CAUSE: ( Status = FA xx 00D8) The I/O subsystem still has the card
configured and marked active.
ACTION: First, try shutting down the link. If the problem continues,
restart the system. If this does not correct the problem, write down the