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

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

Table 4-1 Heartbeat Frame Format, Table 4-2 802.1Q Tagged Heartbeat Frame Format

View all HP Integrity rx2800 manuals

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

Page 36 highlights

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. However, if transmission is not successful, the team will place the port in a state called "Failed (Tx Heartbeat)" and the team will failover to a functional non-Primary port. As long as a port remains in the "Failed (Tx Heartbeat) state, it will attempt to transmit a heartbeat frame at every timer interval. In summary, when using the default transmit path validation timer of 3 seconds, each port may transmit heartbeat frames as often as every 6 seconds and the longest it will take to detect transmit failures will be 9 seconds. • Receive path validation - At the receive path validation timer interval (default = 3 seconds), the team checks to determine if each port has successfully received any frame since the last timer interval. If not, then the port's internal status is degraded by incrementing the port's internal status by 1 (starting at 0). After a port's internal status has degraded to 2 (2 transitions) without receiving any kind of frame, all other ports in the same team will transmit a heartbeat frame with the intention that the port attempting to validate receives will receive at least one of the transmitted heartbeat frames. If the port does receive one of these heartbeats, its internal status is reset to 0. However, if the port still does not receive a frame, then the port is placed in a state called "Failed (Rx Heartbeat)" and the team will fail over to a functional non-Primary port. • Switch MAC table updates with team MAC address - There is no timer associated with this type of heartbeat since it only happens during team initialization or team failover. Heartbeat Frame Format: Heartbeat frame size is 84 bytes including the FCS. Heartbeat frames are LLC test frames with 63 bytes of data. The destination address of all heartbeat frames is a Layer 2 multicast address of 03-00-C7-00-00-EE. This is a HP registered multicast address and used only for heartbeat frames. Below is an example of a heartbeat frame. Table 4-1 Heartbeat Frame Format 802.2 frame format Destination MAC address Source MAC address Length DSAP SSAP SNAP type Data FCS Value 03-00-C7-00-00-EE "MAC address of Teamed port" 66 0xAA 0xAA Unnumbered, TEST "Teaming Proprietary data" "Varies" 84 bytes total 6 bytes 6 bytes 2 bytes 1 byte 1 byte 1 byte 63 bytes 4 bytes Heartbeat frames on a tagged VLAN include an extra 4-byte field used for VLAN identification. The frame size for VLAN tagged heartbeats is 88 bytes. If multiple VLANs are configured for the team, the SA may choose which VLAN interface to use for receive path validation heartbeats via the VLAN Configuration tab. Below is an example of what the heartbeat frame with a VLAN tag would look like. Table 4-2 802.1Q Tagged Heartbeat Frame Format 802.2 frame format Destination MAC address Value 03-00-C7-00-00-EE 88 bytes total 6 bytes 36 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

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. However, if transmission is not

successful, the team will place the port in a state called “Failed (Tx Heartbeat)” and the team

will failover to a functional non-Primary port.

As long as a port remains in the “Failed (Tx Heartbeat) state, it will attempt to transmit a

heartbeat frame at every timer interval.

In summary, when using the default transmit path validation timer of 3 seconds, each port

may transmit heartbeat frames as often as every 6 seconds and the longest it will take to

detect transmit failures will be 9 seconds.

•

Receive path validation

– At the receive path validation timer interval (default = 3 seconds),

the team checks to determine if each port has successfully received any frame since the last

timer interval. If not, then the port’s internal status is degraded by incrementing the port’s

internal status by 1 (starting at 0). After a port’s internal status has degraded to 2 (2

transitions) without receiving any kind of frame, all other ports in the same team will transmit

a heartbeat frame with the intention that the port attempting to validate receives will receive

at least one of the transmitted heartbeat frames. If the port does receive one of these

heartbeats, its internal status is reset to 0. However, if the port still does not receive a frame,

then the port is placed in a state called “Failed (Rx Heartbeat)” and the team will fail over

to a functional non-Primary port.

•

Switch MAC table updates with team MAC address

– There is no timer associated with this type

of heartbeat since it only happens during team initialization or team failover.

Heartbeat Frame Format:

Heartbeat frame size is 84 bytes including the FCS. Heartbeat frames are LLC test frames with

63 bytes of data. The destination address of all heartbeat frames is a Layer 2 multicast address

of 03-00-C7-00-00-EE. This is a HP registered multicast address and used only for heartbeat

frames. Below is an example of a heartbeat frame.

Table 4-1 Heartbeat Frame Format

84 bytes total

Value

802.2 frame format

6 bytes

03-00-C7-00-00-EE

Destination MAC address

6 bytes

“MAC address of Teamed port”

Source MAC address

2 bytes

Length

1 byte

0xAA

DSAP

1 byte

0xAA

SSAP

1 byte

Unnumbered, TEST

SNAP type

63 bytes

“Teaming Proprietary data”

Data

4 bytes

“Varies”

FCS

Heartbeat frames on a tagged VLAN include an extra 4-byte field used for VLAN identification.

The frame size for VLAN tagged heartbeats is 88 bytes. If multiple VLANs are configured for

the team, the SA may choose which VLAN interface to use for receive path validation heartbeats

via the VLAN Configuration tab. Below is an example of what the heartbeat frame with a VLAN

tag would look like.

Table 4-2 802.1Q Tagged Heartbeat Frame Format

88 bytes total

Value

802.2 frame format

6 bytes

03-00-C7-00-00-EE

Destination MAC address

The Mechanics of Teaming for the Advanced User