Dell Broadcom NetXtreme Family of Adapters, Broadcom NetXtreme 57XX Series User Manual

Broadcom NetXtreme® 57XX User Guide

The information below is provided by the supplier of the referenced device without independent verification by Dell and is
subject to the Restrictions and Disclaimers noted below.

Introduction

Functionality and Features
Teaming
Virtual LANs (VLANs)

Manageability

Installing the Hardware
Installing the Driver Software

Creating a Driver Disk

Broadcom Boot Agent Driver Software

NDIS2 Driver Software

ODI Driver Software

Linux Driver Software

NetWare Driver Software

Installing Windows Driver and Management Applications
Using iSCSI
Configuring Teaming
Using Broadcom Advanced Control Suite 3
Specifications
Regulatory Information
User Diagnostics
Troubleshooting

Information in this document is subject to change without notice.
© 2010 Broadcom Corporation. All rights reserved.

Trademarks used in this text: Broadcom, NetXtreme, Ethernet@Wirespeed, LiveLink, and Smart Load Balancing are among
the trademarks of Broadcom Corporation and/or its affiliates in the United States, certain other countries, and/or the EU. Dell
and the DELL logo are trademarks of Dell Inc. Microsoft and Windows are trademarks of Microsoft Corporation. Linux is a
trademark of Linus Torvalds. NetWare is a trademark of Novell Corporation. Intel is a trademark of Intel Corporation. Magic
Packet is a trademark of Advanced Micro Devices, Inc. Red Hat is a trademark of Red Hat, Inc. PCI Express is a trademark of
PCI-SIG. Any other trademarks or trade names mentioned are the property of their respective owners.

Restrictions and Disclaimers

The information contained in this document, including all instructions, cautions, and regulatory approvals and certifications, is
provided by the supplier and has not been independently verified or tested by Dell. Dell cannot be responsible for damage
caused as a result of either following or failing to follow these instructions. All statements or claims regarding the properties,
capabilities, speeds or qualifications of the part referenced in this document are made by the supplier and not by Dell. Dell
specifically disclaims knowledge of the accuracy, completeness or substantiation for any such statements. All questions or
comments relating to such statements or claims should be directed to the supplier.

Export Regulations

Customer acknowledges that these Products, which may include technology and software, are subject to the customs and

export control laws and regulations of the United States ("U.S.") and may also be subject to the customs and export laws and

regulations of the country in which the Products are manufactured and/or received. Customer agrees to abide by those laws
and regulations. Further, under U.S. law, the Products may not be sold, leased or otherwise transferred to restricted end­users or to restricted countries. In addition, the Products may not be sold, leased or otherwise transferred to, or utilized by an
end-user engaged in activities related to weapons of mass destruction, including without limitation, activities related to the
design, development, production or use of nuclear weapons, materials, or facilities, missiles or the support of missile projects,
and chemical or biological weapons.

Last revised: January 2010

2CS57XX-CDUM506-R

Back to Contents Page

Functionality and Features: Broadcom NetXtreme 57XX User
Guide

Functional Description
Features
Supported Operating Environments
Network Link and Activity Indication

Functional Description

Broadcom NetXtreme Gigabit Ethernet adapters connect a PCI, PCI-X (BCM5701 and BCM5703), or PCI Express™ (BCM5751,
BCM5721, and BCM5722) compliant system to a Gigabit Ethernet network. Broadcom NetXtreme Gigabit Ethernet adapters
incorporate a technology that transfers data at a maximum rate of 1 gigabit per second—10 times the rate of Fast Ethernet
adapters.

Broadcom NetXtreme Gigabit Ethernet adapters target the increased congestion experienced at the backbone and system in
today's networks and provide a future upgrade path for systems that require more bandwidth than Fast Ethernet can provide.

Using the Broadcom teaming software, you can split your network into virtual LANs (VLANs) as well as group multiple network
adapters together into teams to provide network load balancing and fault tolerance functionality. See Teaming and Broadcom

Gigabit Ethernet Teaming Services for detailed information about teaming. See Virtual LANs for a description of VLANs. See
Configuring Teaming for instructions on configuring teaming and creating VLANs on Windows and NetWare operating systems.

Features

The following is a list of the Broadcom NetXtreme Gigabit Ethernet adapter features for all supported operating systems:

PCI Express™ x1 Lane support (BCM5751, BCM5721, and BCM5722)
Gigabit Ethernet (IEEE Std 802.3-1999)
Logical Link Control (IEEE Std 802.2)
Flow Control (IEEE Std 802.3x)
Standard Ethernet frame size (1518 bytes)
TBI (SerDes style) transceiver interfaces (except for BCM5721, BCM5751, and BCM5722)
Jumbo frames (up to 9 KB) (except for BCM5721, BCM5751, and BCM5722); NetWare 5.1 does not support Jumbo

frames.
Layer-2 Priority Encoding (IEEE 802.1p)
High-speed on-chip RISC processor
Adaptive interrupt frequency
Up to 4 classes of service (CoS)
Up to 4 send rings and receive rings
Integrated 96 KB frame buffer memory
GMI/MII Management Interface
Statistics for SNMP MIB II, Ethernet-like MIB, and Ethernet MIB (IEEE Std 802.3z, Clause 30)
4 unique MAC unicast addresses
Support for multicast addresses via 128 bits hashing hardware function
Serial EEPROM or serial NVRAM flash memory
Supports PXE 2.1 specification (Linux Red Hat PXE Server, Windows Server 2003, Intel APITEST, DOS UNDI)
JTAG support

PCI v2.3 32/64-bit, 33/66 MHz Bus Interface (BCM5701, BCM5703)

PCI-X v1.0 64-bit 100/133 MHz Bus Interface (BCM5701, BCM5703)
PCI Power Management Interface (v1.1)
PCI Hot-Plug (IBM, Compaq, Dell, and Microsoft)

NOTE: The Dell hot-plug feature is Dell system-dependent.

ACPI and Wake on LAN support
64-bit BAR support
EM64T processor support

