1. Manuals
  2. Brands
  3. HP Manuals
  4. Software
  5. Integrity rx2800 - i2
  6. White paper

HP Integrity rx2800 - i2 White Paper

Windows server 2008 sp2 and windows server 2008 r2 on hp integrity servers network adapter teaming
Hide thumbs Also See for Integrity rx2800 - i2:
Table of Contents

Advertisement

Quick Links

Download this manual See also: User and Service Manual, User Manual
Windows Server 2008 SP2 and Windows
Server 2008 R2 on HP Integrity Servers
Network Adapter Teaming White Paper
HP Part Number: 5992-5629
Published: October 2009

Advertisement

Table of Contents
loading

Related Manuals for HP Integrity rx2800 - i2

Summary of Contents for HP Integrity rx2800 - i2

  • Page 1 Windows Server 2008 SP2 and Windows Server 2008 R2 on HP Integrity Servers Network Adapter Teaming White Paper HP Part Number: 5992-5629 Published: October 2009...
  • Page 2 © Copyright 2009 Hewlett-Packard Development Company, L.P. Legal Notices Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

  • Page 3: Table Of Contents

    Table of Contents 1 Introduction........................9 Abstract..............................9 How to Read This Document.........................9 Section Layout............................9 2 An Executive Overview of Teaming................11 What is HP Integrity Network Adapter Teaming?................11 The Goals of HP Integrity Network Adapter Teaming................11 Fault Tolerance: Self-Healing Network Connectivity..............11 Load Balancing: RAID 5 for Server Network Adapters..............12 Why HP Integrity Network Adapter Teaming?...................13 3 Teaming Fundamentals for the First-Time User............15 A Technical Overview of HP Integrity Network Adapter Teaming.............15...
  • Page 4 Network Adapter Miniport Driver....................30 Teaming Intermediate Driver.....................30 HP Network Configuration Utility....................30 HP Teaming and Layer 2 Versus Layer 3 Addresses...............30 Types of HP Integrity Network Adapter Teams...................31 Network Fault Tolerance Only (NFT).....................31 Network Addressing and Communication with NFT...............32 Scenario 4–A: A Device Pings an NFT Team on the Same Layer 2 Network.......32 NFT Redundancy Mechanisms....................34 Basic Redundancy Mechanisms....................34 Advanced Redundancy Mechanisms...................37...
  • Page 5 Dual Channel Applications......................78 Recommended Configurations for Dual Channel Environments..........78 802.3ad Dynamic Dual Channel Load Balancing................79 802.3ad Dynamic Dual Channel Configuration.................79 Automatic............................79 Team Types and Redundancy Mechanisms Interoperation..............79 Team Type and Redundancy Mechanisms Compatibility Chart............79 Mechanism Priority.........................80 Team Status and Icons...........................81 Network Adapter Teamed Status....................81 Team State............................83 Team Icons............................83...
  • Page 6 List of Figures HP Integrity Network Adapter Teaming..................15 Using Multi-homing for server network redundancy..............16 Using NIC teaming for server network redundancy..............17 Teaming types and functionality....................18 How to choose the best team type....................21 NCU Main page..........................24 Overview of NFT communication....................32 Scenario 4–A: A device pings an NFT team on the same Layer 2 network........33 Team Properties page –...
  • Page 7 List of Tables Basic versus Advanced teaming features..................22 Dual Channel capabilities comparison..................23 Heartbeat Frame Format.......................36 802.1Q Tagged Heartbeat Frame Format..................36 Directed ARP Echo Node Probe REQUEST Frame Format............40 Directed ARP Echo Node Probe REPLY Frame Format..............40 Community Address ARP Echo Node Probe REQUEST Frame Format........43 Community Address ARP Echo Node Probe REPLY Frame Format...........43 Redundancy mechanism comparison chart..................54 Transmit Load Balancing method comparison................61...

  • Page 9: Introduction

    1 Introduction Abstract This white paper provides a high- and low-level discussion of the technology behind HP Integrity Network Adapter Teaming for HP Integrity servers running Microsoft® Windows®. HP Integrity Network Adapter Teaming is software-based technology used by server administrators and network administrators to increase a server’s network availability and performance.
  • Page 10 This white paper specifically discusses HP Integrity Network Adapter Teaming for Windows Server 2008 with Service Pack 2 (SP2) and Windows Server 2008 R2. For technical information on network adapter teaming for other operating systems, refer to www.hp.com. Introduction...

  • Page 11: An Executive Overview Of Teaming

    2 An Executive Overview of Teaming What is HP Integrity Network Adapter Teaming? HP Integrity Network Adapter Teaming is software-based technology used by server administrators and network administrators to increase a server’s network availability and performance. HP Integrity Network Adapter Teaming provides network adapter, network port, network cable, switch, and communication path fault recovery technology, in addition to, transmit and receive load balancing technology.

  • Page 12: Load Balancing: Raid 5 For Server Network Adapters

    administrator to provide a switch port to the server that has 100% uptime. While network administrators can achieve high availability in the network, they can’t promise 100% availability for the switch and switch port to which the server’s network adapter port is connected.

  • Page 13: Why Hp Integrity Network Adapter Teaming

    today’s servers ship standard with at least two network adapter ports, many built directly onto the motherboard (in other words, LAN On Motherboard or LOM). The SA need only install HP Integrity Network Adapter Teaming software, select at least two network adapter ports, and create a team.

  • Page 15: Teaming Fundamentals For The First-Time User

    3 Teaming Fundamentals for the First-Time User A Technical Overview of HP Integrity Network Adapter Teaming HP Integrity Network Adapter Teaming provides fault tolerance and load balancing across a team of two or more network adapter ports. The term “team” refers to the concept of multiple network adapters (teamed ports) working together as a single network adapter, commonly referred to as a virtual network adapter or virtual NIC interface.

  • Page 16: Using Multi-Homing For Server Network Redundancy

    Figure 3-2 Using Multi-homing for server network redundancy 1.1.1.3 1.1.1.1 1.1.1.4 1.1.1.2 1.1.1.5 HP Integrity Server Switch Clients Server has redundant path How do clients know the for outgoing traffic. server has two or more IP addresses? From the server’s IP perspective, Which IP address represents either adapter provides access the server for...

  • Page 17: Load Balancing: Server-Based Routing Protocol Or Nic Teaming

    Figure 3-3 Using NIC teaming for server network redundancy Integrity Server Clients Teaming Switch 1.1.1.3 Driver 1.1.1.1 C o n s o l e 1.1.1.4 1.1.1.5 •Server has redundant path for •Provides redundant connectivity outgoing traffic. from Clients to Server for same Server IP address.

  • Page 18: Network Fault Tolerance Only (Nft)

    Figure 3-4 Teaming types and functionality Advanced Teaming Basic Teaming Receive Load Balancing Basic Teaming Basic Teaming Transmit Load Balancing Switch Fault Tolerance* Switch Fault Tolerance* Network Adapter Fault Tolerance Transmit Load Switch-assisted Switch-assisted Dual Network Fault Balancing with Fault Load Balancing with Channel Load Tolerance Only...

  • Page 19: Transmit Load Balancing With Fault Tolerance (Tlb)

    Transmit Load Balancing with Fault Tolerance (TLB) Transmit Load Balancing with Fault Tolerance (TLB) is a team type that allows the server to load balance its transmit traffic. TLB is switch independent and supports switch fault tolerance by allowing the teamed ports to be connected to more than one switch in the same LAN. With TLB, traffic received by the server is not load balanced.

  • Page 20: 802.3Ad Dynamic Dual Channel Load Balancing

    different switches and one of the switches fail, the team remains available via the group attached to the functional switch. Switch-assisted Dual Channel Load Balancing is an advanced feature of HP Integrity Network Adapter Teaming. Refer to “Basic Teaming Versus Advanced Teaming” for more information.

  • Page 21: How To Choose The Best Team Type

    Figure 3-5 How to choose the best team type What type of NIC Team do I Need? NIC Teaming is not needed I need Team Type NIC Fault Automatically Tolerance and/or set to IEEE Load 802.3ad Balancing Choose All NICs Choose Team connected to a...

  • Page 22: Basic Teaming Versus Advanced Teaming

    Basic Teaming Versus Advanced Teaming You can choose to use the basic HP Integrity Network Adapter Teaming features like NFT, TLB, and SLB, or the advanced teaming features such as Dual Channel, Dynamic Dual Channel, Active Path, and Fast Path. The following table summarizes these Basic and Advanced features. Table 3-1 Basic versus Advanced teaming features Basic Teaming Features Advanced Teaming Features...

  • Page 23: Basic Deployment Steps For Hp Integrity Network Adapter Teaming

    the team’s Primary port among one or more teamed ports with validated connectivity to the preferred Spanning Tree root switch. Fast Path is extremely important for configurations with teamed ports connected to more than one switch. • Dual Channel – Switch-assisted Dual Channel Load Balancing, simply referred to as Dual Channel, is a special team type designed by HP Engineering to accomplish everything that NFT, TLB and SLB team types accomplish all in a single team type (refer to Table...

  • Page 24: Ncu Main Page

    NCU Main Page The NCU main page, labeled HP Network Configuration Utility Properties, is used to create and dissolve teams, monitor the overall health of teams and individual network adapters, and to export team configuration settings to an XML file. The main page is also used to access the Properties pages for team settings and individual NIC settings.

  • Page 25: Team Properties Page Tabs

    Team Properties Page Tabs • Teaming Controls – This tab is used to change the team name, select team type, select the Transmit Load Balancing algorithm, change port preference order for NFT with Preference teams, and to assign group membership for Dual Channel teams. •...

  • Page 26: Getting Started

    Getting Started Example Deployment of Basic Teaming A typical deployment of basic teaming might include the following steps: Perform the initial installation. For example, complete the steps described above in the section:“Basic Deployment Steps for HP Integrity Network Adapter Teaming”. Select the network adapter ports for a team.
  • Page 27 4. Enable and configure advanced redundancy mechanisms. Select the Advanced Redundancy tab from the Team Properties page. Enable Active Path Failover by checking the box. Select Community Address ARP as the Echo Node Response Mechanism. Type the IP address of the designated Echo Node (for example, gateway router) in the Echo Node IP Address field.

  • Page 29: The Mechanics Of Teaming For The Advanced User

    4 The Mechanics of Teaming for the Advanced User Section Objectives and Prerequisites This section is intended to provide an in-depth technical discussion of the mechanics of HP Integrity Network Adapter Teaming for the advanced user. This section assumes the reader has read the previous sections in this white paper and has hands-on experience in the deployment and usage of HP Integrity Network Adapter Teaming.

  • Page 30: Teaming Software Components

    Teaming Software Components HP Integrity Network Adapter Teaming consists of three components: the Miniport driver, Intermediate driver, and configuration GUI. Network Adapter Miniport Driver The Miniport driver used with the HP network adapter is e1g6064.sys or e1e6064.sys or b57nd60i.sys, depending on the adapter in use. Teaming Intermediate Driver The Intermediate driver is CPQTEAM.SYS, and is used for all teaming functions involving HP Integrity supported adapters.

  • Page 31: Types Of Hp Integrity Network Adapter Teams

    event, because the protocol address is directly assigned to the Intermediate (teaming) driver, and not to the Miniport driver. When transmitting frames, the current Primary adapter always transmits using the team’s MAC address as the Layer 2 address and the team’s Protocol address as the Layer 3 address. Non-Primary adapters always transmit using the MAC address assigned to them by the teaming driver and using the team’s protocol address as the Layer 3 address.

  • Page 32: Network Addressing And Communication With Nft

    Figure 4-1 Overview of NFT communication ARP Table: Destination MAC/Source MAC/Destination IP/Source IP Client A ARP Table: 1.1.1.1 1.1.1.2 1.1.1.1 = E 1.1.1.3 = B 1.1.1.2 = A IP Address = 1.1.1.2 1.1.1.1 1.1.1.3 1.1.1.4 = C 1.1.1.3 = B 1.1.1.5 = D 1.1.1.4 = C 1.1.1.1...

  • Page 33: Scenario 4-A: A Device Pings An Nft Team On The Same Layer 2 Network

    Figure 4-2 Scenario 4–A: A device pings an NFT team on the same Layer 2 network Ethernet MAC = A IP = 1.1.1.1 MAC = B MAC = E Primary Non-Primary IP = 1.1.1.2 Blue (server) Red transmits a broadcast ARP request asking for Blue’s MAC address. A user on Red issues the command ping 1.1.1.2 to initiate a ping to Blue.

  • Page 34: Nft Redundancy Mechanisms

    Blue transmits a broadcast ARP request asking for Red’s MAC address. NOTE: The following step may not occur if Blue’s ARP table still contains an entry for Red as a result of Steps 1 and 2. Blue checks its ARP cache for a MAC address entry that matches 1.1.1.1. If Blue does not find one, then Blue broadcasts an ARP request asking for Red’s MAC address.

  • Page 35: Team Properties Page - Settings Tab Containing The Heartbeat Settings

    teamed port under test is able to receive the heartbeat frame, the test succeeds. This feature can be disabled, but fault tolerance will be reduced. • Switch MAC table updates with team MAC address – The Primary Port must ensure that the switch has the team’s MAC address on the correct port, and that the switch keeps the team’s MAC address in its MAC table [or Content Addressable Memory (CAM) table].

  • Page 36: Heartbeat Frame Format

    frame. Therefore, a transmit path validation heartbeat frame may be transmitted once every 6 seconds (if the transmit path validation interval timer is set to the default of 3 seconds) on a port that has not transmitted anything. If the port does successfully transmit a heartbeat or any other kind of frame, its internal status is reset to 0.

  • Page 37: Advanced Redundancy Mechanisms

    Table 4-2 802.1Q Tagged Heartbeat Frame Format (continued) Source MAC address “MAC address of Teamed port” 6 bytes 802.1Q/p tag “Value of VLAN ID and Priority” 4 bytes Length 2 bytes DSAP 0xAA 1 byte SSAP 0xAA 1 byte SNAP type Unnumbered, TEST 1 byte Data...

  • Page 38: Upstream Link Failures Cause Server Isolation

    unplugged/disconnected. This results in the HP Integrity server being effectively disconnected from the entire network except for Switch A. Only the 50 users on Switch A can access the server, whereas the 50 users on Switch B, the 250 users connected via the Core Switch, and the router connection to any external network can no longer communicate with the server.
  • Page 39 the Echo Node will always resolve the team’s IP address to a single port in the team, which would prevent Echo Node probe responses from being sent to every port in the team. Active Path uses a special frame as the Echo Node probe. This frame is identical to a normal ARP request frame except for one field –...

  • Page 40: Directed Arp Echo Node Probe Request Frame Format

    modifications to the designated Echo Node were required. Third, a frame type had to be chosen that would not cause loss of communication for normal data traffic between the Echo Node and the team since, in many environments, the Echo Node could be another server, another client, a switch, or a router functioning as the team’s gateway.
  • Page 41 Table 4-4 Directed ARP Echo Node Probe REPLY Frame Format (continued) ARP operation 0x002 (ARP response) 2 bytes Source MAC address “Echo Node’s MAC Address” 6 bytes Source IP address “Echo Node’s IP Address” 4 bytes Destination MAC address “MAC address of Teamed port” 6 bytes Destination IP address 0.0.0.0...
  • Page 42 the particular Echo Node. In contrast to Directed ARP, each individual teamed port is not necessarily required to transmit its own Echo Node request, yet all teamed ports individually receive an Echo Node probe reply. With Community Address ARP, the team’s Primary port transmits an Echo Node probe request to the designated Echo Node.

  • Page 43: Community Address Arp Echo Node Probe Request Frame Format

    Validate individual connectivity for a teamed port There is no special configuration on the designated Echo Node The Echo Node probe frame can’t cause loss of connectivity for the team Community Address ARP was designed to work with IP stacks that fail to respond to the Directed ARP probe packets.
  • Page 44 Table 4-6 Community Address ARP Echo Node Probe REPLY Frame Format (continued) Protocol address length 0x04 1 byte ARP operation 0x002 (ARP response) 2 bytes Source MAC address “Echo Node’s MAC Address” 6 bytes Source IP address “Echo Node’s IP Address” 4 bytes Destination MAC address “Community Probe MAC from GUI”...
  • Page 45 Active Path Configuration To use Active Path, an SA must enable it on a per-team basis from the Advanced Redundancy tab located on the HP Integrity Network Adapter Teaming configuration GUI. Next, the SA should select which Active Path mechanism to use – Directed ARP or Community Address ARP from the Echo Node Response Mechanism drop-down box.

  • Page 46: Active Path Failover Configuration: Directed Arp

    Figure 4-5 Active Path failover configuration: Directed ARP Community Address ARP Configuration: To enable Active Path’s Community Address ARP mechanism, select Community Address ARP from the Echo Node Response Mechanism drop-down box. In addition to supplying the Echo Node IP address, it is necessary to supply a Community Probe IP Address. Community Address ARP guidelines: •...

  • Page 47: Active Path Failover Configuration: Community Address Arp

    Figure 4-6 Active Path failover configuration: Community Address ARP Fast Path Fast Path is a mechanism used by HP Integrity Network Adapter Teaming to intelligently and proactively determine the best teamed ports to use to provide optimum network connectivity for the server. As with Active Path, Fast Path can determine if teamed ports have become segregated onto different broadcast domains (because of link loss on an upstream switch uplink, server network adapter ports that are connected to the wrong switch ports, VLAN misconfiguration on a switch, etc.) Also, Fast Path is used by HP Integrity Network Adapter...
  • Page 48 • Link loss detection – “Do I have physical link?” • Transmit path validation – “ Can I successfully transmit a frame onto the network?” • Receive path validation – “Can I successfully receive any kind of frame from the network?” These basic redundancy mechanisms do not provide for redundancy beyond the network adapter port in the team.

  • Page 49: Upstream Link Failures Cause Server Isolation

    Figure 4-7 Upstream link failures cause server isolation 50 USERS ACCESS TO SERVER 250 USERS C o n s o l e NO ACCESS TO SERVER Switch A HP NIC TEAMING External NIC 1 Primary Network C o n s o l e NO ACCESS TO SERVER Core Switch 1.1.1.1...

  • Page 50: Upstream Link Failures Cause Server Receive Bandwidth Bottleneck

    Figure 4-8 Upstream link failures cause server receive bandwidth bottleneck Link 5 Gigabit Ethernet C o n s o l e Gigabit Ethernet Switch A NIC 1 Primary HP NIC TEAMING Link 2 100 Mbps Link 3 Link 1 NIC 2 Non-Primary Gigabit Ethernet Gigabit Ethernet...
  • Page 51 The solution to this problem is the Fast Path mechanism designed and developed by HP Engineering. In addition to Fast Path detecting full connectivity loss, as described in the first example, Fast Path can also detect when a server’s teamed ports have different hop count paths to the Core Switch (root switch).

  • Page 52: Fast Path Operation Overview

    Figure 4-10 Fast Path operation overview Fast Path Configuration Fast Path is enabled from the Advanced Redundancy tab in NCU by checking the Fast Path Failover checkbox (refer to Figure 4-11). Fast Path can also be monitored from the Advanced Redundancy tab.

  • Page 53: Fast Path Configuration And Monitoring

    Figure 4-1 1 Fast Path configuration and monitoring Fast Path has two Spanning Tree Protocol configuration options: • Enabled or disabled, as discussed in the previous section • Spanning Tree Protocol (STP) type Both of these settings are located on the Advanced Redundancy tab in NCU. Refer to Figure 4-11.

  • Page 54: Redundancy Mechanism Priority

    Switch ports connected to teamed ports should be configured to bypass Spanning Tree’s block/listen/learn stages. These stages are not needed for ports connected to end node devices (for example, servers, PCs, etc.) Switch ports connected to teamed ports MUST transmit BPDUs. Without BPDUs, Fast Path will not have the information it needs to make decisions.

  • Page 55: Failover Events

    Table 4-7 Redundancy mechanism comparison chart (continued) Detects good ports versus best ports √ Mechanism can be manually disabled √ √ √ √ Failover Events Link Loss When a network port is a member of a team and loses physical link (in other words, wire fault, lost link light), the teaming driver prevents the port from being used by the team.

  • Page 56: Nft Network Adapter Failure Recovery

    teamed port from a set of teamed ports that all have validated connectivity to the main network segment. As a result, Fast Path can initiate a failover from one teamed port operating as the Primary port to another non-Primary teamed port for either of two reasons. The first failover is caused by a teamed port losing connectivity with the main network segment, in which case the team will label the teamed port as Split LAN and will disable the teamed port...

  • Page 57: Recommended Configurations For Nft Environments

    requires fault tolerance in case of a network adapter malfunction, but does not have a demand for receiving or transmitting more than the capacity of the Primary port.) Recommended Configurations for NFT Environments HP recommends the following: • Heartbeats should be enabled (default). •...

  • Page 58: Network Addressing And Communication With Tlb

    However, traffic received by the server is not load balanced, meaning the Primary teamed port is responsible for receiving all traffic destined for the server (refer to Figure 4-12). As with NFT, there are two types of team members, Primary and Non-Primary ports. The Primary port transmits and receives frames and the non-Primary ports only transmit frames.

  • Page 59: Scenario 4-B: A Device Pings A Tlb Team On The Same Layer 2 Network

    Figure 4-13 Scenario 4–B: A device pings a TLB team on the same Layer 2 network Ethernet MAC = A IP = 1.1.1.1 MAC = B MAC = E Primary Non-Primary IP = 1.1.1.2 Blue (server) Red transmits a broadcast ARP request asking for Blue’s MAC address. A user on Red issues the command ping 1.1.1.2 to initiate a ping to Blue.

  • Page 60: Transmit Load Balancing Methods (Algorithms)

    Blue transmits a broadcast ARP request asking for Red’s MAC address. NOTE: The following step may not occur if Blue’s ARP table still contains an entry for Red as a result of Steps 1 and 2. Blue checks its ARP cache for a MAC address entry that matches 1.1.1.1. If Blue does not find one, then Blue broadcasts an ARP request asking for Red’s MAC address.

  • Page 61: Tlb Automatic Method

    Figure 4-14 Transmit Load Balancing Method Configuration Table 4-8 Transmit Load Balancing method comparison Preserves Frame Load Balances Guarantees Equal HP Recommendation Transmission Order through Router Load Balancing Automatic √ √ √ TCP Connection √ √ Destination IP √ √ address Destination MAC √...

  • Page 62: Tlb Tcp Connection Method

    the Automatic mode. By deploying this method now, future upgrades will automatically take advantage of the new intelligence. TLB TCP Connection Method TCP Connection is also a load-balancing method that is designed to preserve frame ordering. This method will load balance outbound traffic based on the TCP port information in the frame’s TCP header.
  • Page 63 Table 4-10 Load Balancing based on Destination IP Address (four- and five-port teams) (continued) network port 1 network port 1 network port 2 network port 2 network port 3 network port 3 network port 4 network port 4 network port 1 network port 5 network port 2 network port 1...

  • Page 64: Tlb Destination Mac Address Method

    Figure 4-15 Scenario 4-C: TLB team using IP address for load balancing algorithm MAC = C MAC = D IP = 1.1.1.3 IP = 2.2.2.3 Green (Router) Network Network 1.0.0.0 2.0.0.0 Ethernet Ethernet MAC = B MAC = F MAC = A MAC = E Primary IP = 1.1.1.4...

  • Page 65: Load Balancing Based On Destination Mac Address (Four- And Five-Port Teams)

    Table 4-1 1 Load balancing based on Destination MAC Address (two- and three-port teams) (continued) network port 2 network port 1 network port 1 network port 2 network port 2 network port 3 network port 1 network port 1 network port 2 network port 2 Table 4-12 Load balancing based on Destination MAC Address (four- and five-port teams) Four-Port Team...

  • Page 66: Tlb Round Robin Method For Outbound Load Balancing

    Figure 4-16 Scenario 4-D: TLB team using MAC address for load-balancing algorithm Ethernet MAC = F MAC = A IP = 1.1.1.4 IP = 1.1.1.1 MAC = B MAC = E Primary Non-Primary Yellow IP = 1.1.1.2 Blue (server) In summary, special consideration should be given when choosing the MAC address-based load-balancing algorithm in an environment where the server and clients are separated by a Layer 3 device such as a router.

  • Page 67: Tlb Redundancy Mechanisms

    ports are equally used. HP recommends that the implications of this method of load balancing be carefully considered before deployment. TLB Redundancy Mechanisms The basic and advanced redundancy mechanisms used by TLB are identical to NFT. Refer to the section, “NFT Redundancy Mechanisms”, for more information.

  • Page 68: Transmit Load Balancing With Fault Tolerance And Preference Order

    switches. This helps prevent switch uplink failure scenarios that leave team members in separate broadcast domains. • TLB teams that communicate with TCP/IP network devices via a router should use the Automatic, TCP port or, IP address-based load balancing algorithm (configured via the NCU).

  • Page 69: Network Addressing And Communication With Slb

    Figure 4-17 Overview of SLB communication ARP Table: ARP Table: Client A 1.1.1.1 = E 1.1.1.3 = B 1.1.1.2 = A IP Address = 1.1.1.2 1.1.1.4 = C 1.1.1.3 = B Destination MAC/Source MAC/Destination IP/Source IP 1.1.1.5 = D 1.1.1.4 = C MAC = A 1.1.1.1 1.1.1.2...

  • Page 70: Cisco Etherchannel

    As an example, a detailed discussion of Cisco’s EtherChannel load-balancing algorithm is described below. Most of the information about how Cisco switches load-balance traffic on a port trunk is applicable to other switch vendors’ Port Trunking technology. Cisco EtherChannel Cisco's Fast EtherChannel (FEC) and Gigabit EtherChannel (GEC) technology is a MAC layer (Layer 2) load-balancing technology using two or more switch ports grouped together as one logical switch port.

  • Page 71: Switch Vendor Port Trunking Technology Supported By Slb

    Table 4-14 Example of load-balancing algorithms #2 (continued) Packet 2 - Destination MAC address: 00-00-00-00-00-01 frame is transmitted out port 2 Last binary bit = 0000 0001 Method 2: SOURCE-BASED ALGORITHM Packet 1 - Source MAC address: 00-00-00-00-00-03 frame is transmitted out port 2 Last binary bit = 0000 0001 Packet 2 - Source MAC address: 00-00-00-00-00-02 frame is transmitted out port 1...

  • Page 72: Slb Redundancy Mechanisms

    SLB Redundancy Mechanisms The only redundancy mechanisms used by SLB are link loss and transmit validation heartbeats. None of the advanced redundancy mechanisms (for example, Active Path and Fast Path) are supported by SLB. The advanced redundancy mechanisms require the ability to predict and control which ports in a team will receive a particular frame.

  • Page 73: 802.3Ad Dynamic With Fault Tolerance

    technology has been designed to allow for flexibility. Therefore, the NCU may allow configuration of an SLB team that will not work correctly with a particular vendor’s switch. • The switch’s load-balancing algorithm should be set to XOR or SOURCE-BASED but not DESTINATION-BASED (refer to the sections, “Switch-assisted Load Balancing with Fault Tolerance (SLB)”...

  • Page 74: Tlb Does Not Provide Receive Load Balancing

    Figure 4-18 TLB does not provide receive load balancing Client ARP Table: Switch 1.1.1.1 = A NIC 1 (A) Client ARP Table: PRIMARY HP Network 1.1.1.1 = A Adapter Switch Team Redundancy NIC 2 (B) SECONDARY (TLB) Client ARP Table: 1.1.1.1 = A NIC 3 (C) SECONDARY...

  • Page 75: Dual Channel & Dynamic Dual Channel Provide Full Load Balancing And Switch Redundancy

    With Dual Channel, a server can have full transmit and receive load balancing with switch redundancy (refer to Figure 4-20). Figure 4-20 Dual Channel & Dynamic Dual Channel provide full load balancing and switch redundancy Switch Client ARP Table: 1.1.1.1 = A Port Client 1 Channel...

  • Page 76: Dual Channel Configuration

    Figure 4-21 Overview of Dual Channel communication ARP Table: ARP Table: Client A 1.1.1.1 = E 1.1.1.3 = B 1.1.1.2 = A IP Address = 1.1.1.2 1.1.1.4 = C 1.1.1.3 = B Destination MAC/Source MAC/Destination IP/Source IP 1.1.1.5 = D 1.1.1.4 = C MAC = A 1.1.1.1...

  • Page 77: Dual Channel Transmit Balancing Algorithm

    Figure 4-22 Dual Channel configuration Dual Channel Transmit Balancing Algorithm The transmit load-balancing algorithms used by Dual Channel are the same methods used by TLB. Refer to “Transmit Load Balancing with Fault Tolerance (TLB)” for a detailed discussion. Dual Channel Receive Load-Balancing Algorithm Receive Load Balancing on a Per-Port Trunk Basis The receive load-balancing algorithm used for a group of teamed ports in a Dual Channel team is identical to the receive load-balancing algorithms used for SLB.

  • Page 78: Dual Channel Redundancy Mechanisms

    The client’s ARP table entries expire after a few minutes; as a result, the clients will re-ARP for the server’s IP address. The clients may or may not get the same IP address for the server depending on the results from the load-balancing algorithm. •...

  • Page 79: 802.3Ad Dynamic Dual Channel Load Balancing

    • Make sure that each group in a Dual Channel team is connected to a different switch. If both groups are attached to the same switch, switch redundancy is lost. • Whenever a Dual Channel team is created with an even number of teamed ports, evenly distribute the ports between both groups.

  • Page 80: Mechanism Priority

    Table 4-16 Team type and redundancy mechanism compatibility (continued) Receive √ √ √ √ validation heartbeats Active Path √ √ √ √ Fast Path √ √ √ √ Mechanism Priority Most team types can support multiple redundancy mechanisms simultaneously. This allows an implementer to deploy any combination of redundancy mechanisms depending on what the network environment will support.

  • Page 81: Team Status And Icons

    mechanism, then NIC 2 will be chosen as the team’s Primary port in the scenario above and NIC 1 will be disabled for use by the team. If Active Path is selected as the higher priority mechanism, the result is the opposite – NIC 1 will be chosen as the team’s Primary port and NIC 2 will be disabled for use by the team.

  • Page 82: Teamed Port Information Tab

    Figure 4-25 Teamed port Information tab Listed below are the possible status conditions with definitions: • Available – The team member is functioning normally. • Not Teamed – The adapter is not part of the team. The most likely cause is adding an adapter to the team but not applying the change.

  • Page 83: Team State

    • Failed (LACP Standby) – The team member has failed because the team has more members than the switch supports in the LACP protocol. The port is blocked by the switch. • Failed (Rx Heartbeat) – The team member is not receiving frames. •...

  • Page 84: Hp Integrity Network Adapter Teaming And Advanced Networking Features

    HP Integrity Network Adapter Teaming and Advanced Networking Features When adapter ports are members of a team, some advanced features are no longer configurable on the port’s Advanced Settings tab. These advanced features are either promoted to the team’s Advanced Settings tab because the features are compatible and supported by all team members, or not promoted because one or more ports do not support the features.

  • Page 85: Q Virtual Local Area Networks (Vlan)

    feature is promoted to the team’s Advanced Settings tab with the lowest size configured for the team members. For example, if there are two adapters, one configured for 4088 bytes and the other for 9014 bytes, and they are teamed, the Maximum Frame Size feature is set to 4088 bytes. A setting of 1514 bytes is equal to Jumbo Frames being disabled.

  • Page 86: Hp Integrity Network Adapter Teaming Configuration And Deployment With Integrity Essentials Rapid Deployment Pack (Rdp)

    4–7 HP Integrity Network Adapter Teaming Configuration and Deployment with Integrity Essentials Rapid Deployment Pack (RDP) One of the methods of deployment for HP Integrity Network Adapter Teaming is to use HP Integrity Essential’s Rapid Deployment Pack (RDP) remote scripting feature. This feature allows an SA to deploy a specific teaming configuration to any number of target servers in a single action.

  • Page 87: Teaming Feature Matrix

    5 Teaming Feature Matrix Table 5-1 Teaming feature matrix NFT & NFT with TLB & TLB with SLB & 802.3ad Dual Channel & Preference Preference Dynamic Dynamic Dual Channel Number of ports supported per team Maximum theoretical 100/100 800/100 800/800 800/800 transmit/receive throughput (in Mbps)
  • Page 88 Table 5-1 Teaming feature matrix (continued) Can team ports of √ √ √ √ different media Load balances TCP/IP √ √ √ Load balances non-IP √ √ √ traffic Supports load √ √ √ balancing by destination IP address, destination MAC address, TCP port, and Round Robin...

  • Page 89: A - Overview Of Network Addressing And Communication

    A – Overview of Network Addressing and Communication Understanding the concepts of network addressing is the key to understanding how HP’s Network Adapter Teaming works. This section provides a brief overview of network addressing as a baseline for explaining how HP’s Network Adapter Teaming can create one logical network port from a team of two or more ports.

  • Page 90: Scenario A-1: One Device Pings Another On The Same Layer 2 Network

    These scenarios provide a baseline of typical network addressing and communication using IP. This baseline will be referred to later in this document to differentiate how HP Integrity Network Adapter Teaming functions in these same scenarios. By understanding the differences in simple examples such as these (without HP’s Network Adapter Teaming technology involved), implementers will have a better understanding of how HP’s Network Adapter Teaming technology may work in their environment.

  • Page 91: Scenario A-2: One Device Pings Another On A Different Layer 2 Network

    NOTE: This step may not occur if Blue’s ARP table still contains an entry for Red as a result of Steps 1 and 2. Blue checks its ARP cache for a MAC address entry that corresponds to 1.1.1.1. If Blue does not find one (in other words, ARP cache timed out since last communication with Red), then Blue broadcasts an ARP request asking for Red’s MAC address.
  • Page 92 is. First, Red checks its own ARP cache for an entry that matches 1.1.1.3. If Red does not have an entry cached, then it must broadcast an ARP request frame on network 1.0.0.0 asking Green to respond and provide its MAC address. Green transmits a unicast ARP reply to Red providing its MAC address (C).
  • Page 93 address as the source MAC address and Blue’s IP address as the source IP address. Green receives the ping reply and determines that the frame is meant for Red because of the Layer 3 address (IP). 10. Green transmits a broadcast ARP request on Network 1.0.0.0 asking for Red’s MAC address.

  • Page 95: B - Frequently Asked Questions

    B – Frequently Asked Questions B.1 HP Integrity Network Adapter Teaming Frequently Asked Questions B.B.1.1 Why is traffic not being load balanced out of my server? (or) Why is traffic not being load balanced during backups? Either TLB or SLB is required for load balancing of transmit traffic. NFT will not provide for any type of load balancing.
  • Page 96 B.B.1.9 How do I uninstall HP Integrity Network Adapter Teaming? HP Integrity Network Adapter Teaming can be uninstalled by opening the properties page of any network interface under Network and Dial-up Connections (Microsoft UI). Select HP Network Teaming and Configuration and click the UNINSTALL button.
  • Page 97 • Understanding Requirements for Failover Clusters: http://technet2.microsoft.com/windowsserver2008/en/library/ 6fe86b30-6820-43a2-8321-3e7b51cbe7631033.mspx • Network Adapter Teaming and Server Clustering: http://support.microsoft.com/kb/254101 B.B.1.15 My switch is set up for Switch-assisted Load Balancing (Port Trunking) but my network adapters are not. Why am I having communication problems? The switch assumes that all ports are capable of receiving on the same MAC address/es and will randomly transmit frames for any of the NICs down any of the links for any of the NICs.
  • Page 98 switch vendor redundancy mechanisms to make a single switch highly redundant. For example, Cisco provides an option called High Availability on some switches. This option allows a Cisco switch to have redundant Supervisor modules. An HP customer using a Cisco switch with redundant Supervisor modules and redundant power supplies can create an SLB team, a Dual Channel team, or a Dynamic Dual Channel team of several ports, connect the team to two modules inside the same Cisco switch, and enable High Availability.

  • Page 99: C - Overview Of Utilities Included With Hp Integrity Network Adapter Teaming

    C – Overview of Utilities Included with HP Integrity Network Adapter Teaming In the Component Pack (CPnnnnn.exe) for HP Integrity Network Adapter Teaming there are several command line utilities provided for special teaming-related management functions. Below is a list of the utilities with a brief description of each. Consult the latest HP Integrity Network Adapter Teaming Component Pack for the latest utilities and associated documentation.

  • Page 101: D - Glossary

    D – Glossary The following networking and teaming terms are used in this document: 802.1D Refers to the IEEE 802.1D specification. This is the original Spanning Tree specification. 802.3ad Dynamic Refers to the IEEE 802.3ad specification. This specification provides for manual and automatic (dynamic) port grouping for fault tolerance and load balancing between two network devices.
  • Page 102 Gigabit EtherChannel. A method of load balancing that both transmits and receives traffic across multiple Gigabit Ethernet (1000 Mbps) connections between two devices. Developed by Cisco Systems. Refer to SLB. Graphical User Interface HP Teaming and Now referred to as the HP Network Configuration Utility (NCU). Refer to NCU. Configuration IEEE Institute of Electrical and Electronics Engineers.
  • Page 103 Network Fault Tolerance. A team of network ports that transmits and receives on only one port with all other ports in standby. Network Interface Card. Synonymous with network adapter. NIC teaming A phrase referring to HP Integrity Network Adapter Teaming. OSI Model Open Systems Interconnect Model.

This manual is also suitable for:

Network adapter teaming

Table of Contents