Broadcom Support Guide v3.03

Broadcom Support Guide
This guide is valid for v12.8 of the Dell Drivers

Contributing Authors:
Brent Caskey, Chris M Davis, Hilson Mota, Michael Ritenour, and Louis Stice.

Table of Contents

Versions ......................................................................................................................................................... 2
Changes and Updates ................................................................................................................................... 2
A. The NIC Configuration appears to Revert back to DHCP .............................................................. 3
B. Yellow Exclamation Point in Device Manager under iSCSI Device ................................................ 4
C. NDIS 6 Error, Broadcom Cannot Team NICs in Windows Server 2008 ......................................... 6
How To… ..................................................................................................................................................... 11
A. How to Install Broadcom Drivers for Windows Server 2003/2008 ............................................. 11
B. How to Install Broadcom Drivers for Windows Server 2008 ...................................................... 12
C. How to Install the Base Device Manager Broadcom Drivers for Windows 2003/2008 .............. 13
D. How to Configure Broadcom and Intel NICs in the same server. ............................................... 15
E. How to Update Drivers and Configure Broadcom and Intel NICs in the Same Server ................ 22
F. How to Team Broadcom NICs ..................................................................................................... 30
G. How to Save an Existing Team while Updating the Broadcom NIC Drivers ................................ 31
H. How to Team Broadcom and Intel Network Adapters (NICs) in the Same Server ...................... 36
I. How to Resolve Performance Tuning and Connectivity Issues ................................................... 45
J. How to Access Network from Guest OS in Virtual Server 2005 .................................................. 53
K. How to use Hyper‐V and Broadcom............................................................................................ 55
L. How to Resolve Issues that May Occur after Running the Script ............................................... 57
Legacy Issues Prior to 12.8 Drivers ............................................................................................................. 58
A. BASP Virtual Adapter (the Team) does not uninstall .................................................................. 58
B. BACS installation almost finishes, then “rolls back” the driver. ................................................. 60
C. Creating a Team displays Internal Error 13 or 15 –or‐ Cannot delete old NIC team .................. 62
D. Broadcom Drivers Do Not Load or Exclamation Point in Device Manager under System .......... 64
E. The Server Reboots when Shutting Down .................................................................................. 66
F. The Teaming Button in the Broadcom Advanced Control Suite is Grayed Out. ......................... 68
G. The Server Blue‐Screens on boot after installing updates from the Dell SUU Update CD. ........ 68

P a g e 1

Versions

The 12.8 Drivers contain the following versions:
• BACS 11.7.5
• Windows 2003 Driver NX2 4.8.5b
• Windows 2008 Driver NX2 4.8.5b
• RIS w2k3 Driver 4.8.2
• Windows iSCSI Driver NX2 4.8.50.0
• VBD Driver 4.6.110

DSET shows the following versions in the following locations.
• System ‐> Main Chassis ‐> Network ‐> Click the IP address for the NIC.
o 4.6.110 (VBD Driver)
• Software ‐> Windows OS ‐> Environment ‐> Installed Applications ‐> Broadcom Advanced
Control Suite (BACS)
o BACS 11.7.5 is the 12.8 Dell Package.
11.6.10 is the 12.6 Dell Package.
• Software ‐> Windows OS ‐> Environment ‐> Drivers
o Bxnd52a.Sys – 4.8.5.0
o BxvBDA.Sys – 4.6.110

Changes and Updates

The Broadcom 12.8 drivers resolve many of the issues that prevented the drivers from installing and
working. The following is a list of changes to existing procedures that simplify the installation of the
drivers.
a. The “Rollback” issue caused by malformed INF files is resolved.
b. The 12.8 drivers maintain existing teams when installing on top of existing drivers.
i. In testing environments, the 12.8 drivers can be installed on top of existing
drivers.
1. Drivers install without issue.
2. Teams are maintained.
ii. NOTE: If there is a question or uneasiness about teams, then it is okay to break
the team first, then install the new drivers, and recreate the team.
c. The Broadcom installation is not sensitive about .Net Framework.
i. Any version of .Net Framework 2.0 works with BACS 12.8.
ii. .Net Framework 3.0 and 3.5 do NOT need to be removed to install BACS 12.8.
iii. .Net Framework 2.0 may be installed AFTER BACS is installed. BACS works fine.
d. Multivendor Teaming is supported.
i. It is okay to put Intel and Broadcom in the same team.
e. Another step in disabling TOE inside of BACS is added.
P a g e 2

A. The NIC Configuration appears to Revert back to DHCP

The Issue:
a. A static IP address is set, but the NIC shows “Obtain an IP address automatically.”
b. Running IPConfig /All shows the static IP address.
c. The Registry shows the static configuration under
HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{GUID}

What to do:
a. Remove the bad configuration from the Registry.

How to do it:
a. Start Æ Run Æ RegEdit
b. Navigate to: HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Control\Network
c. Delete the Config key

d. Click Yes to delete the key.
e. Open Network Connections
f. Right‐Click Local Area Connection
g. Select Properties

P a g e 3

h. Click OK

Note: This process rewrites the Config key without requiring a reboot.

i. Reference:
i. http://support.microsoft.com/kb/937056
ii. “The Internet Protocol (TCP/IP) Properties dialog box displays the default IP
address settings after you manually configure a static IP address in Windows
2000 Server or in Windows Server 2003”
B. Yellow Exclamation Point in Device Manager under iSCSI Device

What to do:
a. Install Microsoft KB article 943545.
http://support.microsoft.com/kb/943545

Symptom
Consider the following scenario:

On a Windows Server 2003‐based computer, you apply the 916048 hotfix, or you install
Windows Server 2003 Service Pack 2 (SP2).

