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

Chapter 16 187
100VG-AnyLAN and 100Base-T Error Messages
SDI Driver Specific Status Values
ACTION: Run NMMAINT.PUB.SYS;PARM=74 or ;PARM=77, for
100VG-AnyLAN or 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
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 an SR.”
MESSAGE: An unexpected timeout occurred.
131 ($83) 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 an SR.”
MESSAGE: Module Configurator cannot access its context area.
132 ($84) 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 an SR.”
MESSAGE: Open table full. Too many driver users.
147 ($93) CAUSE: Too many subsystems are attempting to open the driver at the
same time, or subsystems are shutting down without closing the driver.
ACTION: Shut down any networking subsystems that are not currently
needed and try again. A side-effect of this error may be that the driver
becomes unusable; if so, run VGPBA and execute the Reset function to
see if that restores normal operation.
MESSAGE: Bind table full. Too many upper level protocols.
148 ($94) CAUSE: When a new upper-layer protocol attempted to bind
(rendezvous) to the link driver, the driver determined all available
rendezvous table entries were already in use. Too many different
protocols are trying to use the driver.
ACTION: Shut down any networking subsystems that are not currently
needed and try again.