LAN Error Messages

Bad LINK ID.

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

Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact.

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

Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact.

Bad OPEN ID.

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

Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact.

Unable to obtain a buffer manager buffer.

The buffers are not freed.

Warmstart the system and correct the user programs.

Some other process has obtained buffers reserved for the driver.

Write down the error information displayed on the console, take a system dump, submit an SR, and call your Hewlett-Packard support contact.

Unable to obtain an I/O Services message frame.

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.

Write down the error information displayed on the console, take a system dump, submit an SR, and call your Hewlett-Packard support contact.

A call to IO_CONFIG_INT failed during driver initialization.

Unknown. Need more information.

Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact.

A call to IO_DECONFIG_INT failed during driver shutdown.

Unknown. Need more information.

Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact.

A call to IO_FLUSH_INT failed during power fail recovery.

Unknown. Need more information.

Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact.

Unable to obtain an I/O Services timer.

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

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 support contact.

Unable to release an I/O Services timer.

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

Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact.

Unable to release an I/O Services message frame.

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.

Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact.

Unable to retrieve an I/O Services message frame.

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

Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact.

Unable to send I/O Services message frame to another process.

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.

Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact.

LAN console is not supported.

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

Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact.

Unable to obtain a step data structure from driver internal resources.

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

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 support contact.

Unable to send I/O Services message frame to another process.

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.

Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact.

NIO LAN/Console card reports internal fatal hardware error.

Indicates a problem caused by bad hardware.

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

Unable to release buffer manager buffer.

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.

System dump required. Call your Hewlett-Packard support contact.

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

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.

Write down the error information displayed on the console submit an SR and call your Hewlett-Packard support contact.

Attempt to separate from the driver failed.

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

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

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

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.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

Bad Rendezvous ID.

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.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

Unable to rendezvous with the driver; the rendezvous table is full.

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

Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact.

Attempt to separate from the driver while not having previously rendezvoused with it.

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

Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact.

Bad rendezvous info length.

A bad length of rendezvous info was specified in the rendezvous request.

Write down the error information displayed on the console submit an SR and call your Hewlett-Packard support contact.

The Middle Plane is in wrong state.

The Middle Plane state machine table is corrupted.

Write down the error information displayed on the console submit an SR, take a dump and call your Hewlett-Packard support contact.

Missing inbound pool in the rendezvous request message.

The rendezvous request message does not specify inbound buffer pool.

Write down the error information displayed on the console submit an SR, and call your Hewlett-Packard support contact.

Missing rendezvous info in the rendezvous request message.

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

Write down the error information displayed on the console submit an SR and call your Hewlett-Packard support contact.

Unsupported module type in IODC.

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

Try these actions in this order:

Unsupported software model in IODC.

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

Try these actions in this order:

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

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

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

The NIO LAN/console card register test failed during LAN/console card initialization.

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

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

Unable to obtain IODC information from IO_GET_MODULE_REC during initialization.

Unknown. Need more information.

Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact.

An unknown interrupt type was received from IO_Services.

Unknown. Need more information.

Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact.

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.

The problem is caused by a link driver internal problem.

Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact.

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

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

The NIO LAN/console card detects illegal bind request.

The problem is caused by a link driver internal problem.

Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact.

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

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

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

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

Write down the error information displayed on the console, submit an SR, take a dump and call your Hewlett-Packard support contact.

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

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

The NIO LAN/console card detects bad multicast address in the configuration data.

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

Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact.

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

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

The NIO LAN/console card detects a bind request to illegal register.

The problem is caused by a link driver internal error.

Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact.

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

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

The NIO LAN/console card detects a bad Station Address in CONFIG_SA.

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

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

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

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

The NIO LAN/console card detects a bind request to already bound register.

The problem is caused by a link driver internal error.

Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact.

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

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

The NIO LAN/console card detects an unbind request to an unbound register.

The problem is caused by a link driver internal error.

Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact.

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

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

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

The problem is caused by a link driver internal error.

Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact.

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

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

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

Unknown. Need more information.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

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

Unknown. Need more information.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

The NIO LAN/console card reports that expected CCMD_LINK was not found.

Unknown. Need more information.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

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

Unknown. Need more information.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

The NIO LAN/console card detects unknown CCMD.

Unknown. Need more information.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

The NIO LAN/console card detects fatal backplane error.

Unknown. Need more information.

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

The NIO LAN/console card detects fatal bus error.

Unknown. Need more information.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

The NIO LAN/console card detects fatal error, dinmode.

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

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