P a g e 4

Later, a request is made for SCSI bus 8 (the SCSI_MAXIMUM_BUSES value) on the
computer.

In this scenario, the IOCTL_SCSI_GET_INQUIRY_DATA I/O control operation returns the
following error:
STATUS_INVALID_DEVICE_REQUEST
Cause
a. This issue occurs because of a logic error in the Storport.sys process that prevents the
driver from returning the correct data for SCSI bus 8.
P a g e 5

C. NDIS 6 Error, Broadcom Cannot Team NICs in Windows Server 2008

The error “Please select an adapter with NDIS 6 driver” appears when creating a team.

Environment:
• Server 2008 32‐bit, 64‐bit
• Symantec Endpoint 11
• Broadcom NICs

During the team creation process, the following screen is shown to select the NICs to add to the team.
When Add… is clicked…

…The error message appears.
"[0006] Broadcom {model} does not support teaming. Please select an adapter with NDIS 6 driver."

P a g e 6

Cause:
Broadcom uses an NDIS 6 driver for the team.
Symantec Endpoint uses an NDIS 5 driver for the Network Threat Protection.

Solution:
Uninstall the Network Threat Protection portion of Symantec Endpoint.

1. Navigate to Control Panel Æ Programs and Features
2. Right‐Click Symantec Endpoint Protection
3. Select Change

4. Click Next
P a g e 7

5. Ensure Modify is selected
6. Click Next

7. Click the Down Arrow next to Network Threat Protection
8. Select This feature will not be available

P a g e 8

9. Click Next

10. Click Install

P a g e 9

11. Click Finish

12. The Broadcom NIC team may now be created.

The rest of the teaming process can now proceed normally.

P a g e 10

How To…
A. How to Install Broadcom Drivers for Windows Server 2003/2008
To Ensure the Broadcom Installer Works:

1. Download the new Broadcom drivers
a. 32‐bit http://ftp.dell.com/network/Bcom_LAN_12.8_W2K3_8_A01.exe
b. 64‐bit http://ftp.dell.com/network/Bcom_LAN_12.8_W2K3_8_64_A01.exe

Important!
For Server 2008, leave all .Net Framework Versions in place, continue at step 3.
2. Ensure, at a minimum, Microsoft’s .Net Framework 2.0 SP1 is installed.
a. 32‐bit
http://www.microsoft.com/downloads/details.aspx?FamilyID=79bc3b77‐e02c‐4ad3‐
aacf‐a7633f706ba5&DisplayLang=en
b. 64‐bit
http://www.microsoft.com/downloads/details.aspx?FamilyId=029196ED‐04EB‐471E‐
8A99‐3C61D19A4C5A&displaylang=en
3. Disable/Pause any Antivirus and Threat‐Protection scanners that can interrupt the Broadcom
driver installation.
a. Check for Symantec Endpoint.
b. If it is installed, ensure Endpoint Patch MR4 (Maintenance Release 4 or newer) is
installed.
i. http://service1.symantec.com/SUPPORT/ent‐
security.nsf/docid/2008121712452848
c. If MR4 (Maintenance Release 4 or newer) cannot be installed, then uninstall Endpoint.
i. Endpoint may be re‐installed later.
4. Break all teams inside the Broadcom Advanced Control Suite, if they exist.
5. Uninstall the existing Broadcom drivers through Add/Remove Programs.
6. Reboot
7. If they started, Disable/Pause any Antivirus and Threat‐Protection scanners that can interrupt
the Broadcom driver installation.
8. Install the new Broadcom drivers
a. Double‐click the Broadcom installer to extract the files to C:\Broadcom\w2k3_8.
i. 32‐bit: Bcom_LAN_12.8_W2K3_8_A01.exe
ii. 64‐bit: Bcom_LAN_12.8_W2K3_8_64_A01.exe
b. Navigate to C:\Broadcom\Driver_Management_Apps_Installer
c. Double‐Click Setup.Exe.
d. Follow the installation wizard to complete the installation.

NOTE: Device Manager cannot be used to install the network drivers. It is not a complete installation
of the Broadcom driver. Both the Device manager driver AND the BACS software MUST be
installed for the driver to operate correctly.

9. Reboot, if the driver requests.
10. Restore any Antivirus and Threat‐Protection scanners that were paused during the driver
installation.
a. If Endpoint was uninstalled previously, then reinstall Endpoint.
P a g e 11

B. How to Install Broadcom Drivers for Windows Server 2008

1. Download the new Broadcom drivers
a. 32‐bit http://ftp.dell.com/network/Bcom_LAN_12.8_W2K3_8_A01.exe
b. 64‐bit http://ftp.dell.com/network/Bcom_LAN_12.8_W2K3_8_64_A01.exe

installed.
3. Break all teams inside the Broadcom Advanced Control Suite, if they exist.
5. Reboot
7. Install the new Broadcom drivers
a. Double‐click the Broadcom installer to extract the files to C:\Broadcom\w2k3_8.
i. 32‐bit: Bcom_LAN_12.8_W2K3_8_A01.exe
ii. 64‐bit: Bcom_LAN_12.8_W2K3_8_64_A01.exe
b. Navigate to C:\Broadcom\Driver_Management_Apps_Installer
c. Double‐Click Setup.Exe.
d. Follow the installation wizard to complete the installation.

NOTE: Using Device Manager to install the network drivers is not a complete installation of the
Broadcom driver.
Both the Device manager driver AND the BACS software MUST be installed for the driver to
operate correctly.

installation.

P a g e 12

C. How to Install the Base Device Manager Broadcom Drivers for Windows 2003/2008