3.3 V/1.8 V CMOS with 5V tolerant I/Os
LiveLink™ (supported in both the 32-bit and 64-bit Windows operating systems
Self boot

Power Management

Wake on LAN (Magic Packet, Wake Up Frame, specific pattern) is supported at 10/100 Mbps operation only.

NOTES:

Adapter speed connection when the system is down waiting for a wake-up signal is either 10 Mbps or 100 Mbps,

but can return to 1000 Mbps when the system is up and running if connected to a 1000 Mbps capable switch.

Systems intending to use Wake on LAN (WOL) should be connected to a switch capable of both 1000 and 10/100

Mbps speeds.

Dell supports Wake on LAN on one adapter in the system at a time.

Adaptive Interrupt Frequency

The adapter driver intelligently adjusts host interrupt frequency based on traffic conditions, to increase overall application
throughput. When traffic is light, the adapter driver interrupts the host for each received packet, minimizing latency. When
traffic is heavy, the adapter issues one host interrupt for multiple, back-to-back incoming packets, preserving host CPU
cycles.

Dual DMA Channels

The PCI interface on Broadcom NetXtreme Gigabit Ethernet adapters contains two independent DMA channels for simultaneous
read and write operations.

32-Bit or 64-Bit PCI Bus Master

Compliant with PCI Local Bus Rev 2.3, the PCI interface on Broadcom NetXtreme Gigabit Ethernet adapters is compatible with
both 32-bit and 64-bit PCI buses. As a bus master, the adapter requests access to the PCI bus, instead of waiting to be
polled.

ASIC with Embedded RISC Processor

The core control for Broadcom NetXtreme Gigabit Ethernet adapters resides in a tightly integrated, high-performance ASIC.
The ASIC includes a RISC processor. This functionality provides the flexibility to add new features to the card and adapts it to
future network requirements through software downloads. This functionality also enables the adapter drivers to exploit the
built-in host offload functions on the adapter as host operating systems are enhanced to take advantage of these functions.

Broadcom Advanced Control Suite 3

Broadcom Advanced Control Suite 3 (BACS 3), a component of the Broadcom teaming software, is an integrated utility that
provides useful information about each network adapter that is installed in your system. The BACS 3 utility also enables you
to perform detailed tests, diagnostics, and analyses on each adapter, as well as to modify property values and view traffic
statistics for each adapter. BACS 3 is used on Windows operating systems to configure teaming and to add VLANs. See Using

Broadcom Advanced Control Suite 3 for detailed information and instructions.

Supported Operating Environments

The Broadcom NetXtreme Gigabit Ethernet adapter has software support for the following operating systems:

Microsoft® Windows® (32-bit and 64-bit extended)
Linux® (32-bit and 64-bit extended)
MS-DOS
NetWare

Sun Solaris
SCO® UnixWare
SCO OpenServer

®

®

®

®

Network Link and Activity Indication

For copper-wire Ethernet connections, the state of the network link and activity is indicated by the LEDs on the RJ-45
connector, as described in Table 1: "Network Link and Activity Indicated by RJ-45 Port LEDs". Broadcom Advanced Control
Suite 3 also provides information about the status of the network link and activity (see Viewing Vital Signs).

Table 1. Network Link and Activity Indicated by RJ-45 Port
LEDs

Port LED LED Appearance Network State

Link LED

Activity LED

Off No link (cable disconnected)
Continuously illuminated Link
Off No network activity
Blinking Network activity

Please read all Restrictions and Disclaimers.

Back to Contents Page

Back to Contents Page

Teaming: Broadcom NetXtreme 57XX User Guide

Overview
Load Balancing and Fault Tolerance

NOTE: See Broadcom Gigabit Ethernet Teaming Services for detailed information on the following topics:

Glossary of Terms and Acronyms

Teaming Concepts

Software Components

Hardware Requirements

Supported Teaming by Processor

Configuring Teaming by Operating System

Supported Features by Team Type

Selecting a Team Type

Teaming Mechanisms

Architecture

Types of Teams

Driver Support by Operating System

Supported Teaming Speeds

Teaming and Other Advanced Networking Features

General Network Considerations

Application Considerations

Troubleshooting Teaming Problems

Frequently-Asked Questions

Event Log Messages

Overview

Adapter teaming allows you to group network adapters together to function as a team. The benefits of teaming include
allowing membership to VLANs, providing load balancing between adapters, and offering fault tolerance. These benefits can
be combined such that you can couple the functionality of load balancing for the load balance members and the capability of
employing a failover with having the team participate on different VLANs.

Broadcom Advanced Server Program (BASP) is the Broadcom teaming software for Windows Server 2003, Windows Server
2008, and NetWare operating systems. For Windows operating systems, BASP is configured through the Broadcom Advanced

Control Suite 3 (BACS 3) utility. For NetWare operating systems, teams are configured by loading BASP with all the necessary

frames for the team (see Configuring Teaming). For Linux operating systems, teaming is done with channel bonding (see

Teaming with Channel Bonding).

BASP supports four types of load balancing teams:

Smart Load Balancing and Failover
Link Aggregation (802.3ad)
Generic Trunking (FEC/GEC)/802.3ad-Draft Static
SLB (Auto-Fallback Disable)

NOTE: Enabling Windows Server 2003 built-in bridging is not advisable when you are using teaming software.

Load Balancing and Fault Tolerance

Teaming provides traffic load balancing and fault tolerance (redundant adapter operation in the event that a network
connection fails). When multiple adapters are installed in the same system, they can be grouped with up to four teams.

Each team can consist of up to eight adapters, with one adapter used as a standby for Smart Load Balancing and Failover
(SLB) or SLB (Auto-Fallback Disabled) team types. If traffic is not identified on any of the adapter team member connections
due to failure of the adapter, cable, or switch, the load will be distributed to the remaining team members with an active
connection. In the event that all primary adapters fail, traffic will be distributed to the standby adapter. Existing sessions are
maintained with no impact on the user.

Types of Teams

The available types of teams for the supported operating systems are shown in the following table:

Table 1. Types of Teams

Operating
System

Windows Server
2003
Windows Server
2008

Linux

NetWare

Available Types of Teams

Smart Load Balancing and Failover
Link Aggregation (802.3ad)
Generic Trunking (FEC/GEC)/802.3ad-Draft Static
SLB (Auto-Fallback Disable)

Team adapters using the bonding kernel module and a channel bonding interface. See your Red Hat
documentation for more information.

Smart Load Balancing
Link Aggregation (802.3ad)
Generic Trunking

Smart Load Balancing™ and Failover

Smart Load Balancing™ and Failover is the Broadcom implementation of load balancing based on IP flow. This feature
supports balancing IP traffic across multiple adapters (team members) in a bidirectional manner. In this type of team, all
adapters in the team have separate MAC addresses. This type of team provides automatic fault detection and dynamic failover
to other team member or to a hot standby member. This is done independently of Layer 3 protocol (IP, IPX, NetBEUI);
rather, it works with existing Layer 2 and Layer 3 switches. No switch configuration (such as trunk, link aggregation) is
necessary for this type of team to work.

NOTES:

If you do not enable LiveLink™ when configuring SLB teams, disabling Spanning Tree Protocol (STP) at the

switch or port is recommended. This minimizes the downtime due to spanning tree loop determination when

failing over. LiveLink mitigates such issues.

IPX balances only on the transmit side of the team; other protocols are limited to the primary adapter.

If a team member is linked at 1000 Mbit/s and another team member is linked at 100 Mbit/s, most of the traffic

is handled by the 1000 Mbit/s team member.

Link Aggregation (802.3ad)

This mode supports link aggregation and conforms to the IEEE 802.3ad (LACP) specification. Configuration software allows
you to dynamically configure which adapters you want to participate in a given team. If the link partner is not correctly
configured for 802.3ad link configuration, errors are detected and noted. With this mode, all adapters in the team are
configured to receive packets for the same MAC address. The outbound load-balancing scheme is determined by our BASP
driver. The team link partner determines the load-balancing scheme for inbound packets. In this mode, at least one of the
link partners must be in active mode.

Generic Trunking (FEC/GEC)/802.3ad-Draft Static

The Generic Trunking (FEC/GEC)/802.3ad-Draft Static type of team is very similar to the Link Aggregation (802.3ad) type of
team in that all adapters in the team are configured to receive packets for the same MAC address. The Generic Trunking
(FEC/GEC)/802.3ad-Draft Static) type of team, however, does not provide LACP or marker protocol support. This type of team
supports a variety of environments in which the adapter link partners are statically configured to support a proprietary
trunking mechanism. For instance, this type of team could be used to support Lucent's OpenTrunk or Cisco's Fast
EtherChannel (FEC). Basically, this type of team is a light version of the Link Aggregation (802.3ad) type of team. This

approach is much simpler, in that there is not a formalized link aggregation control protocol (LACP). As with the other types of

teams, the creation of teams and the allocation of physical adapters to various teams is done statically through user
configuration software.

The Generic Trunking (FEC/GEC/802.3ad-Draft Static) type of team supports load balancing and failover for both outbound
and inbound traffic.