The NIO LAN/console card detects parity error.

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

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

The NIO LAN/console card detects assertion of the BUS_ERROR signal.

Unknown. Need more information.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

The NIO LAN/console card detects a severe hardware error.

Unknown. Need more information.

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

The NIO LAN/console card detects a severe internal error.

Unknown. Need more information.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

The NIO LAN/console card detects a fatal error in the bus protocol.

Unknown. Need more information.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

The NIO LAN/console card reports that the selftest failed.

Unknown. Need more information.

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

The NIO/LAN console card detected an internal error.

Unknown. Need more information.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

The NIO/LAN console card detected an internal error.

Unknown. Need more information.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

The NIO/LAN console card detected an internal error.

Unknown. Need more information.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

The BDMARS transferred less DMA data than the host CCMD_IN or CCMD_OUT count requested.

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.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

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

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.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

The NIO LAN/console card reported unknown advisory error.

Unknown. Need more information.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

The NIO LAN/console card reported unknown apstat error.

Unknown. Need more information.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

The NIO LAN/console card reported unknown fatal error.

Unknown. Need more information.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

The NIO LAN/console card detects unknown CCMD.

Unknown. Need more information.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

The NIO LAN/console card reports unknown hard error.

Unknown. Need more information.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

The NIO LAN/console card detects unknown I/O command.

Unknown. Need more information.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

The NIO LAN/console card reports unknown soft error.

Unknown. Need more information.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

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

The problem is caused by a bad packet.

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

Dump request received when driver is dumping.

Unknown. Need more information.

Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact.

Message received in invalid state.

The link driver received an unexpected message.

Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact.

Driver detected unsupported command in received SDI or WAN control message.

Unknown. Need more information.

Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact.

Unknown driver problem.

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

Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact.

Unknown dump manager port number.

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

Run NMMAINT to verify that the dump module is present.

Unable to obtain an I/O Services timer for a dump process.

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

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 support contact.

Unable to send dump request message to dump manager.

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

Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact.

Unexpected timer event message.

Unknown. Need more information.

Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact.

Unimplemented message received.

The message descriptor is not known to the driver.

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

Nil configuration pointer.

A user passed a nil configuration pointer to the driver.

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

Trace manager overrun.

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

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.

Type 2 connection attempt failed.

The remote system did not respond to a SABME with a UA.

Check that the remote is activated, and make sure the local and remote MAC addresses, and SAPs are correctly configured.

Type 2 error during reset or disconnect.

The remote system did not respond to a SABME or DISC with a UA.

Disregard if the connection is working properly, and no other errors occurred. If the connection will not function or other errors have occurred, write down the error information and contact your Hewlett-Packard support contact.

Type 2 connection disconnected.

The remote system transmitted a DISC, causing the Type 2 connection to be dropped.

Disregard if the connection is working properly, and no other errors occurred. If the connection will not function or other errors have occurred, write down the error information and contact your Hewlett-Packard support contact.

Type 2 error during reset or disconnect.

The remote system did not respond to a SABME or DISC with a UA.

Disregard if the connection is working properly, and no other errors occurred. If the connection will not function or other errors have occurred, write down the error information and contact your Hewlett-Packard support contact.

Type 2 connection unexpectedly reset.

A Type 2 protocol error occurred resulting in an FRMR being transmitted or received.

Disregard if the connection is working properly, and no other errors occurred. If the connection will not function or other errors have occurred, write down the error information and contact your Hewlett-Packard support contact.

Type 2 connection unexpectedly reset.

A Type 2 protocol error probably occurred, resulting in a SABME being transmitted or received.

Disregard if the connection is working properly, and no other errors occurred. If the connection will not function or other errors have occurred, write down the error information and contact your Hewlett-Packard support contact.

Type 2 connection unexpectedly reset.

A Type 2 protocol error probably occurred resulting in a SABME being transmitted or received.

Disregard if the connection is working properly, and no other errors occurred. If the connection will not function or other errors have occurred, write down the error information and contact your Hewlett-Packard support contact.

Type 2 Rendezvous ID invalid.

A transport tried to established a connection on a SAP which had not rendezvoused with the driver.

Write down the error information and contact your Hewlett-Packard support contact.

Type 2 connection already exists.

Two transports are configured to use the same MAC addresses and SAPs.

Correct the NMMGR configurations and restart the driver.

Type 2 connection not available.

The driver has reached the maximum number of supported connections.

Shut down some connections to free up resources.

