Home » HP Manuals » Servers » HP Integrity rx2800 » Manual Viewer

HP Integrity rx2800 HP Integrity Network Adapter Teaming Whitepaper - Page 62

TLB TCP Connection Method, TLB Destination IP Address Method

View all HP Integrity rx2800 manuals

Add to My Manuals
Save this manual to your list of manuals

Page 62 highlights

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. This load-balancing method combines the TCP source and destination ports to identify the TCP conversation. Combining these values, the algorithm can identify individual TCP conversations (even multiple conversations between the team and one other network device). The algorithm used to choose which teamed port to use per TCP conversation is similar to the algorithms used in the "TLB Destination IP Address Method" and "TLB Destination MAC Address Method" sections below. If this method is chosen, and the frame has an IP header with and IP address but not a TCP header, then the frame is load balanced by destination IP address (refer to "TLB Destination IP Address Method" below). If the frame doesn't have an IP header, the frame is load balanced by destination MAC address (refer to "TLB Destination MAC Address Method" below). TLB Destination IP Address Method Destination IP Address is a load-balancing method that will attempt to preserve frame ordering. This method makes load-balancing decisions based on the destination IP address of the frame being transmitted by the teaming driver. The frame's destination IP address belongs to the network device that will ultimately receive the frame. The team utilizes the last three bits of the destination IP address to assign the frame to a port for transmission. Because IP addresses are in decimal format, it is necessary to convert them to binary format. For example, an IP address of 1.2.3.4 (dotted decimal) would be 0000 0001 . 0000 0010 . 0000 0011 . 0000 0100 in binary format. The teaming driver only uses the last three bits (100) of the least significant byte (0000 0100 = 4) of the IP address. Utilizing these three bits, the teaming driver will consecutively assign destination IP addresses to each functional network port in its team starting with 000 being assigned to network port 1, 001 being assigned to network port 2, and so on. Of course, how the IP addresses are assigned depends on the number of network ports in the TLB team and how many of those ports are in a functional state (refer to Table 4-9). Table 4-9 Load Balancing based on Destination IP Address (two- and three-port teams) Destination IP 000 001 010 011 100 101 110 111 Two-Port Team Transmitting Port network port 1 network port 2 network port 1 network port 2 network port 1 network port 2 network port 1 network port 2 Destination IP 000 001 010 011 100 101 110 111 Three-Port Team Transmitting Port network port 1 network port 2 network port 3 network port 1 network port 2 network port 3 network port 1 network port 2 Table 4-10 Load Balancing based on Destination IP Address (four- and five-port teams) Destination IP Four-Port Team Transmitting Port Destination IP Five-Port Team Transmitting Port 62 The Mechanics of Teaming for the Advanced User

