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

Chapter 16 263
100VG-AnyLAN and HP-PB 100Base-T Error Messages
SDI Driver Specific Status Values
protocol’s address (SAP), a lower-level routine reported an error, as
described by the Message (“Cause” = 32-bit encoded value of the SAP
being bound). Most likely either the address is already in the driver’s
table, or the table is full.
ACTION: This problem most likely occurred while starting a new
network subsystem. Attempt to determine which subsystem was being
started when the error occurred and, if possible, which upper layer
protocol was binding.
The bind failed. The driver logged the error, then attempted to send an
error reply message back to the protocol module and continue.
If a duplicate address is in the table already, either an attempt has been
made to start the same subsystem twice, or a previous instance of that
subsystem did not properly shut down; a system reboot may be required
to shut it. Otherwise there could be a driver bug, if two protocols are
truly different but the driver thinks they are the same. Shut down the
network and restart it. If the problem happens every time, see
Appendix A , “Submitting a CR.”
8450 CLAS0001 MESSAGE: Driver encountered a software problem.
CAUSE: The driver received a bind (rendezvous) from an upper layer
protocol module and added it to driver tables, but encountered an error
trying to obtain a block of buffers from that protocol’s inbound buffer
pool (“Cause” = 32-bit status from the call to vg_isr_fill_buf_cache).
Most likely a serious, unexpected Buffer Manager error was reported on
a call to bmgr_get_buffer, which was not one of the expected, legal
errors the driver is designed to handle.
ACTION: This problem most likely occurred while starting a new
network subsystem. Attempt to determine which subsystem was being
started when the error occurred and, if possible, which upper layer
protocol was binding.
The bind failed. The driver logged the error, then attempted to clean up,
send an error reply message back to the protocol module, and continue.
There may be something wrong with the buffer pool or Buffer Manager,
system memory may be low, or there may be a driver bug. Shut down
the network and restart it. If the problem happens every time, see
Appendix A , “Submitting a CR.”
8480 CLAS0003 MESSAGE: Subsystem is binding to link driver.
CAUSE: An upper layer protocol has successfully bound (rendezvoused)
to the link driver (“Addr” = 32-bit encoded protocol address (SAP) value
for this protocol module). Being bound means the driver can now route
incoming data frames to this protocol.
ACTION: None. This is an informational message only. A similar
message is logged later, when the protocol unbinds. If this is the first
bind, the link driver will now attempt to reconnect the link.