Fujitsu PG-FCS102, PG-FCS103, BX620 User Manual

Before Reading This Manual

Thank you for purchasing the PRIMERGY 1Gbit/s Ethernet I/O Module (hereinafter referred to as this product or the card). The card can be installed in the expansion card slot of the Fujitsu server blade to configure the Local Area Network (LAN) system. This manual explains the 1Gbit/s Ethernet I/O Modules and the LAN driver (for Windows). Read this manual carefully to handle the product correctly. For details about the LAN driver, refer to manuals supplied with the server blade or the Fujitsu PRIMERGY website: (http://primergy.fujitsu.com)

May, 2007

For Your Safety

This manual contains important information, required to operate this product safely. Thoroughly review the information in this manual before using this product. Especially note the points under "Safety", and only operate this product with a complete understanding of the material provided. This manual should be kept in an easy-to-access location for quick reference when using this product.

High Safety

The Products are designed, developed and manufactured as contemplated or general use, including without limitation, general office use, personal use, household use, and ordinary industrial use, but are not designed, developed and manufactured as contemplated for use accompanying fatal risks or dangers that, unless extremely high safety is secured, could lead directly to death, personal injury, severe physical damage, or other loss (hereinafter "High Safety Required Use"), including without limitation, nuclear reaction control in nuclear facility, aircraft flight control, air traffic control, mass transport control, medical life support system, missile launch control in weapon system. You shall not use this Product without securing the sufficient safety required for the High Safety Required Use. If you wish to use this Product for High Safety Required Use, please consult with our sales representatives in charge before such use.

101

Remarks

Warning Descriptions

Various symbols are used throughout this manual. These are provided to emphasize important points for your safety and that of others. The symbols and their meanings are as follows. Make sure to fully understand these before reading this manual.

WARNING

CAUTION

The following symbols are used to indicate the type of warning or cautions being described.

Ignoring this symbol could be potentially lethal.

Ignoring this symbol may lead to injury and/or damage this product.

The triangle mark emphasizes the urgency of the WARNING and CAUTION. Details are described next to the triangle.

A barred circle ( ) warns against certain actions (Do Not). Details are described next to the circle.

A black circle indicates actions that must be taken. Details are described next to the black circle.

Symbols

The following are symbols used throughout this manual.

Symbols Definition

These sections explain prohibited actions and points to note when using this product. Make sure to read these sections.

These sections explain information needed to operate the hardware and software properly. Make sure to read these sections.

→ This mark indicates reference pages or manuals.

Entering commands (Keys)

CD-ROM drive names are shown as [CD-ROM drive]. Enter your drive name according to your environment.

[CD-ROM drive]:\Setup.exe

102

Abbreviations

The following expressions and abbreviations are used to describe the product names used in this manual.

Product names Expressions and abbreviations

1Gbit/s Ethernet I/O Module (PG-LND201) this product

PG-LND201 LAN Driver LAN driver or the driver

Microsoft

Microsoft Edition

Microsoft

Red Hat

PRIMERGY BX620 S3 Server Blade

PRIMERGY BX620 S4 Server Blade

PRIMERGY BX600 S3 Blade Server System Unit

PRIMERGY BX600 S2 Blade Server System Unit

Switch Blade

Catalyst Blade Switch 3040

FC Pass-Thru Blade FC Pass-Thru Blade

FC Switch Blade (PG-FCS103/PG-FCS102) FC Switch Blade

Windows Server® 2003, Standard Edition

Windows Server® 2003, Enterprise Edition

Windows Server® 2003 R2, Standard Edition

Windows Server® 2003 R2, Enterprise Edition

Windows Server® 2003, Standard x64 Edition

Windows Server® 2003, Enterprise x64 Edition

Windows Server® 2003 R2, Standard x64

Windows Server® 2003 R2, Enterprise x64

Windows® 2000 Server

Windows® 2000 Advanced Server

Enterprise Linux® ES (v.3 for x86)

Enterprise Linux® AS (v.3 for x86)

Enterprise Linux® AS (v.4 for x86)

Enterprise Linux® ES (v.4 for x86)

Enterprise Linux® AS (v.4 for EM64T)

Enterprise Linux® ES (v.4 for EM64T)

Enterprise Linux® 5 (for x86)

Enterprise Linux® 5 (for Intel64)

Windows Server 2003

Windows Server 2003 x64

Windows 2000 Server

Linux

BX620 S3 Server Blade

BX620 S4 Server Blade

Chassis

Switch Blade

Windows

Server Blade

103

Safety

For safe use of this product, it is vital that the following warnings are heeded.

Handling this product

WARNING

• Do not tinker with the product. Doing so may cause fire or electric shock.

• Keep this product away from water. Failure to do so may cause fire or electric shock.

• When there is lightning nearby, unplug all power cords and external connecting cords from this product. Failure to do so may cause destruction of the devices and fire.

CAUTION

• Since this product is delicate, avoid using or storing it under extreme conditions, such as excessively high or low temperature, high humidity, or in direct sunlight. Do not bend or damage the card or subject it to extreme shock. Doing so may cause failure or fire.

Recycle

When scrapping this product, contact an office listed in "Appendix A Contact Information" (

Jpg.195). This product must be disposed of as industrial waste.

Checking the Items Supplied

Before using the product, check that no supplied or attached items are missing. If any items are missing, contact an office listed in "Appendix A Contact Information" (

• 1Gbit/s Ethernet I/O Module

• User's Guide (this manual)

• Screw (3 screws)

Intel is a registered trademark of Intel Corporation in the USA. Microsoft, Windows, and Windows Server are trademarks or registered trademarks of Microsoft Corporation in the United States and other countries. Linux is a trademark or registered trademark of Linus Torvalds in the United States and other countries. Red Hat and all Red Hat-based trademarks and logos are trademarks or registered trademarks of Red Hat, Inc. in the United States and other countries. Other product names used are trademarks or registered trademarks of their respective manufacturers. Other products are copyrights of their respective manufacturers.

104

Jpg.195).

Contents

1 1 Gbit/s Ethernet I/O Module . . . . . . . . . . . . . . . . . . . . . . . . . 106

1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

1.2 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

1.3 Functionality and Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

2 Installing a 1Gbit/s Ethernet I/O Module . . . . . . . . . . . . . . . . 115

2.1 Installing in a Server Blade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

3 Installing the LAN Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

3.1 Installing the Driver Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

4 Broadcom Gigabit Ethernet Teaming Services . . . . . . . . . . . 119

4.1 Broadcom Gigabit Ethernet Overview . . . . . . . . . . . . . . . . . . . . . . . . 119

4.2 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

4.3 Teaming Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

4.4 Teaming Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

4.5 Types of Teams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

4.6 Attributes of the Features Associated with Each Type of Team . . . . 136

4.7 Teaming and Other Advanced Networking Properties . . . . . . . . . . . 138

4.8 General Network Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

4.9 Event Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

5 Broadcom Advanced Control Suite 2 (BACS2) . . . . . . . . . . . 156

5.1 BACS2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

5.2 Installing the BACS2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

5.3 Starting BACS2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

5.4 Setting of BACS2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

5.5 Configuring Teaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Appendix A Contact Information . . . . . . . . . . . . . . . . . . . . . . . 195

105

1 Gbit/s Ethernet I/O Module

This chapter explains the features and specifications of this product.

1.1 Overview

This product is an LAN expansion board exclusive to BX620 S3 Server Blade and BX620 S4 Server Blade. This product has 2 LAN controllers, and provides LAN connection completely separate/ independent of the onboard LAN. The external access is performed via the Switch Blade installed to the network blade slot 3 or 4 (NET3 or NET4) on the chassis.

` A server blade installed with this products and a server blade installed with a fibre

channel expansion board cannot be installed to the same chassis.

` When a Switch Blade is installed to network blade slot 3 or 4 (NET3 or NET4), a FC

Pass-Thru Blade or FC Switch Blade cannot be installed at the same time.

1.2 Specifications

Item Specifications

Product ID PG-LND201

Host bus specifications

External interface 1000BASE-T Ethernet (SerDes) Interface

Controller LSI BCM 5708S

Applicable model

Interface PCI-Express (x4)

Data transfer rate Max. 1 Gbps

Data transfer system Bus master, DMA

BX620 S3 Server Blade BX620 S4 Server Blade

106

1.3 Functionality and Features

1.3.1 Functional Description

This product is a new class of Gigabit Ethernet (GbE) converged network interface controller (CNIC) that can simultaneously perform accelerated data networking, storage networking, and highperformance clustering on a standard Ethernet network. The C-NIC offers acceleration for all popular protocols used in the data center, such as:

• TCP Offload Engine (TOE) for accelerating TCP

` Offloading technologies are supported when this product is installed in a system with

Windows Server 2003 with Scalable Networking Pack (SNP).

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. For details about teaming, refer to " Broadcom Advanced Server Program (BSAP) Overview" ( VLANs, refer to "1.3.4 Virtual LAN Function" ( and creating VLANs on Windows operating systems, refer to "1.3.3 Teaming Function" (

1.3.2 Features

The following is a list of this product features:

• TCP Offload Engine (TOE)

• Single-chip solution

- Standard Ethernet frame size (1518 bytes)

- PCI Express v1.0A, x4

- Full fast-path TCP offload

- Zero copy capable hardware

• Other performance features

- TCP, IP, UDP checksum

- TCP segmentation

• Manageability

- Broadcom Advanced Control Suite2 (BACS2) diagnostic and configuration software suite

- Supports PXE 2.0 specification

- Statistics for SNMP MIB II, Ethernet-like MIB, and Ethernet MIB (IEEE Std 802.3z, Clause

30)

- IPMI support

• Advanced network features

- Jumbo frames (up to 9 KB)

- Virtual LANs

- Flow Control (IEEE Std 802.3x)

- LiveLink™ (supported in both the 32-bit and 64-bit Windows operating systems)

- Logical Link Control (IEEE Std 802.2)

• Layer-2 Priority Encoding (IEEE 802.1p)

Jpg.109) in "1.3.3 Teaming Function" (Jpg.109). For a description of

Jpg.112). For instructions on configuring teaming

Jpg.109).

1 1 Gbit/s Ethernet I/O Module 107

• High-speed on-chip RISC processor

• Up to 4 classes of service (CoS)

• Integrated 96 KB frame buffer memory

• Support for multicast addresses via 128 bits hashing hardware function

• EM64T processor support

TCP Offload Engine (TOE)

The TCP/IP protocol suite is used to provide transport services for a wide range of applications for the Internet, LAN, and for file transfer. Without TCP Offload Engine, the TCP/IP protocol suite runs on the host CPU, consuming a very high percentage of its resources and leaving little resources for applications. With the use of this product, the TCP/IP processing can be moved to hardware, freeing the CPU for more important tasks such as application processing. This product's network adapter's TOE function allows simultaneous operations of up to 1024 fully offloaded TCP connections. The TOE support on the adapter significantly reduces the host CPU utilization while preserving the implementation of the operating system stack.

Broadcom Advanced Control Suite 2 (BACS2)

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

108

1.3.3 Teaming Function

Broadcom Advanced Server Program (BSAP) Overview

Broadcom Advanced Server Program (BASP) is the Broadcom teaming software for Windows Server 2003 and Windows 2000 Server operating systems. BASP runs within the Broadcom Advanced Control Suite 2 (BACS2) utility.

BASP supports four types of teams for Layer 2 teaming:

• Smart Load Balancing and Failover

• Link Aggregation (802.3ad)

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

• Smart Load Balancing (Auto-Fallback Disable)

` Enabling Windows Server 2003 built-in bridging is not advisable when you are using

teaming software.

For more information on network adapter teaming concepts, refer to "4.3 Teaming Concepts"

Jpg.121).

