NS3000/iX Error Messages Reference Manual (36923-90041)
198 Chapter16
100VG-AnyLAN and 100Base-T Error Messages
SDI Driver Specific Status Values
rebooted. Either there is a bug in the driver or upper layer protocol
software, memory data corruption has occurred, or there is a system
software mismatch. You may require additional software patches;
contact your Hewlett-Packard Representative for assistance.
MESSAGE: An illegal bind ID was encountered.
229 ($E5) CAUSE: The driver finished transferring a data frame and was
preparing to pass it to an upper layer protocol, when it discovered the
rendezvous ID associated with the frame was out of range of legal ID
values for this driver. The driver avoided a SysAbort by making this
check.
ACTION: This is a fatal error. The driver will attempt to perform a
dump of all host context memory data structures, then reset itself and
continue. Save the resulting Netdmp##.pub.sys dump data file for
analysis by Hewlett-Packard. If the problem occurs frequently, wait for
the problem to occur, then quickly take a system memory dump. See
Appendix A, “Submitting an SR.”
MESSAGE: Unsupported packet format.
233 ($E9) CAUSE: After transferring a received data frame from the adapter card
to host memory, the link driver found that the frame was not
deliverable because it utilizes frame features not supported by this
driver.
ACTION: This event is informational. No action is required. The driver
dropped the frame and incremented a statistic. However, if the
application sending these frames is a required part of your
environment, you may need to contact your Hewlett-Packard
Representative for assistance.
MESSAGE: The same upper level protocol attempted to bind twice.
235 ($EB) CAUSE: The driver received a bind (rendezvous) from an upper layer
protocol module, but when it attempted to save information about that
protocol’s address (SAP), a lower-level routine reported an error
because the address is already in the driver’s rendezvous table.
ACTION: Attempt to determine which subsystem was being started
when the error occurred and, if possible, which upper layer protocol was
binding. 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 an SR.”