Ethernet NIC FAQ's

Please refer to the Broadcom NetXtreme Gigabit Ethernet Adapter user manual.

• Broadcom NetXtreme II 1G Copper Adapter: Links at 10 Mb, 100 Mb, and 1000 Mb.
• Broadcom NetXtreme II 10G utilizes external phys and depending on phy capabilities can operate at: 10, 100, 1000, 10000 Mb/s.
• Broadcom NetXtreme Copper Adapter: Links at 10 Mb, 100 Mb, and 1000 Mb.
• Broadcom NetXtreme Fiber-Optic Adapter: Only links at 1000 Mb.
• Broadcom 440X 10/100 Integrated Controller: Only links at 10 Mb and 100 Mb.

Yes.

Yes.

Go into the BIOS and assign another IRQ for your adapter. Make sure it's not sharing an IRQ with another device.

1. Make sure the adapter is not defective either by visually inspecting it or by using an adapter diagnostic program.
2. Check your cabling system and its connectivity; check the link LED on the adapter and/or on the switch.
3. Ensure the adapter is placed properly into the PCI slot.
4. Move the adapter into a different PCI slot.
5. Inspect the driver configuration; please refer to the user manual for instruction.
6. In Linux issue command lspci to check if your adapter is listed

• Follow the instruction posted at: http://www.broadcom.com/support/ethernet_nic/determine_driver.php

1. Open Control Panel. Click on Add/Remove Programs or Programs and Features
2. For Windows XP/2003 choose add/remove programs. Click on Broadcom Drivers and then click remove
3. For Windows Vista/2008 choose Uninstall or Change a Program. Click on Broadcom Drivers and then click Uninstall
4. Uninstalling the driver from Device Manager is not recommended and may lead to incomplete removal of the device

1. Run the latest Driver Installation Software
2. Upgrading the driver from Device Manager is not supported

1. Run the latest Driver Installation Software
2. Installing the driver from Device Manager is not supported

You will need to obtain the Client Installation from the Novell CD or download file at http://www.novell.com/coolsolutions/tools/downloads/dw271e.zip.

1. Copy the file into a temporary directory.
2. Run the file.
3. Copy the drivers into the temporary directory.
4. Run INSTALL.EXE.
5. Follow the directions within the installation software.

Requirements:

1. Microsoft Network Client version 3.0 for MS-DOS from Windows NT Server 4.0 installation CD.
2. Blank MS-DOS bootable 3.5" High Density floppy disk.
3. Broadcom NDIS2 driver. (B57.dos or B44.dos)

Windows NT 3.51/4.0 Server users:

1. When using the "Network Client Administrator" tool available in Windows NT, simply choose any other network card from the list (NE2000 Compatible for example) to create the diskette.
2. After creating the diskette, follow the instructions below under "Modifying boot diskette for Broadcom network card".

Windows 2000/XP users:

Method 1: Running "Network Client Administrator" tool from Windows 2000/XP:

1. Create a folder called "NCADMIN" in the root of the C: drive.
2. Copy NCADMIN.CN_, NCADMIN.EX_, and NCADMIN.HL_ from the I386 folder on the Windows NT Server 4.0 cd.
3. Open a command prompt window and change directory to C:\NCADMIN.
4. Type expand -r ncadmin.* and press enter.
5. Close the command prompt window.
6. Start Windows Explorer
7. Open the NCADMIN folder and double-click NCADMIN.EXE.
8. Follow the instructions to make the network startup disk. (Choose "NE2000 Compatible" when selecting the network adapter.)
9. After creating the diskette, follow the instructions below under "Modifying boot diskette for Broadcom network card".

Method 2: Running Microsoft Network Client version 3.0 for MS-DOS setup from a DOS prompt:

1. Copy the NETSETUP directory from the Windows NT Server 4.0 CD located under <cd-rom drive letter>:\clients
2. Open a command prompt window.
3. From the "C:" prompt type cd \NETSETUP and press the ENTER key.
4. Type setup and press the ENTER key.
5. Press the ENTER key to continue.
6. Accept the default installation path of "C:\NET" by pressing the ENTER key.
7. Use the down arrow to scroll down the network adapter list and highlight "NE2000 Compatible". Press ENTER.
8. Accept "Network Buffer" defaults by pressing ENTER.
9. Enter a user name that is valid on the Windows system to which you will be attaching. Press ENTER.
10. On the next screen arrow up to "Change Setup Options" and press ENTER.
11. Arrow up to "Change Redir Options" and press ENTER.
12. Arrow up to "Use the Basic Redirector" and press ENTER.
13. Press ENTER on the next screen. ("The listed options are correct" will be highlighted.)
14. Arrow up to "Change Network Configuration" and press ENTER.
15. Choose and configure the desired protocols from this screen.
16. Once the protocols are configured, select "Network configuration is correct" and press ENTER.
17. Press ENTER again. ("The listed options are correct" should be highlighted.)
18. The configuration files will then be copied to C:\NET. Press ENTER to exit setup.
19. Start "Windows Explorer" and view the contents of the C:\NET directory.
20. Delete any of the following files that exist to insure the directory will fit on the floppy disk: ADDNAME.EXE, EXPAND.EXE, IPCONFIG.EXE, NE2000.DOS, PING.EXE, WIN_SOCK.DLL, WINSOCK.DLL, WSOCKETS.DLL, VSOCKETS.386, VBAPI.386, SETUP.EXE, SOCKETS.EXE
21. Copy C:\NET to a bootable floppy.

Modifying boot diskette for Broadcom network card:

Note: for BCM4401 use "B44" in place of "B57" in the following examples.