(

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 Gigabit Ethernet network adapters are installed in the same system, they can be grouped into teams, creating a virtual adapter.

A team can consist of two to eight network interfaces, and each interface can be designated as a primary interface or a standby interface (standby interfaces can be used only in a Smart Load Balancing™ and Failover type of team, and only one standby interface can be designated per SLB team). If traffic is not identified on any of the adapter team member connections due to failure of the adapter, cable, switch port, or switch (where the teamed adapters are attached to separate switches), the load distribution is reevaluated and reassigned among the remaining team members. In the event that all of the primary adapters are down, the hot standby adapter becomes active. Existing sessions are maintained and there is no impact on the user.

Types of Teams

The available types of teams for the Windows Server 2003/Windows 2000 Server operating systems are:

• Smart Load Balancing and Failover

J" Smart Load Balancing™ and Failover"(pg.110)

• Link Aggregation (802.3ad)

J" Link Aggregation (802.3ad)"(pg.110)

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

J" Generic Trunking (FEC/GEC)/802.3ad-Draft Static"(pg.110)

• SLB (Auto-Fallback Disable)

J" SLB (Auto-Fallback Disable)"(pg.111)

` Link aggregation is not supported in the Blade Server.

1 1 Gbit/s Ethernet I/O Module 109

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); it works with existing Layer 2 and 3 switches. No switch configuration (such as trunk, link aggregation) is necessary for this type of team to work.

` 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 transmitting 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.

` Link aggregation (802.3ad) is not supported in the Blade Server.

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. However, the Generic Trunking (FEC/GEC)/802.3ad-Draft Static) type of team, 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.

110

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 exception of 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.

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 (AutoFallback Disable) Types of Teams

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

Operating System

Protocol IP IPX

Failover/

Fallback - All

Broadcom

Net

Failover/

Fallback -

Multivendor

IP IPX

Load Balance -

All Broadcom

Net

IP IPX

Load Balance -

Net

IP IPX

Multivendor

Net

Windows Server 2003YYNYNNYYNYN N

Windows Server 2003 with SNP

Windows 2000 Server Y Y Y Y N N Y Y N Y N N

YYNYNNYYNYNN

Y = supported, N = not supported

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 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 protocolindependent, and all traffic should be load-balanced and fault-tolerant.

` 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.

1 1 Gbit/s Ethernet I/O Module 111

LiveLink™

LiveLink™ is a feature of BASP that is available only for the Smart Load Balancing™ type of teaming. The purpose of LiveLink is to detect link loss beyond the switch and to route traffic only through team members that have a live link. This function is accomplished though the teaming software. The teaming software periodically probes (issues a link packet from each team member) one or more specified target network device(s). The probe target(s) responds when it receives the link packet. If a team member does not detect the response within a specified amount of time, this indicates that the link has been lost, and 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™ is supported in both 32-bit and 64-bit Windows operating systems. Refer to the Channel Bonding documentation for similar functionality in Linux Channel Bonding (refer to http:// www.redhat.com/docs/manuals/enterprise/RHEL-3-Manual/ref-guide/s1-modules-ethernet.html).

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.

1.3.4 Virtual LAN Function

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.

112

• Example of Servers Supporting Multiple VLANs with Tagging

"• Example of Servers Supporting Multiple VLANs with Tagging" ( 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 "• Example VLAN Network Topology" (

• Example VLAN Network Topology

Component Description

VLAN #1 An IP subnet consisting of the Main Server, PC #3, and PC #5. This subnet

VLAN #2 Includes the Main Server, PCs #1 and #2 via shared media segment, and PC

VLAN #3 Includes the Main Server, the Accounting Server and PC #4. This VLAN is

Main Server A high-use server that needs to be accessed from all VLANs and IP subnets.

Accounting Server

PCs #1 and #2 Attached to a shared media hub that is then connected to the switch. PCs #1

Jpg.113).

represents an engineering group.

#5. This VLAN is a software development group.

an accounting group.

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.

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.

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.

Jpg.113)" shows an example

1 1 Gbit/s Ethernet I/O Module 113

Component Description

PC #3 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.

PC #4 A member of VLAN #3, PC #4 can only communicate with the servers.

Tagging is not enabled on PC #4 switch port.

PC #5 A member of both VLANs #1 and #2, PC #5 has a 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.

` 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.

Adding VLANs to Teams

Each team supports up to 64 VLANs (63 tagged and 1 untagged). 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, refer to "5.5 Configuring Teaming" (

` 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.

Jpg.176).

114

Installing a 1Gbit/s Ethernet I/O Module

This chapter explains the installation procedure in the server blade.

WARNING

• When installing or removing this product, make sure to remove the server blade from the chassis. Failure to do so may cause electric shock. For details on how to remove the server blade from the chassis, refer to "Blade Server System Unit Hardware Guide".

CAUTION

• The circuit boards and soldered parts of internal options are exposed. They can be damaged by static electricity. Before handling them, first touch a metal part of the server blade to discharge static electricity from your body.

• Do not touch the circuitry on boards or soldered parts. Hold the metallic areas or the edges of the circuit boards.

• These products are susceptible to static electricity. Place them on conductive pads or keep them in their packaging as long as they are not necessary.

2 Installing a 1Gbit/s Ethernet I/O Module 115

2.1 Installing in a Server Blade

` To connect a 1Gbit/s Ethernet I/O Module to the external LAN (device), it is necessary to

install a Switch Blade or GbE Pass-Thru Blade to network blade slot 3 or network blade slot 4 (NET3 or NET4) of the chassis.

2.1.1 Installation Position of the 1Gbit/s Ethernet I/O Module

Install the 1Gbit/s Ethernet I/O Module in the expansion board slot in the BX620 S3/BX620 S4 Server Blade.

Expansion board slot

2.1.2 Installation Procedure for the 1Gbit/s Ethernet I/O Module

1 Turn off the server blade where the 1Gbit/s Ethernet I/O Module

will be installed.

→

"3.3 Turning Off the Server " in "Blade Server System Unit Hardware Guide"

2 Touch a metal part of the chassis to discharge static electricity

from your body.

3 Remove the server blade from the chassis.

→"4.2 Installing Server Blades" in "Blade Server System Unit Hardware Guide"

116

4 Remove the top cover.

→"7.2 Removing and Attaching the Top Cover" in "Server Blade User's Guide"

5 Install the 1Gbit/s Ethernet I/O Module.

Make sure the 1Gbit/s Ethernet I/O Module is securely on the slot.

[Rear]

1Gbit/s Ethernet I/O Module

Expansion board slot

6 Secure the 1Gbit/s Ethernet I/O Module with the screws.

Secure the 1Gbit/s Ethernet I/O Module with the three screws included with this product.

Screws

7 Attach the top cover.

→"7.2 Removing and Attaching the Top Cover" in "Server Blade User's Guide"

8 Install the server blade to the chassis.

→"4.2 Installing Server Blades" in "Blade Server System Unit Hardware Guide"

2 Installing a 1Gbit/s Ethernet I/O Module 117

Installing the LAN Driver

This chapter explains how to install the LAN driver.

3.1 Installing the Driver Software

` Get the LAN driver from the ServerStart CD-ROM included with the BX620 S4 server blade

and install. If using a LAN driver, refer to the operation manual or help file included with the driver.

` Do not use LAN drivers downloaded from Broadcom's online service in the PRIMERGY

server.

` Before installing the driver software, verify that the Windows operating system has been

upgraded to the latest version with the latest service pack applied.

` To use TCP/IP Offload Engine (TOE), you must have Windows Server 2003 with Scalable

Networking Pack (SNP)

3.1.1 Installing the LAN Drivers

The installer will detect if SNP for Windows Server 2003 is installed on your machine. If it is, the installer will install the NDIS 5.2 driver, which is necessary in order to use TOE. If SNP for Windows Server 2003 is not installed on your machine, the installer will install the NDIS 5.1 driver and you will not be able to use TOE.

1 Insert the ServerStart Disc1 CD-ROM.

118

2 Execute the following EXE file.

• For Windows Server 2003 x64

\DRIVERS\LAN\Broadcom\Ext\W2K3x64\DrvInst\setup.exe

• For Windows Server 2003

\DRIVERS\LAN\Broadcom\Ext\W2K3\DrvInst\setup.exe

• For Windows Server 2000

\DRIVERS\LAN\Broadcom\Ext\W2K\DrvInst\setup.exe

3 Click [Next].

The installation of the LAN driver is started.

4 Click [Finish].

5 Eject the CD-ROM, and restart the server blade.

Broadcom Gigabit Ethernet Teaming Services

This chapter explains the technology and considerations when working with the network teaming services.

4.1 Broadcom Gigabit Ethernet Overview

The goal of Broadcom teaming services is to provide fault tolerance and link aggregation across a team of two or more adapters. The information in this manual is provided to assist IT professionals during the deployment and troubleshooting of system applications that require network fault tolerance and load balancing.

4.2 Glossary

Item Definition

ARP Address Resolution Protocol

BACS Broadcom Advanced Control Suite

BASP Broadcom Advanced Server Program (intermediate driver)

DNS Domain Name Service

G-ARP Gratuitous Address Resolution Protocol

Generic Trunking (FEC/GEC)/

802.3ad-Draft Static

HSRP Hot Standby Router Protocol

ICMP Internet Control Message Protocol

IGMP Internet Group Management Protocol

IP Internet Protocol

LACP Link Aggregation Control Protocol

Link Aggregation (802.3ad)

LOM LAN on Motherboard

MAC Media Access Control

NDIS Network Driver Interface Specification

NLB Network Load Balancing (Microsoft)

Switch-dependent load balancing and failover type of team in which the intermediate driver manages outgoing traffic and the switch manages incoming traffic.

Switch-dependent load balancing and failover type of team with LACP in which the intermediate driver manages outgoing traffic and the switch manages incoming traffic.

4 Broadcom Gigabit Ethernet Teaming Services 119

Item Definition

PXE Preboot Execution Environment

RAID Redundant Array of Inexpensive Disks

Smart Load Balancing™ and Failover

Smart Load Balancing (SLB)

TCP Transmission Control Protocol

UDP User Datagram Protocol

WINS Windows name service

WLBS Windows Load Balancing Service

Switch-independent failover type of team in which the primary team member handles all incoming and outgoing traffic while the standby team member is idle until a failover event (for example, loss of link occurs). The intermediate driver (BASP) manages incoming/outgoing traffic.

Switch-independent load balancing and failover type of team, in which the intermediate driver manages outgoing/incoming traffic.

120

4.3 Teaming Concepts

Storage devices use RAID technology to group individual hard drives. Switch ports can be grouped together using technologies such as Cisco Gigabit EtherChannel, IEEE 802.3ad Link Aggregation, Bay Network Multilink Trunking, and Extreme Network Load Sharing. Network interfaces on servers can be grouped together into a team of physical ports called a virtual adapter.

4.3.1 Teaming and Network Addresses

Network Addressing

To understand how teaming works, it is important to understand how node communications work in an Ethernet network. This Section is based on the assumption that the reader is familiar with the basics of IP and Ethernet network communications. The following information provides the concepts of network addressing used in an Ethernet network. Every Ethernet network interface in a host platform, such as a computer system, requires a globally unique Layer 2 address and at least one globally unique Layer 3 address. Layer 2 is the Data Link Layer, and Layer 3 is the Network layer as defined in the OSI model. The Layer 2 address is assigned to the hardware and is often referred to as the MAC address or physical address. This address is preprogrammed at the factory and stored in NVRAM on a network interface card or on the system motherboard for an embedded LAN interface. The Layer 3 addresses are referred to as the protocol or logical address assigned to the software stack. IP and IPX are examples of Layer 3 protocols. In addition, Layer 4 (Transport Layer) uses port numbers for each network upper level protocol such as Telnet or FTP. These port numbers are used to differentiate traffic flows across applications. The combination of the IP address and the TCP port number is called a socket. Ethernet devices communicate with other Ethernet devices using the MAC address, not the IP address. However, most applications work with a host name that is translated to an IP address by a Naming Service such as WINS and DNS. Therefore, a method of identifying the MAC address assigned to the IP address is required. The Address Resolution Protocol for an IP network provides this mechanism. For IPX, the MAC address is part of the network address and ARP is not required. ARP is implemented using an ARP Request and ARP Reply frame. ARP Requests are typically sent to a broadcast address while the ARP Reply is typically sent as unicast traffic. A unicast address corresponds to a single MAC address or a single IP address. A broadcast address is sent to all devices on a network.

Teaming and Network Addresses

A team of adapters will function as a single virtual network interface, and do not appear to be any different than a non-teamed adapter to other network devices. A virtual network adapter advertises a single Layer 2, and one or more Layer 3 addresses. When the teaming driver initializes, it selects one MAC address from one of the physical adapters that make up the team to be the Team MAC address. This address is typically taken from the first adapter that gets initialized by the driver. When the system hosting the team receives an ARP request, it selects one MAC address from among the physical adapters in the team to use as the source MAC address in the ARP Reply. In Windows operating systems, the IPCONFIG /all command shows the IP and MAC address of the virtual adapter and not the individual physical adapters. The protocol IP address is assigned to the virtual network interface and not to the individual physical adapters.

4 Broadcom Gigabit Ethernet Teaming Services 121

For switch-independent teaming modes, all physical adapters that make up a virtual adapter must use the unique MAC address assigned to them when transmitting data. That is, the frames that are sent by each of the physical adapters in the team must use a unique MAC address to be IEEE compliant. It is important to note that ARP cache entries are not learned from received frames, but only from ARP requests and ARP replies.

4.3.2 Types of Teams

"Available Teaming Types" shows a summary of the teaming types and their classification. Available Teaming Types

Link

Aggregation

Teaming Type

Smart Load Balancing and Failover

SLB (Auto-Fallback Disable)

Link Aggregation (802.3ad)

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

*1: Switch must support specific type of team.

*2: Link aggregation is not supported in the Blade Server.

Switch-

Dependent

––



 – 

Control Protocol

Required on the

Support

Switch

Load

Balancing

Failover

Smart Load Balancing and Failover

The Smart Load Balancing™ and Failover type of team provides both load balancing and failover when configured for load balancing, and only failover when configured for fault tolerance. This type of team works with any Ethernet switch and requires no trunking configuration on the switch. The team advertises multiple MAC addresses and one or more IP addresses (when using secondary IP addresses). The team MAC address is selected from the list of load balance members. When the system receives an ARP request, the software-networking stack will always send an ARP Reply with the team MAC address. To begin the load balancing process, the teaming driver will modify this ARP reply by changing the source MAC address to match one of the physical adapters.

122

Smart Load Balancing enables both transmit and receive load balancing based on the Layer 3/Layer 4 IP address and TCP/UDP port number. In other words, the load balancing is not done at a byte or frame level but on a TCP/UDP session basis. This methodology is required to maintain in-order delivery of frames that belong to the same socket conversation. Load balancing is supported on 2-8 ports. These ports can include any combination of add-in adapters and LAN on Motherboard (LOM) devices. Transmit load balancing is achieved by creating a hashing table using the source and destination IP addresses and TCP/UDP port numbers.The same combination of source and destination IP addresses and TCP/UDP port numbers will generally yield the same hash index and therefore point to the same port in the team. When a port is selected to carry all the frames of a given socket, the unique MAC address of the physical adapter is included in the frame, and not the team MAC address. This is required to comply with the IEEE 802.3 standard. If two adapters transmit using the same MAC address, then a duplicate MAC address situation would occur that the switch could not handle.

Receive load balancing is achieved through an intermediate driver by sending gratuitous ARPs on a client by client basis using the unicast address of each client as the destination address of the ARP request (also known as a directed ARP). This is considered client load balancing and not traffic load balancing. When the intermediate driver detects a significant load imbalance between the physical adapters in an SLB team, it will generate G-ARPs in an effort to redistribute incoming frames. The intermediate driver (BASP) does not answer ARP requests; only the software protocol stack provides the required ARP Reply. The receive load balancing is a function of the number of clients that are connecting to the system through the team interface.

SLB receive load balancing attempts to load balance incoming traffic for client machines across physical ports in the team. It uses a modified gratuitous ARP to advertise a different MAC address for the team IP Address in the sender physical and protocol address. This G-ARP is unicast with the MAC and IP Address of a client machine in the target physical and protocol address respectively. This causes the target client to update its ARP cache with a new MAC address map to the team IP address. G-ARPs are not broadcast because this would cause all clients to send their traffic to the same port. As a result, the benefits achieved through client load balancing would be eliminated, and could cause out of order frame delivery. This receive load balancing scheme works as long as all clients and the teamed system are on the same subnet or broadcast domain.

When the clients and the system are on different subnets, and incoming traffic has to traverse a router, the received traffic destined for the system is not load balanced. The physical adapter that the intermediate driver has selected to carry the IP flow carries all of the traffic. When the router sends a frame to the team IP address, it broadcasts an ARP request (if not in the ARP cache). The server software stack generates an ARP reply with the team MAC address, but the intermediate driver modifies the ARP reply and send it over a particular physical adapter, establishing the flow for that session.

The reason is that ARP is not a routable protocol. It does not have an IP header and therefore is not sent to the router or default gateway. ARP is only a local subnet protocol. In addition, since the GARP is not a broadcast packet, the router will not process it and will not update its own ARP cache.

The only way that the router would process an ARP that is intended for another network device is if it has Proxy ARP enabled and the host has no default gateway. This is very rare and not recommended for most applications.

4 Broadcom Gigabit Ethernet Teaming Services 123

Transmit traffic through a router will be load balanced as transmit load balancing is based on the source and destination IP address and TCP/UDP port number. Since routers do not alter the source and destination IP address, the load balancing algorithm works as intended.

Configuring routers for Hot Standby Routing Protocol (HSRP) does not allow for receive load balancing to occur in the adapter team. In general, HSRP allows for two routers to act as one router, advertising a virtual IP and virtual MAC address. One physical router is the active interface while the other is standby. Although HSRP can also load share nodes (using different default gateways on the host nodes) across multiple routers in HSRP groups, it always points to the primary MAC address of the team.

SLB (Auto-Fallback Disable)

This type of team is identical to the Smart Load Balance 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. This type of team is supported only for situations in which the network cable is disconnected and reconnected to the network adapter. It is not supported for situations in which the adapter is removed/ installed through Device Manager or Hot-Plug PCI. 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.

Link Aggregation (IEEE 802.3ad LACP)

Link Aggregation is similar to Generic Trunking except that it uses the Link Aggregation Control Protocol to negotiate the ports that will make up the team. LACP must be enabled at both ends of the link for the team to be operational. If LACP is not available at both ends of the link, 802.3ad provides a manual aggregation that only requires both ends of the link to be in a link up state. Because manual aggregation provides for the activation of a member link without performing the LACP message exchanges, it should not be considered as reliable and robust as an LACP negotiated link. LACP automatically determines which member links can be aggregated and then aggregates them. It provides for the controlled addition and removal of physical links for the link aggregation so that no frames are lost or duplicated. The removal of aggregate link members is provided by the marker protocol that can be optionally enabled for Link Aggregation Control Protocol (LACP) enabled aggregate links. The Link Aggregation group advertises a single MAC address for all the ports in the trunk. The MAC address of the Aggregator can be the MAC addresses of one of the MACs that make up the group. LACP and marker protocols use a multicast destination address. The Link Aggregation control function determines which links may be aggregated and then binds the ports to an Aggregator function in the system and monitors conditions to determine if a change in the aggregation group is required. Link aggregation combines the individual capacity of multiple links to form a high performance virtual link. The failure or replacement of a link in an LACP trunk will not cause loss of connectivity. The traffic will simply be failed over to the remaining links in the trunk.

124

` Link aggregation is not supported in the Blade Server.

Generic Trunking

Generic Trunking is a switch-assisted teaming mode and requires configuring ports at both ends of the link: server interfaces and switch ports. This is often referred to as Cisco Fast EtherChannel or Gigabit EtherChannel. In addition, generic trunking supports similar implementations by other switch OEMs such as Extreme Networks Load Sharing and Bay Networks or IEEE 802.3ad Link Aggregation static mode. In this mode, the team advertises one MAC Address and one IP Address when the protocol stack responds to ARP Requests. In addition, each physical adapter in the team uses the same team MAC address when transmitting frames. This is possible since the switch at the other end of the link is aware of the teaming mode and will handle the use of a single MAC address by every port in the team. The forwarding table in the switch will reflect the trunk as a single virtual port. In this teaming mode, the intermediate driver controls load balancing and failover for outgoing traffic only, while incoming traffic is controlled by the switch firmware and hardware. As is the case for Smart Load Balancing, the BASP intermediate driver uses the IP/TCP/UDP source and destination addresses to load balance the transmit traffic from the server. Most switches implement an XOR hashing of the source and destination MAC address.

4.3.3 Software Components

Teaming is implemented via an NDIS intermediate driver in the Windows Operating System environment. This software component works with the miniport driver, the NDIS layer, and the protocol stack to enable the teaming architecture (refer to "• Process for Selecting a Team Type" (

Jpg.129)). The miniport driver controls the host LAN controller directly to enable functions such as

send, receive, and interrupt processing. The intermediate driver fits between the miniport driver and the protocol layer multiplexing several miniport driver instances, and creating a virtual adapter that looks like a single adapter to the NDIS layer. NDIS provides a set of library functions to enable the communications between either miniport drivers or intermediate drivers and the protocol stack. The protocol stack implements IP, IPX and ARP. A protocol address such as an IP address is assigned to each miniport device instance, but when an Intermediate driver is installed, the protocol address is assigned to the virtual team adapter and not to the individual miniport devices that make up the team.

The Broadcom supplied teaming support is provided by three individual software components that work together and are supported as a package. When one component is upgraded, all the other components must be upgraded to supported versions. "• Broadcom Teaming Software Component" (

Jpg.126) describes the three software components and their associated files for supported operating

systems.

4 Broadcom Gigabit Ethernet Teaming Services 125

• Broadcom Teaming Software Component

Software

Component

– Virtual Bus Driver (VBD) bxvbdx.sys

Miniport Driver Broadcom Base Driver bxnd50x.sys

Intermediate Driver

Configuration User Interface

Broadcom Name Windows File Name

bxvbda.sys

bxnd51x.sys bxnd51a.sys bxnd52x.sys bxnd52a.sys*

Broadcom Advanced Server Program (BASP)

Broadcom Advanced Control Suite 2 (BACS2)

Baspxp32.sys Baspw2k.sys

BACS2

*: For 64-bit systems

4.3.4 Hardware Requirements

The various teaming modes described in this manual place certain restrictions on the networking equipment used to connect clients to teamed systems. Each type of network interconnect technology has an effect on teaming as described in the following sections.

• Repeater Hub

A Repeater Hub allows a network administrator to extend an Ethernet network beyond the limits of an individual segment. The repeater regenerates the input signal received on one port onto all other connected ports, forming a single collision domain. This means that when a station attached to a repeater sends an Ethernet frame to another station, every station within the same collision domain will also receive that message. If two stations begin transmitting at the same time, a collision occurs, and each transmitting station must retransmit its data after waiting a short (random) amount of time. The use of a repeater requires that each station participating within the collision domain operate in half-duplex mode. Although half-duplex mode is supported for Gigabit Ethernet adapters in the IEEE 802.3 specification, half-duplex mode is not supported by the majority of Gigabit Ethernet adapter manufacturers. Therefore, half-duplex mode will not be considered here. Teaming across hubs is supported for troubleshooting purposes (such as connecting a network analyzer) for SLB teams only.

•Switching Hub

Unlike a repeater hub, a switching hub (or more simply a switch) allows an Ethernet network to be broken into multiple collision domains. The switch is responsible for forwarding Ethernet packets between hosts based solely on Ethernet MAC addresses. A physical network adapter that is attached to a switch may operate in half-duplex or full-duplex mode. To support Generic Trunking and 802.3ad Link Aggregation, a switch must specifically support such functionality. If the switch does not support these protocols, it may still be used for Smart Load Balancing.

126

• Router

A router is designed to route network traffic based on Layer 3 or higher protocols, although it often also works as a Layer 2 device with switching capabilities. The teaming of ports connected directly to a router is not supported.

4.3.5 Configuring Teaming

The Broadcom Advanced Control Suite 2 (BACS2) utility is used to configure teaming in the supported operating system environments.

The BACS2 utility is designed to run in one of the following 32-bit and 64-bit Windows operating systems: Microsoft Windows 2000 Server and Windows Server 2003. BACS2 is used to configure load balancing and fault tolerance teaming, and VLANs. In addition, it displays the MAC address, driver version, and status information. BACS2 also includes a number of diagnostics tools such as hardware diagnostics, cable testing, and a network topology test.

4.3.6 Supported Features by Team Type

"Comparison of Team Types" provides a feature comparison across the team types. Use this table to determine the best type of team for your application. The teaming software supports up to eight ports in a single team and up to four teams in a single system. The four teams can be any combination of the supported teaming types, but each team must be on a separate network or subnet.

• Comparison of Team Types

Switch-

Type of Team

Function

Number of ports per team (same broadcast domain)

Number of teams 4 4 4 4

Adapter fault tolerance

Switch link fault tolerance (same broadcast domain)

TX load balancing No Yes Yes Yes

RX load balancing

Requires compatible switch

Heartbeats to check connectivity

Fault

Tolerance

SLB with

(*1)

Standby

2-8 2-8 2-8 2-8

Ye s Ye s Ye s Ye s

Ye s Ye s

No Yes

No No Yes Yes

No No No No

Load

Balancing

SLB

Dependent

Static

Trunking

Generic

Trunking

Switch-

dependent

Yes (performed

by the switch)

Switch-

Independent

Dynamic Link

Aggregation

(IEEE 802.3ad)

Link Aggregation

Switch-dependent

Yes (performed by

the switch)

4 Broadcom Gigabit Ethernet Teaming Services 127

Type of Team

Function

Fault

To le r a nc e

SLB with

Standby

(*1)

Load

Balancing

SLB

Mixed media (adapters with

Ye s Ye s

different media)

Mixed speeds (adapters that do not support a common speed(s), but can

Yes Yes No No

operate at different speeds)

Mixed speeds (adapters that support a common speed(s), but can

Ye s Ye s

operate at different speeds)

Load balances TCP/ IP

Mixed vendor teaming

Load balances nonIP No

N o Ye s Yes Ye s

Ye s

(*2)

Ye s

(*2)

Yes ( I P X

outbound

traffic only)

Same MAC address for all team

No No Yes Yes

members

Same IP address for all team members

Load balancing by IP address

Load balancing by MAC address

Ye s Ye s Ye s Ye s

N o Ye s Yes Ye s

Yes (used for

no-IP/IPX)

*1: SLB with one primary and one standby member. *2: Requires at least one Broadcom adapter in the team.

Switch-

Dependent

Static

Trunking

Generic

Trunking

Yes (switch-

dependent)

No (must be the

same speed)

(*2)

Ye s

Ye s Ye s

Switch-

Independent

Dynamic Link

Aggregation

(IEEE 802.3ad)

Link Aggregation

–

Ye s

(*2)

Ye s

128

` Link aggregation is not supported in the Blade Server.

4.3.7 Selecting a Team Type

The following flow chart provides the decision flow when planning for Layer 2 teaming. The primary rationale for teaming is the need for additional network bandwidth and fault tolerance. Teaming offers link aggregation and fault tolerance to meet both of these requirements. Preference teaming should be selected in the following order: IEEE 802.3ad as the first choice, Generic Trunking as the second choice, and SLB teaming as the third choice when using unmanaged switches or switches that do not support the first two options. if switch fault tolerance is a requirement, however, then SLB is the only choice (refer to "• Process for Selecting a Team Type" (

• Process for Selecting a Team Type

Jpg.129)).

Yes

Do you need additional

network bandwidth or fault

tolerance?

Yes

Do you need switch

fault tolerance?

Are you using a

switch that supports IEEE

802.3ad LACP?

Are you using a

switch that supports Static

Trunking (FEC/GEC?)

Yes

No Teaming

Set up a Dynamic

Trunking Team

Set up a Generic

Trunking Team

Set up an SLB

Tea m

4 Broadcom Gigabit Ethernet Teaming Services 129

4.4 Teaming Mechanisms

4.4.1 Architecture

The Broadcom Advanced Server Program (BASP) is implemented as an NDIS intermediate driver (refer to "• Teaming Across Switches Without an Interswitch Link" ( protocol stacks such as TCP/IP and IPX and appears as a virtual adapter. This virtual adapter inherits the MAC Address of the first port initialized in the team. A Layer 3 address must also be configured for the virtual adapter. The primary function of BASP is to balance inbound (for SLB) and outbound traffic (for all teaming modes) among the physical adapters installed on the system selected for teaming. The inbound and outbound algorithms are independent and orthogonal to each other. The outbound traffic for a particular session can be assigned to a given port while its corresponding inbound traffic can be assigned to a different port.

• Intermediate Driver

Jpg.141)). It operates below

TCP/IP

Broadcom Intermediate Driver

Virtual NIC Interface #1

Hash

Physical NIC

Interface #1

Miniport Driver Interface #1

NIC 1

IP/X

NDIS

Te am 1

Physical NIC

Interface #2

NDIS

Miniport Driver Interface #2

NetBEUI

NIC 2

130

+ 68 hidden pages