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

Chapter 18 393
PCI LAPBMUX Link Error Messages
SDI Driver Specific Status Values
the reason this error is now occurring.
120 ($78) 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.”
121 ($79) MESSAGE: Error in configuring Download Surrogate.
CAUSE: During the link start up process, the module configurator tries
to configure the Download Surrogate and encountered an error where it
got the surrogate’s port number as Nil.
ACTION: This is a error. Try to restart the link again If the problem
persists with a known good card, see Appendix A , “Submitting a CR.”
122 ($7A) MESSAGE: The subsys link products are not installed.
CAUSE: Probably not all software required to operate this type of link is
installed. Software was incorrectly Installed, or you may need to
purchase additional software or install new patches.
ACTION: If this status is reported during a startup operation, Reinstall
the link software or contact your HP Representative for assistance.
150 ($94) MESSAGE: Bind table full. Too many upper level protocols.
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.
151 ($93) MESSAGE: Open table full. Too many driver users.
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.
152 ($98) MESSAGE: Driver initialization failed.
CAUSE: While processing its very first startup message, the driver
encountered a problem. Probably the configured hardware is not
present, is not the correct kind of adapter card, or there was a problem
configuring the ISR into the I/O system.