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

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

Table 4-5 Community Address ARP Echo Node Probe REQUEST Frame Format

View all HP Integrity rx2800 manuals

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

Page 43 highlights

1. Validate individual connectivity for a teamed port 2. There is no special configuration on the designated Echo Node 3. 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. Community Address ARP allows practically any network device to function as the Echo Node. Although Directed ARP works with most IP stacks, certain routers fail to respond to the Directed ARP probes. The most likely cause of the failure was the Echo Node not creating an ARP entry because the Source IP in the ARP request is intentionally blank. In several IP stacks, this prevented the device designated as the Echo Node from responding to the Echo Node probe used by Directed ARP. Due to the above considerations, Community Address ARP was designed to use a standard ARP request frame as the Echo Node probe, as opposed to Directed ARP's modified ARP request frame. Also, Community Address ARP utilizes a special "Echo Node Only" MAC and IP address called the Community Probe MAC address and Community Probe IP address (configured in the GUI). The Echo Node Only addresses are used to prevent Echo Node probes from changing the team's ARP entry in the Echo Node's ARP table and to allow a single response from the Echo Node to be received by multiple teamed ports. Each teamed port that transmits an Echo Node probe using the Community Address ARP mechanism inserts its individual MAC address in the Echo Node probe request's (ARP request) Ethernet header. However, every teamed port inserts the Community Probe IP address and Community Probe MAC address in the Source IP and Source MAC ARP header fields, respectively. Since the Echo Node receives a standard ARP request frame with a Source IP and Source MAC, any device with an IP address can be designated as the Echo Node (usually with no configuration required on the Echo Node end). As a result, Community Address ARP's Echo Node probe provides for validation to each individual teamed port, works with any IP protocol stack, and does not cause loss of communication with the team for normal data traffic. Table 4-5 Community Address ARP Echo Node Probe REQUEST Frame Format Ethernet V2 Frame Format Destination MAC address Source MAC address 802.1Q/p tag (optional) Type Hardware type Protocol type Hardware address length Value "Broadcast" unless specified in GUI "MAC address of Teamed port" "Value of VLAN ID and Priority" 0x0806 (ARP) 0x01 (Ethernet) 0x800 (IP) 0x06 128 Bytes Total 6 bytes 6 bytes 4 bytes 2 bytes 2 bytes 2 bytes 1 byte Table 4-6 Community Address ARP Echo Node Probe REPLY Frame Format Ethernet V2 Frame Format Destination MAC address Source MAC address 802.1Q/p tag (optional) Type Hardware type Protocol type Hardware address length Value 64 Bytes Total "Community Probe MAC from GUI" 6 bytes "Echo Node's MAC Address" 6 bytes "Value of VLAN ID and Priority" 4 bytes 0x0806 (ARP) 2 bytes 0x01 (Ethernet) 2 bytes 0x800 (IP) 2 bytes 0x06 1 byte Types of HP Integrity Network Adapter Teams 43

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

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. Community Address ARP allows practically any network

device to function as the Echo Node. Although Directed ARP works with most IP stacks,

certain routers fail to respond to the Directed ARP probes. The most likely cause of the

failure was the Echo Node not creating an ARP entry because the Source IP in the ARP

request is intentionally blank. In several IP stacks, this prevented the device designated as

the Echo Node from responding to the Echo Node probe used by Directed ARP.

Due to the above considerations, Community Address ARP was designed to use a standard

ARP request frame as the Echo Node probe, as opposed to Directed ARP’s modified ARP

request frame. Also, Community Address ARP utilizes a special “Echo Node Only” MAC

and IP address called the Community Probe MAC address and Community Probe IP address

(configured in the GUI). The Echo Node Only addresses are used to prevent Echo Node

probes from changing the team’s ARP entry in the Echo Node’s ARP table and to allow a

single response from the Echo Node to be received by multiple teamed ports. Each teamed

port that transmits an Echo Node probe using the Community Address ARP mechanism

inserts its individual MAC address in the Echo Node probe request’s (ARP request) Ethernet

header. However, every teamed port inserts the Community Probe IP address and

Community Probe MAC address in the Source IP and Source MAC ARP header fields,

respectively. Since the Echo Node receives a standard ARP request frame with a Source IP

and Source MAC, any device with an IP address can be designated as the Echo Node (usually

with no configuration required on the Echo Node end). As a result, Community Address

ARP’s Echo Node probe provides for validation to each individual teamed port, works with

any IP protocol stack, and does not cause loss of communication with the team for normal

data traffic.

Table 4-5 Community Address ARP Echo Node Probe REQUEST Frame Format

128 Bytes Total

Value

Ethernet V2 Frame Format

6 bytes

“Broadcast” unless specified in GUI

Destination MAC address

6 bytes

“MAC address of Teamed port”

Source MAC address

4 bytes

“Value of VLAN ID and Priority”

802.1Q/p tag (optional)

2 bytes

0x0806 (ARP)

Type

2 bytes

0x01 (Ethernet)

Hardware type

2 bytes

0x800 (IP)

Protocol type

1 byte

0x06

Hardware address length

Table 4-6 Community Address ARP Echo Node Probe REPLY Frame Format

64 Bytes Total

Value

Ethernet V2 Frame Format

6 bytes

“Community Probe MAC from GUI”

Destination MAC address

6 bytes

“Echo Node’s MAC Address”

Source MAC address

4 bytes

“Value of VLAN ID and Priority”

802.1Q/p tag (optional)

2 bytes

0x0806 (ARP)

Type

2 bytes

0x01 (Ethernet)

Hardware type

2 bytes

0x800 (IP)

Protocol type

1 byte

0x06

Hardware address length

Types of HP Integrity Network Adapter Teams