Type 2 Connection ID invalid.

A transport tried to send a message to the driver with an invalid connection identifier.

Write down the error information and contact your Hewlett-Packard support contact.

Type 2 non-fatal protocol error.

An unexpected packet format was received.

Disregard if the connection is working properly, and no other errors occurred. If the connection will not function or other errors have occurred, write down the error information and contact your Hewlett-Packard support contact.

Type 2 non-fatal protocol error.

An unexpected packet format was received.

Disregard if the connection is working properly, and no other errors occurred. If the connection will not function or other errors have occurred, write down the error information and contact your Hewlett-Packard support contact.

Type 2 non-fatal software error.

A non-fatal Type 2 driver software error occurred.

Disregard if the connection is working properly, and no other errors occurred. If the connection will not function or other errors have occurred, write down the error information and contact your Hewlett-Packard support contact.

Type 2 non-fatal protocol error.

An unexpected packet format was received.

Disregard if the connection is working properly, and no other errors occurred. If the connection will not function or other errors have occurred, write down the error information and contact your Hewlett-Packard support contact.

Type 2 non-fatal software error.

A non-fatal Type 2 driver software error occurred.

Disregard if the connection is working properly, and no other errors occurred. If the connection will not function or other errors have occurred, write down the error information and contact your Hewlett-Packard support contact.

Unable to send I/O Services message frame LINKNAME

A call to a system message send routine returned in error.

Write down the error information displayed on the console, submit an SR and call your Hewlett-Packard support contact.

Unable to obtain a buffer manager buffer LINKNAME

Some other process has obtained buffers reserved for the driver.

Write down the error information displayed on the console, take a system dump, submit an SR and call your Hewlett-Packard support contact.

Unable to obtain a system timer LINKNAME

A call to obtain a timer resource returned an error.

Take a system dump and call your Hewlett-Packard support contact.

Unable to release a system timer LINKNAME

The driver tried to free a timer that was not recognized by the system as a valid timer.

Take a system dump and call your Hewlett-Packard support contact.

Type 2 non-fatal software error.

A non-fatal Type 2 driver software error occurred.

Disregard if the connection is working properly, and no other errors occurred. If the connection will not function or other errors have occurred, write down the error information and contact your Hewlett-Packard support contact.

Type 2 non-fatal protocol error.

An unexpected packet format was received.

Disregard if the connection is working properly, and no other errors occurred. If the connection will not function or other errors have occurred, write down the error information and contact your Hewlett-Packard support contact.

Type 2 non-fatal protocol error.

An unexpected packet format was received.

Disregard if the connection is working properly, and no other errors occurred. If the connection will not function or other errors have occurred, write down the error information and contact your Hewlett-Packard support contact.

Type 2 non-fatal software error.

A non-fatal Type 2 driver software error occurred.

Disregard if the connection is working properly, and no other errors occurred. If the connection will not function or other errors have occurred, write down the error information and contact your Hewlett-Packard support contact.

Type 2 non-fatal protocol error.

An unexpected packet format was received.

Disregard if the connection is working properly, and no other errors occurred. If the connection will not function or other errors have occurred, write down the error information and contact your Hewlett-Packard support contact.

Could not read the link name from the LSS link table.

The link table does not exist.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

Could not add the link name to the LSS link table.

The link table does not exist.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

Could not delete the link name from the LSS link table.

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

Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard support contact.

Could not read multicast addresses table.

The multicast addresses table does not exist.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

Could not open NMCONFIG.PUB.SYS file.

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

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.

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

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

Link data not found in NMCONFIG.PUB.SYS.

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

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

The link data record is incorrect for this driver.

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

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

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

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

A call to IO_GET_MGR_ENTRY failed during driver configuration.

Unknown. Need more information.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

A call to IO_CONFIG failed during driver configuration.

Wrong physical path is configured for the installed LAN card.

Use NMMGR to correct the Physical Path for the link.

The card for the configured path is bad.

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

A call to IO_UNCONFIG failed during driver deconfiguration.

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

Write down the error information displayed on the console, submit an SR, take a system dump, and call your Hewlett-Packard support contact.

The LAN card is used by another link.

The card was configured by another link.

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

Could not create driver buffer pool.

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

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

Could not delete the driver buffer pool.

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

Write down the error information displayed on the console submit an SR, take a system dump, and call your Hewlett-Packard support contact.

Could not open trace file.

The indicated trace file might be opened with exclusive access.

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

