HP 3000 Manuals HP 3000 Manuals
Chapter 16 FDDI Error Messages
The following error messages may appear when using or installing FDDI on
your system. The following list consists of error messages that you may
be able to resolve yourself. Other error messages may appear, but
require the help of your HP representative. If the message number does
not appear in this list, either write down the error if it is displayed
on your console, take a system dump, or run the diagnostics before
calling your HP representative for help.
1 MESSAGE FDDI link ! aborted user's request.
CAUSE Your request has been aborted due to power fail
recovery or the driver was shutting down.
ACTION This is a warning.
19 MESSAGE FDDI link ! received frame with unknown 802.2 ctrl
option.
CAUSE Unknown.
ACTION This is only a warning.
20 MESSAGE FDDI link ! received frame with unknown 802.2 ctrl
option.
CAUSE Unknown.
ACTION This is only a warning.
21 MESSAGE FDDI link ! trace manager overrun.
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 debugging is a problem use partial
tracing if possible (when full data frames are not
needed) to ensure trace data is not lost.
31 MESSAGE FDDI link ! aborted user's request.
CAUSE Your request has been aborted due to the power fail
recovery or the driver was shutting down.
ACTION This is a warning.
60 MESSAGE FDDI link ! hardware reported that the ring went
down.
CAUSE Unknown.
ACTION This is a warning. If the ring does not come up
shortly, then check network components (adapters,
cables, etc.). Have your network provider examine the
network.
73 MESSAGE FDDI link ! found incorrect HW or SW ID.
CAUSE The FDDI driver found an old or incorrect version of
the firmware or hardware on the FDDI interface card.
ACTION Update the card to the correct version.
74 MESSAGE FDDI link ! could not read hardware ID
CAUSE The FDDI driver could not read the FDDI hardware
identification codes.
ACTION Run the diagnostic program to see if the hardware has
failed. If so, replace the card.
84 MESSAGE Could not open NMCONFIG file for link !
CAUSE The file NMCONFIG.PUB.SYS does not exist or is not
readable.
ACTION Create NMCONFIG.PUB.SYS with NMMGR.
85 MESSAGE Could not read NMCONFIG file for link !
CAUSE The file NMCONFIG.PUB.SYS either did not exist or was
not readable.
ACTION Use NMMGR to create a NMCONFIG file. Check that its
file protections are correct.
86 MESSAGE NMCONFIG file link ! not validated
CAUSE NMCONFIG.PUB.SYS was not validated after being
updated.
ACTION Use NMMGR to validate NMCONFIG.PUB.SYS.
87 MESSAGE Invalid card at path specified for link !
CAUSE The card, as the configured path, is not an FDDI card.
ACTION Change your configuration in NMCONFIG.PUB.SYS to the
correct path.
88 MESSAGE No card at path specified for link !
CAUSE The FDDI subsystem could not find a card at the
configured path.
ACTION Change your configuration in NMCONFIG.PUB.SYS to the
correct path.
92 MESSAGE FDDI driver already created.
CAUSE The driver was already created under a different
linkname, or by the diagnostic.
ACTION Check your NMCONFIG.PUB.SYS file and correct it if
needed, or check to see if the diagnostic is running.