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

Table 4-3 Directed ARP Echo Node Probe REQUEST Frame Format, Source MAC Address field

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 40 highlights

modifications to the designated Echo Node were required. Third, a frame type had to be chosen that would not cause loss of communication for normal data traffic between the Echo Node and the team since, in many environments, the Echo Node could be another server, another client, a switch, or a router functioning as the team's gateway. To comply with the above requirements, Directed ARP was designed to use a modified ARP request frame as the Echo Node probe. The format of the ARP request frame was chosen in order to prevent Echo Node probes from changing the team's ARP cache entry in the Echo Node's ARP table. By omitting the Source IP address in the ARP frame, the designated Echo Node doesn't have enough information to modify its ARP entry for the team's IP address. However, the Echo Node will respond back to the Source MAC address in the ARP frame with an ARP response. Since each teamed port inserts its own unique MAC address in the Source MAC Address field, each teamed port receives an individual response from the Echo Node. As a result, Directed ARP's Echo Node probe provides for validation to each teamed port, works with most (but not all) IP protocol stacks, and does not cause loss of communication with the team for normal data traffic. Table 4-3 Directed 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 Protocol address length ARP operation Source MAC address Source IP address Destination MAC address Destination IP address Checksum Value "Broadcast" unless specified in GUI "MAC address of Teamed port" "Value of VLAN ID and Priority" 0x0806 (ARP) 0x01 (Ethernet) 0x800 (IP) 0x06 0x04 0x001 (ARP request) "MAC address of Teamed port" 0.0.0.0 00:00:00:00:00:00 "Echo Node IP Address from GUI" "varies" 64 Bytes Total 6 bytes 6 bytes 4 bytes 2 bytes 2 bytes 2 bytes 1 byte 1 byte 2 bytes 6 bytes 4 bytes 6 bytes 4 bytes 4 bytes Table 4-4 Directed 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 Protocol address length Value "MAC address of Teamed port" "Echo Node's MAC Address" "Value of VLAN ID and Priority" 0x0806 (ARP) 0x01 (Ethernet) 0x800 (IP) 0x06 0x04 64 Bytes Total 6 bytes 6 bytes 4 bytes 2 bytes 2 bytes 2 bytes 1 byte 1 byte 40 The Mechanics of Teaming for the Advanced User

  • 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
modifications to the designated Echo Node were required. Third, a frame type had to be
chosen that would not cause loss of communication for normal data traffic between the Echo
Node and the team since, in many environments, the Echo Node could be another server,
another client, a switch, or a router functioning as the team’s gateway.
To comply with the above requirements, Directed ARP was designed to use a modified ARP
request frame as the Echo Node probe. The format of the ARP request frame was chosen in
order to prevent Echo Node probes from changing the team’s ARP cache entry in the Echo
Node’s ARP table. By omitting the Source IP address in the ARP frame, the designated Echo
Node doesn’t have enough information to modify its ARP entry for the team’s IP address.
However, the Echo Node will respond back to the Source MAC address in the ARP frame
with an ARP response. Since each teamed port inserts its own unique MAC address in the
Source MAC Address field, each teamed port receives an individual response from the Echo
Node. As a result, Directed ARP’s Echo Node probe provides for validation to each teamed
port, works with most (but not all) IP protocol stacks, and does not cause loss of
communication with the team for normal data traffic.
Table 4-3 Directed ARP Echo Node Probe REQUEST Frame Format
64 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
1 byte
0x04
Protocol address length
2 bytes
0x001 (ARP request)
ARP operation
6 bytes
“MAC address of Teamed port”
Source MAC address
4 bytes
0.0.0.0
Source IP address
6 bytes
00:00:00:00:00:00
Destination MAC address
4 bytes
“Echo Node IP Address from GUI”
Destination IP address
4 bytes
“varies”
Checksum
Table 4-4 Directed ARP Echo Node Probe REPLY Frame Format
64 Bytes Total
Value
Ethernet V2 Frame Format
6 bytes
“MAC address of Teamed port”
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
1 byte
0x04
Protocol address length
40
The Mechanics of Teaming for the Advanced User