Intermediate Driver (Virtual Adapter/Team) - Dell Broadcom NetXtreme Family of Adapters User Manual

Broadcom Teaming Services: Broadcom NetXtreme II Network Adapter User Guide
19 Error
20 Error
21 Informational
22 Error
23 Error

Intermediate Driver (Virtual Adapter/Team)

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.
Table 9: Intermediate Driver Event Log Messages
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
file:///T|/htdocs/NETWORK/BroadCom/71921/NetXtremeII/en/teamsvcs.htm[9/26/2012 3:29:14 PM]
This driver does not
support this device. The driver does not recognize
Upgrade to the latest the installed adapter.
driver.
Driver initialization Unspecified failure during
failed. driver initialization.
The adapter has been
Network controller
manually configured for the
configured for 10Gb
selected line speed and
full-duplex link.
duplex settings.
Network controller
failed initialization Insufficient system memory
because it cannot prevented the initialization of
allocate system the driver.
memory.
Network controller
failed to exchange the The driver and the bus driver
interface with the bus are not compatible.
driver.
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.
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).
Upgrade to a driver version that supports
this adapter.
Reinstall the driver, update to a newer
driver, run Broadcom Advanced Control
Suite diagnostics, or replace the adapter.
No action is required.
Increase system memory.
Update to the latest driver set, ensuring the
major and minor versions for both NDIS and
the bus driver are the same.
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.