HPlogo NS 3000/iX Error Messages Reference Manual > Chapter 15 LAN, LAN/Console, Token Ring LAN Error Messages

Chapter 15 LAN, LAN/Console, Token Ring LAN Error Messages

MPE documents

Complete PDF
Table of Contents
Index

Messages generated by the LAN, LAN/console, Token Ring LAN are the following type:

Internal driver error in SYSLINK (LANWARN ###) or (LANERR ###) where ### is an error number.

MESSAGE: Bad LINK ID.
Level: 2

CAUSE: An invalid LINK ID was passed to the link driver's write initiator.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.

CAUSE: An invalid LINK ID was specified in the rendezvous request message.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.


MESSAGE: Bad OPEN ID.
Level: 3

CAUSE: An invalid OPEN ID was specified in the rendezvous request message.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.


MESSAGE: Unable to obtain a buffer manager buffer.
Level: 5

CAUSE: The buffers are not freed.

ACTION: Warmstart the system and correct the user programs.

CAUSE: Some other process has obtained buffers reserved for the driver.

ACTION: Write down the error information displayed on the console, take a system dump, submit an CR, and call your Hewlett-Packard representative.


MESSAGE: Unable to obtain an I/O Services message frame.
Level: 6

CAUSE: The driver could not obtain a message frame from a user port for newly arrived LAN packet (or from CAM's port, in the case of a CIO card) for a new DMA request to the card.

ACTION: Write down the error information displayed on the console, take a system dump, submit an CR, and call your Hewlett-Packard representative.


MESSAGE: A call to IO_CONFIG_INT failed during driver initialization.
Level: 7

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.


MESSAGE: A call to IO_DECONFIG_INT failed during driver shutdown.
Level: 8

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.


MESSAGE: A call to IO_FLUSH_INT failed during power fail recovery.
Level: 9

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.


MESSAGE: Unable to obtain an I/O Services timer.
Level: 10

CAUSE: A call to obtain a timer resource returned an error. Too many timers may be in use.

ACTION: If you suspect your system might be low on timer resources because of heavy loading, try restarting the link later. If repeated attempts fail, try warmstarting your system. If the problem persists, a system dump will be required. Call your Hewlett-Packard representative.


MESSAGE: Unable to release an I/O Services timer.
Level: 11

CAUSE: The driver tried to free a timer that was not recognized by the system as valid. Memory data corruption may have occurred.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.


MESSAGE: Unable to release an I/O Services message frame.
Level: 12

CAUSE: A call to the system message freeing routine returned an error. The port may belong to a process that no longer exists or is not operating with the required capabilities. Also, the message frame may not have been recognized by the system as a valid message frame.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.


MESSAGE: Unable to retrieve an I/O Services message frame.
Level: 13

CAUSE: A call to the system message retrieve routine returned an error.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.


MESSAGE: Unable to send I/O Services message frame to another process.
Level: 14

CAUSE: A call to a system message SEND routine returned an error. The destination port may belong to a process that no longer exists or is not operating with required capabilities.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.


MESSAGE: LAN console is not supported.
Level: 16

CAUSE: The console DM tries to bind with a driver as a LAN Console DM.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.


MESSAGE: Unable to obtain a step data structure from driver internal resources.
Level: 17

CAUSE: All steps are in use and wait for DMA completion. The driver may be low on steps because of heavy LAN traffic.

ACTION: Ignore this problem unless other problems are occurring. If you are experiencing other problems, write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: Unable to send I/O Services message frame to another process.
Level: 18

CAUSE: A call to a system message send routine returned in error. The destination port may belong to a process that no longer exists or is not operating with required capabilities.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.


MESSAGE: NIO LAN/Console card reports internal fatal hardware error.
Level: 19

CAUSE: Indicates a problem caused by bad hardware.

ACTION: Your Hewlett-Packard representative must run diagnostics on the LAN/console card.


MESSAGE: Unable to release buffer manager buffer.
Level: 20

CAUSE: The driver tried to free memory that the buffer manager did not recognize as a valid buffer because of a driver problem or memory data corruption. Also, the driver may have tried to free a buffer that is already freed.

ACTION: System dump required. Call your Hewlett-Packard representative.


MESSAGE: Attempt to rendezvous with a link driver with SAP or SAP+XSAP or Ethernet Type already being used.
Level: 32

CAUSE: The user is trying to rendezvous twice with a link driver or two different users are using the same SAP, SAP+XSAP or Ethernet Type.

ACTION: Write down the error information displayed on the console submit an CR and call your Hewlett-Packard representative.


MESSAGE: Attempt to separate from the driver failed.
Level: 33

CAUSE: An attempt was made to separate from the driver using console Link ID.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: Attempt to rendezvous with the driver or separate from the driver when the Middle Plane is in CLOSED state.
Level: 34

CAUSE: The driver shuts itself down because of a fatal hardware error or driver internal error and the user tries to rendezvous with the driver or separate from it.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: Bad Rendezvous ID.
Level: 36

CAUSE: An attempt was made to use a bad rendezvous ID in a process of separating from the driver or changing its inbound buffer pool. This may be caused by data corruption.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: Unable to rendezvous with the driver; the rendezvous table is full.
Level: 37

CAUSE: An attempt to rendezvous with the driver failed due to running out of free entries in the rendezvous table.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: Attempt to separate from the driver while not having previously rendezvoused with it.
Level: 38

CAUSE: An attempt is made to separate twice from the link driver.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: Bad rendezvous info length.
Level: 39

CAUSE: Write down the error information displayed on the console submit an CR and call your Hewlett-Packard representative.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: The Middle Plane is in wrong state.
Level: 40

CAUSE: The Middle Plane state machine table is corrupted.

ACTION: Write down the error information displayed on the console submit an CR, take a dump and call your Hewlett-Packard representative.


MESSAGE: Missing inbound pool in the rendezvous request message.
Level: 41

CAUSE: The rendezvous request message does not specify inbound buffer pool.

ACTION: Write down the error information displayed on the console submit an CR, and call your Hewlett-Packard representative.


MESSAGE: Missing rendezvous info in the rendezvous request message.
Level: 42

CAUSE: The rendezvous request message does not have a pointer to the rendezvous information buffer.

ACTION: Write down the error information displayed on the console submit an CR and call your Hewlett-Packard representative.


MESSAGE: Unsupported module type in IODC.
Level: 48

CAUSE: The problem is caused by bad NIO LAN hardware, the wrong path number, or the wrong type of card.

ACTION: Try these actions in this order:
  1. Verify that the configured physical path is correct by using NMMGR.

  2. Verify that the card is a NIO LAN/console card.

  3. If you have tried both of the actions above and are still experiencing difficulties, your Hewlett-Packard representative must run diagnostics on the LAN/console card.



MESSAGE: Unsupported software model in IODC.
Level: 49

CAUSE: The problem is caused by bad NIO LAN hardware, the wrong path number, or the wrong type of card.

ACTION: Try these actions in this order:
  1. Verify that the configured physical path is correct by using NMMGR.

  2. Verify that the card is a NIO LAN/console card.

  3. If you have tried both of the actions above and are still experiencing difficulties, your Hewlett-Packard representative must run diagnostics on the LAN/console card.



MESSAGE: The NIO LAN/console card did not return to a ready state after a reset was issued.
Level: 50

CAUSE: The problem is caused by bad NIO LAN/console hardware.

ACTION: Your Hewlett-Packard representative must run diagnostics on the LAN/console card.


MESSAGE: The NIO LAN/console card register test failed during LAN/console card initialization.
Level: 52

CAUSE: The problem is caused by bad NIO LAN/console hardware.

ACTION: Your Hewlett-Packard representative must run diagnostics on the LAN/console card.


MESSAGE: Unable to obtain IODC information from IO_GET_MODULE_REC during initialization.
Level: 53

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.


MESSAGE: An unknown interrupt type was received from IO_Services.
Level: 55

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.


MESSAGE: The NIO LAN/console card detects that bind request for a given 802.2 SAP or 802.2 SAP + XSAP or ETHERNET Type is already bound.
Level: 57

CAUSE: The problem is caused by a link driver internal problem.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.

CAUSE: The problem is caused by a bad NIO LAN/console backplane.

ACTION: Your Hewlett-Packard representative must run diagnostics on the LAN/console card.


MESSAGE: The NIO LAN/console card detects illegal bind request.
Level: 58

CAUSE: The problem is caused by a link driver internal problem.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.

CAUSE: The problem is caused by a bad NIO LAN/console backplane.

ACTION: Your Hewlett-Packard representative must run diagnostics on the LAN/console card.


MESSAGE: The NIO LAN/console card detects illegal bind request.
Level: 58

CAUSE: The problem is caused by a link driver internal problem.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.

CAUSE: The problem is caused by a bad NIO LAN/console backplane.

ACTION: Your Hewlett-Packard representative must run diagnostics on the LAN/console card.


MESSAGE: The NIO LAN/console card detects a bad length of the configuration data buffer.
Level: 59

CAUSE: The problem is caused by data corruption in the configuration quad.

ACTION: Write down the error information displayed on the console, submit an CR, take a dump and call your Hewlett-Packard representative.

CAUSE: The problem is caused by a bad NIO LAN/console backplane.

ACTION: Your Hewlett-Packard representative must run diagnostics on the LAN/console card.


MESSAGE: The NIO LAN/console card detects bad multicast address in the configuration data.
Level: 60

CAUSE: A bad multicast address was entered into the Multicast Address Table.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.

CAUSE: The problem is caused by a bad NIO LAN/console backplane.

ACTION: Your Hewlett-Packard representative must run diagnostics on the LAN/console card.


MESSAGE: The NIO LAN/console card detects a bind request to illegal register.
Level: 61

CAUSE: The problem is caused by a link driver internal error.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.

CAUSE: The problem is caused by a bad NIO LAN/console backplane.

ACTION: Your Hewlett-Packard representative must run diagnostics on the LAN/console card.


MESSAGE: The NIO LAN/console card detects a bad Station Address in CONFIG_SA.
Level: 62

CAUSE: The problem is caused by configuring the wrong Station Address in NMMGR.

ACTION: Use NMMGR to verify that the configured Station Address is correct.

CAUSE: The problem is caused by a bad NIO LAN/console backplane.

ACTION: Your Hewlett-Packard representative must run diagnostics on the LAN/console card.


MESSAGE: The NIO LAN/console card detects a bind request to already bound register.
Level: 63

CAUSE: The problem is caused by a link driver internal error.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.

CAUSE: The problem is caused by a bad NIO LAN/console backplane.

ACTION: Your Hewlett-Packard representative must run diagnostics on the LAN/console card.


MESSAGE: The NIO LAN/console card detects an unbind request to an unbound register.
Level: 64

CAUSE: The problem is caused by a link driver internal error.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.

CAUSE: The problem is caused by a bad NIO LAN/console backplane.

ACTION: Your Hewlett-Packard representative must run diagnostics on the LAN/console card.


MESSAGE: The NIO LAN/console card detects too many multicast addresses in the configuration buffer.
Level: 65

CAUSE: The problem is caused by a link driver internal error.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.

CAUSE: The problem is caused by a bad NIO LAN/console backplane.

ACTION: Your Hewlett-Packard representative must run diagnostics on the LAN/console card.


MESSAGE: The NIO LAN/console card reports that expected CCMD_IN or CCMD_OUT was not found.
Level: 66

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: The NIO LAN/console card reports that CCMD_OUT was sent to an inbound only register set.
Level: 67

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: The NIO LAN/console card reports that expected CCMD_LINK was not found.
Level: 68

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: The NIO LAN/console card reports that CCMD_IN was sent to an outbound only register set.
Level: 69

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: The NIO LAN/console card detects unknown CCMD.
Level: 70

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: The NIO LAN/console card detects fatal backplane error.
Level: 71

CAUSE: Unknown. Need more information.

ACTION: Your Hewlett-Packard representative must run diagnostics on the LAN/console card.


MESSAGE: The NIO LAN/console card detects fatal bus error.
Level: 72

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: The NIO LAN/console card detects fatal error, dinmode.
Level: 73

CAUSE: The problem is caused by bad NIO LAN/console hardware.

ACTION: Your Hewlett-Packard representative must run diagnostics on the LAN/console card.


MESSAGE: The NIO LAN/console card detects parity error.
Level: 74

CAUSE: The problem is caused by bad NIO LAN/console hardware.

ACTION: Your Hewlett-Packard representative must run diagnostics on the LAN/console card.


MESSAGE: The NIO LAN/console card detects assertion of the BUS_ERROR signal.
Level: 75

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: The NIO LAN/console card detects a severe hardware error.
Level: 76

CAUSE: Unknown. Need more information.

ACTION: Your Hewlett-Packard representative must run diagnostics on the LAN/console card.


MESSAGE: The NIO LAN/console card detects a severe internal error.
Level: 77

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: The NIO LAN/console card detects a fatal error in the bus protocol.
Level: 78

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: The NIO LAN/console card reports that the selftest failed.
Level: 79

CAUSE: Unknown. Need more information.

ACTION: Your Hewlett-Packard representative must run diagnostics on the LAN/console card.


MESSAGE: The NIO/LAN console card detected an internal error.
Level: 80

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: The NIO/LAN console card detected an internal error.
Level: 81

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: The NIO/LAN console card detected an internal error.
Level: 82

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: The BDMARS transferred less DMA data than the host CCMD_IN or CCMD_OUT count requested.
Level: 83

CAUSE: The NIO LAN/console card did not have enough data bytes to completely fill the inbound buffer. Or the NIO/LAN console card did not accept all the data that the host tried to send; for example, the number of bytes were bigger than maximum LAN packet size.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: The BDMARS expected more DMA data to be transferred than the host CCMD_IN or CCMD_OUT count requested.
Level: 84

CAUSE: The NIO LAN/console card was prepared to send more data bytes to the host, but the host did not provide enough buffers. Or the LAN/console card expected more data than the host provided.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: The NIO LAN/console card reported unknown advisory error.
Level: 85

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: The NIO LAN/console card reported unknown apstat error.
Level: 86

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: The NIO LAN/console card reported unknown fatal error.
Level: 87

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: The NIO LAN/console card detects unknown CCMD.
Level: 88

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: The NIO LAN/console card reports unknown hard error.
Level: 89

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: The NIO LAN/console card reports unknown soft error.
Level: 90

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: The NIO LAN/console card detects unknown I/O command.
Level: 91

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: The CIO bottom plane is unable to obtain buffer manager buffer.
Level: 112

CAUSE: Buffers have not been freed or some other process has obtained buffers reserved for the driver.

ACTION: Warmstart the system and correct the user programs. If you are still experiencing problems, write down the error information displayed on the console, take a system dump, submit an CR, and call your Hewlett-Packard representative.


MESSAGE: The CIO bottom plane detects unknown reply message from buffer manager.
Level: 114

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: The bind request to CAM failed.
Level: 115

CAUSE: The driver is already bound to CAM.

ACTION: Write down the error information displayed on the console, take a system dump, submit an CR, and call your Hewlett-Packard representative.

CAUSE: The value of CIO_META_TAG was not specified in the bind request message.

ACTION: Write down the error information displayed on the console, take a system dump, submit an CR, and call your Hewlett-Packard representative.

CAUSE: The hardware address in the bind request was invalid.

ACTION: Write down the error information displayed on the console, take a system dump, submit an CR, and call your Hewlett-Packard representative.


MESSAGE: The CIO LAN card selftest failed.
Level: 116

CAUSE: The problem is caused by bad CIO LAN hardware.

ACTION: Your Hewlett-Packard representative must run diagnostics on the CIO LAN card.


MESSAGE: The CIO LAN card detects a fatal backplane error.
Level: 117

CAUSE: Unknown. Need more information.

ACTION: Your Hewlett-Packard representative must run diagnostics on the CIO LAN card.


MESSAGE: The Identity Request to the CIO LAN card failed.
Level: 118

CAUSE: Unknown. Need more information.

ACTION: Your Hewlett-Packard representative must run diagnostics on the CIO LAN card.


MESSAGE: The CIO LAN card reports an invalid hardware ID.
Level: 119

CAUSE: The problem is caused by bad CIO LAN hardware, the wrong path number, or the wrong type of card.

ACTION: Try these actions in this order:
  1. Verify that the configured physical path is correct by using NMMGR.

  2. Verify that the card is a NIO/LAN console card.

  3. If you have verified that the physical path and card type are correct and are still experiencing problems, your Hewlett-Packard representative must run diagnostics on the LAN/console card.



MESSAGE: The Status Request to the CIO LAN card failed.
Level: 120

CAUSE: Unknown. Need more information.

ACTION: Your Hewlett-Packard representative must run diagnostics on the CIO LAN card.


MESSAGE: The CIO LAN card can not sense MAU heartbeat.
Level: 122

CAUSE: The MAU is disconnected or bad.

ACTION: Check your cables and if this error still appears, your Hewlett-Packard representative must run diagnostics on the CIO LAN card.


MESSAGE: The unbind request to the CAM failed.
Level: 123

CAUSE: The driver is not bound to the CAM.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.

CAUSE: The driver still has outstanding requests to the CAM.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.


MESSAGE: The driver detects unknown option in the 802.2 control field of a test or xid packet.
Level: 125

CAUSE: The problem is caused by a bad packet.

ACTION: If this error appears repeatedly, write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: The CIO LAN configuration request failed.
Level: 128

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.


MESSAGE: The CIO LAN statistics request failed.
Level: 129

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console, submit an CR and call your Hewlett-Packard representative.


MESSAGE: The CIO LAN reset statistics request failed.
Level: 130

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console, submit an CR and call your Hewlett-Packard representative.


MESSAGE: The CIO LAN card reports Dead-or-Dying ARQ status.
Level: 131

CAUSE: The problem is caused by bad CIO LAN card hardware.

ACTION: Your Hewlett-Packard representative must run diagnostics on the CIO LAN card.


MESSAGE: The CIO LAN card reports Protocol Error ARQ.
Level: 132

CAUSE: Violation of the CIO LAN card backplane protocol.

ACTION: Your Hewlett-Packard representative must run diagnostics on the CIO LAN card.


MESSAGE: The CIO bottom plane received invalid request at a given state.
Level: 133

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.


MESSAGE: The CIO LAN card hard reset request failed.
Level: 135

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.


MESSAGE: Dump request received when driver is dumping.
Level: 144

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.


MESSAGE: Message received in invalid state.
Level: 145

CAUSE: The link driver received an unexpected message.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.


MESSAGE: Driver detected unsupported command in received SDI or WAN control message.
Level: 146

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.


MESSAGE: Unknown driver problem.
Level: 147

CAUSE: The driver detected an error, but did not say what type of error was found.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.


MESSAGE: Unknown dump manager port number.
Level: 148

CAUSE: The driver detects unrecoverable error and tries to dump its PDA and the NIO LAN/console card but the dump module is missing.

ACTION: Run NMMAINT to verify that the dump module is present.


MESSAGE: Unable to obtain an I/O Services timer for a dump process.
Level: 149

CAUSE: A call to obtain a timer resource returned an error. Too many timers may be in use.

ACTION: If you suspect your system might be low on timer resources be cause of heavy loading, try restarting the link later. If repeated attempts fail, try warmstarting your system. If the problem persists, a system dump will be required. Call your Hewlett-Packard representative.


MESSAGE: Unable to send dump request message to dump manager.
Level: 150

CAUSE: A call to a system message SEND routine returned in error. The dump manager port is not operating with required capabilities.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.


MESSAGE: Unexpected timer event message.
Level: 151

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.


MESSAGE: Unimplemented message received.
Level: 152

CAUSE: The message descriptor is not known to the driver.

ACTION: Call your Hewlett-Packard representative and explain what you are trying to do.


MESSAGE: Nil configuration pointer.
Level: 160

CAUSE: A user passed a nil configuration pointer to the driver.

ACTION: Call your Hewlett-Packard representative and explain what you are trying to do.


MESSAGE: Trace manager overrun.
Level: 161

CAUSE: The driver is generating trace entries faster than the trace manager can process them. This causes some trace entries to be lost.

ACTION: This is only a warning and is indicative of a very busy system. If not debugging a problem, then tracing should be turned off. This will improve system performance in general. If a problem is being looked at, use partial tracing whenever possible (when full data frames are not needed) to ensure that no trace data is lost.


MESSAGE: Could not read the link name from the LSS link table.
Level: 224

CAUSE: The link table does not exist.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: Could not add the link name to the LSS link table.
Level: 225

CAUSE: The link table does not exist.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: Could not delete the link name from the LSS link table.
Level: 226

CAUSE: The link name specified the LAN_KILL_MODULE call is not in the LSS link table.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.


MESSAGE: Could not read multicast addresses table.
Level: 227

CAUSE: The multicast addresses table does not exist.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: Could not open NMCONFIG.PUB.SYS file.
Level: 228

CAUSE: The configuration file NMCONFIG.PUB.SYS was purged or renamed or the NMCONFIG.PUB.SYS configuration file may be opened with exclusive access.

ACTION: Type a LISTF NMCONFIG.PUB.SYS to determine if the file has been opened with exclusive access. If it has, wait for the program or process that has this file opened exclusively to close it. If the configuration file is missing, restore the file from a backup tape and restart the link again.

CAUSE: The configuration file NMCONFIG.PUB.SYS may be opened with exclusive access.

ACTION: Wait for the program or process that has this file opened exclusively to close it.


MESSAGE: Link data not found in NMCONFIG.PUB.SYS.
Level: 229

CAUSE: The link data is not found in the configuration file NMCONFIG.PUB.SYS.

ACTION: Use NMMGR to create the link data for the link you are trying to start. Try to start the link again.


MESSAGE: The link data record is incorrect for this driver.
Level: 230

CAUSE: The link data record is corrupted in the configuration file NMCONFIG.PUB.SYS.

ACTION: Restore the file from a backup tape and restart the link again.

CAUSE: The configuration file NMCONFIG.PUB.SYS was not converted to a version supported by the driver.

ACTION: Run NMMGRVER on the configuration file NMCONFIG.PUB.SYS.


MESSAGE: A call to IO_GET_MGR_ENTRY failed during driver configuration.
Level: 233

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: A call to IO_CONFIG failed during driver configuration.
Level: 234

CAUSE: Wrong physical path is configured for the installed LAN card.

ACTION: Use NMMGR to correct the Physical Path for the link.

CAUSE: The card for the configured path is bad.

ACTION: To determine whether the LAN card is good your Hewlett-Packard representative must run diagnostics on the LAN card.


MESSAGE: A call to IO_UNCONFIG failed during driver deconfiguration.
Level: 235

CAUSE: Wrong physical path was specified in IO_UNCONFIG call due to configuration data corruption in the driver PDA.

ACTION: Write down the error information displayed on the console, submit an CR, take a system dump, and call your Hewlett-Packard representative.


MESSAGE: The LAN card is used by another link.
Level: 236

CAUSE: The card was configured by another link.

ACTION: Use NMMGR to correct the Physical Path for this link or change the link name to point to a different LAN card.


MESSAGE: Could not create inbound buffer pool for the CIO LAN card.
Level: 237

CAUSE: The buffer manager cannot allocate a new logical buffer pool entry or cannot allocate virtual memory for the buffers.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: Could not delete the CIO LAN card inbound buffer pool.
Level: 238

CAUSE: Wrong pool ID was specified in the call to delete inbound buffer pool due to configuration data corruption in the driver's PDA.

ACTION: Write down the error information displayed on the console submit an CR, take a system dump, and call your Hewlett-Packard representative.


MESSAGE: Could not open trace file.
Level: 239

CAUSE: The indicated trace file might be opened with exclusive access.

ACTION: Wait for the program or process that has the trace file opened exclusively to close it.


MESSAGE: Could not stop trace.
Level: 240

CAUSE: Tracing might have been turned off with LINKCONTROL TRACEOFF command, but the link software information indicates that it was on.

ACTION: Ignore this problem unless you are experiencing other problems. If you are experiencing other problems, write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: Could not start trace.
Level: 241

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: Could not get Write Initiator label.
Level: 242

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: Could not release Write Initiator label.
Level: 243

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: Could not open NML Gxxxx.PUB.SYS file.
Level: 244

CAUSE: The indicated log file may be opened with exclusive access.

ACTION: Wait for the program or process that has the log file opened exclusively to close it.

CAUSE: The driver subsystem is not configured in logging configuration.

ACTION: Use NMMGR to check logging configuration for subsystem 25 or write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: Could not close the NMLGxxxx.PUB.SYS file.
Level: 245

CAUSE: Invalid LOG ID due to configuration data corruption in the driver's PDA.

ACTION: Write down the error information displayed on the console, submit an CR, take a system dump and call your Hewlett-Packard representative.


MESSAGE: Could not freeze the configuration record in memory.
Level: 246

CAUSE: Memory shortage problems are occurring.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: Could not unfreeze the configuration record in memory.
Level: 247

CAUSE: Memory problems are occurring.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: Could not send config request message.
Level: 248

CAUSE: An internal system ports problem has occurred.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: Could not receive config reply message.
Level: 249

CAUSE: An internal system ports problem has occurred.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: Timeout waiting for the config reply message.
Level: 250

CAUSE: The link software or the card could not be configured.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: Driver's PDA is corrupted.
Level: 251

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console, submit an CR, take a dump and call your Hewlett-Packard representative.


MESSAGE: Configuration of the dump manager failed.
Level: 252

CAUSE: Unknown. Need more information.

ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.


MESSAGE: The link type is not LAN.
Level: 253

CAUSE: The link name type in NMCONFIG.PUB.SYS is not set to LAN.

ACTION: Use NMMGR to correct the link name type.


MESSAGE: The link driver failed to start.
Level: 253

CAUSE: Incorrect physical path was specified in the NMCONFIG file.

ACTION: Correct the physical path in the NMCONFIG file using NMMGR.




Chapter 14 VALERR and VALWARN Messages


Chapter 16 100VG-AnyLAN and HP-PB 100Base-T Error Messages