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

Red transmits a unicast ping request to Blue using Blue's destination MAC address.

Get HP Integrity rx2800 - i2 PDF manuals and user guides View all HP Integrity rx2800 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 59 highlights

Figure 4-13 Scenario 4-B: A device pings a TLB team on the same Layer 2 network Ethernet MAC = A IP = 1.1.1.1 Red MAC = B Primary MAC = E Non-Primary TLB IP = 1.1.1.2 Blue (server) 1. Red transmits a broadcast ARP request asking for Blue's MAC address. A user on Red issues the command ping 1.1.1.2 to initiate a ping to Blue. First, Red determines whether or not Blue is on the same Layer 2 network. Once Red has determined that Blue is on the same Layer 2 network, Red must find out what Blue's MAC address is. First, Red checks its own ARP cache for a MAC address entry matching the IP address of 1.1.1.2. If Red does not have a static entry or an entry cached from a previous conversation with Blue, then it must broadcast an ARP request frame on the network asking Blue to respond and provide its MAC address. Red must broadcast this ARP request because without knowing Blue's unique MAC address, it has no way of sending a frame directly (unicast) to Blue. 2. Blue transmits a unicast ARP reply to Red, providing its MAC address. Blue sees the ARP request (the frame is received on both the Primary and Non-Primary teamed ports because the frame is broadcast onto the network. However, the team discards all non-heartbeat frames incoming on Non-Primary ports), and responds with a unicast ARP reply to Red. In Blue's ARP reply, Blue provides the MAC address of its teaming driver, which is the same as the current Primary port's MAC address (B) (refer to "HP Teaming and Layer 2 Versus Layer 3 Addresses"). Blue also takes note of Red's MAC address (A) and IP address (1.1.1.1) and enters them into its ARP cache. Red receives the reply and enters the MAC address (B) and the IP address of Blue (1.1.1.2) into its own ARP cache. 3. Red transmits a unicast ping request to Blue using Blue's destination MAC address. Red can now create a ping request frame using Blue's MAC address (B). Red sends the ping request to Blue. Blue receives the frame on its Primary port (B) and notices that a station with an IP address of 1.1.1.1 is asking for it to respond. Types of HP Integrity Network Adapter Teams 59

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
Figure 4-13 Scenario 4–B: A device pings a TLB team on the same Layer 2 network
Ethernet
MAC = A
IP = 1.1.1.1
MAC = B
Primary
MAC = E
Non-Primary
Blue
(server)
Red
TLB
IP = 1.1.1.2
1.
Red transmits a broadcast ARP request asking for Blue’s MAC address.
A user on Red issues the command ping 1.1.1.2 to initiate a ping to Blue. First, Red determines
whether or not Blue is on the same Layer 2 network.
Once Red has determined that Blue is on the same Layer 2 network, Red must find out what
Blue’s MAC address is. First, Red checks its own ARP cache for a MAC address entry
matching the IP address of 1.1.1.2. If Red does not have a static entry or an entry cached
from a previous conversation with Blue, then it must broadcast an ARP request frame on
the network asking Blue to respond and provide its MAC address. Red must broadcast this
ARP request because without knowing Blue’s unique MAC address, it has no way of sending
a frame directly (unicast) to Blue.
2.
Blue transmits a unicast ARP reply to Red, providing its MAC address.
Blue sees the ARP request (the frame is received on both the Primary and Non-Primary
teamed ports because the frame is broadcast onto the network. However, the team discards
all non-heartbeat frames incoming on Non-Primary ports), and responds with a unicast ARP
reply to Red.
In Blue’s ARP reply, Blue provides the MAC address of its teaming driver, which is the same
as the current Primary port’s MAC address (B) (refer to
“HP Teaming and Layer 2 Versus
Layer 3 Addresses”
). Blue also takes note of Red’s MAC address (A) and IP address (1.1.1.1)
and enters them into its ARP cache. Red receives the reply and enters the MAC address (B)
and the IP address of Blue (1.1.1.2) into its own ARP cache.
3.
Red transmits a unicast ping request to Blue using Blue’s destination MAC address.
Red can now create a ping request frame using Blue’s MAC address (B). Red sends the ping
request to Blue. Blue receives the frame on its Primary port (B) and notices that a station
with an IP address of 1.1.1.1 is asking for it to respond.
Types of HP Integrity Network Adapter Teams
59