1. Edit A:\NET\PROTOCOL.INI with Notepad or similar text editor.
   • Change "DriverName=$" to "DriverName=B57$"
   • Remove all other parameter entries under the [MS$NE2CLONE] or equivalent section such as "IOBASE=0x300" or "INTERRUPT=3", etc.

   Example Protocol.ini for IP:

   [network.setup]
   version=0x3110
   netcard=ms$ne2clone,1,MS$NE2CLONE,1
   transport=tcpip,TCPIP
   lana0=ms$ne2clone,1,tcpip
   
   [MS$NE2CLONE]
   DriverName=B57$
   
   [protman]
   DriverName=PROTMAN$
   PRIORITY=MS$NDISHLP
   
   [tcpip]
   NBSessions=6
   DefaultGateway=0
   ; SubNetMask=255 0 0 0
   ; IPAddress=192 168 0 1
   DisableDHCP=0
   DriverName=TCPIP$
   BINDINGS=MS$NE2CLONE
   LANABASE=0
   

   Example Protocol.ini for IPX:

   [network.setup]
   version=0x3110
   netcard=ms$ne2clone,1,MS$NE2CLONE,1
   transport=ms$ndishlp,MS$NDISHLP
   transport=ms$nwlink,MS$NWLINK
   lana0=ms$ne2clone,1,ms$nwlink
   lana1=ms$ne2clone,1,ms$ndishlp
   
   [MS$NE2CLONE]
   DriverName=B57$
   
   [protman]
   DriverName=PROTMAN$
   PRIORITY=MS$NDISHLP
   
   [MS$NDISHLP]
   DriverName=ndishlp$
   BINDINGS=ms$ne2clone
   
   [ms$nwlink]
   DriverName=nwlink$
   FRAME=Ethernet_802.2
   BINDINGS=MS$NE2CLONE
   LANABASE=0
   

   Example Protocol.ini for NetBEUI:

   [network.setup]
   version=0x3110
   netcard=ms$ne2clone,1,MS$NE2CLONE,1
   transport=ms$ndishlp,MS$NDISHLP
   transport=ms$netbeui,MS$NETBEUI
   lana0=ms$ne2clone,1,ms$ndishlp
   lana1=ms$ne2clone,1,ms$netbeui
   
   [MS$NE2CLONE]
   DriverName=B57$
   
   [protman]
   DriverName=PROTMAN$
   PRIORITY=MS$NDISHLP
   
   [MS$NDISHLP]
   DriverName=ndishlp$
   BINDINGS=MS$NE2CLONE
   
   [MS$NETBEUI]
   DriverName=netbeui$
   SESSIONS=10
   NCBS=12
   BINDINGS=MS$NE2CLONE
   LANABASE=0
   

2. Edit A:\NET\SYSTEM.INI.
   • Change "netcard=" to "netcard=b57.dos"
   • Check for references to "C:\NET" and change "C:\NET" to "A:\NET" if necessary.
   Example SYSTEM.INI

   [network]
   sizworkbuf=1498
   filesharing=no
   printsharing=no
   autologon=yes
   computername=MYPC
   lanroot=A:\NET
   username=USER1
   workgroup=WORKGROUP
   reconnect=yes
   dospophotkey=N
   lmlogon=0
   logondomain=
   preferredredir=basic
   autostart=basic
   maxconnections=8
   
   [network drivers]
   netcard=B57.dos
   transport=ndishlp.sys,*netbeui
   devdir=A:\NET
   LoadRMDrivers=yes
   

3. Copy B57.dos to A:\NET.
4. Create the appropriate AUTOEXEC.BAT file in A:\ for the chosen protocol as shown below.
   • For TCP/IP:

     path=a:\net
     a:\net\net initialize
     a:\net\netbind.com
     a:\net\umb.com
     a:\net\tcptsr.exe
     a:\net\tinyrfc.exe
     a:\net\nmtsr.exe
     a:\net\emsbfr.exe
     a:\net\net start basic
     net use z: \\SERVERNAME\SHARENAME
     

   • For IPX:

     SET PATH=A:\NET
     A:\net\net initialize
     A:\net\nwlink
     A:\net\net START BASIC
     net use z: \\SERVERNAME\SHARENAME
     

   • For NetBEUI:

     SET PATH=A:\NET
     A:\net\net START BASIC
     net use z: \\SERVERNAME\SHARENAME
     

   • Create a CONFIG.SYS file in A:\ as shown below.

     files=30
     device=a:\net\ifshlp.sys
     lastdrive=z

1. Run pkgadd to install the drivers. E.g., pkgadd -d <install_path>.
2. Please follow the UnixWare user manual to configure the NIC.

1. Copy the drivers to a temporary directory.
2. Run custom to install the drivers.
3. To configure the NIC, please follow the directions in the SCO OpenServer manual or the readme.txt.

1. Copy the driver (.tar.gz) into a temporary folders
2. tar xzvf driver file.tar.gz
3. cd bnx...version/ ( directory just created by tar)
4. cd src
5. do make clean; make install
6. rmmod bnx2 or bnx2x
7. modprobe bnx2 or bnx2x
8. Refer to Readme.txt for .rpm file

Type: B57.COM /s

Type: config

Type: custom

Type: custom

Type: less /proc/net/nicinfo/eth0.info. Replace 0 with the number of the NIC you want to query. Issue command ethtool -i ethx (x= number of NIC you want to query)

Run B57UDIAG.EXE from a machine booted to DOS. This program will not function properly in Windows.

Try uninstalling the driver and re-installing upon reboot. If it is still banged out, the driver being used may not support the adapter. Only drivers that were provided on the CD that shipped with the adapter should be used.

