Checking for Network Link and Activity
Checking if Current Drivers are Loaded
Software Problems and Solutions
NOTE: For additional information, go to Broadcom Ethernet NIC Frequently Asked Questions at http://www.broadcom.com/support/ethernet_nic/faq_drivers.php
Loopback diagnostic tests are available for testing the adapter hardware. These tests provide access to the adapter internal/external diagnostics, where packet information is transmitted across the physical link (for instructions and information on running tests in an MS-DOS environment, see User Diagnostics. For Windows environments, see Running Diagnostic Tests).
If any of the following tests fail while running the diagnostic tests from the Running Diagnostic Tests tab in BACS 3, this may indicate a hardware issue with the NIC or LOM that is installed in the system.
Below are troubleshooting steps that may help correct the failure.
Typically, the BACS 3 Testing the Network failures are the result of a configuration problem on the network or with the IP addresses. Below are common steps when troubleshooting the network.
CAUTION! Before you open the case of your system, review Safety Precautions.
The following checklist provides recommended actions to take to resolve problems installing the Broadcom NetXtreme Gigabit Ethernet adapter or running it in your system.
See Testing Network Connectivity or Viewing Vital Signs to check the state of the network link and activity as indicated by the port LEDs.
See Viewing Vital Signs to view useful information about the adapter, its link status, and network connectivity.
To verify that the driver is loaded properly, type
LOAD B57.LAN FRAME_ETHERNET_II NAME=B57_1_EII
This command automatically verifies if the link is active. If the link is active, the command returns Link is up.
From the command line, type config
then press ENTER. The following status information is displayed:
Broadcom NetXtreme Gigabit Ethernet Adapter
Version:
Hardware Setting:
Node Address:
Frame Type:
Board Name:
LAN Protocol: ARP (see note)
LAN Protocol: IP Addr: (see note)
NOTE: The LAN protocol status is displayed after an IP address is assigned to the adapter.
To verify that the TG3 Linux driver is loaded properly, run:
lsmod | grep tg3
If the driver is loaded, a line similar to the one below is displayed, where size is the size of the driver in bytes, and n is the number of adapters configured.
In Windows environments, a cable length test can be run. See Analyzing Cables for information about running a cable length test.
NOTE: When using forced link speeds, verify that both the adapter and the switch are forced to the same speed, or that both sides are configured for auto-negotiation.
Use the ping command to determine if the network connection is working.
NOTE: Network connectivity can also be tested using the Testing the Network feature in Broadcom Advanced Control Suite 2.
The ping statistics that are displayed indicate whether the network connection is working or not.
Ping an IP host on the network to verify connection has been established:
From the command line, type ping IP address, and then press ENTER.
The ping statistics that are displayed indicate whether the network connection is working or not.
To verify that the Ethernet interface is up and running, run ifconfig to check the status of the Ethernet interface. It is possible to use netstat -i to check the statistics on the Ethernet interface. Go to Linux Driver Software for information on ifconfig and netstat.
Ping an IP host on the network to verify connection has been established:
From the command line, type ping IP address, and then press ENTER.
The ping statistics that are displayed indicate whether the network connection is working or not.
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.
[Unattended]
OemPreinstall = yes
OemPnpDriversPath = \Drivers\Nic
net stop binlsvc
net start binlsvc
Problem: The following message is received when attempting to deploy a RIPREP image through Remote Installation Services (RIS): "The operating system image you selected does not contain the necessary drivers for your network adapter. Try selecting a different operating system image. If the problem persists, contact your administrator. Setup cannot continue. Press any key to exit."
Solution: This problem is not isolated to the Broadcom adapter. However, based on several inquiries, we are publishing the following instructions based on other customers successfully working around this issue:
Example: i:\RemoteInstall\Setup\English\Images\(Original Image)
Example: i:\RemoteInstall\Setup\English\Images\(Original Image)\i386
Example: i:\RemoteInstall\Setup\English\Images\(RIPREP Image)
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
OemPreinstall = yes
OemPnPDriversPath = "Drivers
DriverSigningPolicy = Ignore
OemPreinstall = yes
OemPnPDriversPath = "Drivers
DriverSigningPolicy = Ignore
net stop binlsvc
net start binlsvc
Problem: I want to be sure that my Broadcom NetXtreme adapter works properly if I use the System Preparation utility (Sysprep.exe) to install an existing configuration on my system.
Solution: On the Sysprep.inf file, modify the [Unattend] header as shown below:
[Unattend]
OemPnPDriversPath=Drivers\Net
OemPreinstall = Yes
The driver files for the Broadcom NetXtreme adapter must reside in this folder, which is located on 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:
Example:
OemPnpDriversPath=Drivers\Video;Drivers\Net
For Windows XP, the driver files to be included are B57win32.inf, B57win32.cat, and B57xp32.sys.
For Windows 2000, the driver files to be included are B57win32.inf, B57win32.cat, and B57w2k.sys.
The Sysprep utility must run with the pnp switch, which enables the system to rescan for new devices that can be added during the mini-setup.
A Sample Sysprep.inf file 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
------------------------------------------------------------------------
Problem: I brought down the interface and now I cannot bring it back up. When I try, the following message appears, `SIOCSIFFLAGS: Resource temporarily unavailable.'
Solution: When ASFIPMon is running, it does a quick access to flash ROM every 30 seconds or so. If the interface is brought down while this is happening, you cannot bring the interface back up in the usual way. To bring up the interface, unload and then reload the driver module.
Problem: Unable to obtain network settings through DHCP using PXE.
Solution: For proper operation make sure that the Spanning Tree Protocol (STP) is disabled or that portfast mode (for Cisco) is enabled on the port to which the PXE client is connected. For instance, set spantree portfast 4/12 enable.
Problem: The 802.3ad team member links disconnect and reconnect continuously (applies to all operating systems).
Solution: This is a third-party issue. It is seen only when configuring an 802.3ad team with more than 2 members on the system and connecting to an HP2524 switch, with LACP enabled as passive or active. The HP switch shows an LACP channel being brought up successfully with only 2 team members. All other team member links disconnect and reconnect. This does not occur with a Cisco Catalyst 6500.
Problem: A Generic Trunking (GEC/FEC) 802.3ad-Draft Static type of team may lose some network connectivity if the driver to a team member is disabled.
Solution: If a team member supports underlying management software (ASF/IPMI/UMP) or Wake-On-LAN, the link may be maintained on the switch for the adapter despite its driver being disabled. This may result in the switch continuing to pass traffic to the attached port rather than route the traffic to an active team member port. Disconnecting the disabled adapter from the switch will allow traffic to resume to the other active team members.
Problem: The teaming changes I made when I modified my team using INETCFG did not take effect.
Solution: When you modify a team using INETCFG, you may need to reboot after reinitialization for the changes to the team to take effect.
Problem: Although installled, the Broadcom Advanced Control Suite 3 (BACS) application does not start.
Solution: .NET Framework 2.0 is required for BACS 3 to operate. Install .NET Framework 2.0.
Problem: When the bus on the system is operating in PCI mode, the Broadcom NetXtreme Gigabit Ethernet adapter performs at PCI mode if it is added after the system has booted.
Solution: When the system is booted up without any adapter, the bus operates at the lowest mode, which is PCI mode. Reboot the system after the adapter has been added.
Problem: The Broadcom NetXtreme Gigabit Ethernet adapter may not perform at optimal level on some systems if it is added after the system has booted.
Solution: The system BIOS in some systems does not set the cache line size and the latency timer if the adapter is added after the system has booted. Reboot the system after the adapter has been added.
Problem: Large Send Offload (LSO) and Checksum Offload are not working on my team.
Solution: If one of the adapters on a team does not support LSO, LSO does not function for the team. Remove the adapter that does not support LSO from the team, or replace it with one that does. The same applies to Checksum Offload.
Problem: When using the TG3 driver and Red Hat 4 (with any release prior to release 6), after setting the speed and duplex with ethtool, autonegotiation is disabled and cannot be restored.
Solution: Unload or reload the TG3 driver, or upgrade to the latest version of ethtool.
Problem: A DCOM error message (event ID 10016) appears in the System Even Log during the installation of the Broadcom adapter drivers.
Solution: This is a Microsoft issue. For more information, see Microsoft knowledge base KB913119 at http://support.microsoft.com/kb/913119.