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).
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. Ignoring this symbol could be potentially lethal.
Red Hat Enterprise Linux 5 (for Intel64) 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...
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. All Rights Reserved, Copyright© FUJITSU LIMITED 2007...
Contents 1 1 Gbit/s Ethernet I/O Module ......106 Overview ..........Specifications .
1 Gbit/s Ethernet I/O Module This chapter explains the features and specifications of this product. 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.
Functionality and Features 1.3.1 Functional Description This product is a new class of Gigabit Ethernet (GbE) converged network interface controller (C- NIC) that can simultaneously perform accelerated data networking, storage networking, and high- performance clustering on a standard Ethernet network. The C-NIC offers acceleration for all popular protocols used in the data center, such as: •...
• 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 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.
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.
• Example of Servers Supporting Multiple VLANs with Tagging "• Example of Servers Supporting Multiple VLANs with Tagging" ( pg.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.
Component 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.
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".
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...
Remove the top cover. → "7.2 Removing and Attaching the Top Cover" in "Server Blade User's Guide" Install the 1Gbit/s Ethernet I/O Module. Make sure the 1Gbit/s Ethernet I/O Module is securely on the slot. 1Gbit/s Ethernet I/O Module Expansion board slot Secure the 1Gbit/s Ethernet I/O Module with the screws.
Installing the LAN Driver This chapter explains how to install the LAN driver. 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.
Broadcom Gigabit Ethernet Teaming Services This chapter explains the technology and considerations when working with the network teaming services. 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 Preboot Execution Environment RAID Redundant Array of Inexpensive Disks Smart Load Switch-independent failover type of team in which the primary team member Balancing™ and handles all incoming and outgoing traffic while the standby team member is Failover idle until a failover event (for example, loss of link occurs). The intermediate driver (BASP) manages incoming/outgoing traffic.
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.
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.
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.
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 – Miniport Driver Intermediate Driver Configuration User Interface 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.
• 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...
Type of Team Function Mixed media (adapters with different media) Mixed speeds (adapters that do not support a common speed(s), but can operate at different speeds) Mixed speeds (adapters that support a common speed(s), but can operate at different speeds) Load balances TCP/ Mixed vendor teaming...
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.
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" ( pg.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.
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.
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.
4.4.5 Performance Modern network interface cards provide many hardware features that reduce CPU utilization by offloading certain CPU intensive operations ( "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.
• 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).
Attributes of the Features Associated with Each Type of Team The attributes of the features associated with each type of team are summarized below. • Smart Load Balancing Feature User interface Number of teams Number of adapters per team Hot replace Hot add Hot remove Link speed support...
Feature MAC address Multivendor teaming *1: Some switches require matching link speeds to correctly negotiate between trunk connections. *2: Make sure that Port Fast or Edge Port is enabled. • Dynamic Trunking Feature User interface Number of teams Number of adapters per team Hot replace Hot add Hot remove...
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.
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 With Interconnect ARP Table: .100=49:C9 SLB Team .102=5E:CA 192.168.1.101 82:83 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* *Bottom Switch Port24 MAC Address "•...
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.
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.
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.
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.
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. •...
Question Can I connect the teamed adapters to a hub? Can I connect the teamed adapters to ports in a router? Can I use teaming with Microsoft Cluster Services? Can PXE work over a virtual adapter (team)? What is the maximum number of ports that can be teamed together? What is the maximum number of teams that can be configured on the same server?
Question Can I configure NLB and teaming concurrently? Should both the backup server and client servers that are backed up be teamed? Is there any special configuration required in the tape backup software or hardware to work with adapter teaming? How do I know what driver I am currently using? Can SLB detect a switch failure in a Switch...
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)" ( pg.151) and "4.9.3 Intermediate Driver (Virtual Adapter/Team)" ( pg.153). As a Broadcom adapter driver loads, Windows places a status code in the system event viewer.
Message Message Number Network controller configured for 10Mb full- duplex link. Network controller configured for 100Mb half-duplex link. Network controller configured for 100Mb full-duplex link. Network controller configured for 1Gb half- duplex link. Network controller configured for 1Gb full- duplex link. Medium not supported.
Message Message Number Unknown PHY detected. Using a default PHY initialization routine. This driver does not support this device. Upgrade to the latest driver. Driver initialization failed. 4.9.3 Intermediate Driver (Virtual Adapter/Team) The intermediate driver is identified by BLFM regardless of the base driver revision. "• Intermediate Driver Event Log Messages"...
Message Number Could not bind to adapter. Successfully bind to adapter. Network adapter is disconnected. Network adapter is connected. Broadcom Advanced Program Features Driver is not designed to run on this version of Operating System. Hot-standby adapter is selected as the primary adapter for a team without a load balancing adapter.
Message Message Number Network adapter is disabled via management interface. Network adapter is activated and is participating in network traffic. Network adapter is de- activated and is no longer participating in network traffic. Cause Corrective Action The driver has Informational message successfully disabled a only.
Broadcom Advanced Control Suite 2 (BACS2) This chapter explains the Broadcom Advanced Control Suite 2 (BACS2). 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 • IP Address • Speed • Driver Name • Firmware Version •...
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. To use TCP/IP Offload Engine (TOE), you must have Windows Server 2003 with Scalable Networking Pack (SNP) The installer checks if SNP for Windows Server 2003 is installed on the machine.
For Windows Server 2003 x64 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. Click [Next]. License agreement window appears 5 Broadcom Advanced Control Suite 2 (BACS2)
Click "I accept the terms in the license agreement" and click [Next]. Custom Set up window appears. 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. Start the following EXE file from the ServerStart Disc1 CD-ROM attached to the BX620 S4.
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. Setting of BACS2 5.4.1 Vital Sign...
Item Driver Status Loaded Not Loaded Information Not Available Driver Name/Version/Date LiveLink IP Address Offload Capabilities BASP State Network Status The following network status information is provided. Item Link Status The indicator is green if a link is established. A red indicator means that a link is not established.
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.
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 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.
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 ASIC Version Boot Code 1 Version Boot Code 2 Version Vendor ID Device ID Subsystem Vendor ID Subsystem ID Description The chip version of the Broadcom adapter (this information is not...
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.
Item Checksum Offload Flow Control Large Send Offload Description 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. •...
Item Locally Administered The Locally Administered Address is a user-defined MAC address that is Address 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.
Item 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.
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 Frames Tx.
Item 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.
Custom Statistics Item Out of Recv. Buffer Frames size less than 64-byte with bad FCS MAC Rx w/ Pause Command and Length = 0 MAC Rx w/ Pause Command and Length greater than 0 MAC Rx w/ no Pause Command MAC Sent X-on MAC Sent X-off Large Send Offload...
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 Broadcom Advanced Control Suite 2 (BACS2)
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 On the BACS2 "Tools"...
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.
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.
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.
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.
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 team name cannot exceed 39 characters, cannot begin with spaces, and cannot contain any of the following characters: & \ / : * ? < > | 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).
Type the VLAN tag value and then click [Next]. The value must be between 1 and 4094. Click [Yes] to add another VLAN and then click [Next]. Repeat until you do not want to add any additional VLANs. You can define up to 64 VLANs per team (63 VLANs that are tagged and 1 VLAN that is not tagged).
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.
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"...
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]. Assign any available adapter or adapters to the team by moving the adapter from the "Available Adapters" list to the "Load Balance Members"...
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.
The following shows how to modify a team. Click the BACS2 "Tools" menu → "Create a Team". The wizard Welcome screen appears. Click [Next] to continue modifying a team using the wizard or click [Expert Mode] to work in Expert Mode. Make the desired changes, and then click [OK].
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. 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". 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].
The following shows how to configure a LiveLink. Right-click the name of the Smart Load Balance and Failover (SLB) team, and then click "Configure LiveLink". 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"...
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.
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.
Fax: +852-2827-4724 Address: 10/F., Lincoln House, 979 King's Road Taikoo Place, Island East, Hong Kong • Indonesia: PT. Fujitsu Systems Indonesia Offices Headquarters Tel: +62-21-570-9330 (Hunting) Fax: +62-21-573-5150 Address: Wisma Kyoei Prince 10th Floor Jl. Jend. Sudirman Kav 3-4 Jakarta, Indonesia 10220 •...
Address: Unit 802-8th floor, Fortuna Tower Hanoi 6B Lang ha Street, Ba dinh District, Hanoi Socialist Republic of Vietnam • United States: Fujitsu Computer Systems Corporation Tel: +1-800-831-3183 Fax: +1-408-496-0575 Address: 1250 East Arques Avenue, Sunnyvale, CA USA 94088-3470 For the latest information, refer to the Fujitsu PRIMERGY website (http://primergy.fujitsu.com).
● 落丁、乱丁本は、お取り替えいたします。 • The contents of this manual may be revised without prior notice. • Fujitsu assumes no liability for damages to third party copyrights or other rights arising from the use of any information in this manual. • No part of this manual may be reproduced in any form without the prior written permission of Fujitsu.
こ のマ ニ ュ アルは リ サイ ク ルに配慮 し て製本 さ れています。 不要にな っ た際は、 回収 ・ リ サイ ク ルに出 し て く だ さ い。...