1. Check your IP address and IP Mask (please refer to documentation for respective OS).
2. Ping your default gateway.
3. Ping another client on the same subnet connected to the same switch or HUB.
4. Ping the switch's management IP address if it is on the same subnet as yours.
5. Refer to the troubleshooting section of the user manual.

1. In Microsoft Windows, right-click the Network Adapter in Network Connections and click Properties.
2. Click the Configure button and then the General tab.
3. Set the speed to 10 Mb Full, 10 Mb Half, 100 Mb Full, 100 Mb Half, or Auto.

Netware: Adapter speed is forced by adding "Speed=XXXX" parameter to driver load command line in the AUTOEXEC.NCF file, where XXXX are 10 HD, 10 FD, 100 HD or 100 FD.

Linux: This can be done using the "ethtool -s" command. Please refer to the respective man page for command syntax.

The "802.1p QOS" parameter is a standard that enables Quality of Service (QoS). It is responsible for the QoS provisions on the local segment, and the avoidance of the "all packets are treated equally" issue, which falls onto the hub or switch servicing segment. 802.1p QOS provides prioritization of packets traversing a subnet.

1. In Microsoft Windows, right-click the Network Adapter in "Network Connections" and click Properties.
2. Click the Configure button and then the General tab.
3. Set the "802.1p QOS" parameter to Enable or Disable.

Normally the "Checksum Offload" function is computed by the protocol stack. By selecting one of the "Checksum Offload" parameters, the checksum can be computed by the Gigabit Ethernet Adapter.

1. In Microsoft Windows, right-click the Network Adapter in Network Connections and then click Properties.
2. Click the Configure button and then the General tab.
3. Set the Checksum Offload parameter to None, Rx TCP/IP Checksum, Tx TCP/IP Checksum, or Tx/Rx TCP/IP Checksum.

Netware: Checksum Offload is configured by adding the "CHECKSUM=ON" parameter to the driver load command line in the AUTOEXEC.NCF file. To disable, change the value to OFF or do not include the parameter, since the default is set to disable.

Linux: The can be done using the "ethtool -K" command. Please refer to the respective man page for command syntax.

"Ethernet@WireSpeed" is a parameter that enables a 1000BASE-T Ethernet adapter to establish a link at a lower speed when only two pairs of wires are available in the cable plant.

1. In Microsoft Windows, right-click the Network Adapter in Network Connections and, then click Properties.
2. Click the Configure button and then the General tab.
3. Set the "Ethernet@WireSpeed" parameter to Disable or None.

In Linux, SCO, Unixware and Solaris operating systems this feature is always enabled on supported Broadcom adapters.

"Flow Control" is a parameter that allows the user to enable or disable the receipt or transmission of PAUSE frames. PAUSE frames enable the adapter and the switch to control the transmit rate. The side that is receiving the PAUSE frame temporarily stops transmitting.

1. In Microsoft Windows, right-click the Network Adapter in Network Connections and then click Properties.
2. Click the Configure button and then the General tab.
3. Set the "Flow Control" parameter to Auto, Disable, Rx Pause, Rx/Tx Pause, or Tx Pause.

Netware: Flow Control is configured by adding either the "TxFlow=ON" or "RxFlow=ON" (transmit and receive respectively) parameter to the driver load command line in the AUTOEXEC.NCF file. Both transmit and receive can be enabled concurrently. To disable, change the value to OFF or do not include the parameter, since the default is set to disable.

Linux: The can be done using the "ethtool -A" command. Please refer to the respective man page for command syntax.

"Jumbo MTU" is a parameter that allows the adapter to transmit and receive oversized Ethernet frames that are greater than 1514 bytes but less than 9000 bytes in length. Note that this parameter requires a switch that is able to process large frames.

1. In Microsoft Windows, right-click the Network Adapter in Network Connections, and then click Properties.
2. Click the Configure button and then the General tab. Jumbo MTU is set at 1500 bytes by default. To increase the size of the received frames, increase the byte quantity in 500-byte increments up to 9000 bytes.

Netware: Jumbo Frame is configured by adding the "Jumbo=XXXX" parameter to the driver load command line in the AUTOEXEC.NCF file, where XXXX is a value between 1514 and 9000 bytes.

Linux: The MTU can be changed on the device in which support this feature using the following command: "ifconfig eth mtu the can be between 1500 to 9000. The is the device ID.

NOTE: Please note that not all Broadcom networking devices support Jumbo-frame. Please consult the respective product documentation to confirm that your device supports this feature.

Normally the TCP segmentation is done by the protocol stack. By enabling the Large Send Offload value, the TCP segmentation can be done by the Gigabit Ethernet Adapter.

1. In Microsoft Windows, right-click the Network Adapter in Network Connections and then click Properties.
2. Click the Configure button and then the General tab.
3. Set the "Large Send Offload" parameter to Disable or Enable.

Locally Administered Address is a user-defined address that is used in place of the MAC address that was originally assigned to the adapter. Every adapter in the network must have its own unique MAC address. This locally administered address consists of a 12-digit hexadecimal number.

1. In Microsoft Windows, right-click the Network Adapter in Network Connections and then click Properties.
2. Click the Configure button and then the General tab.
3. Configure the "Locally Administered Address" parameter by assigning a unique node address for the adapter.

Netware: The Mac Address is configured by the adding Node=XXXXXXXXXXXX parameter to driver load command line in the AUTOEXEC.NCF file, where XXXXXXXXXXXX is the Locally Administered address.

Linux: Virtual MAC addresses can be set using "ifconfig". Please view the ifconfig man page for further details.