Section	Page
Network Adapter Teaming White Paper	1
Table of Contents	3
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
Fault Tolerance: Dual Homing or Network Adapter Teaming?	15
Load Balancing: Server-Based Routing Protocol or NIC Teaming?	17
Overview of Team Types	17
Network Fault Tolerance Only (NFT)	18
Network Fault Tolerance Only with Preference Order	18
Transmit Load Balancing with Fault Tolerance (TLB)	19
Transmit Load Balancing with Fault Tolerance and Preference Order	19
Switch-assisted Load Balancing with Fault Tolerance (SLB)	19
802.3ad Dynamic with Fault Tolerance	19
Switch-assisted Dual Channel Load Balancing	19
802.3ad Dynamic Dual Channel Load Balancing	20
Automatic	20
How to Choose the Best Team Type	20
Basic Teaming Versus Advanced Teaming	22
Basic Deployment Steps for HP Integrity Network Adapter Teaming	23
Download	23
Install	23
Launch	23
Overview of the HP Network Configuration Utility	23
NCU Main Page	24
Primary Actions from the NCU Main Page	24
Team Properties Page	24
Team Properties Page Tabs	25
Adapter Properties Page	25
Adapter Properties Page Tabs	25
Getting Started	26
Example Deployment of Basic Teaming	26
Example Deployment of Advanced Teaming	26
4 The Mechanics of Teaming for the Advanced User	29
Section Objectives and Prerequisites	29
Architecture of HP Integrity Networking Adapter Teaming	29
The “Networking Layers” of an Operating System	29
Teaming Software Components	30
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
Active Path	37
General Description of Active Path Operation	38
Active Path Configuration	45
Fast Path	47
General Description of Fast Path Operation	51
Fast Path Configuration	52
Redundancy Mechanism Priority	54
Redundancy Mechanism Comparison Chart	54
Failover Events	55
NFT Network Adapter Failure Recovery	56
NFT Applications	56
Recommended Configurations for NFT Environments	57
Network Fault Tolerance Only with Preference Order	57
NFT with Preference Order Applications	57
Transmit Load Balancing with Fault Tolerance (TLB)	57
Network Addressing and Communication with TLB	58
Scenario 4–B: A Device Pings a TLB Team on the Same Layer 2 Network	58
Transmit Load Balancing Methods (Algorithms)	60
TLB Automatic Method	61
TLB TCP Connection Method	62
TLB Destination IP Address Method	62
Scenario 4-C: A TLB Team Using IP Address-Based Load Balancing	63
TLB Destination MAC Address Method	64
Scenario 4-D: A TLB Team Using Destination MAC Address Load-Balancing Method	65
TLB Round Robin Method for Outbound Load Balancing	66
TLB Redundancy Mechanisms	67
TLB Network Adapter Failure Recovery	67
TLB Applications	67
Recommended Configurations for TLB Environments	67
Transmit Load Balancing with Fault Tolerance and Preference Order	68
Transmit Load Balancing with Fault Tolerance and Preference Order Applications	68
Switch-Assisted Load Balancing with Fault Tolerance (SLB)	68
Network Addressing and Communication with SLB	69
SLB Outbound Load-Balancing Algorithms	69
SLB Inbound Load-Balancing Algorithm	69
Cisco EtherChannel	70
Switch Vendor Port Trunking Technology Supported by SLB	71
SLB Redundancy Mechanisms	72
SLB Network Adapter Failure Recovery	72
SLB Applications	72
Recommended Configurations for SLB Environments	72
802.3ad Dynamic with Fault Tolerance	73
Switch-assisted Dual Channel Load Balancing	73
Dual Channel Configuration	76
Dual Channel Transmit Balancing Algorithm	77
Dual Channel Receive Load-Balancing Algorithm	77
Receive Load Balancing on a Per-Port Trunk Basis	77
Receive Load Balancing on Multiple Trunks	77
Dual Channel Redundancy Mechanisms	78
Basic Redundancy Mechanisms	78
Advanced Redundancy Mechanisms	78
Dual Channel Network Adapter Failure Recovery	78
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
HP Integrity Network Adapter Teaming and Advanced Networking Features	84
Checksum Offloading	84
802.1p QoS Tagging	84
Large Send Offload (LSO)	84
Maximum Frame Size (Jumbo Frames)	84
802.1Q Virtual Local Area Networks (VLAN)	85
4–7 HP Integrity Network Adapter Teaming Configuration and Deployment with Integrity Essentials Rapid Deployment Pack (RDP)	86
5 Teaming Feature Matrix	87
A – Overview of Network Addressing and Communication	89
Layer 2 Versus Layer 3	89
Address – Unicast Versus Broadcast Versus Multicast	89
Example Scenarios of Network Addressing and Communication	89
Scenario A-1: One Device Pings Another on the Same Layer 2 Network	90
Scenario A-2: One Device Pings Another on a Different Layer 2 Network	91
B – Frequently Asked Questions	95
C – Overview of Utilities Included with HP Integrity Network Adapter Teaming	99

Match case Limit results 1 per page

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. This load-balancing method combines the TCP source and destination ports to

identify the TCP conversation. Combining these values, the algorithm can identify individual

TCP conversations (even multiple conversations between the team and one other network device).

The algorithm used to choose which teamed port to use per TCP conversation is similar to the

algorithms used in the

“TLB Destination IP Address Method”

and

“TLB Destination MAC

Address Method”

sections below.

If this method is chosen, and the frame has an IP header with and IP address but not a TCP

header, then the frame is load balanced by destination IP address (refer to

“TLB Destination IP

Address Method”

below). If the frame doesn’t have an IP header, the frame is load balanced by

destination MAC address (refer to

“TLB Destination MAC Address Method”

below).

TLB Destination IP Address Method

Destination IP Address is a load-balancing method that will attempt to preserve frame ordering.

This method makes load-balancing decisions based on the destination IP address of the frame

being transmitted by the teaming driver. The frame’s destination IP address belongs to the

network device that will ultimately receive the frame. The team utilizes the last three bits of the

destination IP address to assign the frame to a port for transmission.

Because IP addresses are in decimal format, it is necessary to convert them to binary format. For

example, an IP address of 1.2.3.4 (dotted decimal) would be 0000 0001 . 0000 0010 . 0000 0011 .

0000 0100 in binary format. The teaming driver only uses the last three bits (100) of the least

significant byte (0000 0100 = 4) of the IP address. Utilizing these three bits, the teaming driver

will consecutively assign destination IP addresses to each functional network port in its team

starting with 000 being assigned to network port 1, 001 being assigned to network port 2, and

so on. Of course, how the IP addresses are assigned depends on the number of network ports in

the TLB team and how many of those ports are in a functional state (refer to

Table 4-9

Table 4-9 Load Balancing based on Destination IP Address (two- and three-port teams)

Three-Port Team

Two-Port Team

Transmitting Port

Destination IP

Transmitting Port

Destination IP

network port 1

000

network port 1

000

network port 2

001

network port 2

001

network port 3

010

network port 1

010

network port 1

011

network port 2

011

network port 2

100

network port 1

100

network port 3

101

network port 2

101

network port 1

110

network port 1

110

network port 2

111

network port 2

111

Table 4-10 Load Balancing based on Destination IP Address (four- and five-port teams)

Five-Port Team

Four-Port Team

Transmitting Port

Destination IP

Transmitting Port

Destination IP

The Mechanics of Teaming for the Advanced User