Broadcom NetXtreme II User Manual page 61

User Guide
January 2010
I D
NTERMEDIATE RIVER
The intermediate driver is identified by source BLFM, regardless of the base driver revision.
messages supported by the intermediate driver, explains the cause for the message, and provides the recommended action.
System
Event
Severity
Message
Number
1 Informational
2 Error
3 Error
4 Error
5 Informational
6 Informational
7 Error
8 Warning
9 Informational
10 Warning
11 Informational
12 Error
13 Informational
Document ENGSRVT52-CDUM100-R
(V A
IRTUAL DAPTER
Table 9: Intermediate Driver Event Log Messages
Message
Event logging enabled for
Broadcom Advanced Server
Program driver.
Unable to register with
NDIS.
Unable to instantiate the
management interface.
Unable to create symbolic
link for the management
interface.
Broadcom Advanced Server
Program Driver has started.
Broadcom Advanced Server
Program Driver has
stopped.
Could not allocate memory
for internal data structures.
Could not bind to adapter.
Successfully bind to
adapter.
Network adapter is
disconnected.
Network adapter is
connected.
Broadcom Advanced
Program Features Driver is
not designed to run on this
version of Operating
System.
Hot-standby adapter is
selected as the primary
adapter for a team without a
load balancing adapter.
Bro adco m Co rp or atio n
/T )
EAM
Cause
–
The driver cannot register
with the NDIS interface.
The driver cannot create a
device instance.
Another driver has created a
conflicting device name.
The driver has started.
The driver has stopped.
The driver cannot allocate
memory from the operating
system.
The driver could not open
one of the team physical
adapters.
The driver successfully
opened the physical
adapter.
The physical adapter is not
connected to the network (it
has not established link).
The physical adapter is
connected to the network (it
has established link).
The driver does not support
the operating system on
which it is installed.
A standby adapter has been
activated.
Appendix A: Event Log Messages
NetXtreme II
Table 9 lists the event log
Corrective Action
No action is required.
Unload other NDIS drivers.
Reboot the operating
system.
Unload the conflicting device
driver that uses the name
Blf .
No action is required.
No action is required.
Close running applications
to free memory.
Unload and reload the
physical adapter driver,
install an updated physical
adapter driver, or replace
the physical adapter.
No action is required.
Check that the network
cable is connected, verify
that the network cable is the
right type, and verify that the
link partner (switch or hub) is
working correctly.
No action is required.
Consult the driver release
notes and install the driver
on a supported operating
system or update the driver.
Replace the failed physical
adapter.
Page 61