The "Wake Up Capabilities" parameter allows the user to set the adapter to wake up from a low power mode when it receives a network wake up frame. There are two wake up frames: Magic Packet and IP frame.

1. In Microsoft Windows, right-click the Network Adapter in Network Connections and then click Properties.
2. Click the Configure button and then the General tab.
3. Set the "Wake Up Capabilities" parameter to Both, Magic Packet, None, or Wake Up Frame.

Netware: Only supports DOS WOL and is configured by adding "MagicP=1" parameter to driver load command line in the AUTOEXEC.NCF file. To disable, change value to "0" or do not include parameter, since default is set to disable.

Linux: The can be done using the "ethtool -g" command. Please refer to the respective man page for command syntax.

"WOL Speed" is a parameter that allows the user to select the speed at which the adapter connects to the network during Wake-on-LAN mode.

1. In Microsoft Windows, right-click the Network Adapter in Network Connections and then click Properties.
2. Click the Configure button and then the General tab.
3. Set the "WOL Speed" parameter to 10 Mb, 100 Mb, or Auto.

In Linux, the feature is not supported. The interface will automatically link at the lowest speed supported by your switch.

Yes.

There is a folder labeled "MakeDisk" on the CD (provided) where a driver disk can be created for the adapter. Run the setup.exe and follow the directions to create the driver disk.

Broadcom Advanced Control Suite (BACS) is an integrated graphical user interface application that provides the following functions:

• Vital Signs: At-a-glance status reports of all LAN adapters/controllers in your systems.
• Network Test: The Network Test will confirm network connectivity to a remote station.
• Diagnostics: A comprehensive diagnostic for Broadcom NetXtreme Gigabit Ethernet controllers.
• Cable Analysis: An in depth analysis on CAT5 cable characterization performed by the Broadcom NetXtreme Gigabit Ethernet controller.
• Load Balance/Virtual LAN: An easy way to configure the load balance and failover by grouping multiple adapters/controllers.
• Statistics: A detailed performance statistics on each selected adapter/controller.

Windows XP/Server 2003/Vista/Windows 2008/Windows 7/Windows 2008 R2.

Broadcom Advanced Control Suite (BACS) can be installed from the Management Applications Installer provided on the OEM's CD or from the Broadcom's website.

1. From the Windows Control Panel, double-click Add/Remove Programs.
2. At the Add/Remove window, select "Broadcom Management Programs" and click Change/Remove . The InstallShield Wizard screen appears.
3. Click the Remove radio button and click Next. The Confirm File Deletion screen appears.
4. Click OK. An information screen will appear confirming update.
5. Reboot your system to complete the BACS removal.

1. Click Start button, click Settings, then click Control Panel.
2. Double-click the Broadcom NetXtreme™ Gigabit Ethernet icon.

BASP is a Broadcom intermediate software driver for Windows 2008 R2, Windows 2008, Windows 2003, Windows 2000, and NetWare that provides load-balancing, fault-tolerance, and VLAN features. These features are provided by creating teams (virtual adapters) that consist of multiple NIC interfaces. A team can consist of one to eight NIC interfaces, and each interface can be designated as primary or standby. All primary interfaces in a team will participate in load-balancing operations by sending and receiving a portion of the total traffic. Standby interfaces will take over in the event that all primary interfaces have lost their links. VLANs can be added to a team to allow multiple VLANs with different VLAN IDs. A virtual adapter is created for each VLAN added. Load-balancing and fault-tolerance features will work with any third party's NIC adapters. VLANs only work with Broadcom NIC adapters.

Windows 2000, Windows Server 2003, Windows 2008, Windows 2008 R2, and Netware.

TCP/IP and IPX protocols. NetBeui is supported in some operating systems. Please refer to the Broadcom NetXtreme Gigabit Ethernet Adapter user manual for details.

Microsoft Windows: Go to Vital Signs tab of BACS (Broadcom Advanced Control Suite) and look for the Driver Name/Version field to identify the driver version

Linux: Use "ethtool -i eth" where is the device ID.

SCO: Install the respective driver per documentation. At the shell prompt type custom. The driver version information will be displayed.

UnixWare: Install the driver package per documentation. At the command prompt enter pkginfo -l . Search for bcme software. The driver version will be listed there.

Solaris 8.0 for X86: Install the respective driver package per documentation. At the command prompt, type: modinfo | grep bcme. The driver version will be displayed on the screen.

Microsoft Windows: Go to the Vital Signs tab of BACS (Broadcom Advanced Control Suite) and look for the ASIC/Firmware Version field to identify the chipset.

Netware: There is no simple way to determine a chipset, but PRODID.NLM will output the device ID that can be used to determine a chipset.

Linux: After loading the Broadcom Linux core driver, a virtual directory and file(s) are created under /proc/net/nicinfo/. There will be one virtual file for each Broadcom interface in your system. You can use vi or more to view information and various stats of your Broadcom NIC.

SCO and UnixWare: Install the respective driver per documentation. At the shell prompt, type grep BCM /var/adm/messages. The chipset information will be displayed at chip=BCM57xxS for fiber or chip=BCM57xx for copper.

Solaris 8.0 for X86: Install the respective driver package per documentation. At the command prompt, type: kstat -m bcme | grep macDeviceType. The chipset information will display on the screen.

DOS: Execute b57udiag -cmd at the DOS prompt. The first column will display the chipset information.

Microsoft Windows: Go to the VBD node (System devices) under Device Management icon in BACS (Broadcom Advanced Control Suite) and under the Information tab, in the Resources section, you can find which PCI Bus Mode the adapter is installed.

