LAN Error Messages

MPE documents

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

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

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

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

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

CAUSE: Unknown. Need more information.

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

CAUSE: Unknown. Need more information.

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

CAUSE: Unknown. Need more information.

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

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

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

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

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

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

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

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

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

CAUSE: Indicates a problem caused by bad hardware.

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

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

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

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

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

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

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, submit an CR, and call your Hewlett-Packard support contact.

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

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

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

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

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

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

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

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.

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.

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

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

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

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

CAUSE: Unknown. Need more information.

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

CAUSE: Unknown. Need more information.

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

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

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.

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

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.

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

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.

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

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.

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

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.

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.

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

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.

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

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.

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

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.

CAUSE: Unknown. Need more information.

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

CAUSE: Unknown. Need more information.

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

CAUSE: Unknown. Need more information.

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

CAUSE: Unknown. Need more information.

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

CAUSE: Unknown. Need more information.

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

CAUSE: Unknown. Need more information.

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

CAUSE: Unknown. Need more information.

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

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

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

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

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

CAUSE: Unknown. Need more information.

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

CAUSE: Unknown. Need more information.

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

CAUSE: Unknown. Need more information.

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

CAUSE: Unknown. Need more information.

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

CAUSE: Unknown. Need more information.

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

CAUSE: Unknown. Need more information.

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

CAUSE: Unknown. Need more information.

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

CAUSE: Unknown. Need more information.

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

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

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

CAUSE: Unknown. Need more information.

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

CAUSE: Unknown. Need more information.

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

CAUSE: Unknown. Need more information.

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

CAUSE: Unknown. Need more information.

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

CAUSE: Unknown. Need more information.

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

CAUSE: Unknown. Need more information.

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

CAUSE: Unknown. Need more information.

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

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

CAUSE: Unknown. Need more information.

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

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

CAUSE: Unknown. Need more information.

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

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

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.

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

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

CAUSE: Unknown. Need more information.

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

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

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

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.

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.

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

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

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

ACTION: 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.

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

ACTION: 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.

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

ACTION: 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.

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

ACTION: 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.

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

ACTION: 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.

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

ACTION: 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.

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

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

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

ACTION: Correct the NMMGR configurations and restart the driver.

CAUSE: The driver has reached the maximum number of supported connections.

ACTION: Shut down some connections to free up resources.

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

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

CAUSE: An unexpected packet format was received.

ACTION: 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.

CAUSE: An unexpected packet format was received.

ACTION: 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.

CAUSE: A non-fatal Type 2 driver software error occurred.

ACTION: 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.

CAUSE: An unexpected packet format was received.

ACTION: 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.

CAUSE: A non-fatal Type 2 driver software error occurred.

ACTION: 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.

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

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

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

CAUSE: A call to obtain a timer resource returned an error.

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

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

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

CAUSE: A non-fatal Type 2 driver software error occurred.

ACTION: 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.

CAUSE: An unexpected packet format was received.

ACTION: 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.

CAUSE: An unexpected packet format was received.

ACTION: 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.

CAUSE: A non-fatal Type 2 driver software error occurred.

ACTION: 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.

CAUSE: An unexpected packet format was received.

ACTION: 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.

CAUSE: The link table does not exist.

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

CAUSE: The link table does not exist.

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

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

CAUSE: The multicast addresses table does not exist.

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

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.

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.

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.

CAUSE: Unknown. Need more information.

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

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.

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

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.

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

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

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.

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

CAUSE: Unknown. Need more information.

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

CAUSE: Unknown. Need more information.

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

CAUSE: Unknown. Need more information.

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

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

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

CAUSE: Memory shortage problems are occurring.

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

CAUSE: Memory problems are occurring.

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

CAUSE: An internal system ports problem has occurred.

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

CAUSE: An internal system ports problem has occurred.

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

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

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

CAUSE: Unknown. Need more information.

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

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

ACTION: Use NMMGR to correct the link name type.

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

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

CAUSE: The Token Ring adapter detected an error.

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

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

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

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

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

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

ACTION: 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.

CAUSE: This station has stopped receiving data.

ACTION: 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.

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

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

CAUSE: This station detected an error.

ACTION: 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.

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

ACTION: 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.

CAUSE: This is the only station on the network.

ACTION: 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.

CAUSE: The network is attempting to recover from a failure.

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

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

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

CAUSE: A station on the network is not receiving data properly.

ACTION: 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.

CAUSE: More information is needed to isolate this failure.

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

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

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