SLB (Auto-Fallback Disable)

The SLB (Auto-Fallback Disable) type of team is identical to the Smart Load Balancing and Failover type of team, with the
following exception—when the standby member is active, if a primary member comes back on line, the team continues using
the standby member, rather than switching back to the primary member.

If any primary adapter assigned to a team is disabled, the team functions as a Smart Load Balancing and Failover type of
team in which auto-fallback occurs.

All primary interfaces in a team participate in load-balancing operations by sending and receiving a portion of the total traffic.
Standby interfaces take over in the event that all primary interfaces have lost their links.

Failover teaming provides redundant adapter operation (fault tolerance) in the event that a network connection fails. If the
primary adapter in a team is disconnected because of failure of the adapter, cable, or switch port, the secondary team
member becomes active, redirecting both inbound and outbound traffic originally assigned to the primary adapter. Sessions
will be maintained, causing no impact to the user.

Limitations of Smart Load Balancing and Failover/SLB (Auto-Fallback Disable) Types of Teams

Smart Load Balancing™ (SLB) is a protocol-specific scheme. The level of support for IP, IPX, and NetBEUI protocols is listed
below.

Table 2. Smart Load Balancing

Operating System Failover/Fallback—All Broadcom Failover/Fallback—Multivendor
Protocol IP IPX NetBEUI IP IPX NetBEUI

Windows Server 2003 Y Y N/S Y N N/S
Windows Server 2008 Y Y N/S Y N N/S
NetWare 5.1/6.5 Y Y N/S Y N N/S
Red Hat Linux 4 Y N/S N/S Y N/S N/S

Operating System Load Balance—All Broadcom Load Balance—Multivendor
Protocol IP IPX NetBEUI IP IPX NetBEUI

Windows Server 2003 Y Y N/S Y N N/S
Windows Server 2008 Y Y N/S Y N N/S
NetWare 5.1/6.5 Y Y N/S Y Y N/S
Red Hat Linux 4 Y N/S N/S Y N/S N/S

Legend: Y = yes
N = no
N/S = not supported

Drivers for third-party network adapters must be NetWare Event Service Layer (NESL) compliant for NetWare to be fault­tolerant and load-balanced in a multivendor team.

The Smart Load Balancing type of team works with all Ethernet switches without having to configure the switch ports to any
special trunking mode. Only IP traffic is load-balanced in both inbound and outbound directions. IPX traffic is load-balanced in
the outbound direction only. Other protocol packets are sent and received through one primary interface only. Failover for
non-IP traffic is supported only for Broadcom network adapters. The Generic Trunking type of team requires the Ethernet
switch to support some form of port trunking mode (for example, Cisco's Gigabit EtherChannel or other switch vendor's Link
Aggregation mode). The Generic Trunking type of team is protocol-independent, and all traffic should be load-balanced and
fault-tolerant.

NOTE: If you do not enable LiveLink™ when configuring teams, disabling Spanning Tree Protocol (STP) at the switch is
recommended. This minimizes the downtime due to the spanning tree loop determination when failing over. LiveLink
mitigates such issues.

LiveLink™ Functionality

LiveLink™ functionality is a feature of BASP that is available only for the Smart Load Balancing™ and Failover type of
teaming. The purpose of LiveLink is to detect network connectivity beyond the switch and to route traffic only through team
members that have a live link. This function is accomplished though the teaming software (see Configuring LiveLink for a

Smart Load Balancing and Failover and SLB (Auto-Fallback Disable) Team). The teaming software periodically probes (issues

a link packet from each team member) one or more specified target network adapter(s). The probe target(s) responds when
it receives the link packet. If a team member does not detect a response within a specified amount of time after a specified
number of retries, the teaming software discontinues passing traffic through that team member. Later, if that team member
begins to detect a response from a probe target, this indicates that the link has been restored, and the teaming software
automatically resumes passing traffic through that team member. LiveLink works only with TCP/IP.

LiveLink™ functionality is supported in both 32-bit and 64-bit Windows operating systems, but is not supported in NetWare
systems. For similar functionality in Linux operating systems, refer to Channel Bonding in your Red Hat documentation.

Teaming and Large Send Offload/Checksum Offload Support

Large Send Offload (LSO) and Checksum Offload are enabled for a team only when all of the members support and are
configured for the feature.

Please read all Restrictions and Disclaimers.

Back to Contents Page

Back to Contents Page

Virtual LANs: Broadcom NetXtreme 57XX User Guide

VLAN Overview
Adding VLANs to Teams

VLAN Overview

Virtual LANs (VLANs) allow you to split your physical LAN into logical parts, to create logical segmentation of workgroups, and
to enforce security policies for each logical segment. Each defined VLAN behaves as its own separate network with its traffic
and broadcasts isolated from the others, increasing bandwidth efficiency within each logical group. Up to 64 VLANs (63
tagged and 1 untagged) can be defined for each Broadcom adapter on your server, depending on the amount of memory
available in your system.

VLANs can be added to a team to allow multiple VLANs with different VLAN IDs. A virtual adapter is created for each VLAN
added.

Although VLANs are commonly used to create individual broadcast domains and/or separate IP subnets, it is sometimes
useful for a server to have a presence on more than one VLAN simultaneously. Broadcom adapters support multiple VLANs on
a per-port or per-team basis, allowing very flexible network configurations.

Figure 1: Example of Servers Supporting Multiple VLANs with Tagging

Figure 1 shows an example network that uses VLANs. In this example network, the physical LAN consists of a switch, two

servers, and five clients. The LAN is logically organized into three different VLANs, each representing a different IP subnet.
The features of this network are described in Table 1:

Table 1: Example VLAN Network Topology

Component Description

VLAN #1 An IP subnet consisting of the Main Server, PC #3, and PC #5. This subnet represents an engineering group.
VLAN #2
VLAN #3 Includes the Main Server, the Accounting Server and PC #4. This VLAN is an accounting group.

Main Server

Includes the Main Server, PCs #1 and #2 via shared media segment, and PC #5. This VLAN is a software
development group.

A high-use server that needs to be accessed from all VLANs and IP subnets. The Main Server has a Broadcom
adapter installed. All three IP subnets are accessed via the single physical adapter interface. The server is
attached to one of the switch ports, which is configured for VLANs #1, #2, and #3. Both the adapter and the
connected switch port have tagging turned on. Because of the tagging VLAN capabilities of both devices, the
server is able to communicate on all three IP subnets in this network, but continues to maintain broadcast

separation between all of them.

Accounting
Server

PCs #1 and
#2

PC #3

PC #4

PC #5

NOTE: VLAN tagging is only required to be enabled on switch ports that create trunk links to other switches, or on ports
connected to tag-capable end-stations, such as servers or workstations with Broadcom adapters.

Available to VLAN #3 only. The Accounting Server is isolated from all traffic on VLANs #1 and #2. The switch
port connected to the server has tagging turned off.

Attached to a shared media hub that is then connected to the switch. PCs #1 and #2 belong to VLAN #2 only,
and are logically in the same IP subnet as the Main Server and PC #5. The switch port connected to this
segment has tagging turned off.

A member of VLAN #1, PC #3 can communicate only with the Main Server and PC #5. Tagging is not enabled
on PC #3 switch port.

A member of VLAN #3, PC #4 can only communicate with the servers. Tagging is not enabled on PC #4 switch
port.

A member of both VLANs #1 and #2, PC #5 has an Broadcom adapter installed. It is connected to switch port
#10. Both the adapter and the switch port are configured for VLANs #1 and #2 and have tagging enabled.

