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

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

Scenario A-2: One Device Pings Another on a Different Layer 2 Network

View all HP Integrity rx2800 manuals

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

Page 91 highlights

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. 5. Red transmits a unicast ARP reply to Blue providing its MAC address (A). NOTE: The following step will not occur if Step 4 does not take place. Red sees the ARP request and transmits a unicast ARP reply directly to Blue providing its MAC address (A). Blue receives the ARP reply and puts Red's MAC address (A) and IP address (1.1.1.1) in its ARP cache. 6. Blue transmits a unicast ping reply to Red using Red's destination MAC address (A). Blue transmits a unicast ping reply to Red using Red's MAC address (A) and the user sees the ping REPLY message printed on the screen. This completes the entire conversation. Scenario A-2: One Device Pings Another on a Different Layer 2 Network Figure A-2 Scenario A-2: one device pings another on a different Layer 2 network MAC = C IP = 1.1.1.3 Green (Router) MAC = D IP = 2.2.2.3 Network 1.0.0.0 Ethernet Network 2.0.0.0 Ethernet MAC = A IP = 1.1.1.1 MAC = B IP = 2.2.2.1 Red Blue 1. Red transmits a broadcast ARP request on Network 1.0.0.0 asking for Green's MAC address. A user on Red issues the command ping 2.2.2.1 to initiate a ping to Blue. The number 2.2.2.1 refers to Blue's IP address, or protocol address. First, Red determines whether or not Blue is on the same Layer 2 network by running an algorithm (details of this algorithm are beyond the scope of this document) using its own IP address of 1.1.1.1, its own subnet mask (not shown), and Blue's IP address of 2.2.2.1. If Blue is on a different Layer 2 network, then Red will need to use its gateway or router (Green) to get to Blue. Once Red has determined that Blue is on a different Layer 2 network, Red must use Green as a gateway to get to Blue. Red communicates directly with Green at Layer 2 but communicates directly with Blue at Layer 3. This means that Red must transmit a frame with the Layer 2 address (MAC) of Green, but the same frame will have Blue's Layer 3 address (IP) in it. When Green receives the frame, it sees the Layer 3 data destined for Blue and forwards the frame onto Blue via Green's interface that is attached to Blue's Layer 2 network (Network 2.0.0.0). This means that Red must find out what Green's MAC address Example Scenarios of Network Addressing and Communication 91

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

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.

Red transmits a unicast ARP reply to Blue providing its MAC address (A).

NOTE:

The following step will not occur if Step 4 does not take place.

Red sees the ARP request and transmits a unicast ARP reply directly to Blue providing its

MAC address (A). Blue receives the ARP reply and puts Red’s MAC address (A) and IP

address (1.1.1.1) in its ARP cache.

Blue transmits a unicast ping reply to Red using Red’s destination MAC address (A).

Blue transmits a unicast ping reply to Red using Red’s MAC address (A) and the user sees

the ping REPLY message printed on the screen. This completes the entire conversation.

Scenario A-2: One Device Pings Another on a Different Layer 2 Network

Figure A-2 Scenario A-2: one device pings another on a different Layer 2 network

Ethernet

MAC = A

IP = 1.1.1.1

MAC = C

IP = 1.1.1.3

Network

1.0.0.0

Network

2.0.0.0

MAC = D

IP = 2.2.2.3

Red

Green

(Router)

MAC = B

IP = 2.2.2.1

Blue

Ethernet

Red transmits a broadcast ARP request on Network 1.0.0.0 asking for Green’s MAC

address.

A user on Red issues the command ping 2.2.2.1 to initiate a ping to Blue. The number 2.2.2.1

refers to Blue’s IP address, or protocol address. First, Red determines whether or not Blue

is on the same Layer 2 network by running an algorithm (details of this algorithm are beyond

the scope of this document) using its own IP address of 1.1.1.1, its own subnet mask (not

shown), and Blue’s IP address of 2.2.2.1. If Blue is on a different Layer 2 network, then Red

will need to use its gateway or router (Green) to get to Blue.

Once Red has determined that Blue is on a different Layer 2 network, Red must use Green

as a gateway to get to Blue. Red communicates directly with Green at Layer 2 but

communicates directly with Blue at Layer 3. This means that Red must transmit a frame

with the Layer 2 address (MAC) of Green, but the same frame will have Blue’s Layer 3

address (IP) in it. When Green receives the frame, it sees the Layer 3 data destined for Blue

and forwards the frame onto Blue via Green’s interface that is attached to Blue’s Layer 2

network (Network 2.0.0.0). This means that Red must find out what Green’s MAC address

Example Scenarios of Network Addressing and Communication