Could not stop trace.

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

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 support contact.

Could not start trace.

Unknown. Need more information.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

Could not get Write Initiator label.

Unknown. Need more information.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

Could not release Write Initiator label.

Unknown. Need more information.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

Could not open NMLGxxxx.PUB.SYS file.

The indicated log file may be opened with exclusive access.

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

The driver subsystem is not configured in logging configuration.

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

Could not close the NMLGxxxx.PUB.SYS file.

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

Write down the error information displayed on the console, submit an SR, take a system dump and call your Hewlett-Packard support contact.

Could not freeze the configuration record in memory.

Memory shortage problems are occurring.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

Could not unfreeze the configuration record in memory.

Memory problems are occurring.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

Could not send config request message.

An internal system ports problem has occurred.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

Could not receive config reply message.

An internal system ports problem has occurred.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

Timeout waiting for the config reply message.

The link software or the card could not be configured.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

Driver's PDA is corrupted.

Unknown. Need more information.

Write down the error information displayed on the console, submit an SR, take a dump and call your Hewlett-Packard support contact.

Configuration of the dump manager failed.

Unknown. Need more information.

Write down the error information displayed on the console and call your Hewlett-Packard support contact.

The link type is not LAN.

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

Use NMMGR to correct the link name type.

The link driver failed to start.

Incorrect physical path was specified in the NMCONFIG file.

Correct the physical path in the NMCONFIG file using NMMGR.

Token Ring adapter detected a network error on LINKNAME

The Token Ring adapter detected an error.

Write down the Cause Status and call your Hewlett-Packard support contact.

Token Ring adapter detected signal loss on LINKNAME

This station has detected a loss of signal on the ring.

Verify that this station is properly attached to the network. Check network components (adapters, cables, MSAUs, etc.). Have your network provider examine the network.

Token Ring adapter detected a hard error on LINKNAME

A station has stopped receiving data and is transmitting beacon frames.

If this error persists, check network components (adapters, cables, MSAUs, etc.). Have your network provider examine the network.

Token Ring adapter detected a soft error on LINKNAME

This station has detected an error and notified the Ring Error Monitor.

If this error persists, query your Ring Error Monitor to determine the type of error. Check network components (adapters, cables, MSAUs, etc.). Have your network provider examine the network.

Token Ring adapter beaconing on LINKNAME

This station has stopped receiving data.

If this error persists, then verify that all stations are configured to the proper data rate. Check network components (adapters, cables, MSAUs, etc.). Have your network provider examine the network.

Token Ring adapter detected lobe cable fault on LINKNAME

An open or short circuit was detected in the lobe cable.

Verify that this station is properly attached to the network. Check network components (adapters, cables, MSAUs, etc.). Have your network provider examine the network.

Token Ring adapter auto-removed from network on LINKNAME

This station detected an error.

Verify that this station is properly attached to the network. Verify that all stations are configured to the proper data rate. Check this station's station address. Check network components (adapters, cables, MSAUs, etc.). Have your network provider examine the network.

Token Ring adapter removed from network on LINKNAME

The Network Manager has requested that this station be removed from the network.

Verify that this station is properly configured. Query your Network Manager to determine why this station was removed. Check network components (adapters, cables, MSAUs, etc.). Have your network provider examine the network.

Token Ring adapter detected no other stations on LINKNAME

This is the only station on the network.

Verify that any other stations are properly attached to the network. Check network components (adapters, cables, MSAUs, etc.). Have your network provider examine the network.

Token Ring adapter detected Claim Token Frame on LINKNAME

The network is attempting to recover from a failure.

If this warning persists, check network components (adapters, cables, MSAUs, etc.). Have your network provider examine the network.

Token Ring adapter detected duplicate address on LINKNAME

Two stations on the network are configured with the same station address.

Locate the improperly configured station and configure a unique station address, or use the default address.

Token Ring adapter detected beacon on LINKNAME

A station on the network is not receiving data properly.

If this error persists, verify that all stations are properly attached to the network. Verify that all stations are configured to the proper data rate. Check network components (adapters, cables, MSAUs, etc.). Have your network provider examine the network.

Token Ring adapter detected network failure on LINKNAME

More information is needed to isolate this failure.

Check network components (adapters, cables, MSAUs, etc.). Have your network provider examine the network.

Token Ring adapter jumper set improperly on LINKNAME

The data rate jumper on the token ring adapter is not set properly.

Have your Hewlett-Packard representative set the data rate jumper correctly.