Adding VLANs to Teams

Each team supports up to 64 VLANs (63 tagged and 1 untagged). Note that only Broadcom adapters and Alteon® AceNIC
adapters can be part of a team with VLANs. With multiple VLANs on an adapter, a server with a single adapter can have a
logical presence on multiple IP subnets. With multiple VLANs in a team, a server can have a logical presence on multiple IP
subnets and benefit from load balancing and failover. For instructions on adding a VLAN to a team, see Adding a VLAN for
Windows operating systems or see Configuring VLANs for NetWare operating systems.

NOTE: Adapters that are members of a failover team can also be configured to support VLANs. Because VLANs are not
supported for an Intel LOM, if an Intel LOM is a member of a failover team, VLANs cannot be configured for that team.

Please read all Restrictions and Disclaimers.

Back to Contents Page

Back to Contents Page

Manageability: Broadcom NetXtreme 57XX User Guide

CIM
SNMP

CIM

The Common Information Model (CIM) is an industry standard defined by the Distributed Management Task Force (DMTF).
Microsoft implements CIM on Windows platforms such as Windows Server 2003 and Windows Server 2008. Broadcom will
support CIM on the Windows Server 2003 and Windows Server 2008 platforms.

Broadcom's implementation of CIM will provide various classes to provide information to users through CIM client applications.
Note that Broadcom CIM data provider will provide data only, and users can choose their preferred CIM client software to
browse the information exposed by Broadcom CIM provider.

Broadcom CIM provider provides information through BRCM_NetworkAdapter and BRCM_ExtraCapacityGroup classes.
BRCM_NetworkAdapter class provides network adapter information pertaining to a group of adapters, including both
Broadcom and other vendors' controllers. BRCM_ExtraCapacityGroup class provides team configuration for the Broadcom
Advanced Server Program (BASP) Program. Current implementation will provide team information and information of physical
network adapters in the team.

Broadcom Advanced Server Program provides events through event logs. Users can use the "Event Viewer" provided by
Windows Server 2003 Windows Server 2008, or use CIM to inspect or monitor these events. Broadcom CIM provider will also
provide event information through the CIM generic event model. These events are __InstanceCreationEvent,
__InstanceDeletionEvent and __InstanceModificationEvent, and are defined by CIM. CIM requires the client application to
register the events from the client application using queries, as examples shown below in order to receive events properly.

SELECT * FROM __InstanceModificationEvent
where TargetInstance ISA "BRCM_NetworkAdapter"
SELECT * FROM __InstanceModificationEvent
where TargetInstance ISA "BRCM_ExtraCapacityGroup"
SELECT * FROM __InstanceCreationEvent
where TargetInstance ISA "BRCM_NetworkAdapter"
SELECT * FROM __InstanceDeletionEvent
where TargetInstance ISA "BRCM_NetworkAdapter"
SELECT * FROM __InstanceCreationEvent
where TargetInstance ISA "BRCM_ActsAsSpare"
SELECT * FROM __InstanceDeletionEvent
where TargetInstance ISA "BRCM_ActsAsSpare"

For detailed information about these events, see the CIM documentation at

http://www.dmtf.org/standards/published_documents/DSP0004V2.3_final.pdf.

SNMP

BASP Subagent

The BASP subagent, baspmgnt.dll, is designed for the Windows Server 2003 and Windows Server 2008 SNMP service. It is
required to install the SNMP service before installing the BASP subagent.

The BASP subagent allows an SNMP manager software to actively monitor the configurations and performance of the
Broadcom Advanced Server features. The subagent also provides an alarm trap to an SNMP manager to inform the manager
of any changes to the conditions of the BASP component.

The BASP subagent allows monitoring of the configurations and statistics for the BASP teams, the physical NIC adapters
participating in a team, and the virtual NIC adapters created as the result of teaming. Non-teamed NIC adapters are not
monitored at this time. The BASP configuration data includes information such as team IDs, physical/virtual/VLAN/team
adapter IDs, physical/virtual/VLAN/team/ adapter descriptions, and MAC addresses of the adapters.

The statistics include detailed information such as data packets transmitted and received for the physical/virtual/VLAN/team
adapters.

The alarm trap forwards information about the changes in configuration of the physical adapters participating in a team, such

as physical adapter link up/down, and adapter installed/removed events.

To monitor this information, an SNMP manager must load the Broadcom BASP MIB database files to allow monitoring of the
information described above. These files, which are shown below, are included with the driver source media:

baspcfg.mib
baspstat.mib
basptrap.mib

BASP Extensible-Agent

The Broadcom NetXtreme Gigabit Ethernet Controller Extended Information SNMP extensible-agent, bcmif.dll, is designed for
Windows Server 2003 and Windows Server 2008 SNMP service.

The extensible-agent allows the SNMP manager software to actively monitor the configurations of the Broadcom NetXtreme
adapter. It is intended to supplement the information already provided by the standard SNMP Management Network Interface
information.

The extensible-agent provides in-depth information about a Broadcom NetXtreme adapter such as:

MAC address
Bound IP address
IP subnet mask
Physical link status
Adapter state
Line speed
Duplex mode
Memory range
Interrupt setting
Bus number
Device number
Function number

To monitor this information, a SNMP manager needs to load the Broadcom Extended information MIB file to allow monitoring
of the information described above. This file, bcmif.mib, is included on the Broadcom NetXtreme adapter installation CD.

The monitored workstation requires the installation of the Broadcom Extended Information SNMP extensible-agent, bcmif.dll,
and requires the Microsoft Windows Server 2003 and Windows Server 2008 SNMP service to be installed and loaded.

Please read all Restrictions and Disclaimers.

Back to Contents Page

Back to Contents Page

Installing the Hardware: Broadcom NetXtreme 57XX User Guide

System Requirements
Safety Precautions
Preinstallation Checklist
Installing the Adapter
Connecting the Network Cables

NOTE: This section applies only to add-in NIC models of Broadcom NetXtreme Gigabit Ethernet adapters.

System Requirements

Before you install the Broadcom NetXtreme Gigabit Ethernet adapter, verify that your system meets the requirements listed
for your operating system:

Hardware Requirements

Pentium-based system that meets operating system requirements
One open 32-bit or 64-bit PCI and/or PCI Express slot
128-MB RAM (minimum) for Windows and Linux. 64-MB RAM (minimum) for NetWare

Operating System Requirements

General

PCI v2.3 33/66 MHz Bus Interface (BCM5701/BCM5703)
PCI-X v1.0 64-bit 100-MHz Bus Interface (BCM5701 only)
PCI-X v1.0 64-bit 133-MHz Bus Interface (BCM5703 only)
PCI Express v1.0a, x1 (or greater) Host Interface (BCM5721)

Microsoft Windows

One of the following versions of Microsoft Windows:

Windows Server 2003 Family
Windows Server 2008 Family

Novell NetWare

One of the following versions of Novell NetWare: NetWare 5.1or NetWare 6.5, with the latest support pack.

Linux

NOTE: The current version of the adapter driver has been tested on the latest Red Hat, SuSE, and other Linux distributions
for i386, ia64, and x86_64 CPU architectures using 2.6.x kernels. The driver has been tested up to kernel version 2.6.13. The
driver should work on other little endian or big endian CPU architectures, but only very limited testing has been done on some
of these machines. The Makefile may have to be modified to include architecture-specific compile switches, and some minor
changes in the source files may also be required. On these machines, patching the driver into the kernel is recommended.

Safety Precautions