Netware: To determine PCI Bus Mode, load NCMCON.NLM and select slot information.

Linux: After loading the Broadcom Linux core driver, a virtual directory and file(s) are created under /proc/net/nicinfo/. There will be one virtual file for each Broadcom interface in your system. You can use vi or more to view information and various stats of your Broadcom NIC.

In Microsoft Windows, a quick network test can be done by going to the NDIS node in BACS, click on the Diagnostics tab and click on Run. Please note, if a default gateway is not specified for the adapter, BACS will prompt for an ip address.

In Microsoft Windows, there is a diagnostics feature in BACS (Broadcom Advanced Control Suite). For a NX1 device, go to the NDIS node under Device Management, click on the Diagnostics tab. Click on the "Select a test to run:" pull down menu, select Diagnostics test. For NX2/Everest devices, go to the VBD node (System Devices), click on the Diagnostics tab, Select "Diagnostics Tests" from the pull down menu. Then click on Run to perform the tests. The test includes Control Registers Test, MII Registers Test , EEPROM Test, Internal Memory Test, On-Chip CPU Test, Interrupt Test, MAC and PHY Loopback Test, and LED Test.

In Microsoft Windows, there is a Cable Analysis feature in BACS (Broadcom Advanced Control Suite). For a NX1 device, go to the NDIS node under Device Management, click on the Diagnostics tab. Click on the "Select a test to run:" pull down menu, select Cable Analysis. For NX2/Everest devices, go to the VBD node (System Devices), click on the Diagnostics tab, Select "Cable Analysis" from the pull down menu. Then click on Run to perform the test.

In Microsoft Windows, go to the Statistics tab of BACS (Broadcom Advanced Control Suite).

1. In Microsoft Windows, click on the Team Management icon in BACS (Broadcom Advanced Control Suite), select Teams from the menu, and select "Create a Team". A teaming wizard will display. Follow the instructions to the end, and click finish to create the desired teaming configuration.

1. In Microsoft windows, click on the Team Management icon in BACS (Broadcom Advanced Control Suite), right-click on the adapter that you want removed from the team, select Remove from Team.

A maximum of eight adapters.

VLAN stands for Virtual Local Area Network. VLAN is a logical grouping of network users and resources connected to a switch. By default, all switches make up a large broadcast domain in the layer-2 switched network. By creating VLAN, we could break up broadcast domains into smaller ones within a switch by assigning different ports of the switch into different subnets. The benefits of using VLAN include broadcast control, security, flexibility, scalability, etc.

Refer to the Broadcom NetXtreme Gigabit Ethernet Adapter User Guide for details.

A maximum of 64 VLANs.

1. In Microsoft Windows, click on File from the menu in BACS (Broadcom Advanced Control Suite 3).
2. Select Team Save As.
3. Browse to where you want to save this configuration file, type its name and then click the Save button.

1. In Microsoft Windows, click on File from the menu in BACS (Broadcom Advanced Control Suite 3).
2. Select Team Restore. Browse to where you saved the configuration file, select the file and then click the Open button.
3. Click the Apply button. Restart your system.

PXE (Preboot Execution Environment) is a software module that allows your networked computer to boot with the images provided by remote servers across the network.

• Use b57udiag utility with the commands below:
  b57udiag -mba [ 0-disable | 1-enable ] -c <devnum>
• Or:
  b57diag -mba [ 0-disable | 1-enable ] -c <devnum>

• B57diag -c 0 -pxe a:b57mmba.nic

• Use b57udiag utility with the commands below:
  b57udiag -mbas [ 0-Auto | 1-10HD | 2-10FD | 3-100H | 4-100F ]
