NS3000/iX Error Messages Reference Manual (36923-90043)

186 Chapter16
100VG-AnyLAN and HP-PB 100Base-T Error Messages
SDI Driver Specific Status Values
packets, so operation of the system and applications may continue with
only minimal degradation. Exhausting all receive resources would be a
highly unusual condition. If all receive resources have really been
exhausted, network load may be extremely high, and/or the HP-PB bus
may be preventing frames from being returned to the card in a timely
manner; incoming frames are probably now being dropped. Otherwise
there may be a bug in the link driver. If the problem happens often, see
Appendix A , “Submitting a CR.”
130 ($82) MESSAGE: Cannot read current multicast list.
CAUSE: During a link-open or close operation by an upper level
subsystem, the link module configurator tried to read the current list of
multicast addresses produced by the subsystem, but encountered an
error on the read.
ACTION: Run NMMAINT.PUB.SYS;PARM=74 or ;PARM=77, for
100VG-AnyLAN or HP-PB 100Base-T respectively, and check that the
multicast services are present. If present, try starting a ThinLAN link,
to see if the same errors occur; or try restarting the system, then retry
the operation. If not present, you may need to reinstall ThinLAN
software (which contains the multicast for 100VG-AnyLAN and HP-PB
100Base-T) or obtain newer patches; contact your Hewlett-Packard
Representative for assistance. If reinstalling software does not solve the
problem, see Appendix A , “Submitting a CR.”
131 ($83) MESSAGE: An unexpected timeout occurred.
CAUSE: This is a generic error reporting that a timeout occurred during
a link driver operation, such as a diagnostic loopback test or a dump
operation, or while awaiting a reply message from the driver for an
operation initiated by the link module configurator or deconfigurator.
ACTION: A required message or interrupt has not arrived in time. Reset
the link driver using VGPBA diagnostics, or shut it down and restart.
Retry the operation. If the same problem occurs, replace the adapter
card if this is a loopback test, otherwise check system load or see
Appendix A , “Submitting a CR.”
132 ($84) MESSAGE: Module Configurator cannot access its context area.
CAUSE: During a link-close operation by an upper level subsystem, the
link module deconfigurator checked its context memory area for
validity, but did not find the expected data.
ACTION: The module deconfigurator’s context memory area is being
overwritten, or is not working properly. The deconfigurator did not
perform the close. If this happens every time, wait until the next time
the link is to be closed; instead of closing the link, halt the system and
take a memory dump, and see Appendix A , “Submitting a CR.”