This installs ONLY the device driver in the Device Manager.
This does not install the Broadcom Advanced Control Suite (BACS).


1. Download the correct Broadcom drivers for the server OS:
a. Windows Server 2003
i. 32‐bit NetXtreme
http://ftp.us.dell.com/network/NIC_DRVR_WIN_R212658.EXE
ii. 32‐bit NetXtreme II
iii. 64‐bit NetXtreme
iv. 64‐bit NetXtreme II

b. Windows Server 2008
i. 32‐bit NetXtreme
ii. 32‐bit NetXtreme II
iii. 64‐bit NetXtreme
iv. 64‐bit NetXtreme II

installed.
4. Reboot.
6. Install the new Broadcom drivers.
a. Double‐click the Base Driver Dell Update Package (DUP).
b. Click Install.
c. Click Yes at the question to install the update.
d. The driver is installed automatically.
e. Click OK when the update was completed successfully.
f. Click Finish to close the Dell Update Package.
P a g e 13

installation.
P a g e 14

D. How to Configure Broadcom and Intel NICs in the same server.

What to do:
a. Disable Offloading technologies on all network adapters.

How to do it:

Broadcom Configuration
a. On each NIC inside the Broadcom Advanced Control Suite (BACS)
i. Disable IPv4 Checksum Offload
ii. Disable IPv4 Large Send Offload (LSO)
iii. Disable Receive Side Scaling (RSS)

P a g e 15

Disable TOE in the Broadcom Advanced Control Suite (BACS)

i. Select the first NIC under System Devices

ii. Select the Configurations tab

P a g e 16

iii. Expand the Resource Reservations section

iv. Uncheck the TCP Offload Engine (TOE) checkbox
v. Click Apply

P a g e 17

vi. Select Yes

vii. Repeat for the second NIC.

viii. Select Yes

P a g e 18

Disable Offloading in Windows
a. Disable the TOE chimney in Windows Server 2003
i. Start Æ Run
ii. Netsh int ip set chimney disabled
b. Disable TOE and RSS in Server 2008
i. Start Æ Run
ii. netsh int tcp set global chimney=disabled
iii. netsh interface tcp set global rss=disabled

Intel Configuration
a. Open Device Manager
b. On each Intel NIC in Device Manager, disable the following:
c. NOTE: Not every option is available or exist on the Advanced Tab.
i. Offload Receive IP Checksum
ii. Offload Receive TCP Checksum
iii. Offload TCP Segmentation
iv. Offload Transmit IP Checksum
v. Offload Transmit TCP Checksum
vi. IPV4 Checksum Offload
vii. Large Send Offload v2 (IPV4)
viii. Large Send Offload v2 (IPV6)
ix. Receive‐Side Scaling
x. TCP Checksum Offload (IPV4)
xi. TCP Checksum Offload (IPV6)
xii. UDP Checksum Offload (IPV4)
xiii. UDP Checksum Offload (IPV6)

P a g e 19

The screen looks similar to one of these two:

Windows Server 2003
P a g e 20

Windows Server 2008

P a g e 21

E. How to Update Drivers and Configure Broadcom and Intel NICs in the Same Server

Issue:
a. Broadcom and Intel have incompatible TCP/IP offloading technologies.
b. These offloading technologies must be disabled if both network adapters are installed in
the server at the same time.

What to do:
a. Ensure both Intel and Broadcom Drivers are up‐to‐date.
b. Disable Offloading technologies on all network adapters.

How to do it:

Install the newest Intel Drivers
a. Download the appropriate Intel NIC Driver from Dell. (It’s 10‐14 MB in size)

b. Uninstall any existing Intel Drivers from Add/Remove Programs.
c. Reboot the Server, if the OS requests.
d. Install the Dell drivers.
i. Ensure Proset (in Device Manager) is selected during the installation.
e. The configuration for the Intel NICs is located in Device Manager.

Install the newest Broadcom Drivers
f. Download the new Broadcom drivers
i. 32‐bit http://ftp.dell.com/network/Bcom_LAN_12.8_W2K3_8_A01.exe
ii. 64‐bit http://ftp.dell.com/network/Bcom_LAN_12.8_W2K3_8_64_A01.exe

Important!
For Server 2008, leave all .Net Framework Versions in place, continue at step H.

g. Ensure, at a minimum, Microsoft’s .Net Framework 2.0 SP1 is installed.
(.Net Framework 2.0 SP2 also works)
i. 32‐bit
http://www.microsoft.com/downloads/details.aspx?FamilyID=79bc3b77‐e02c‐
4ad3‐aacf‐a7633f706ba5&DisplayLang=en
ii. 64‐bit
http://www.microsoft.com/downloads/details.aspx?FamilyId=029196ED‐04EB‐
471E‐8A99‐3C61D19A4C5A&displaylang=en

h. Disable/Pause any Antivirus and Threat‐Protection scanners that can interrupt the
Broadcom driver installation.
i. Check for Symantec Endpoint.
ii. If it is installed, ensure Endpoint Patch MR4 (Maintenance Release 4 or newer)
is installed.
1. http://service1.symantec.com/SUPPORT/ent‐
iii. If MR4 (Maintenance Release 4 or newer) cannot be installed, then uninstall
Endpoint.
P a g e 22

1. Endpoint may be re‐installed later.

i. Uninstall the existing Broadcom drivers through Add/Remove Programs.
j. Reboot
k. If they started, Disable/Pause any Antivirus and Threat‐Protection scanners that can
interrupt the Broadcom driver installation.
l. Install the new Broadcom drivers
i. Double‐click the Broadcom installer to extract the files to
C:\Broadcom\w2k3_8.
1. 32‐bit: Bcom_LAN_12.8_W2K3_8_A01.exe
2. 64‐bit: Bcom_LAN_12.8_W2K3_8_64_A01.exe
ii. Navigate to C:\Broadcom\Driver_Management_Apps_Installer
iii. Double‐Click Setup.Exe.
iv. Follow the installation wizard to complete the installation.