• Or: B57diag -c 0 -pxes [ 0-Auto | 1-10HD | 2-10FD | 3-100H | 4-100F

Microsoft Remote Installation Service(RIS) Instructions for Adding Broadcom Network Adapter Driver

Problem: An error is encountered when attempting to load the Broadcom device driver for a 32-bit version of Windows XP or later operating system using a Windows 2000 Remote Installation Server: File b57w2k.sys caused an unexpected error (21) at line 3752 in d:\xpsp1\base\boot\setup\setup.c.

Solution: A modification to the b57win32.inf file can be made to allow for the installation to complete successfully. This will be in conjunction with instructions from the Microsoft Knowledge Base Article 315279 that describe "How to Add Third-Party OEM Network Adapters to RIS Installations."

Requirement: The Windows 2000 Server must be running Service Pack 3 or later.

1. Obtain the latest driver for your Broadcom adapter.
2. The driver files included for the Broadcom 57xx adapter are b57win32.inf, b57win32.cat, and b57xp32.sys. Create a copy of the b57win32.inf and b57xp32.sys files and locate them in a separate folder called RIS. This will allow you to distinguish them from the originals.
3. For the b57win32.inf file located in the RIS folder, make the following change using a text editor like Notepad:
   1. Locate [Manufacturer] within the file.
   2. Review the line below which reads: %BRCM% = Broadcom, NTx86.5.1, NTamd64.
   3. Modify that line to read: %BRCM% = Broadcom.NTx86.5.1, NTamd64. The change made replaces the comma and space after "Broadcom" with a period.
   4. Save the file.
4. On the RIS server, copy the b57win32.inf and b57xp32.sys files from the RIS folder to the RemoteInstall\Setup\Language\Images\Dir_name\i386 folder. (This allows Setup to use the driver during the text-mode portion of the installation).
   1. At the same level as the i386 folder on the RIS image, create a $oem$ folder. Use the recommended structure: \$oem$\$1\Drivers\Nic
   2. Copy the original b57win32.inf, b57xp32.sys, and b57win32.cat driver files to this folder.
   3. Make the following changes to the .sif file that is used for this image installation:

      [Unattended]
      OemPreinstall = yes
      OemPnpDriversPath = \Drivers\Nic
      

      Stop and then restart the Remote Installation service on the RIS server. To do this, type the following from a command prompt:

      net stop binlsvc
      net start binlsvc

In b57diag, check if PXE is enabled, and the MBA Delay Time should not be set to 15.

In b57diag, check if PXE is enabled.

Check the DHCP server to see if it is functioning properly.

Simply follow the steps outlined in the Zenworks Readme file.

Solution 1: Ghost is not compatible with the new Serial ATA standard. If you are experiencing problems such as Ghost hanging, locking up, or freezing when loading, the problem lies with the interrupt handling for the Intel 865 Chipsets and later. To fix this problem, use the -FNI switch which forces Ghost to use the BIOS to gain access to the IDE drive.

Solution 2: If you are using Norton Ghost 2003, the latest LiveUpdate includes the fix for this issue. To run LiveUpdate for Ghost 2003, open the program and then click LiveUpdate.

If you have a licensed copy of Symantec Ghost 7.5, contact the Symantec Customer Center at 1-800-927-4017 to obtain information on an updated file that fixes this problem. The Customer Center will confirm your serial number for your copy of Symantec Ghost 7.5.

To set forced 100 Mbps full duplex:

insmod bcm5700 line_speed=100 full_duplex=1 auto_speed=0

or set the following in modules.conf

options bcm5700 line_speed=100 full_duplex=1 auto_speed=0

or use ethtool:

ethtool -s eth0 speed 100 duplex full autoneg off

Note: If the auto_speed is not set to zero it would negotiate at the speed and duplex that were set with respective parameters.

1. Download the latest "Netware (ODI16)" driver for 570x.
2. Run PowerQuest "Boot Disk Builder".
3. During the process of creating the "PowerCast Boot Disk" you will be asked to select a network adapter. Choose any Ethernet adapter listed. The 3Com 3C509 will be used in this example.
4. Once "Boot Disk Builder" is finished creating the diskette, open Windows Explorer and view the contents of A: drive.
5. Delete 3C5X9.COM or other existing ODI driver
6. Copy the file B57.COM that was downloaded in step 1 to A:\.
7. Use Notepad or another text editor to edit NET.CFG.
8. In NET.CFG replace references to 3C5X9 with B57
   Example NET.CFG:

   LINK SUPPORT
   	BUFFERS 6 1600
   
   PROTOCOL
   	BIND B57
   
   LINK DRIVER B57
   	FRAME ETHERNET_802.2
   FRAME ETHERNET_II
   

9. Save the changes to NET.CFG.
10. Use Notepad or other text editor to edit AUTOEXEC.BAT
11. In AUTOEXEC.BAT replace 3C5X9.COM with B57.COM.
    Example AUTOEXEC.BAT:

    @ECHO OFF
    @PROMPT $P$G
    kicknic
    lsl
    b57.com
    REM mouse
    ECHO.
    ECHO.
    ECHO ImageCenter 5.0
    ECHO Copyright 1994-2001 PowerQuest Corporation.
    ECHO All rights reserved. U.S. Patents 5,675,769;
    5,706,472; 5,930,831, 6,088,778, and 6,108,759.
    Other patents pending.
    ECHO.
    ECHO Loading. Please wait...
    pqpcast /msn="session1" /dsk=1
    

12. Save changes to AUTOEXEC.BAT.

1. Run the LAN Manager installation.
2. When prompted to select the Network Adapter Driver, choose "Novell NE2000 Adapter (And Compatibles)"
3. Complete the installation.
4. Copy the Broadcom NDIS2 driver (B57.DOS or B44.DOS) to "C:\LANMAN.DOS\DRIVERS\ETHERNET\NE2000\"
5. Edit "C:\LANMAN.DOS\PROTOCOL.INI" and make the following changes to the [NE2000_NIF] section located at the bottom of the file:
   • Change "DRIVERNAME = NE2000$" to "DRIVERNAME = B57$"
   • Remove "IOBASE = 0x300" and "INTERRUPT = 3" entries.
6. Save PROTOCOL.INI
7. Edit "C:\LANMAN.DOS\SETUP.INI" and make the following changes to the [ConfigSys] section:
   • Change the line: "DEVICE = C:\LANMAN.DOS\DRIVERS\ ETHERNET\NE2000\NE2000.DOS" to "DEVICE = C:\LANMAN.DOS\DRIVERS\ ETHERNET\NE2000\B57.DOS"
8. Save SETUP.INI
9. Edit "C:\CONFIG.SYS" and make the following changes:
   • Change the line: "DEVICE = C:\LANMAN.DOS\DRIVERS\ ETHERNET\NE2000\NE2000.DOS" to "DEVICE = C:\LANMAN.DOS\DRIVERS\ ETHERNET\NE2000\B57.DOS"
10. Save CONFIG.SYS

The System Preparation tool, Sysprep.exe, is a disk-image-based deployment tool that you can use to install identical configurations on multiple computers. The information pertaining to how to use this tool is supplied with the Sysprep software or can be located through various sections of Microsoft's website (i.e. Knowledge Base, Technet, etc.). Therefore, our intent is not to instruct on how this tool is used but how to include the driver for our adapter to work in conjunction with this utility.

On the sysprep.inf file, the following will need to be added to the "Unattend" header:

[Unattend]
OemPnPDriversPath=Drivers\Net

The driver files for our adapter depending on the operating system must reside in this directory that will be located in the System Drive (where the operating system resides). If other drivers are to be loaded, then Drivers\Net can be appended to the paths listed and separated by a semicolon (e.g. OemPnpDriversPath=Drivers\Video;Drivers\Net)

For Windows XP, the driver files to be included will be b57win32.inf, b57win32.cat, and b57xp32.sys.

For Windows 2000, the driver files to be included will be b57win32.inf, b57win32.cat, and b57w2k.sys.

The Sysprep utility must run with the -pnp switch in order to rescan for new devices which can be added during the mini-setup. Although there are differences between the Sysprep utility for Windows 2000 and Windows XP, the instructions outlined above should cover the only difference needed to set it up for the different operating systems.

A Sample Sysprep.inf for Windows XP is shown below:

------------------------------------------------------------------------

;SetupMgrTag
[Unattended]
	OemSkipEula=Yes
	OemPreinstall=Yes
	TargetPath=\Windows
	UnattendedInstall=Yes
	OemPnpDriversPath=Drivers\Net

[GuiUnattended]
	AdminPassword="password"
	EncryptedAdminPassword=NO
	AutoLogon=Yes
	AutoLogonCount=99
	OEMSkipRegional=1
	OEMDuplicatorstring="XP System"
	TimeZone=4
	OemSkipWelcome=1

[UserData]
	FullName="User"
	OrgName="Organization"
	ComputerName=*

[SetupMgr]
	DistFolder=C:\sysprep\i386
	DistShare=whistlerdist

[Identification]
	JoinDomain=workgroup

[Networking]
	InstallDefaultComponents=Yes

Per the IEEE standard, the only IEEE compliant way to operate at 1000Mb/s-Full duplex is through auto-negotiation. If the network switch being used is IEEE compliant, the link speed will auto-negotiate to 1000Mb/s-Full duplex when autoneg is selected.

Download the BCM57xx or BCM4401 user diagnostic from our website and follow these instructions:

1. Create a DOS bootable floppy and unzip the respective diagnostic package into it
2. Boot to Dos and run b57udiag or b44udiag, respectively

The reason is that the BASP process is periodically waking up to check for events whereas most other processes will be sleeping indefinitely until woken up by external events. Because we are constantly running and sleeping even when the system is idle, it is showing up in the load average. But the important thing is that the CPU utilization remains at almost 100% idle even when the load average is non-zero.

Microsoft's implementation of the Windows Firewall feature included in Service Pack 2 appears to cause Large Send Offload (LSO) to stop working correctly. They provide the solution to this problem in Knowledge Base article 842264. If the problem persists, you may need to run the latest Windows update in order for this feature to begin working again. Specifically, the security update available at the following link should re-activate the LSO capability of our adapter: Microsoft security update.

This problem is not isolated to the Broadcom adapter. However, based on several inquiries, we list the following instructions based on other customers successfully working around this issue:

1. Place the Broadcom driver files in the original image folder (the image folder created when risetup.exe was executed for the first time).
   Example: i:\RemoteInstall\Setup\English\Images\(Original Image)
2. Place the Broadcom driver files in the i386 subfolder under the original image folder
   Example: i:\RemoteInstall\Setup\English\Images\(Original Image)\i386
3. Place the Broadcom driver files for the network adapter in the RIPREP Image folder.
   Example: i:\RemoteInstall\Setup\English\Images\(RIPREP Image)
4. Place the Broadcom adapter drivers in the i386 subfolder where the RIPREP Image is located.
   Example: i:\RemoteInstall\Setup\English\Images\(RIPREP Image)\i386
   
   The Microsoft Knowledge base articles listed below were used as a reference for the following instructions:
   
   http://support.microsoft.com/default.aspx?scid=kb;EN-US;254078
   http://support.microsoft.com/default.aspx?scid=kb;EN-US;246184
   
   
5. Create the following path and place all Broadcom driver files in ..\(RIPREP Image)\$oem$$1\Drivers\network
6. Edit the riprep.sif file located in ..\(RIPREP Image)\i386\Template to include the following information under the [Unattend] section:
   OemPreinstall = yes
   OemPnPDriversPath = "Drivers\network"
   DriverSigningPolicy = Ignore
7. Create the following path and place all Broadcom driver files in ..\(Original Image)\$oem$\$1\Drivers\nic
8. Edit the ristndrd.sif file located in ..\(Original Image)\i386\templates to include the following information under the [Unattend] section:
   OemPreinstall = yes
   OemPnPDriversPath = "Drivers\nic"
   DriverSigningPolicy = Ignore
9. Restart the Remote Installation service. This can be performed from a command line with the following commands:
   net stop binlsvc
   net start binlsvc

To better support users, Broadcom has been actively supporting, maintaining, and testing the in-kernel Linux drivers for the NetXtreme, NetXtreme II, NetLink and 4401 product lines. The following is list of drivers supported for each product line:

• NetXtreme and NetLink - tg3
• NetXtreme II - bnx2 1G
• NetXtreme II - bnx2x 10G
• 4401 - b44

Broadcom officially releases the Linux drivers as packages. The Linux driver packages released by Broadcom are based on the latest in-kernel drivers with some added compatibility code to make it backwards compatible with most 2.6 kernels and some 2.4 kernels (generally newer than 2.4.24). If you are using the latest upstream kernel from www.kernel.org, you generally do not need to download the Linux driver packages from Broadcom as the latest upstream kernel has the latest Linux driver patches.

For the NetXtreme and NetLink product lines, the tg3 driver is now the only Linux driver that Broadcom supports. Accordingly, Broadcom has discontinued support for the bcm5700 driver and no longer provides updates.

Due to limitations in Microsoft's operating systems not supporting the Virtual Bus Device architecture of the NetXtreme II adapter under certain circumstances, separate drivers were created to address these limitations. The NetXterme II monolithic driver allows the adapter to behave similarly to standard network adapters and only provides network connectivity without the advanced offerings of the device. The monolithic driver should be used for connectivity during the text mode portion of a RIS installation (by placing in the I386 or MAD directory), in a Windows Pre-Installation Environment (PE), and for the agent used for Microsoft's Automated Deployment Services. There are no additional special instructions necessary when these drivers are used in the above scenarios.

Currently, Microsoft does not support assigning network properties through an answer file for devices that use a virtual bus when using the PCI Bus Number, Device Number, and Function Number as the network adapter's identifier. Due to the current and future advanced offerings of the NetXtreme II adapter, the use of a virtual bus device was required. Please refer to Microsoft Knowledge Base Article 920293 at http://support.microsoft.com/kb/920293/en-us for information on its proposed workaround based on the current operating system limitation.

There was a compatibility issue between MSVS and IPMI. The issue has been addressed in the latest drivers posted on our website: http://www.broadcom.com/support/ethernet_nic/netxtremeii.php

Microsoft Knowledge Base Article 326152 (http://support.microsoft.com/kb/326152/) indicates that Gigabit Ethernet adapters may experience problems with connectivity to a domain controller due to link fluctuation while the driver initializes and negotiates link with the network infrastructure. The link negotiation is further affected when the Gigabit adapters are participating in an 802.3ad team due to the additional negotiation with a switch required for this team type. As suggested in the Knowledge Base Article above, disabling media sense as described in a separate Knowledge Base Article 239924 (http://support.microsoft.com/kb/239924/) has shown to be a valid workaround when this problem occurs.

The Broadcom 5700, 5701, and 5702 devices are only supported in Vista and Windows Server 2008 using drivers originally intended for Windows XP and/or Windows Server 2003. Although Windows Vista and Windows Server 2008 are backward compatible to use drivers from the previous operating systems, Microsoft's NDIS 5.1 to NDIS 6 translation layer used to do so inhibits the feature from working properly.

Windows XP and 2003 Server does not recognize an IPv6 neighbor solicitation packet as a valid wake up frame. If the sender of the interesting packet does not have the MAC address of the adapter in the system you're trying to wake, this packet will be sent out similarly to an ARP packet would with the IPv4 protocol. Windows Vista and later does not exhibit this limitation.

This is due to the fact that BASP expects to have one and only one binding to the miniport driver, in this case some other 3rd party driver has binding to the miniport. This is usually seen when an anti-virus driver is installed. Please ensure there are no other drivers bound to the mini-port driver, if you want to use BASP teaming Software. To see if there are any 3rd party drivers bound to the miniport driver, open device manager, click on show hidden devices, Network Adapters.

The IPv6 Helper Service within the OS may take too long to start or not start correctly. This may occur when multiple VNICs/VLANs have been created on a system where the IPv6 driver has been installed. When the IPv6 driver, which is not native to Windows Server 2003 SP2, binds to many network adapters, it stops responding to all TCP/IPv6 requests.
Applying Microsoft hotfix KB 968597 (http://support.microsoft.com/kb/968597) will resolve the issue.

The inbox driver supplied in Windows Server 2008 R2 for the NetXtreme II 1Gb device does not contain support for iSCSI devices. Updated drivers from your manufacturer or through our website should contain the necessary drivers for this device.

To find out the current version of the bnx2 or bnx2x driver:

1. esxupdate query --vib-view

To load or unload bnx2 or bnx2x drivers manually:

1. vmkload_mod bnx2 or bnx2x (load driver)
2. vmkload_mod bnx2 or bnx2x (unload driver)

To upgrade bnx2 or bnx2x drivers:

1. esxupdate update -bundle=<filename> --maintenancemode
2. After the update is complete, reboot ESX.

To remove bnx2 or bnx2x drivers:

1. esxupdate query --vib-view (to query the driver version)
2. esxupdate -b <driver filename> remove

To add a vSwitch and assign a virtual NIC as an uplink network:

1. esxcfg-vswitch -a <vSwitch1> (add virtual switch)
2. esxcfg-vswitch -L <vmnicX> <vSwitch1> (assign virtual NIC to the virtual switch)
3. esxcfg-vswitch --add-pg="Console1" vSwitch1 (assign a new portgroup)

To assign an IP to an interface:

1. esxcfg-vswif -a -I <IP_address> -n <Netmask> -p "Console1" vswif1

To assign an IPv6 to an interface:

1. Lsmod -l|grep ipv6 (ensure IPv6 modprobe is loaded)
2. ifconfig vswifX inet6 add 3ffe::101/96 up

To change the port speed as below steps:

1. esxcfg-nics -s 1000 -d full vmnicX
2. esxcfg-nics -l (to observe new speed setting)

To open firewall:

1. esxcfg-firewall --allowOutgoing
2. esxcfg-firewall --allowIncoming

To configure jumbo frame on virtual NIC and virtual switch:

1. ifconfig vswifX mtu <size>
2. esxcfg-vswitch -m <size> vSwitchX

To configure FPT, ensure your system supports and has Virtual Technology enabled.

1. Login to ESX via the VMware vSphere client.
2. Navigate to the host configuration tab and then click on the "Advanced Settings"option on the left column.
3. The PCI devices will be displayed and select the desired NIC.
4. Reboot the ESX server.
5. Add the desired NIC as a PCI device to the appropriate virtual machine.
6. Power on virtual machine and load the driver.