This chapter provides the following information:
Checking
if Correct Drivers are Loaded
Software
Problems and Solutions
The adapter has four LEDs, one for each
port speed option (10 Mbps, 100 Mbps, and 1 Gbps), and one for Activity. The
three port speed LEDs indicate active links, and the Activity LED indicates
data transfer status. Once the driver is loaded and the cables are connected
properly, the appropriate speed LED is lit and the data LED is on if data traffic
is present.
Before the port LEDs can provide troubleshooting information, the adapter must be connected to the network (see "Installing the Hardware"), and the network drivers for your particular operating system must be installed.
LED | State | Description |
1000 | On | Good Gigabit Ethernet link. |
Off | No 1000 Mbps link; possible link at different speed, possible bad cable, bad connector, or configuration mismatch. | |
100 | On | Good 100 Mbps Fast Ethernet link. |
Off | No 100 Mbps link; possible link at different speed, possible bad cable, bad connector, or configuration mismatch. | |
10 | On | Good 10 Mbps Fast Ethernet link. |
Off | No 10 Mbps link; possible link at different speed, possible bad cable, bad connector, or configuration mismatch. | |
ACT | Blinking | Brief bursts of data detected on the port. |
On | Streams of data detected on the port. | |
Off | No data detected on the port. |
The adapter has two LEDs, one for each Activity (ACT and LINK). The ACT LED indicates data transfer status. Once the adapter is installed and the cables are connected properly, the speed LED is lit and the ACT LED is on if data traffic is present. The LINK LED indicates the port speed option (10 Mbps, 100 Mbps, and 1000 Mbps) for ports 0 and 1.
Before the port LEDs can provide troubleshooting information, the adapter must be connected to the network (see "Installing the Hardware"), and the network drivers for your particular operating system must be installed.
Table 3. Gigabit Ethernet Port LED Status
for Ports 1 and 2 (5704 only)
LED | State | Description |
ACT | Blinking | Brief bursts of data detected on the port. |
On | Streams of data detected on the port. | |
Off | No data detected on the port. | |
LINK | On | Good 10, 1000, and 1000 Mbps Fast Ethernet link. |
Off | No link; possible link at different speed, possible bad cable, bad connector, or configuration mismatch. |
![]() |
WARNING — Before opening the cabinet of your system for removing or inserting the adapter, please review all precautions outlined under "Safety Precautions." |
The following checklist provides recommended actions to take to resolve problems installing the Gigabit Ethernet Adapter or running it in your system.
The following section describes how to check if the correct drivers are loaded for Windows, NetWare, and Linux.
The Broadcom Advanced Control Suite, Vital Sign screen allows you to view vital adapter information, network status, and network connectivity. Active adapters are listed.
![]() |
NOTE – Information for non-Broadcom adapters is less comprehensive than information listed for Broadcom adapters. |
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, and if so displays "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 appears after assigning an IP address to the adapter (i.e., bind). |
To verify that the bcm5700.o driver is loaded properly, run
lsmod
If
the driver is loaded, a line similar to the one below appears, where <size>
Module
|
Size
|
Used by
|
BCM5700
|
<size>
|
<n>
|
To verify that the bcme driver is loaded properly, run
modinfo | grep bcme
A line appears showing that the driver is loaded.
The following section describes how to test network connectivity for Windows 2000, Windows Server 2003, NetWare, and Linux.
![]() |
NOTE – Ensure that when using forced link speeds, that both the adapter and switch are forced to the same speed OR at least one link partner is configured for Auto-negotiation. |
![]() |
NOTE – Network connectivity can also be tested using the Network Test feature on the Broadcom Advanced Control Suite. |
Use the ping command to determine if network connectivity is working.
Ping an IP host on the network to verify connection has been established:
From the command line, type ping <IP address>, then press Enter.
This will display the packet send/receive status.
To verify that the Ethernet interface is up and running, run 'ifconfig' to check the status of the Ethernet interface. 'netstat -i' can also be used to check the statistics on the Ethernet interface. Consult manual pages for more 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>, then press Enter.
This will display the packet send/receive status.
This section provides a list of known software problems and solutions for the operating systems below.
The following table lists know problems and solutions using Windows 2000 or Windows Server 2003:
Problem: Able to create Broadcom LAC connections icons having same name under network properties menu. |
Solution: In Windows 2000, each network adapter installed properly will have an icon in Network Properties window. The name of the icon is usually in the form of "Local Area Connection ##" and where ## is a number starting from 1. The names of icon can be changed by right clicking the icon and selecting rename. The name of the icon is only meaningful to the Network Properties window. Sometimes the system administrators will rename these icons to easily differentiate the network connections. When BASP is configured, BASP will create additional adapter icons and rename the icons. The naming convention is to allow end users to quickly identify the adapter with corresponding team and VLAN. The names of the icons created by BASP therefore are not recommended to be changed. |
Problem: Uninstalling the BASP software and user is prompted to reboot early |
Solution: In Windows 2000, after configuring BASP team, the system may sometimes prompt user to reboot. This is because Plug and Play on W2k may fail to commit any change in the network protocol binding. Users can choose not to reboot and continue configuring intermediate driver without having any side effect. When user has finished all the configuration, it is required to reboot. |
Problem: Cannot enable VLAN after it is disabled |
Solution: In Windows 2000, BASP creates additional network connections in "Network Connection and Dail-up" Window. Similar to physical network connections, these virtual connections can be disabled via the context menu. However, if these virtual connections are re-enabled, the system will report error as "connection failed!". This is known problem with Windows 2000. When this happens, reboot the system will enable the virtual connection again. |
Problem: Able to configure Internet Connection Sharing (ICS) when there aren't any unassigned adapters. | Solution: Windows 2000 networking is shipped with the Internet Connection Sharing (ICS), which is designed to allow multiple computers accessing the Internet via a Windows 2000 system. To configure ICS, a user would need to select a network connection as "outside" connection, and another network connection as "inside" connection. Broadcom has observed that ICS allow any available network connection to be "outside" and "inside" connection, regardless of the BASP team configuration. Broadcom recommends that the user not select any network connection that is part of the BASP team to be "outside" and "inside." |
Problem: Team configuration is not retained when user goes back to edit. |
Solution: In configuring BASP team configuration, the actual changes of the configuration is not committed until the user click "OK" in "Network Properties" window. If a user chooses not click OK and instead goes back to the BASP team configuration window, all the previous uncommitted changes will be lost and user will need to reenter the configurations. As a workaround, the user should always click "OK" in "Network Properties" window after making changes. |
Problem: IP address is configurable on a member of the team. |
Solution: When a team is created, the TCP/IP properties for the adapters are unselected. The user can manually select and configure TCP/IP properties of the adapters and configure an IP address. This is a limitation of the Windows 2000 network installation paradigm, where this invalid configuration is still allowed. |
Problem: When creating 64 VLANs, all virtual adapters show disconnected or one of the 64 VLANs show disabled. |
Solution: The maximum VLAN configurations are 63 tagged and one untagged VLAN ID 0. If 64 tagged VLANs are created, they are disconnected. A reboot is required and only 63 tagged VLANs show links, while a 64th is disabled. |
The following table lists known problems and solutions using Linux:
Linux-Basp |
|||
Problem: When obtaining the IP for a SLB's virtual interface via DHCP, the IP-gets lost under heavy traffic. |
Solution: Always set a static IP for all the virtual interfaces in a SLB team. |
||
Problem: Make install fails on Turbo Linux 7.0 IA64. |
Solution: The symbolic link under /lib/modules/<kernel-version>/build
points to an |
||
Linux-Core |
|||
Problem: Compiling the driver fails under SuSE's 7.x. |
Solution: If compiling the driver under SuSE's 7.x distributions and errors are reported, follow the general guidelines below to rebuild the kernel source tree:
where <kernel_version>
is the actual kernel version used in the SuSE distribution.
|
||
Problem: Zero copy performance is low on Red Hat 7.1. |
Solution: Red
Hat 7.1 loads the ipchains module by default. IPCHAINS is not Example:
|
The following table lists known Broadcom Boot Agent problems and solutions:
Problem: Unable to obtain network settings through DHCP using PXE. |
Solution: For proper operation make sure that the STP (spanning tree protocol) is disabled or portfast mode (for Cisco) is enabled on the port to which the PXE client is connected. For instance, set spantree portfast 4/12 enable. |
The following table lists known BASP problems and solutions that apply to all operating systems:
Problem: 802.3ad team
member links disconnect and reconnect |
Solution: This is a
3rd party issue. It is seen only when configuring an 802.3ad team This does not occur with a Cisco Catalyst 6500. |
||
Problem: When members of a team consist of other vender's adapters, the team fails to failover and load balance theIPX traffic |
Solution: IPX failover and load balance is only supported when
all members of the team |
The following table lists known UnixWare problems and solutions:
Problem:
In some instances with a Broadcom LOM, when you try to add the LAN adapter,
multiple devices may show up. |
Solution: Login as root
and run "/sbin/resmgr |more" You should see the following:
|
The following table lists known miscellaneous problems and solutions:
Problem: When the bus on the system is operating at PCI mode, Broadcom NetXtreme Gigabit Ethernet will perform at PCI mode if it is added by Hot Plug. |
Solution: When the system is booted up without any adapter, the bus will operate at the lowest mode which is PCI. This problem can be overcome by rebooting the system. |
||
Problem: The Broadcom NetXtreme Gigabit Ethernet adapter may not perform at optimal level when it is added by Hot Plug on some system. |
Solution: This is because the system BIOS in some system does not set the cache line size and the latency timer, after the adapter is added by Hot Plug. This problem can be overcome by rebooting the system. |
||
Problem: The Broadcom NetXtreme Gigabit Ethernet adapter can not be seen on the PCI BUS. |
Solution: This is because some of the older servers are advertising themselves as PCI-X capable systems. This causes the NetXtreme network adapter to operate in PCI-X mode; therefore; not to be seen by the PCI bus. This problem can be overcome by configuring the firmware to operate in forced pci mode. Refere to b57diag for configuration instructions. |