CAUTION! The adapter is being installed in a system that operates with voltages that can be lethal. Before
you remove the cover of your system, you must observe the following precautions to protect yourself and to
prevent damage to the system components:

Remove any metallic objects or jewelry from your hands and wrists.
Make sure to use only insulated or nonconducting tools.
Verify that the system is powered OFF and unplugged before you touch internal components.
Install or remove adapters in a static-free environment. The use of a properly grounded wrist strap or other

personal antistatic devices and an antistatic mat is strongly recommended.

Preinstallation Checklist

1. Verify that your server meets the hardware and software requirements listed under System Requirements.

2. Verify that your server is using the latest BIOS.

NOTE: If you acquired the adapter software on a disk or from the Dell support website

(http://www.support.dell.com), verify the path to the adapter driver files.

3. If your system is active, shut it down.

4. When system shutdown is complete, turn off the power and unplug the power cord.

5. Holding the adapter card by the edges, remove it from its shipping package and place it on an antistatic surface.

6. Check the adapter for visible signs of damage, particularly on the card edge connector. Never attempt to install any
damaged adapter.

Installing the Adapter

The following instructions apply to installing the Broadcom NetXtreme Gigabit Ethernet adapter (add-in NIC) in most servers.
Refer to the manuals that were supplied with your server for details about performing these tasks on your particular server.

1. Review the Safety Precautions and Preinstallation Checklist. Before installing the adapter, ensure the system power is
OFF and unplugged from the power outlet, and that proper electrical grounding procedures have been followed.

2. Open the system case, and select any empty PCI/PCI-X/PCI Express slot. If you do not know how to identify any of
these PCI slots, refer to your system documentation.

3. Remove the blank cover-plate from the slot that you selected.

4. Align the adapter connector edge with the connector slot in the system.

5. Applying even pressure at both corners of the card, push the adapter card into the slot until it is firmly seated. When
the adapter is properly seated, the adapter port connectors are aligned with the slot opening, and the adapter faceplate
is flush against the system chassis.

CAUTION! Do not use excessive force when seating the card as this may damage the system or the

adapter. If you have difficulty seating the adapter, remove it, realign it, and try again.

6. Secure the adapter with the adapter clip or screw.

7. Close the system case and disconnect any personal antistatic devices.

Connecting the Network Cables

Copper

The Broadcom NetXtreme Gigabit Ethernet adapter has one RJ-45 connector used for attaching the system to an Ethernet
copper-wire segment.

NOTE: The Broadcom NetXtreme Gigabit Ethernet adapter supports Automatic MDI Crossover (MDIX), which eliminates the
need for crossover cables when connecting machines back-to-back. A straight-through Category 5 cable allows the machines
to communicate when connected directly together.

1. Select an appropriate cable. Table 1: "10/100/1000BASE-T Cable Specifications" lists the cable requirements for

connecting to 10/100/1000BASE-T ports:

Table 1: 10/100/1000BASE-T Cable Specifications

Port Type Connector Media Maximum Distance

10BASE-T RJ-45 Category 3, 4, or 5 UTP 100 meters (328 feet)
100/1000BASE-T

1

1000BASE-T signaling requires four twisted pairs of Category 5 balanced cabling, as specified in ISO/IEC

1

RJ-45

Category 5

2

UTP

100 meters (328 feet)

11801:1995 and EIA/TIA-568-A (1995) and tested using procedures defined in TIA/EIA TSB95.

2

Category 5 is the minimum requirement. Category 5e and Category 6 are fully supported.

2. Connect one end of the cable to the adapter.

3. Connect the other end of the cable to an RJ-45 Ethernet network port.

NOTE: After the cable is properly connected at both ends, the port LEDs on the adapter should be functional. See

Table 1: "10/100/1000BASE-T Cable Specifications" for a description of network link and activity indications

Please read all Restrictions and Disclaimers.

Back to Contents Page

Back to Contents Page

Creating a Driver Disk: Broadcom NetXtreme 57XX User Guide

Refer to the documentation that was supplied with your system for instructions for creating a driver disk.

Please read all Restrictions and Disclaimers.

Back to Contents Page

Back to Contents Page

Broadcom Boot Agent Driver Software: Broadcom NetXtreme
57XX User Guide

Overview
Setting Up MBA in a Client Environment
Setting Up MBA in a Server Environment

Overview

Broadcom NetXtreme Gigabit Ethernet adapters support Preboot Execution Environment (PXE), Remote Program Load (RPL),
iSCSI boot, and Bootstrap Protocol (BootP). Multi-Boot Agent (MBA) is a software module that allows your networked system
to boot with the images provided by remote systems across the network. The Broadcom MBA driver complies with the PXE

2.1 specification and is released with both monolithic and split binary images. This provides flexibility to users in different
environments where the motherboard may or may not have built-in base code.

The MBA module operates in a client/system environment. A network consists of one or more boot systems that provide boot
images to multiple systems through the network. The Broadcom implementation of the MBA module has been tested
successfully in the following environments:

Linux® Red Hat® PXE Server. Broadcom PXE clients are able to remotely boot and use network resources (NFS
mount, and so forth) and to perform Linux installations. In the case of a remote boot, the Linux universal driver binds
seamlessly with the Broadcom Universal Network Driver Interface (UNDI) and provides a network interface in the Linux
remotely-booted client environment.

Intel® APITEST. The Broadcom PXE driver passes all API compliance test suites.
MS-DOS UNDI. The MS-DOS Universal Network Driver Interface (UNDI) seamlessly binds with the Broadcom UNDI to

provide a network device driver interface specification (NDIS2) interface to the upper layer protocol stack. This allows
systems to connect to network resources in an MS-DOS environment.

Remote Installation Service (RIS). The Broadcom PXE clients are able to remotely boot to a Windows Server 2003
(SP1 and older) system running RIS to initialize and install Windows Server 2003 and prior operating systems.

Windows Deployment Service (WDS). For Windows Server 2003 SP2, RIS was replaced by WDS, which offers a
Broadcom PXE client to install Windows operating systems, including Windows Server 2008.

Automated Deployment Service (ADS). The Broadcom PXE client can connect to a Windows Server 2003 system
and run a deployment agent that allows one to perform some administrative functions, including, but not limited to,
deploying a Windows Server 2003 image.

Setting Up MBA in a Client Environment

Use the following procedure for add-in NICs. For LOMs, refer to your computer's system guide.
Setting up MBA in a client environment involves the following steps:

1. Enabling the MBA driver.

2. Configuring the MBA driver.

3. Setting up the BIOS for the boot order.

Enabling the MBA Driver

To enable or disable the MBA driver:

1. Insert an MS-DOS 6.22 or Dell Real Mode Kernel bootable disk containing the B57udiag.exe file in the removable disk
drive and power up your system.

2. Type:

drive:\dos\utility

where

To boot from the network with the MBA, make the MBA enabled adapter the first bootable device under the BIOS. This

drive is the drive letter of the CD-ROM drive.

NOTE: The B57udiag.exe file is on the installation CD or in the DOS Utilities package available from

http://support.dell.com/.

3. Type:

b57udiag -mba [ 0-disable | 1-enable ] -c devnum

where
devnum is the specific device(s) number (0,1,2, ...) to be programmed.

Configuring the MBA Driver

NOTE: You can use the MBA Configuration Menu to configure the MBA driver one adapter at a time as described below, or
you can use the Broadcom NetXtreme User Diagnostics MS-DOS based application to simultaneously configure the MBA driver
for multiple adapters.

1. Restart your system.

2. Press CTRL+S within 4 seconds after you are prompted to do so.

NOTE: The message prompting you to press CTRL+S is displayed once for each Broadcom NetXtreme Gigabit
Ethernet adapter you have in your system. The messages are displayed in the same order as the assigned adapter
device number.

3. Use the UP ARROW and DOWN ARROW keys to move to the Boot Protocol menu item. Then use the RIGHT ARROW or
LEFT ARROW key to select the boot protocol of choice if other boot protocols besides Preboot Execution Environment
(PXE) are available. If available, other boot protocols include Remote Program Load (RPL) and Bootstrap Protocol
(BOOTP).

NOTE: If you have multiple adapters in your system and you are unsure which adapter you are configuring, press

CTRL+F6, which causes the port LEDs on the adapter to start blinking.

4. Use the UP ARROW, DOWN ARROW, LEFT ARROW, and RIGHT ARROW keys to move to and change the values for
other menu items, as desired.

5. Press F4 to save your settings.

6. Press ESC when you are finished.

Setting Up the BIOS

procedure depends on the system BIOS implementation. Refer to the user manual for the system for instructions.

Setting Up MBA in a Server Environment

Linux Red Hat PXE Server

The Red Hat Enterprise Linux has PXE Server support. It allows users to remotely perform a complete Linux installation over
the network. The distribution comes with the boot images boot kernel (vmlinuz) and initial ram disk (initrd), which are located
on the Red Hat disk#1:

/images/pxeboot/vmlinuz

/images/pxeboot/initrd.img
Refer to the Red Hat documentation for instructions on how to install PXE Server on Linux.
The Initrd.img file distributed with Red Hat 8.0, however, does not have a Linux network driver for the Broadcom NetXtreme

Gigabit Ethernet adapter.
This version requires drivers that are not part of the standard distribution. You can create a driver disk for the Broadcom

NetXtreme Gigabit Ethernet adapter from the image distributed with the driver source media. Refer to the Linux Readme.txt
file for more information.

A remote boot does not require a standard Linux network driver for the Broadcom NetXtreme Gigabit Ethernet adapter. After
the PXE client downloads the Linux kernel and initial ram disk, the Linux universal driver that came with the Linux distribution
binds with the UNDI code of the PXE to form a Linux network driver.

Windows Server 2003

The current version of Windows Server 2003 does not include the latest released network driver for the Broadcom NetXtreme
Gigabit Ethernet adapter. You can create a driver disk for the adapter from the image distributed by Dell. To perform remote
installations with PXE, include a network driver for the NetXtreme Gigabit Ethernet adapter as a part of the client installation
image on the server. Refer to Microsoft Knowledge Base Article, "How to Add Third-Party OEM Network Adapters to RIS
Installations." See also Troubleshooting for details.

DOS UNDI/Intel APITEST

To boot in DOS mode and connect to a network for the DOS environment, download the Intel PXE PDK from the Intel website.
This PXE PDK comes with a TFTP/ProxyDHCP/Boot server. The PXE PDK can be downloaded from Intel at

http://downloadcenter.intel.com/default.aspx.

Please read all Restrictions and Disclaimers.

Back to Contents Page

Back to Contents Page

NDIS2 Driver Software: Broadcom NetXtreme 57XX User Guide

Preinstallation Requirements
Installing the NDIS2 Driver Software for Use on MS-DOS Platforms
Installing the NDIS2 Driver Software for Use in IBM-OS/2 Environments
Configuring the NDIS2 Driver Software
Using Keywords for the B57.dos Drivers

Preinstallation Requirements

Before you can successfully install the NDIS2 driver software, the Broadcom network adapter must be physically installed in
the server. Networking software that is appropriate to the operating system (such as Microsoft LAN Manager 2.2 for MS-DOS)
must already be running on your server.

Installing the NDIS2 Driver Software for Use on MS-DOS Platforms

The NDIS2 driver software can be run from an MS-DOS startup disk using Microsoft Network Client 3.0 or from the hard disk
using Microsoft LAN Manager 2.2.

Creating a Startup Disk to Run Microsoft Network Client

To perform this installation you must have the following items:

Windows NT Server 4.0 CD-ROM
A blank MS-DOS system disk (3.5" high-density floppy disk)
Access to the Broadcom NDIS2 driver file (B57.dos). This file is located on the Dell-provided driver source media in the

DOS Utilities package, or any of the Windows driver packages downloaded from Dell.

NOTES:

Windows NT Server 4.0 users. When running Setup for Microsoft Network Client v3.0 for MS-DOS, click
any network card from the list (NE2000 Compatible, for example) to create the startup disk.

After creating the startup disk, follow the instructions in Modifying the Startup Disk.

To create a startup disk

1. Create a folder called NCADMIN in the root of the C drive.

2. Copy the NCADMIN.CN_, NCADMIN.EX_, and NCADMIN.HL_ files from the I386 folder on the Windows NT Server 4.0
CD-ROM.

3. Open a command prompt window and change the directory to C:\NCADMIN.

4. Type expand -r ncadmin.* and press ENTER.

5. Close the command prompt window by typing exit and then pressing ENTER.

6. Start Windows Explorer.

7. Open the NCADMIN folder and double-click ncadmin.exe.

8. Follow the on-screen instructions to make the network startup disk (choose NE2000 Compatible from the list of
adapters).

Modifying the Startup Disk

To modify the startup disk

1. Edit A:\Net\Protocol.ini with Notepad or a similar text editor.

a. Change DriverName=$ to DriverName=B57$.
b. Remove all other parameter entries under the [MS$NE2CLONE] or equivalent section such as IOBASE=0x300 or

INTERRUPT=3, and so on.

Example Protocol.ini file 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 file 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 file 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.

a. Change netcard= to netcard=b57.dos.
b. Check for references to C:\NET and change C:\NET to A:\NET if necessary.

Example System.ini file

[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 drive 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

5. Create a Config.sys file on the startup disk in drive A as shown below.

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

Installing the DOS NDIS2 Driver Software on the Hard Disk

To install the DOS NDIS2 Driver Software on the hard disk

1. Verify that the system has Microsoft LAN Manager 2.2 installed, with a protocol such as NetBEUI configured.

2. Create a folder on your hard disk to store the NDIS 2.01 driver.

Example: C:\LANMAN

3. Copy the B57.dos file to this folder.

4. Edit the Config.sys file by adding the following lines:

DEVICE = C:\LANMAN\PROTMAN.DOS
DEVICE = C:\LANMAN\B57.DOS
DEVICE = C:\LANMAN\NETBEUI.DOS

5. Edit the Autoexec.bat file by adding the following lines:

C:\LANMAN\NETBIND.EXE
C:\LANMAN\NET START WORKSTATION
C:\LANMAN\NET USE drive letter: \\server name\resource name

6. Edit the Protocol.ini file (located in C:\LANMAN) to configure the driver to bind with NetBEUI or any other protocols.

Example:

[PROTOCOL MANAGER]
DriverName = PROTMAN$
[NETBEUI_XIF]
DriverName = netbeui$
BINDINGS = B57
[B57]
DriverName = "B57$"

7. Restart the computer to complete the installation.

NOTE: The driver loads during system configuration and displays the Broadcom banner, controller name, MAC

address, IRQ number, detected line speed, and the controller BusNum and DevNum. If the driver fails to load, an

initialization fail message is displayed.

[B57 3]

Installing the NDIS2 Driver Software for Use in IBM-OS/2
Environments

To perform this installation you must have a disk that contains the Broadcom NDIS2 driver files (B57.NIF and B57.OS2).
These files are located on the Dell-provided driver source media in the DOS Utilities package, or any of the Windows driver
packages downloaded from Dell.

To install the NDIS2 driver software

1. At the OS/2 desktop, double-click System Setup.

2. Select MPTS Network Adapter and Protocol Services, and then click OK.

3. In Multi-Protocol Transport Services, click Configure.

4. In Configure, verify that LAN Adapters and Protocol is selected, and then click Configure.

5. In Adapter and Protocol Configuration under Network Adapters, click Other Adapters.

6. Insert the disk that contains the B57.NIF and B57.OS2 files, and then click OK.

7. In Adapter and Protocol Configuration under Network Adapters, search for and select Broadcom NetXtreme
Gigabit Ethernet, and then click Add.

8. In Protocols, select IBM OS/2 NETBIOS, and then click Add.

9. Click OK.

10. In Multi-Protocol Transport Services, click Close, and then click Exit.

11. Restart the system.

Configuring the NDIS2 Driver Software

The NDIS2 driver software can be configured by adding specific optional keywords to the Protocol.ini file. If multiple (or
multiport) Broadcom NetXtreme Gigabit Ethernet adapters are installed in a system, the NDIS2 driver software loads by
default on the adapter/port that has a good link. If 2 or more adapters have a good link, the NDIS2 driver software loads on
the adapter having the latest Device ID. If 2 or more adapters that have a good link have the same Device ID, the NDIS2
driver software loads on the adapter that is located in the slot having the lowest bus number.

NOTE: On MS-DOS platforms, it is not recommended to load the NDIS2 driver software on more than 1 adapter; the

required NDIS2 protocol manager that supports multiple binds is not available in the MS-DOS environment.
If it is necessary to have the NDIS2 driver load on certain adapters in a certain order, the BusNum, DevNum, and FuncNum

keywords can be used. Do not use these keywords unless you know how to configure PCI devices.
The BusNum keyword value, which represents the PCI bus number in which the adapter is located, is a decimal number

ranging from 0 to 255.
The FuncNum keyword value, which represents the function (port) number of a multiport adapter, is a decimal number, with

0 representing the first port, and 1 representing the second port.
The DevNum keyword value, which represents the assigned device number, is a decimal number ranging from 0 to 31.

NOTE: At the end of the NDIS2 driver software installation process, note the BusNum and DevNum values that are
displayed. Alternatively, use Broadcom Advanced Control Suite 3 (see Broadcom Advanced Control Suite 3) to view the bus
number, function (port) number, and device number assigned to each adapter (Windows users only).

Example BusNum, DevNum, and FuncNum keyword entries for loading the NDIS2 driver on multiple adapters in a certain
order are shown below:

[B57]
DRIVERNAME = B57$
BUSNUM = 3
DEVNUM = 10
[B57_2]
DRIVERNAME = B572$
BUSNUM 3
DEVNUM 11

DRIVERNAME = B573$

BUSNUM 3

NodeAddress = 001020304050

DEVNUM 12
[B57_4]
DRIVERNAME = B574$
BUSNUM 3
DEVNUM 13

The LineSpeed keyword is used to force the speed of the network connection. The LineSpeed keyword requires a decimal
number and of either 10, 100, or 1000. Technically, a line speed of 1000 Mbit/s cannot be forced and can be achieved only
through auto-negotiation. For the sake of simplicity, the driver performs auto-negotiation when the line speed is set to a
value of 1000. Forced 1000 Mbit/s speed is not needed for copper links; auto-negotiation is the proper supported
configuration under the IEEE Ethernet specification.

The Duplex keyword is used to force the duplex mode of the adapter. The Duplex keyword requires a text string of either
HALF or FULL. When the Duplex keyword is used, the LineSpeed keyword must also be used. If neither keyword is used, the
network adapter defaults to auto-negotiation mode.

The NodeAddress keyword specifies the network address used by the adapter. If a multicast address or a broadcast address is
specified, the adapter uses the default MAC address.

The FixCheckSumOff keyword turns off the driver workaround for the TCP/IP stack to recognize the ones complement version
of the checksum.

Example entries for the LineSpeed, Duplex, and NodeAddress keywords are shown below:

[B57]
DRIVERNAME = B57$
BUSNUM = 3
DEVNUM = 10
PORTNUM = 0
LINESPEED = 100
DUPLEX = FULL
NODEADDRESS = "001020304050"

Using Keywords for the B57.dos Drivers

The Protocol.ini file contains certain keywords that are used by the B57.dos drivers. These keywords are listed below:

BusNum. Specifies the number of the PCI bus on which the network adapter is located. Requires a decimal number having
a value ranging from 0 to 255.

DevNum. Specifies the device number assigned to the network adapter when it is configured by the PCI BIOS. Requires a
decimal number having a value ranging from 0 to 255.

FuncNum or PortNum. Specifies the PCI function or port number assigned to the network controller. Requires a decimal
number having a value ranging from 0 to 7.

NOTE: These keywords, BusNum, DevNum, and FuncNum (or PortNum), are needed when multiple adapters are
installed in the server and when a specific controller must be loaded in a certain order. These keywords are used concurrently
and are included for manufacturing purposes. Do not use them unless you are familiar with how to configure PCI devices. A
PCI device scan utility is needed to find this information.

LineSpeed. Specifies the speed of the network connection in Mbit/s. Requires the decimal number 10, 100, or 1000.
Technically, a line speed of 1000 Mbit/s cannot be forced and is achievable only through auto-negotiation. For the sake of
simplicity, the driver performs auto-negotiation when the line speed is set to a value of 1000.

Duplex. Specifies the duplex mode of the network adapter. Requires a setting of either Half or Full. When this keyword is
used, the LineSpeed keyword must also be used. If neither keyword is used, the network adapter defaults to auto­negotiation mode.

NodeAddress. Specifies the network address used by the network adapter. If a multicast address or a broadcast address
is specified, the adapter uses the default MAC address.

Example:

[B57]
DriverName = "B57$"
BusNum = 3
DevNum = 14
PortNum = 2
LineSpeed = 1000
Duplex = Full

Please read all Restrictions and Disclaimers.

Back to Contents Page

Back to Contents Page

ODI Driver Software: Broadcom NetXtreme 57XX User Guide

Installing the Driver Software
Configuring Parameters for the B57.com Driver (in the Net.cfg file)

The Open Data-Link Interface (ODI) driver software allows LAN drivers to work together irrespective of differences between
the hardware and/or the protocol stacks of communicating systems. An intervening layer, called the link support layer (LSL),
is responsible for routing different packet types between LAN drivers and protocol stacks.

Installing the Driver Software

Installing the ODI driver software involves the following steps:

1. Verify that the MS-DOS operating system files are installed on your system hard disk or are available on a removable
storage device.

2. Install the ODI driver software in the MS-DOS environment.

3. If necessary, reconfigure the driver software after installation.

Preinstallation Requirements

Verify that the Broadcom NetXtreme Gigabit Ethernet adapter driver software has been installed on your system. If it has not,
install it (see Installing the Driver Software). Otherwise, you cannot use a Broadcom NetXtreme Gigabit Ethernet adapter in
the MS-DOS environment.

NOTE: To be able to successfully install the adapter driver in the MS-DOS environment, the adapter must be installed

before you install the adapter driver.

Installing the ODI Driver in the MS-DOS 6.22 Environment

1. Copy the ODI driver file (B57.com) to the root directory of the hard disk (the B57.com file is on the installation CD).

2. Copy the Lsl.com, Ipxodi.com, and Vlm.com files to the same directory (these files are provided by Novell).

3. Edit the Autoexec.bat file by adding the following lines:

C:\LSL
C:\B57
C:\IPXODI
C:\VLM

4. Edit the Net.cfg file and place the file in the same location as the Autoexec.bat file (located in drive C) to configure the
driver to bind with different frame types.

LINK DRIVER B57
FRAME ETHERNET_802.2
FRAME ETHERNET_802.3
FRAME ETHERNET_II
FRAME ETHERNET_SNAP
NetWare DOS Requester
FIRST NETWORK DRIVE=F
NETWARE PROTOCOL=NDS BIND
PROTOCOL IPXODI

5. Restart the computer to complete the install.

6. As the files are being loaded, the computer attempts to attach to a NetWare server using the frame types specified in
Net.cfg. If the connection is successful, a dialog box appears.

7. Change to drive F and log on to the NetWare server.

NOTE: The driver loads during system configuration, and the Broadcom banner, the adapter name, the MAC
address, the IRQ number, the detected line speed, and the BUSNUM and DEVNUM of the adapter are displayed. If the
driver fails to load, an initialization fail message appears.

Configuring Parameters for the B57.com Driver (in the Net.cfg file)

The following are optional custom keywords used in the Net.cfg file:

BUSNUM
DEVNUM
FUNNUM
SUBVID
MODEL

The first two keywords (BUSNUM and DEVNUM) are used concurrently and have been included for manufacturing purposes.
Do not use them unless you are familiar with PCI device configuration. These two keywords are needed if multiple Broadcom
NetXtreme Gigabit Ethernet adapters are installed in a system, and each adapter must be loaded in a specific order.

BUSNUM specifies the PCI bus number and DEVNUM specifies the device number that is assigned to the adapter when it is
configured by the PCI BIOS.

The values for these adapter parameters are displayed in hexadecimal notation when the driver loads (the Net.cfg file expects
hexadecimal values). A PCI device scan utility can also be used to find this information. If the driver loads on a single
adapter, the displayed values can be used in the Net.cfg file.

If a PCI scan utility displays adapter 1 at bus 4 and device 11 (hexadecimal), and adapter 3 at bus 3 and device 13
(hexadecimal), the following load instructions are written to the Net.cfg file (load adapter 3 first, and optionally load adapter 1
second):

LINK DRIVER B57
BUSNUM 3
DEVNUM 13 (13 hex = 19 decimal)
LINK DRIVER B57
BUSNUM 4
DEVNUM 11 (11 hex = 17 decimal)

The FUNNUM keyword is used to determine which function/port the driver is to load on when using a multifunction (multiport)
adapter. Function number values are limited to 0 and 1, for the first and second ports of the adapter.

The SUBVID keyword is used to for load the driver only on the first adapter found that has a subvendor ID (SVID) that
matches the one set in Net.cfg. The driver ignores all other adapters that do not have a matching SVID. SUBVID expects a
hexadecimal number.

Example:

LINK DRIVER B57
SUBVID 14E4

SUBVID cannot be used with BUSNUM, DEVNUM or FUNNUM.
The MODEL keyword is for loading the driver only on the first adapter found that has a subvendor ID (SVID) that matches the

one set in MODEL. The driver ignores all other adapters that do not have a matching SVID. MODEL expects a decimal
number.

Example:

LINK DRIVER B44
MODEL 534

Please read all Restrictions and Disclaimers.

Back to Contents Page

Back to Contents Page

Linux Driver Software: Broadcom NetXtreme 57XX User Guide

Limitations
Packaging
Installing TG3 Driver Software
Network Installations
Patching PCI Files (Optional)
Unloading/Removing the TG3 Driver
Driver Messages
Teaming with Channel Bonding

Limitations

The current version of the adapter driver has been tested on the latest Red Hat, SuSE, and other Linux distributions for i386,
ia64, and x86_64 CPU architectures using 2.6.x kernels. The driver has been tested up to kernel version 2.6.13. The driver
should work on other little endian or big endian CPU architectures, but only very limited testing has been done on some of
these machines. The Makefile may have to be modified to include architecture-specific compile switches, and some minor
changes in the source files may also be required. On these machines, patching the driver into the kernel is recommended.

Packaging

The Linux TG3 driver is released in the following packaging formats (file names):

Source RPM (tg3-version.3dkms.src.rpm)
Source RPM (tg3-version.3dkms.noarch.rpm)
Supplemental (tg3_sup-version.tar.gz)
Compressed tar (tg3-version.tar.gz)

Identical source files to build the driver are included in both RPM and TAR source packages. The tar file contains additional
utilities such as patches and driver disk images for network installation.

Installing TG3 Driver Software

Installing the DKMS RPM Driver Package
Installing the Source RPM Package
Building the Driver from the Source TAR File

Installing the DKMS RPM Driver Package

Dynamic Kernel Module Support (DKMS) is designed to simplify the rebuilding of modules whenever you upgrade the kernel.
This rebuilding is accomplished by creating a framework where a kernel-dependent module source can reside.

To install the DKMS RPM driver package

1. Download the DKMS binary RPM from http://linux.dell.com/dkms/.

dkms -version.noarch.rpm

2. Install the DKMS binary RPM package.

rpm -ivh dkms-version.src.rpm

3. Install the DKMS RPM driver package.

rpm -ivh tg3-version dkms.noarch.rpm

For more information, go to http://linux.dell.com/projects.shtml.

Installing the Source RPM Package

1. Install the source RPM package.

rpm -ivh tg3-version.src.rpm

2. Change the directory to the RPM path and build the binary driver for your kernel (the RPM path is different for different
Linux distributions).

cd /usr/src/redhat,OpenLinux,turbo,packages,rpm ...
rpm -bb SPECS/tg3.spec or rpmbuild -bb SPECS/tg3.spec
rpmbuild -bb SPECS/tg3.spec (for RPM version 4.x.x)

NOTE: During your attempt to install a source RPM package, the following message may be displayed:

error: cannot create %sourcedir /usr/src/redhat/SOURCE

The most likely cause of the error is that the rpm-build package has not been installed. Locate the rpm-build
package on the Linux installation media and install it using the following command:

rpm -ivh rpm-build-version.i386.rpm

Complete the installation of the source RPM.

3. Install the newly-built package (driver and man page).

rpm -ivh RPMS/i386/tg3-version.i386.rpm

Depending on the kernel, the driver is installed to the following path:

2.6.x kernels:
/lib/modules/kernel_version/kernel/drivers/net/tg3.ko

4. Load the driver.

modprobe tg3

To configure the network protocol and address, refer to the Linux version-specific documentation.

Building the Driver from the Source TAR File

1. Create a directory (tg3-version) and extract the TAR files to the directory.

tar xvzf tg3-version.tgz

2. Build the driver tg3.o as a loadable module for the running kernel.

CD tg3-version
make clean
make; make install

3. Test the driver by loading it.

rmmod tg3
modprobe tg3

No message should be returned if this command runs properly.

NOTE: See the RPM instructions above for the location of the installed driver.

4. To configure network protocol and address, refer to the manuals supplied with your operating system.

Network Installations

For network installations through NFS, FTP, or HTTP (using a network boot disk or PXE), a driver disk that contains the tg3
driver may be needed. The driver disk images for the most recent Red Hat versions are included. Boot drivers for other Linux
versions can be compiled by modifying the Makefile and the make environment. Further information is available from the Red
Hat website, http://www.redhat.com.

To create the driver disk, select the appropriate image file (located in tg3_sup-version.tar.gz) and type the following:

dd if=<version>.dd.img of=/dev/fd0