Note: Using Device Manager to install the network drivers is not a complete installation of the
Broadcom driver.
operate correctly.

m. Reboot, if the driver requests.
n. Restore any Antivirus and Threat‐Protection scanners that were paused during the

Configure Broadcom and Intel NICs to Co‐Exist

On each NIC inside the Broadcom Advanced Control Suite (BACS)
a. Disable IPv4 Checksum Offload
b. Disable IPv4 Large Send Offload (LSO)
c. Disable Receive Side Scaling (RSS)

P a g e 23


d. Select the first NIC under System Devices

P a g e 24

e. Select the Configurations tab

f. Expand the Resource Reservations section

P a g e 25

g. Uncheck the TCP Offload Engine (TOE) checkbox
h. Click Apply

i. Select Yes

P a g e 26

j. Repeat for the second NIC.

k. Select Yes

i. netsh int ip set chimney disabled
b. Disable TOE and RSS in Server 2008 (http://support.microsoft.com/kb/951037 )
i. netsh int tcp set global chimney=disabled
ii. netsh interface tcp set global rss=disabled

Intel Configuration
c. Note: Not every option is available or exists on the Advanced Tab.
P a g e 27



Windows Server 2003
P a g e 28

Windows Server 2008

P a g e 29

F. How to Team Broadcom NICs

What to do:
a. Use the Broadcom Advanced Control Suite to Team Broadcom NICs.

How to do it:
a. How to team using the Broadcom Advanced Control Suite v3:
http://support.dell.com/support/edocs/network/BroadCom/R125875/en/bacs.htm#wp
398670

b. Downloaded version of the BCOM Manual:
http://ftp.us.dell.com/network/Bcom_LAN_12.8_Manual_A00.exe

c. How to team using the Broadcom Advanced Control Suite v2:
http://support.dell.com/support/edocs/network/BroadCom/R125805/en/teaming.htm
P a g e 30

G. How to Save an Existing Team while Updating the Broadcom NIC Drivers

NOTE: The Broadcom 12.8 NIC driver installation should automatically backup and restore existing
teams while updating the drivers.

However, if teaming information is critical, then follow these steps.

What to do:
a. Backup the Teaming information.
b. Uninstall the old Broadcom NIC drivers.
c. Install the new Broadcom NIC drivers.
d. Restore the Teaming information.

How to do it:
a. Download the new Broadcom drivers

Important!
For Server 2008, leave all .Net Framework Versions in place, continue at step C.
b. Ensure, at a minimum, Microsoft’s .Net Framework 2.0 SP1 is installed.
i. 32‐bit
ii. 64‐bit

Save the existing Teaming Configuration

Note: There are two ways of accomplishing this – from Command Prompt OR from BACS

c. Command Line method
i. Click Start Æ Run
ii. Type CMD
iii. Type CD C:\Broadcom\Driver_Managment_Apps_Installer\BASPSCfg
iv. Type BaspSCfg –save Team1 ‐nicid PCIINFO

d. Broadcom Advanced Control Suite method
i. Click File
ii. Select Team Save As
P a g e 31

iii. Type a filename
iv. Click Save

e. Disable/Pause any Antivirus and Threat‐Protection scanners that can interrupt the
is installed.
Endpoint.
f. Break all teams inside the Broadcom Advanced Control Suite, if they exist.
g. Uninstall the existing Broadcom drivers through Add/Remove Programs.
h. Reboot
P a g e 32

i. If they started, Disable/Pause any Antivirus and Threat‐Protection scanners that can
j. Install the new Broadcom drivers
iv. Double‐click the Broadcom installer to extract the files to
C:\Broadcom\w2k3_8.
v. Navigate to C:\Broadcom\Driver_Management_Apps_Installer
vi. Double‐Click Setup.Exe.
vii. Follow the installation wizard to complete the installation.

Broadcom driver.
operate correctly.

k. Reboot, if the driver requests.
l. Restore any Antivirus and Threat‐Protection scanners that were paused during the
viii. If Endpoint was uninstalled previously, then reinstall Endpoint.
Restore Team Configuration

Note: There are two ways of accomplishing this – from Command Prompt OR from BACS

a. Command Line method
i. Start Æ Run
ii. Type CMD
iii. Type CD C:\Broadcom\Driver_Managment_Apps_Installer\BASPSCfg
iv. Type BaspSCfg –restore Team1
a. The original Team is created from the file Team1.

b. Broadcom Advanced Control Suite method
a. Click File
b. Select Team Restore

P a g e 33

c. Select file
d. Click Open

e. Click Apply/Exit if no changes are required.

P a g e 34

f. Click the Edit Team tab at the top if changes are required.
g. Make the changes.
h. Click Apply/Exit after making any changes.

i. Click Yes.

Note: This process will work as long as all the NICs involved in the Team configuration of the system
remain intact.
P a g e 35

H. How to Team Broadcom and Intel Network Adapters (NICs) in the Same Server

What to do:
a. Ensure the newest NIC drivers are installed.
b. Disable Offloading technologies on all network adapters.
i. Broadcom and Intel have incompatible TCP/IP offloading technologies.
ii. These offloading technologies must be disabled if both network adapters are
installed in the server at the same time.

How to do it:
l. Ensure both Intel and Broadcom NIC drivers are the newest.




Important!

i. 32‐bit
ii. 64‐bit

c. Disable/Pause any Antivirus and Threat‐Protection scanners that can interrupt the
is installed.
P a g e 36

Endpoint.

d. Break all teams inside the Broadcom Advanced Control Suite, if they exist.
e. Uninstall the existing Broadcom drivers through Add/Remove Programs.

f. Reboot

g. If they started, Disable/Pause any Antivirus and Threat‐Protection scanners that can

h. Install the new Broadcom drivers
C:\Broadcom\w2k3_8.

NOTE: Using Device Manager to install the Broadcom drivers is not a complete installation of the
Broadcom driver.

Both the Device manager driver AND the BACS software MUST be installed for the Broadcom
drivers to operate correctly.
i. Reboot.
j. Restore any Antivirus and Threat‐Protection scanners that were paused during the

Configure Broadcom and Intel NICs to Co‐Exist

Disable Offloading in Broadcom


P a g e 37




P a g e 38


P a g e 39

v. Click Apply

vi. Select Yes

P a g e 40


viii. Select Yes

i. netsh int ip set chimney disabled
b. Disable TOE and RSS in Server 2008 (http://support.microsoft.com/kb/951037 )
i. netsh int tcp set global chimney=disabled
ii. netsh interface tcp set global rss=disabled

Intel Configuration
P a g e 41



Windows Server 2003
P a g e 42

Windows Server 2008

Teaming the NICS
a. Two Broadcom NICs may exist in the same team.
b. Two Intel NICs may exist in the same team.
c. The Broadcom Advanced Control Suite (BACS) may state that it cannot team the Intel
NICs without a Broadcom Adapter in the team.
i. Either ensure one Broadcom NIC is part of each team with Intel,
ii. Or, check the Intel NIC Properties in Device Manager. It likely has a Teaming
Tab to team the Intel NICs.

BACS V3 teaming:
http://support.dell.com/support/edocs/network/BroadCom/R125875/en/bacs.htm#wp398670

Note: If the Broadcom Advanced Control Suite (BACS) states that it cannot team the Intel NICs, then
check the Intel NIC Properties in Device Manager. It likely has a Teaming Tab to team the Intel
NICs.

P a g e 43

d. If the Intel drivers are older than 10.x, then use the Broadcom Advanced Control Suite to
team.
e. If the Intel drivers are version 10.x or newer, then use the Teaming tab in Adapter
properties inside of Device Manager.
f. If in doubt, try creating a team of two Intel NICs in the Broadcom Advanced Control
Suite.
i. If it doesn’t work, then use the Teaming tab inside of the Adapter Properties
inside of Device Manager.

(Note this is a screen‐capture of the Intel NIC driver – NOT the Dell driver.)

P a g e 44

I. How to Resolve Performance Tuning and Connectivity Issues

While enabling network adapter offload features is typically beneficial, there are configurations where
these advanced features are a detriment to overall performance.

In some cases the network adapter is not powerful enough to handle the offload capabilities at high
throughput. For example, enabling segmentation offload can reduce the maximum sustainable
throughput on some network adapters because of limited hardware resources.

Additionally, there are technologies used in Windows that are not compatible with offloading
technologies.

The incompatible technologies are:
• Windows Firewall
• Internet Protocol security (IPsec)
• Internet Protocol Network Address Translation (IPNAT)
• Third‐party firewalls
• NDIS 5.1 intermediate drivers

Because of this, disabling the advanced offloading features can greatly improve connectivity.
What to do:
a. Disable Offloading technologies on all network adapters.
i. Disable TOE in Windows
ii. Disable TOE in the Broadcom Advanced Control Suite
iii. Disable Receive Side Scaling
iv. Disable Large Send Offload

How to do it:


P a g e 45



P a g e 46



P a g e 47

v. Click Apply

vi. Select Yes

P a g e 48


viii. Select Yes

a. Windows Server 2003
i. Start Æ Run
1. netsh int ip set chimney disabled
ii. OR Apply Microsoft update 948496
1. http://support.microsoft.com/kb/948496
b. Windows Server 2008
i. Start Æ Run
1. netsh int tcp set global chimney=disabled
2. netsh interface tcp set global rss=disabled

P a g e 49

Intel Configuration


Windows Server 2003
P a g e 50

Windows Server 2008

c. If BACS is not installed, disable RSS in Windows
‐ Choose one of the two methods below
i. In Server 2003 with Service Pack 2
1. Start Æ Run Æ RegEdit
2. Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\P
arameters
3. On the Edit menu, point to New, click DWORD Value.
4. Type EnableRSS.
5. Double‐click EnableRSS
6. Type 0
7. Click OK.

ii. In Windows Server 2008
1. Start Æ Run Æ CMD
2. netsh interface tcp set global rss=disabled
P a g e 51

d. If BACS is not installed, disable IPV4 Large Send Offload (LSO) in Windows
i. In Server 2003 with Service Pack 2
1. Start Æ Run Æ RegEdit
2. Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\P
arameters
3. On the Edit menu, point to New, click DWORD Value.
4. Type DisableTaskOffload.
5. Double‐click DisableTaskOffload.
6. Type 1
7. Click OK.

e. If BACS is not installed, Registry File method to Disable RSS and Large Send Offload
i. Copy the text below to a notepad file called, “Disable RSS and LSO.Reg.”
ii. Double‐click the file to import the file into the Registry.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
"EnableRSS"=dword:00000000
"DisableTaskOffload"=dword:00000001

f. To update SNP,
i. http://support.microsoft.com/kb/950224
ii. Scalable Networking Pack (SNP) hotfix rollup.

g. Check TOE status
i. Start Æ Run Æ CMD

ii. Windows Server 2003
1. Type: netstat –ton

iii. Windows Server 2008
1. netsh interface tcp show global

h. If all connections are “InHost” then TOE is likely disabled
i. If any connection shows “Offloaded” then TOE is enabled.

Note: Windows Server 2008 AutoTuning could also cause performance issues.

a. netsh int tcp set global autotuninglevel=disable
P a g e 52

J. How to Access Network from Guest OS in Virtual Server 2005

What to do:
a. Install newest drivers for Broadcom and Intel
b. Bind the Guest Network to the BASP Virtual Adapter.

How to do it:
a. Make sure that the latest drivers are installed to resolve connectivity issues that were
present in older versions.

b. Ensure both Intel and Broadcom NIC drivers are the newest.




Important!

i. 32‐bit
ii. 64‐bit

is installed.
Endpoint.
P a g e 53


d. Uninstall the existing Broadcom drivers through Add/Remove Programs.

e. Reboot

f. If they started, Disable/Pause any Antivirus and Threat‐Protection scanners that can

g. Install the new Broadcom drivers
C:\Broadcom\w2k3_8.

NOTE: Using Device Manager to install the Broadcom drivers is not a complete installation of the
Broadcom driver.

Both the Device manager driver AND the BACS software MUST be installed for the Broadcom
drivers to operate correctly.
h. Reboot.
i. Restore any Antivirus and Threat‐Protection scanners that were paused during the

BIND the NICs
j. Bind the guest network to the BASP Virtual Adapter on a BCOM NIC Teamed network
interface.
P a g e 54

K. How to use Hyper‐V and Broadcom

What to do:
a. Broadcom Teams are only supported on the Host OS. They cannot be attached to the
Virtual Switch.

How to do it:
a. The Dell documentation states that network teams cannot be bound to Hyper‐V virtual
Networks.
b. http://support.dell.com/support/edocs/software/ws2k8/en/Hyper‐V/IIG.pdf
i. Page 15 under known issues..

There is currently no workaround to support Hyper-V virtual networking on
BACS-based teams or VLANs. A resolution may be available in a future release.
Dell currently does not support BACS-based Teams or VLANs on network
adapters bound to Hyper-V virtual networks
There is currently no workaround to support Hyper-V virtual networking on

PROSet-based teams or VLANs. A resolution may be available in a future
release. Dell currently does not support PROSet-based Teams or VLANs on
network adapters bound to Hyper-V virtual networks.
c. Teaming
i. Possible workaround (not tested)
http://social.technet.microsoft.com/Forums/en‐
US/winserverhyperv/thread/5af859d0‐d26f‐4125‐9f24‐a52378933d80/
“We had a similar issue in our environment as well. We're running a Dell
M1000e Blade chassis with M600 dual‐quad cores, 16GB RAM, mirrored SAS
drives, Windows Server 2008 x64 host with multiple windows 2003 32‐bit
guests. The host has broadcom BCM5708S netxtreme II GigE adapters. BACS 3
version 11.0.20.0, NIC driver version 4.1.3.0.
The symptoms in our case were that the guests had no network connectivity off
of the host machine. That is to say that the host could ping the guests, the
guests could ping the host, but the guests could not ping any other computers
on the network and no computers on the network could ping the guests ‐
although other computers could ping the host. If we broke our team and bound
the IP to one of the NIC's all would work fine, going back to teaming would
break network communications once again.
After much playing we found that the following resolved our issue:
• Force speed/duplex, disable IPV4 checksum offload and receive side
scaling
• Break the team
• In Hyper‐V Manager remove the virtual network
• Recreate the team using the "create team" wizard
P a g e 55

• Team type is Smart Load Balancing
• Set one adapter to be a secondary adapter
• Enable auto‐fallback disable mode
• No VLANs are in use
In our case the 2 physical Broadcom adapters in Network Connections have only
QOS Packet Scheduler and Broadcom Advanced Server Program Driver checked
The team in Network Connections has only Broadcom Advanced Server Program
Driver and Microsoft Virtual Network Switch Protocol checked
Go back into hyper‐v manager and create a new external virtual network
adapter and bind it to the BASP Virtual adapter.
Assign your static ip to the hyper‐v external virtual network adapter created
above. In properties of the external virtual network adapter everything except
Microsoft virtual network switch protocol is checked.
After this was done we found that we now had full network connectivity to the
guests and vice versa. Failover also worked beautifully as well in this
configuration. Disabling a switch port to the primary nic in the team caused the
secondary nic to take over without even dropping a packet. One thing to note ‐
not setting one of the nic's as secondary appears to work fine until you
shutdown both switch ports and try to bring them back up ‐ network
connectivity is not restored. Configuring the team with one adapter as
secondary overcomes this issue.
Hope this helps someone out there...we fooled around with it forever to get it
working correctly.

NOTE: There is some feedback on this that suggests that under heavy load, this
will BSOD the system. However, this was done using older versions of the driver.
On our site, the following is noted under the fixes and enhancements section for
the new driver.

This release fixes BSOD Hyper‐V issue with Broadcom devices. This release
supports Windows 2003 and Windows 2008 64‐bit driver update for NetXtreme
I and NetXtreme II devices i.e., BCM5708, BCM5709 and BCM57710 based
adapters. Please review release.txt in Readme First folder for further details

P a g e 56

L. How to Resolve Issues that May Occur after Running the Script
1. Intel NIC configuration is lost if the server has Intel NICs installed.
2. Windows 2008 Servers:
a. Windows 2008 DHCP Servers may not bind a NIC to the DHCP service
i. Remove and Reinstall the DHCP role to resolve.
b. The NICs don’t function properly if Hyper‐V was installed.
i. Remove and Re‐install the Hyper‐V role to resolve.
c. This is also happens when the Broadcom NICs were teamed before installing the
Hyper‐V role
i. Again, Remove and Re‐install the Hyper‐V role to resolve.

P a g e 57

Legacy Issues Prior to 12.8 Drivers

A. BASP Virtual Adapter (the Team) does not uninstall

Note: This issue appears to be resolved in the current Broadcom 12.8 Drivers.
Recommend installing the 12.8 Drivers.

What to do:
a. Change permissions and remove two Registry Keys.
i. HKLM\SYSTEM\CurrentControlSet\Enum\Root\Brcm_...
ii. HKLM\SYSTEM\CurrentControlSet\Enum\B06BDRV

How to do it:

a. Start Æ Run Æ Regedit.

b. For each of the following keys…
c. HKLM\SYSTEM\CurrentControlSet\Enum\Root\Brcm_...
d. HKLM\SYSTEM\CurrentControlSet\Enum\B06BDRV

i. Right‐Click the Key.
ii. Select Permissions.
iii. Click Add…
iv. Type Everyone.
v. Click OK.
1. If asked, select the Everyone for the Domain.
2. Click OK.
vi. Check Full Control under Allow.
vii. Click OK.
viii. Delete the key after changing permissions

e. Create the team in the Broadcom Advanced Control Suite.

Teaming the NICS
f. Two Broadcom NICs may exist in the same team.
g. Two Intel NICs may exist in the same team.

h. It is not recommended to team a Broadcom NIC with an Intel NIC in the same team.

BACS V3 teaming:

NICs.

P a g e 58

i. If the Intel drivers are older than 10.x, then use the Broadcom Advanced Control Suite to
team.
j. If the Intel drivers are version 10.x or newer, then use the Teaming tab in Adapter
k. If in doubt, try creating a team of two Intel NICs in the Broadcom Advanced Control
Suite.


P a g e 59

B. BACS installation almost finishes, then “rolls back” the driver.

Note: This is resolved in the current Broadcom 12.8 Drivers.

What to do:
a. Relocate INF files so the Broadcom Installer does not read them.

How to do it:

a. It is presumed that the newest driver is already downloaded.

Important!

i. .Net Framework 2.0 SP1 32‐bit
ii. .Net Framework 2.0 Sp1 64‐bit

is installed.
Endpoint.

d. Relocate INF files so the Broadcom Installer does not read them.
i. Navigate to the %WINDIR% folder (i.e. C:\Windows)
ii. Create a new folder, %WINDIR%\INF_TEMP (i.e. C:\Windows\INF_TEMP)
iii. Open the INF folder.
iv. Move all *.INF files to the INF_TEMP folder.

e. Install the Broadcom Drivers
C:\Broadcom\w2k3_8.
P a g e 60


f. After installation, and before reboot ‐ RESTORE INF Files
i. Create a folder, %WINDIR%\INF_NEW (i.e. C:\Windows\INF_NEW)
ii. Copy the new *.INF files from the \INF folder to the \INF_NEW folder.
iii. Copy the old *.INF files from \INF_TEMP to the \INF folder
iv. Copy the new *.INF files from \INF_NEW to the \INF folder
g. Reboot

P a g e 61

C. Creating a Team displays Internal Error 13 or 15
–or‐ Cannot delete old NIC team


What to do:
a. Uninstall BASP from the Broadcom Advanced Control Suite
b. Reboot
c. Reinstall BASP from the Broadcom Advanced Control Suite
d. Recreate the Team.

How to do it:
a. Remove BASP
i. Start Æ Control Panel Æ Add/Remove Programs
ii. Select Broadcom Drivers and Applications
iii. Click Change
iv. Uncheck BASP during the wizard.
v. Complete the installer.

b. Reboot the server.

c. Install BASP
i. Start Æ Control Panel Æ Add/Remove Programs
ii. Select Broadcom Drivers and Applications
iii. Click Change
iv. Check BASP during the wizard.
v. Complete the installer.

d. Reboot the server.

e. Create the team in the Broadcom Advanced Control Suite.

BACS V3 teaming:

NICs.

OR, ensure one Broadcom NIC is a member of each team created.

f. If the Intel drivers are older than 10.x, then use the Broadcom Advanced Control Suite to
team.
g. If the Intel drivers are version 10.x or newer, then use the Teaming tab in Adapter
P a g e 62

h. If in doubt, try creating a team of two Intel NICs in the Broadcom Advanced Control
Suite.


P a g e 63

D. Broadcom Drivers Do Not Load or Exclamation Point in Device Manager under
System
(…and all BCOM devices can be manually removed from device manager)

Note: This issue is resolved in the current Broadcom 12.8 Drivers.

What to do:
a. Uninstall old Broadcom Advanced Control Suite.
b. Clean the system of older Broadcom file versions.
c. Reinstall the Broadcom Drivers.

How to do it:
Important!
i. 32‐bit
ii. 64‐bit

is installed.
Endpoint.

BCOMRemove v1_1
3-24-2009.zip

e. Reboot and go into the BIOS
f. Disable the Broadcom NICs in BIOS
g. Boot to the OS.
h. Extract BCOMRemove.zip
i. Rename the following files:
i. BCOM_Remove.txt Æ BCOM_Remove.vbs
ii. BCOM_Finalize.txt Æ BCOM_Finalize.vbs
P a g e 64

j. Uninstall the existing Broadcom drivers through Add/Remove Programs.
k. Select No for restart now
l. Uninstall all Broadcom NICs and BASFND from Device Manager.
i. Click Start Æ Run Æ Type CMD.
ii. Type set devmgr_show_nonpresent_devices=1.
iii. Type Start DEVMGMT.MSC.
iv. Click View.
v. Click Show Hidden Devices.
vi. Expand the Network Adapters section on the left.
vii. Remove all listed Broadcom network adapters.
1. Right-click the network adapter
2. Click Uninstall.
viii. Expand the Non-Plug and Play Drivers section on the left.
ix. Remove all instances of BASFND

x. Expand the System devices section on the left.
xi. Remove all instances of BASFND
xii. Remove all listed Broadcom network adapters.
2. Click Uninstall

m. Double‐Click BCOM_Remove.vbs
n. Reboot and go into the BIOS
o. Enable the Broadcom NICs in BIOS
p. Boot to the OS.
q. Cancel the Found new hardware wizard
r. Double‐click BCOM_Finalize.vbs
s. Install the Broadcom Drivers
C:\Broadcom\w2k3_8.

Note: If the system is a Domain Controller, then the installation may need to be performed in
Directory Services Restore Mode (DSRM).

If the Directory Services Restore Mode password is unknown, it may be reset by following:
“Click, Start, click Run, type ntdsutil, and then click OK.
At the Ntdsutil command prompt, type set dsrm password.”

Note: As a last resort, try installing the older Broadcom Advanced Control Suite v2.
a. Windows 2003 x86: http://ftp.us.dell.com/network/Bcom_LAN_10_30_W2K3_A03.exe
b. Windows 2003 x64:
http://ftp.us.dell.com/network/Bcom_LAN_10_30_W2K364_A03.exe
P a g e 65

E. The Server Reboots when Shutting Down


What to do:
a. Install the newest Broadcom NIC drivers.

How to do it:

Note: The server is crashing upon shutdown. The cause is old Broadcom NIC drivers.
If one NIC is enabled, and the other is disabled, the server crashes upon shutdown.

Solution ‐ Install the newest Broadcom Drivers


Important!

i. 32‐bit
ii. 64‐bit

is installed.
Endpoint.

e. Uninstall the existing Broadcom drivers through Add/Remove Programs.
f. Reboot

g. If they started, Disable/Pause any Antivirus and Threat‐Protection scanners that can
P a g e 66

h. Install the new Broadcom drivers
C:\Broadcom\w2k3_8.

Broadcom driver.

operate correctly.

i. Reboot, if the driver requests.
j. Restore any Antivirus and Threat‐Protection scanners that were paused during the

Work‐Around
a. If installing new drivers is not an option, the following work‐around works.
a. Enable the second NIC.
b. Set it to an IP address that is not used on the network with no Gateway and
does not register itself inside of DNS.

P a g e 67

F. The Teaming Button in the Broadcom Advanced Control Suite is Grayed Out.


What to do:
a. Remove a DLL that prevents the button from working.

How to do it:
a. Navigate to C:\Program Files\Broadcom\SNMP\

b. Rename the file BASPMgnt.Dll to BASPMgnt.Dll.BAK

c. Restart the Broadcom Advanced Control Suite

G. The Server Blue‐Screens on boot after installing updates from the Dell SUU Update
CD.


What to do:
a. Boot to Safe Mode
b. Disable Broadcom NIC drivers in Device Manager
c. Boot Normally
d. Uninstall old Broadcom Advanced Control Suite.
e. Clean the system of older Broadcom file versions.
f. Reinstall the Broadcom Drivers.

How to do it:
a. Boot into Safe Mode
b. Disable the Broadcom drivers in Device Manager
i. Check under Network Connections
ii. Check under System Devices
c. Boot normally
d. Download the new Broadcom drivers

Important!
For Server 2008, leave all .Net Framework Versions in place, continue at step F.
e. Ensure, at a minimum, Microsoft’s .Net Framework 2.0 SP1 is installed.
i. 32‐bit
P a g e 68

ii. 64‐bit

f. Disable/Pause any Antivirus and Threat‐Protection scanners that can interrupt the
is installed.
Endpoint.

BCOMRemove v1_1
3-24-2009.zip

g. Extract BCOMRemove.zip

h. Rename the following files:
i. BCOM_Remove.txt Æ BCOM_Remove.vbs
ii. BCOM_Finalize.txt Æ BCOM_Finalize.vbs
i. Uninstall the existing Broadcom drivers through Add/Remove Programs.
j. Select No for restart now
k. Uninstall all Broadcom NICs and BASFND from Device Manager.
i. Click Start Æ Run Æ Type CMD.
ii. Type set devmgr_show_nonpresent_devices=1.
iii. Type Start DEVMGMT.MSC.
iv. Click View.
v. Click Show Hidden Devices.
vi. Expand the Network Adapters section on the left.
vii. Remove all listed Broadcom network adapters.
2. Click Uninstall.
viii. Expand the Non-Plug and Play Drivers section on the left.
ix. Remove all instances of BASFND

x. Expand the System devices section on the left.
xi. Remove all instances of BASFND
xii. Remove all listed Broadcom network adapters.
2. Click Uninstall

l. Double‐Click BCOM_Remove.vbs

m. Cancel the Found new hardware wizard

n. Double‐click BCOM_Finalize.vbs
P a g e 69

o. Install the Broadcom Drivers
C:\Broadcom\w2k3_8.

Note: If the system is a Domain Controller, then the installation may need to be performed in
Directory Services Restore Mode (DSRM).

If the Directory Services Restore Mode password is unknown, it may be reset by following:
“Click, Start, click Run, type ntdsutil, and then click OK.
At the Ntdsutil command prompt, type set dsrm password.”

P a g e 70

Broadcom Support Guide v3.03

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Broadcom Support Guide v3.03

Uploaded by

Copyright:

Available Formats

Broadcom Support Guide

There is currently no workaround to support Hyper-V virtual networking on

You might also like