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

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

Mechanism Priority

View all HP Integrity rx2800 manuals

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

Page 80 highlights

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. All basic redundancy mechanisms (in other words, link loss, transmit path validation heartbeats, and receive path validation heartbeats) and all advanced redundancy mechanisms (in other words, Active Path and Fast Path) can be used together. As a result, an implementer may need to prioritize the mechanisms in case of a conflict. When multiple mechanisms are in use on the same team, certain network scenarios may result in one mechanism in use by the team choosing a different resolution to the problem than another mechanism in use by the same team. For instance, there are situations when Active Path and Fast Path may disagree on which teamed port should be the team's Primary port (refer to Figure 4-23). In this scenario, a team has been deployed with both Active Path and Fast Path. In this situation, Active Path prefers NIC 1 while Fast Path prefers NIC 2. Active Path prefers NIC 1 because only NIC 1 can reach the Echo Node connected to Switch A. Fast Path prefers NIC 2 because NIC 2 has access to the best root switch (root switch 1 - Core Switch). NIC 1 connected to Root Switch 2 (Switch A) is inferior because of its Spanning Tree bridge priority. If Switch A and the Core Switch could communicate, Switch A would agree that the Core Switch is the root switch since the Core Switch's Spanning Tree Bridge Priority is better than its own (Switch A). Remember, Spanning Tree calculations always prefer a lower number - the lowest Path Cost is the best, the lowest Bridge ID is the best, the lowest Bridge Priority is the best, etc. Figure 4-23 Active Path and Fast Path disagree on Primary teamed port Link 5 Gigabit Ethernet Root Switch 2 (Bridge Priority 32768) C on so le NIC 1 Active Path (Passed) Fast Path (Failed) Switch A Echo Node HP NIC Teaming Root Switch 1 (Bridge Priority 16384) NIC 2 Fast Path (Passed) Active Path (Failed) Link 4 Gigabit Ethernet Link 1 Gigabit Ethernet HP Integrity Server C on so le Switch B Core Switch Because Active Path and Fast Path disagree, the implementer needs to designate which mechanism has a higher priority. On the Advanced Redundancy tab in the NCU (refer to Figure 4-24), the implementer may highlight the individual mechanism and use the arrows on the right to move a mechanism higher or lower on the priority list. If Fast Path is selected as the higher priority 80 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

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. All basic redundancy mechanisms (in other words, link loss,

transmit path validation heartbeats, and receive path validation heartbeats) and all advanced

redundancy mechanisms (in other words, Active Path and Fast Path) can be used together. As

a result, an implementer may need to prioritize the mechanisms in case of a conflict.

When multiple mechanisms are in use on the same team, certain network scenarios may result

in one mechanism in use by the team choosing a different resolution to the problem than another

mechanism in use by the same team. For instance, there are situations when Active Path and

Fast Path may disagree on which teamed port should be the team’s Primary port (refer to

Figure 4-23

). In this scenario, a team has been deployed with both Active Path and Fast Path. In

this situation, Active Path prefers NIC 1 while Fast Path prefers NIC 2. Active Path prefers NIC

1 because only NIC 1 can reach the Echo Node connected to Switch A. Fast Path prefers NIC 2

because NIC 2 has access to the best root switch (root switch 1 – Core Switch). NIC 1 connected

to Root Switch 2 (Switch A) is inferior because of its Spanning Tree bridge priority. If Switch A

and the Core Switch could communicate, Switch A would agree that the Core Switch is the root

switch since the Core Switch’s Spanning Tree Bridge Priority is better than its own (Switch A).

Remember, Spanning Tree calculations always prefer a lower number – the lowest Path Cost is

the best, the lowest Bridge ID is the best, the lowest Bridge Priority is the best, etc.

Figure 4-23 Active Path and Fast Path disagree on Primary teamed port

Echo Node

NIC 1

Fast Path (Failed)

NIC 2

Gigabit Ethernet

Switch A

Switch B

Root Switch 2

(Bridge Priority 32768)

Root Switch 1

(Bridge Priority 16384)

Link 5

Gigabit Ethernet

Link 4

Gigabit Ethernet

Link 1

HP Integrity Server

Core Switch

Active Path (Passed)

Fast Path (Passed)

Active Path (Failed)

HP NIC

Teaming

Because Active Path and Fast Path disagree, the implementer needs to designate which mechanism

has a higher priority. On the Advanced Redundancy tab in the NCU (refer to

Figure 4-24

), the

implementer may highlight the individual mechanism and use the arrows on the right to move

a mechanism higher or lower on the priority list. If Fast Path is selected as the higher priority

The Mechanics of Teaming for the Advanced User