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

Scenario 4-C: A TLB Team Using IP Address-Based Load Balancing

Page 63 highlights

Table 4-10 Load Balancing based on Destination IP Address (four- and five-port teams) (continued) 000 network port 1 000 network port 1 001 network port 2 001 network port 2 010 network port 3 010 network port 3 011 network port 4 011 network port 4 100 network port 1 100 network port 5 101 network port 2 101 network port 1 110 network port 3 110 network port 2 111 network port 4 111 network port 3 If the Destination IP Address algorithm is chosen, and the frame doesn't have an IP header, the frame is load balanced by destination MAC address (refer to "TLB Destination MAC Address Method" below). Scenario 4-C: A TLB Team Using IP Address-Based Load Balancing Using the concepts reviewed in "Scenario A-2: One Device Pings Another on a Different Layer 2 Network" in Appendix A and Figure A-2, this section describes how TLB IP addressed- based load-balancing functions. Beginning at the point in Scenario A-2 where Blue/2.2.2.1 transmits the ping reply to Red/1.1.1.1, Blue must decide whether to use network port B or E. Blue's teaming driver calculates using the IP address of Red (1.1.1.1) because Red is the frame's destination. Because a dotted decimal 1.1.1.1 is equal to 0000 0001 . 0000 0001 . 0000 0001 . 0000 0001 in binary, and the last three bits (001) are used to determine the transmitting network port (refer to Table 4-9 - Two-port team), 001 is assigned to network port 2 (or the Non-Primary port). Therefore, when communicating with Red, Blue will always use the Non-Primary port to transmit frames. If Blue transmits a frame to Yellow, the same calculation must be made. Yellow's IP address in dotted decimal is 1.1.1.4 and equal to 0000 0001 . 0000 0001 . 0000 0001 . 0000 0100 in binary. Blue's teaming driver will again use the last three bits to determine which network port will transmit the frame. Referring to Table 4-9 - Two-port team, 100 is assigned to network port 1 (or the Primary port). Therefore, when communicating with Yellow, Blue will always use the Primary port to transmit frames. It is important to note that if an implementer uses the MAC address load balancing algorithm for the network in Figure 4-15, load balancing will not function as expected, and traffic will not be load balanced using all teamed ports. Because Blue transmits all frames destined for Red and Yellow via Green (Blue's gateway), Blue uses Green's Layer 2 address (MAC) as the frame's Destination MAC Address but uses Red's and Yellow's Layer 3 addresses (IP) as the frame's Destination IP Address. Blue never transmits frames directly to Red's or Yellow's MAC address because Blue is on a different Layer 2 network. Because Blue always transmits to Red and Yellow using Green's MAC address, the teaming driver will assign all conversations with clients on Network 1.0.0.0 to the same network port. When an HP Integrity Network adapter team needs to load balance traffic that traverses a Layer 3 device (router), at a minimum IP address-based load balancing should be used. Ideally, Automatic should be used. Types of HP Integrity Network Adapter Teams 63

  • 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

Table 4-10 Load Balancing based on Destination IP Address (four- and five-port teams)
(continued)
network port 1
000
network port 1
000
network port 2
001
network port 2
001
network port 3
010
network port 3
010
network port 4
011
network port 4
011
network port 5
100
network port 1
100
network port 1
101
network port 2
101
network port 2
110
network port 3
110
network port 3
111
network port 4
111
If the Destination IP Address algorithm is chosen, and the frame doesn’t have an IP header, the
frame is load balanced by destination MAC address (refer to
“TLB Destination MAC Address
Method”
below).
Scenario 4-C: A TLB Team Using IP Address-Based Load Balancing
Using the concepts reviewed in
“Scenario A-2: One Device Pings Another on a Different Layer
2 Network”
in Appendix A and
Figure A-2
, this section describes how TLB IP addressed- based
load-balancing functions.
Beginning at the point in Scenario A-2 where Blue/2.2.2.1 transmits the ping reply to Red/1.1.1.1,
Blue must decide whether to use network port B or E. Blue’s teaming driver calculates using the
IP address of Red (1.1.1.1) because Red is the frame’s destination. Because a dotted decimal 1.1.1.1
is equal to 0000 0001 . 0000 0001 . 0000 0001 . 0000 0001 in binary, and the last three bits (001) are
used to determine the transmitting network port (refer to
Table 4-9
– Two-port team), 001 is
assigned to network port 2 (or the Non-Primary port). Therefore, when communicating with
Red, Blue will always use the Non-Primary port to transmit frames.
If Blue transmits a frame to Yellow, the same calculation must be made. Yellow’s IP address in
dotted decimal is 1.1.1.4 and equal to 0000 0001 . 0000 0001 . 0000 0001 . 0000 0100 in binary.
Blue’s teaming driver will again use the last three bits to determine which network port will
transmit the frame. Referring to
Table 4-9
– Two-port team, 100 is assigned to network port 1 (or
the Primary port). Therefore, when communicating with Yellow, Blue will always use the Primary
port to transmit frames.
It is important to note that if an implementer uses the MAC address load balancing algorithm
for the network in
Figure 4-15
, load balancing will not function as expected, and traffic will not
be load balanced using all teamed ports. Because Blue transmits all frames destined for Red and
Yellow via Green (Blue’s gateway), Blue uses Green’s Layer 2 address (MAC) as the frame’s
Destination MAC Address but uses Red’s and Yellow’s Layer 3 addresses (IP) as the frame’s
Destination IP Address. Blue never transmits frames directly to Red’s or Yellow’s MAC address
because Blue is on a different Layer 2 network. Because Blue always transmits to Red and Yellow
using Green’s MAC address, the teaming driver will assign all conversations with clients on
Network 1.0.0.0 to the same network port. When an HP Integrity Network adapter team needs
to load balance traffic that traverses a Layer 3 device (router), at a minimum IP address-based
load balancing should be used. Ideally, Automatic should be used.
Types of HP Integrity Network Adapter Teams
63