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.
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 Ignoring this symbol could be potentially lethal. CAUTION Ignoring this symbol may lead to injury and/or damage this product. The following symbols are used to indicate the type of warning or cautions being described.
Abbreviations The following expressions and abbreviations are used to describe the product names used in this manual.
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.
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 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. ` ` 1.
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.
• • • • • 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.
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.
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.
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.
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.
• Example of Servers Supporting Multiple VLANs with Tagging "• Example of Servers Supporting Multiple VLANs with Tagging" (Jpg.113)" 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 "• Example VLAN Network Topology" (Jpg.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.
2 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.
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.
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.
3 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.
4 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.
Item 120 Definition PXE Preboot Execution Environment RAID Redundant Array of Inexpensive Disks Smart Load Balancing™ and Failover 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.
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.
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.
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 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.
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.
• Broadcom Teaming Software Component Software Component – Broadcom Name Windows File Name Virtual Bus Driver (VBD) bxvbdx.sys bxvbda.sys* Miniport Driver Broadcom Base Driver bxnd50x.sys bxnd51x.sys bxnd51a.sys* bxnd52x.sys bxnd52a.sys* Intermediate Driver Broadcom Advanced Server Program (BASP) Baspxp32.sys Baspw2k.sys Configuration User Interface Broadcom Advanced Control Suite 2 (BACS2) BACS2 *: For 64-bit systems 4.3.
• 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.
Type of Team Fault Tolerance Load Balancing Function SLB with Standby(*1) SLB Generic Trunking Link Aggregation Mixed media (adapters with different media) Yes Yes Yes (switchdependent) – Mixed speeds (adapters that do not support a common speed(s), but can operate at different speeds) Yes Yes No No Mixed speeds (adapters that support a common speed(s), but can operate at different speeds) Yes Yes No (must be the same speed) Yes Load balances TCP/ IP No Yes Yes Yes Yes(*2) Yes(*
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.
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" (Jpg.141)). It operates below 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.
4.4.2 Outbound Traffic Flow The Broadcom Intermediate Driver manages the outbound traffic flow for all teaming modes. For outbound traffic, every packet is first classified into a flow, and then distributed to the selected physical adapter for transmission. The flow classification involves an efficient hash computation over known protocol fields. The resulting hash value is used to index into an Outbound Flow Hash Table.
On the inbound code path, the Inbound Flow Head Hash Table is also designed to allow concurrent access. The link lists of Inbound Flow Entries are only referenced in the event of processing ARP packets and the periodic load balancing. There is no per packet reference to the Inbound Flow Entries. Even though the link lists are not bounded; the overhead in processing each non-ARP packet is always a constant.
4.4.5 Performance Modern network interface cards provide many hardware features that reduce CPU utilization by offloading certain CPU intensive operations (J"4.7 Teaming and Other Advanced Networking Properties"(pg.138)). In contrast, the BASP intermediate driver is a purely software function that must examine every packet received from the protocol stacks and react to its contents before sending it out through a particular physical interface.
• Applications The SLB algorithm is most appropriate in home and small business environments where cost is a concern, or with commodity switching equipment. SLB teaming works with unmanaged Layer 2 switches and is a cost-effective way of getting redundancy and link aggregation at the server. Smart Load Balancing also supports teaming physical adapters with differing link capabilities. In addition, SLB is recommended when switch fault tolerance with teaming is required.
• Configuration Recommendations Static trunking supports connecting the teamed ports to switches if they are on the same broadcast domain and support generic trunking. It does not support connecting to a router or Layer 3 switches since the ports must be on the same subnet. Dynamic Trunking (IEEE 802.3ad Link Aggregation) This mode supports link aggregation through static and dynamic configuration via the Link Aggregation Control Protocol (LACP).
4.6 Attributes of the Features Associated with Each Type of Team The attributes of the features associated with each type of team are summarized below.
Feature Attribute MAC address Same for all adapters Multivendor teaming Yes *1: Some switches require matching link speeds to correctly negotiate between trunk connections. *2: Make sure that Port Fast or Edge Port is enabled.
4.7 Teaming and Other Advanced Networking Properties Before creating a team, adding or removing team members, or changing advanced settings of a team member, make sure each team member has been configured in a similar way. Settings to check include VLANs and QoS Packet Tagging, Jumbo Frames, and the various offloads. Advanced adapter properties and teaming support are listed below.
Checksum Offload Checksum Offload is a property of the Broadcom network adapters that allows the TCP/IP/UDP checksums for send and receive traffic to be calculated by the adapter hardware rather than by the host CPU. In high-traffic situations, this can allow a system to handle more connections more efficiently than if the host CPU were forced to calculate the checksums. This property is inherently a hardware property and would not benefit from a software-only implementation.
Preboot Execution Environment The Preboot Execution Environment (PXE) allows a system to boot from an operating system image over the network. By definition, PXE is invoked before an operating system is loaded, so there is no opportunity for the BASP intermediate driver to load and enable a team. As a result, teaming is not supported as a PXE client, though a physical adapter that participates in a team when the operating system is loaded may be used as a PXE client.
Furthermore, a failover event would cause additional loss of connectivity. Consider a cable disconnect on the Top Switch port 4. In this case, Gray would send the ICMP Request to Red 49:C9, but because the Bottom switch has no entry for 49:C9 in its CAM Table, the frame is flooded to all its ports but cannot find a way to get to 49:C9. • Teaming Across Switches Without an Interswitch Link ARP Table: .100=49:C9 .102=5E:CA W2K Blue SLB Team 192.168.1.101 STOP Can not ping W2K3 Gray SLB Team 192.168.1.
• Teaming Across Switches With Interconnect ARP Table: .100=49:C9 .102=5E:CA W2K3 Gray SLB Team 192.168.1.102 W2K Blue SLB Team 192.168.1.101 82:82 (P) 5E:C9 82:83 1 24 Top Switch CAM Table: Eth 1: 82:83 Eth 2: 49:C9 Eth 4: 5E:C9 Eth 24: 82:82 Eth 24: 49:C8 Eth 24: 5E:CA Eth 24: A2:12* 5E:CA (P) 1 4 4 24 Bottom Switch 2 CAM Table: Eth 1: 82:82 Eth 2: 49:C8 Eth 4: 5E:CA Eth 24: 82:83 Eth 24: 49:C9 Eth 24: 5E:C9 Eth 24: B0:30** 2 49:C9 (P) ARP Table: .100=49:C9 .
4.8.3 Spanning Tree Algorithm In Ethernet networks, only one active path may exist between any two bridges or switches. Multiple active paths between switches can cause loops in the network. When loops occur, some switches recognize stations on both sides of the switch. This situation causes the forwarding algorithm to malfunction allowing duplicate frames to be forwarded.
4.8.4 Topology Change Notice (TCN) A bridge/switch creates a forwarding table of MAC addresses and port numbers by learning the source MAC address that received on a particular port. The table is used to forward frames to a specific port rather than flooding the frame to all ports. The typical maximum aging time of entries in the table is 5 minutes. Only when a host has been silent for 5 minutes would its entry be removed from the table. It is sometimes beneficial to reduce the aging time.
4.8.5 Port Fast/Edge Port To reduce the effect of TCNs on the network (for example, increasing flooding on switch ports), end nodes that are powered on/off often should use the Port Fast or Edge Port setting on the switch port they are attached to. Port Fast or Edge Port is a command that is applied to specific ports and has the following effects: • Ports coming from link down to link up will be put in the forwarding STP mode instead of going from listening to learning and then to forwarding.
4.8.9 SLB Teams SLB teams are the only teaming type not dependant on switch configuration. The server intermediate driver handles the load balancing and fault tolerance mechanisms with no assistance from the switch. These elements of SLB make it the only team type that maintains failover and fallback characteristics when team ports are connected directly to a hub. SLB Team Connected to a Single Hub SLB teams configured as shown in "• Team Connected to a Single Hub" (Jpg.
4.8.10 Troubleshooting Teaming Problems When running a protocol analyzer over a virtual adapter teamed interface, the MAC address shown in the transmitted frames may not be correct. The analyzer does not show the frames as constructed by BASP and shows the MAC address of the team and not the MAC address of the interface transmitting the frame. It is suggested to use the following process to monitor a team: • Mirror all uplink ports from the team at the switch.
Troubleshooting Guidelines Before you call for support, make sure you have completed the following steps for troubleshooting network connectivity problems when the server is using adapter teaming. • Make sure the link light is ON for every adapter and all the cables are attached. • Check that the matching base and intermediate drivers belong to the same release and are loaded correctly. • Check for a valid IP Address using the Windows ipconfig command.
Question Answer Can I connect the teamed adapters to a hub? Teamed ports can be connected to a hub for troubleshooting purposes only. However, this practice is not recommended for normal operation because the performance would be degraded due to hub limitations. Connect the teamed ports to a switch instead. Can I connect the teamed adapters to ports in a router? No. All ports in a team must be on the same network; in a router, however, each port is a separate network by definition.
Question 150 Answer Can I configure NLB and teaming concurrently? Yes, but only when running NLB in a multicast mode (NLB is not supported with MS Cluster Services). Should both the backup server and client servers that are backed up be teamed? Because the backup server is under the most data load, it should always be teamed for link aggregation and failover. A fully redundant network, however, requires that both the switches and the backup clients be teamed for fault tolerance and link aggregation.
4.9 Event Log Messages 4.9.1 Windows System Event Log messages The known base and intermediate Windows System Event Log status messages for this product are listed in "4.9.2 Base Driver (Physical Adapter/Miniport)" (Jpg.151) and "4.9.3 Intermediate Driver (Virtual Adapter/Team)" (Jpg.153). As a Broadcom adapter driver loads, Windows places a status code in the system event viewer.
Message Number 152 Message Cause Corrective Action 7 Network controller configured for 10Mb fullduplex link. The adapter has been manually configured for the selected line speed and duplex settings. Informational message only. No action is required. 8 Network controller configured for 100Mb half-duplex link. The adapter has been manually configured for the selected line speed and duplex settings. Informational message only. No action is required.
Message Number Message Cause Corrective Action 17 Unknown PHY detected. Using a default PHY initialization routine. The driver could not read the PHY ID. Replace the adapter. 18 This driver does not support this device. Upgrade to the latest driver. The driver does not recognize the installed adapter. Upgrade to a driver version that supports this adapter. 19 Driver initialization failed. Unspecified failure during driver initialization.
Message Number 154 Message Cause Corrective Action 7 Could not bind to adapter. The driver could not open one of the team physical adapters. Unload and reload the physical adapter driver, install an updated physical adapter driver, or replace the physical adapter. 8 Successfully bind to adapter. The driver successfully opened the physical adapter. Informational message only. No action is required. 9 Network adapter is disconnected.
Message Number Message Cause Corrective Action 15 Network adapter is disabled via management interface. The driver has successfully disabled a physical adapter through the management interface. Informational message only. No action is required. 16 Network adapter is activated and is participating in network traffic. A physical adapter has been added to or activated in a team. Informational message only. No action is required.
5 Broadcom Advanced Control Suite 2 (BACS2) This chapter explains the Broadcom Advanced Control Suite 2 (BACS2). 5.1 BACS2 Overview BACS2 is an integrated utility that provides useful information about each network adapter that is installed in your system. BACS2 also enables you to perform detailed tests, diagnostics, and analyses on each adapter, as well as to view and modify property values and view traffic statistics for each adapter.
5.1.1 Types of Information Provided by BACS2 BACS2 lists all of the network adapters in your system and provides the following information (if available) about each adapter: • Driver Status • MAC Address • Link Status • IP Address • Memory Address • Physical Address • Speed • Duplex • Slot No. • Driver Name • Driver Version • Driver Date • Firmware Version • ASIC Version • Bus Type • Bus No. • Device No. • Function No.
5.2 Installing the BACS2 If [Broadcom Control Suite 2] is not displayed in the "Control Panel", install BACS2 according to the following installation procedures: ` ` ` Ensure that this product is installed in the Server Blade before installing BACS2. Before you begin the installation, close all applications, windows, or dialog boxes.
For Windows Server 2003 x64 1 Start the following EXE file from the ServerStart Disc1 CD-ROM attached to the BX620 S4. [CD-ROM drive]: \PROGRAMS\GENERAL\Broadcom\MgmtApps_x64\setup.exe The installer starts up. 2 Click [Next].
3 Click "I accept the terms in the license agreement" and click [Next]. Custom Set up window appears. 4 Click [Next]. Proceed the installation by following the window instructions.
For Windows Server 2003, Windows 2000 Server ` If the OS is installed using ServerStart, "BACS2" is already installed with the driver. If the OS is installed manually, BACS2 will not be installed. 1 Start the following EXE file from the ServerStart Disc1 CD-ROM attached to the BX620 S4. [CD-ROM drive]: \PROGRAMS\GENERAL\Broadcom\MgmtApps\setup.exe The installer starts up. 2 Proceed the installation by following the window instructions.
5.3 Starting BACS2 To start BACS2, click "Control Panel" → "Broadcom Control Suite 2". Click the tab that provides the information of interest or from which to perform a desired test, diagnostic, analysis, or set adapter properties. To create a team, from the "Tools" menu, click [Create a Team], which starts the Teaming Wizard. 5.4 Setting of BACS2 5.4.
Item Driver Status Description The status of the adapter driver Loaded Normal operating mode. The adapter driver has been loaded by Windows and is functioning. Not Loaded The driver associated with the adapter has not been loaded by Windows. Information Not Available The value is not obtainable from the driver that is associated with the adapter. Driver Name/Version/Date The file name of the adapter driver. LiveLink IP Address The network address of the LiveLink enabled adapter.
Team Status The team status is indicated by the appearance of the icons representing the team and the team members. If the adapter icon shows only the adapter, the adapter is connected to a network, but is not correctly participating in the team, which corresponds to a Not Active BASP state. This condition does not apply to an adapter that is a standby member of a team. The standby adapter may be working properly even though it is Not Active.
5.4.2 Resources The following information can be checked on the "Resources" tab. ` Some information may not be available for all network adapters. Item Bus Type Description The type of input/output (I/O) interconnect used by the adapter Bridge The bridge type, which is the PCI-E to PCI-X bridge. Bridge Lanes The number of PCI-E lanes connected to the bridge. Bridge Speed The clock speed on PCI-E bus. Slot No The slot number on the system board occupied by the adapter.
5.4.3 Hardware The following information can be checked on the "Hardware" tab. ` Some information may not be available for all network adapters. Item 166 Description ASIC Version The chip version of the Broadcom adapter (this information is not available for adapters made by others). Boot Code 1 Version The version of boot code 1. Boot Code 2 Version The version of boot code 2. Vendor ID The vendor ID. Device ID The adapter ID. Subsystem Vendor ID The subsystem vendor ID.
5.4.4 Advanced The following information can be checked on the "Advanced" tab. The "Advanced" tab allows you to view and change the values of the available properties of the selected adapter. The potentially available properties and their respective settings are described below. To view the value of a property, click the name of the property in the "Property" list. The property value is displayed in the "Value" box.
Item 168 Description Checksum Offload Normally, the checksum function is computed by the protocol stack. When you select one of the Checksum Offload property values (other than None), the checksum can be computed by the network adapter. • Rx TCP/IP Checksum Enables receive TCP/IP/UDP checksum offload. • Tx TCP/IP Checksum Enables transmit TCP/IP/UDP checksum offload. • Tx/Rx TCP/IP Checksum (default) Enables transmit and receive TCP/IP/UDP checksum offload. • None Disables checksum offload.
Item Description Locally Administered Address The Locally Administered Address is a user-defined MAC address that is used in place of the MAC address originally assigned to the network adapter. Every adapter in the network must have its own unique MAC address. This locally administered address consists of a 12-digit hexadecimal number.
5.4.5 Network Test On the "Network Test" tab, you can verify IP network connectivity. This test verifies if the driver is installed correctly and tests connectivity to a gateway or other specified IP address on the same subnet. Network Test uses TCP/IP. The network test sends ICMP packets to remote systems and waits for a response. If a gateway is configured, the test automatically sends packets to that system.
Item Description Control Registers This test verifies the read and write capabilities of the network adapter registers by writing various values to the registers and verifying the results. The adapter driver uses these registers to perform network functions such as sending and receiving information. A test failure indicates that the adapter may not be working properly. MII Registers This test verifies the read and write capabilities of the registers of the physical layer (PHY).
5.4.7 Statistics On the "Statistics" tab, you can view traffic statistics for both Broadcom network adapters and network adapters made by others. Statistical information and coverage are more comprehensive for Broadcom adapters. ` Some statistics may not be available for all network adapters. General Statistics Item 172 Description Frames Tx. OK A count of the frames that were successfully transmitted. This counter is incremented when the transmit status is reported as Transmit OK. Frames Rx.
Item Description Multicast Frames Rx. A count of frames that were successfully received and are directed to an active nonbroadcast group address. This does not include frames received with frame-too-long, FCS, length, or alignment errors, or frames lost because of internal MAC sublayer errors. This counter is incremented as indicated by the Receive OK status. Broadcast Frames Rx. A count of frames that were successfully received and are directed to a broadcast group address.
Custom Statistics Item 174 Description Out of Recv. Buffer The number of times the adapter ran out of Receive Buffer Descriptors. Frames size less than 64-byte with bad FCS The number of frames with a size less than 64 bytes with bad FCS. MAC Rx w/ Pause Command and Length = 0 MAC control frames with the pause command and a length equal to 0. MAC Rx w/ Pause Command and Length greater than 0 MAC control frames with the pause command and a length greater than 0.
5.4.8 Licenses On the "Licenses" tab, you can view the number of connections available for TOE, iSCSI, and RDMA offload technologies. You can also upgrade your license for additional connections. ` ` The "Licenses" tab is only available for this product. Not all offload technologies are available with all adapters.
5.5 Configuring Teaming The teaming function allows you to group any available network adapters together to function as a team. Teaming is a method of creating a virtual LAN (a group of multiple adapters that functions as a single adapter). The benefit of this approach is that it enables load balancing and failover. Teaming is done through the Broadcom Advanced Server Program (BASP) software.
5.5.1 Using the Broadcom Teaming Wizard You can use the Broadcom Teaming Wizard to create a team, configure an existing team if a team has already been created, or create a VLAN. 5.5.2 Creating and Modifying a Team Using the Teaming Wizard 1 On the BACS2 "Tools" menu, click "Create a Team". ` If you prefer to work without the wizard for now, click [Expert Mode] and then click [Next].
4 Select the type of team you want to create and then click [Next]. If the team type is an SLB type team, click [Next]. If the team type is not an SLB type team, then a dialog box appears. Verify that the network switch connected to the team members is configured correctly for the team type, click [OK], and continue. 5 From the "Available Adapters" list, click the adapter you want to add to the team and then click [Add].
The Large Send Offload (LSO) and Checksum Offload (CO) columns indicate if the LSO and/or the CO properties are supported (Y) or not supported (N) for the adapter. The LSO and CO properties are enabled for a team only when all of the members support and are configured for the feature. If this is the case, then the team offload capabilities appear on the bottom of the screen.
7 Select the standby member from the list of adapters. The Auto-Fallback Disable mode feature allows the team to continue using the standby member rather than switching back to the primary member if the primary member comes back online. To enable this feature, click "Enable Auto-Fallback Disable mode" and then click [Next]. The Auto-Fallback Disable mode feature is enabled, LiveLink cannot be used. 8 If you want to configure LiveLink, click [Yes] and then click [Next].
10 Click the probe target at the top of the list, click "Edit Target IP Address", type the target IP address in the "IP Address" box for one or all probe targets, and then click [OK]. Click [Next]. ` Only the first probe target is required. You can specify up to three additional probe targets to serve as backups by assigning IP addresses to the other probe targets. 11 Click a listed team member, click "Edit Member IP Address", and then type the member IP address in the IP Address box.
12 If you want to create a VLAN on the team, click [Yes] and then click [Next]. If you do not want to create a VLAN to the team, click [No], click [Next], and continue with the wizard from the "Finish" screen (refer to Step 17 of this procedure). VLANs enable you to add multiple virtual adapters that are on different subnets. The benefit of this is that your system can have one network adapter that can belong to multiple subnets. ` VLANs can only be created when all team members are Broadcom adapters.
` The team name cannot exceed 39 characters, cannot begin with spaces, and cannot contain any of the following characters: & \ / : * ? < > | 14 To tag the VLAN, click "Tagged" and then click [Next]. Otherwise, click "Untagged", click [Next], and continue with the wizard to add additional VLANs (refer to Step 16 of this procedure).
15 Type the VLAN tag value and then click [Next]. The value must be between 1 and 4094. 16 Click [Yes] to add another VLAN and then click [Next]. Repeat until you do not want to add any additional VLANs. ` 184 You can define up to 64 VLANs per team (63 VLANs that are tagged and 1 VLAN that is not tagged). Adding several VLANS may slow down the reaction time of the Windows interface due to memory and processor time usage for each VLAN.
17 To apply and commit the changes to the team, click "Commit changes and return to Broadcom Advanced Control Suite 2" and then click [Finish]. To preview the changes to the team in BACS2, click "Preview changes in Broadcom Advanced Control Suite 2" and then click [Finish]. The wizard exits and BACS2 opens. 18 Click [Finish] to commit the changes. Click [Cancel] to discard the changes.
5.5.3 Using Expert Mode Use Expert Mode to create a team, modify a team, add a VLAN, and configure LiveLink for a Smart Load Balance and Failover team. To create a team using the wizard, refer to "5.5.2 Creating and Modifying a Team Using the Teaming Wizard" (Jpg.177). To switch to the Teaming Wizard from the BACS2 "Tools" menu, click "Customize". Select the "Default Teaming Mode" tab and select "Wizard Mode".
3 Type a team name in the "Enter a name you will use to identify this team" box, and click the type of team, and then click [Next]. 4 Assign any available adapter or adapters to the team by moving the adapter from the "Available Adapters" list to the "Load Balance Members" list. 5 Assign any other available adapter or adapters to the team by moving the adapter from the "Available Adapters" list to the "Standby Member" list. ` There must be at least one network adapter assigned to the team.
6 Click [Yes] when the message is displayed indicating that the network connection will be temporarily interrupted. ` ` ` ` The team name cannot exceed 39 characters, cannot begin with spaces, and cannot contain any of the following characters: & \ / : * ? < > | Team names must be unique. If you attempt to use a team name more than once, an error message is displayed indicating that the name already exists. The maximum number of team members is 8.
The following shows how to modify a team. 1 Click the BACS2 "Tools" menu → "Create a Team". The wizard Welcome screen appears. 2 Click [Next] to continue modifying a team using the wizard or click [Expert Mode] to work in Expert Mode. 3 Make the desired changes, and then click [OK]. 4 Click [Apply]. 5 Click [Yes] when the message is displayed indicating that the network connection will be temporarily interrupted. Adding a VLAN You also can add virtual LANs (VLANs) to a team.
3 Type the VLAN ID and VLAN name, and click [Apply]. ` If you type a VLAN name or ID and the name already exists, an error message is displayed. 4 Click [Yes] when the message is displayed indicating that the network connection will be temporarily interrupted. ` To maintain optimum adapter performance, your system should have 64 MB of system memory for each of the eight VLANs created per adapter.
Deleting a VLAN To delete a VLAN, right-click the VLAN and select "Remove VLAN". 1 Click the "Tools" menu → "Configure a Team". If there is more than one team, click the name of the team that has the VLAN you want to delete, and then click [OK]. 2 Click [Remove VLAN]. 3 Click [Apply]. Click [Yes] when the message is displayed indicating that the network connection will be temporarily interrupted. ` If you delete a team, any VLANs configured for that team are also deleted.
The following shows how to configure a LiveLink. 1 Right-click the name of the Smart Load Balance and Failover (SLB) team, and then click "Configure LiveLink". 2 Check the "Enable LiveLink" box. It is recommended to accept the default values for "Probe interval" (the number of seconds between each retransmission of a link packet to the probe target) and "Probe maximum retries" (the number of consecutively missed responses from a probe target before a failover is triggered).
4 Click one of the listed team members, click "Edit Member IP Address", type the member IP address in the "IP Address" box, and then click [OK]. ` All of the member IP addresses must be in the same subnet as the subnet for the probe targets. 5 Repeat step 4 for each of the other listed team members. 6 Click [Apply].
8 Click one of the listed team members, click "Edit Member IP Address", type the member IP address in the "IP Address" box, and then click [OK]. ` All of the member IP addresses must be in the same subnet as the subnet for the probe targets. 9 Repeat step 8 for each of the other listed team members. 10 Click [Apply]. Viewing the Team Properties and Statistics The following shows how to view the team properties and statistics. 1 Click the name of the newly created team.
Appendix A Contact Information • Australia: Fujitsu Australia Limited Tel: +61-2-9776-4555 Fax: +61-2-9776-4556 Address: 2 Julius Avenue (Cnr Delhi Road) North Ryde, Australia N.S.W. 2113 • China: Fujitsu (China) Holdings Co., Ltd. Tel: +86-21-5292-9889 Fax: +86-21-5292-9566 Address: 18F, Citic Square, 1168 West Nanjing Road Shanghai, China 200041 • Hong Kong: Fujitsu Hong Kong Limited Tel: +852-2827-5780 Fax: +852-2827-4724 Address: 10/F.
• Singapore: Fujitsu Asia Pte. Ltd. Tel: +65-6777-6577 Fax: +65-6771-5502 Address: 20, Science Park Road, #03-01 TeleTech Park, Singapore Science Park II, Singapore 117674 • Taiwan: Fujitsu Taiwan Limited Tel: +886-2-2311-2255 Fax: +886-2-2311-2277 Address: 19F, No.39, Section 1, Chung hwa Road Taipei, Taiwan • Thailand: Fujitsu Systems Business (Thailand) Ltd.
PRIMERGY LAN 拡張ボード(1Gbps) (PG-LND201) 取扱説明書 1Gbit/s Ethernet I/O Module (PG-LND201) User’s Guide B7FY-2091-01-00 発行日 発行責任 2007 年 5 月 富士通株式会社 Issued on Issued by May, 2007 FUJITSU LIMITED Printed in Japan ● 本書の内容は、改善のため事前連絡なしに変更することがあります。 ● 本書に記載されたデータの使用に起因する、第三者の特許権およびその他の 権利の侵害については、当社はその責を負いません。 ● 無断転載を禁じます。 ● 落丁、乱丁本は、お取り替えいたします。 • The contents of this manual may be revised without prior notice.
こ のマ ニ ュ アルは リ サイ ク ルに配慮 し て製本 さ れています。 不要にな っ た際は、 回収 ・ リ サイ ク ルに出 し て く だ さ い。