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

ad Dynamic with Fault Tolerance, Switch-assisted Dual Channel Load Balancing

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

technology has been designed to allow for flexibility. Therefore, the NCU may allow configuration of an SLB team that will not work correctly with a particular vendor's switch. • The switch's load-balancing algorithm should be set to XOR or SOURCE-BASED but not DESTINATION-BASED (refer to the sections, "Switch-assisted Load Balancing with Fault Tolerance (SLB)" and "Cisco EtherChannel"). The switch's load-balancing algorithm should be set to balance by IP address if most traffic destined for the server originates on a different network and must traverse a router. 802.3ad Dynamic with Fault Tolerance 802.3ad Dynamic is exactly like SLB in every way except for one - switch configuration of Port Trunking. With SLB, the switch ports connected to the team must have Port Trunking manually enabled in order for SLB to work correctly. With 802.3ad Dynamic, the Link Aggregation Control Protocol (LACP) is used by the team to communicate with the switch and automatically configure Port Trunking. This eliminates the need for manual configuration on the switch. All other aspects of 802.3ad Dynamic are identical to SLB. Refer to the SLB sections for more details. Switch-assisted Dual Channel Load Balancing Switch-assisted Dual Channel Load Balancing, simply referred to as Dual Channel, is a special team type designed by HP to accomplish everything that NFT, TLB and SLB team types accomplish all in a single team type. Prior to Dual Channel, an HP Integrity Network Adapter Teaming user had to choose between inbound load balancing or switch redundancy. Inbound load balancing is defined as the ability to receive server traffic on more than one teamed port in the same team. Switch redundancy is defined as connecting teamed ports to more than one switch to recover from a switch failure. Prior to the introduction of Dual Channel, HP Integrity Network Adapter Teaming did not provide a team type that would accomplish both needs: • TLB can provide switch redundancy since it allows you to connect teamed ports from the same team to one or more switches (refer to Figure 4-18). TLB also supports transmit load balancing. However, TLB does not support receive load balancing. Types of HP Integrity Network Adapter Teams 73

  • 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
technology has been designed to allow for flexibility. Therefore, the NCU may allow
configuration of an SLB team that will not work correctly with a particular vendor’s switch.
•
The switch’s load-balancing algorithm should be set to XOR or SOURCE-BASED but not
DESTINATION-BASED (refer to the sections,
“Switch-assisted Load Balancing with Fault
Tolerance (SLB)”
and
“Cisco EtherChannel”
).
The switch’s load-balancing algorithm should be set to balance by IP address if most traffic
destined for the server originates on a different network and must traverse a router.
802.3ad Dynamic with Fault Tolerance
802.3ad Dynamic is exactly like SLB in every way except for one – switch configuration of Port
Trunking. With SLB, the switch ports connected to the team must have Port Trunking manually
enabled in order for SLB to work correctly. With 802.3ad Dynamic, the Link Aggregation Control
Protocol (LACP) is used by the team to communicate with the switch and automatically configure
Port Trunking. This eliminates the need for manual configuration on the switch.
All other aspects of 802.3ad Dynamic are identical to SLB. Refer to the SLB sections for more
details.
Switch-assisted Dual Channel Load Balancing
Switch-assisted Dual Channel Load Balancing, simply referred to as Dual Channel, is a special
team type designed by HP to accomplish everything that NFT, TLB and SLB team types
accomplish all in a single team type. Prior to Dual Channel, an HP Integrity Network Adapter
Teaming user had to choose between inbound load balancing or switch redundancy. Inbound
load balancing is defined as the ability to receive server traffic on more than one teamed port in
the same team. Switch redundancy is defined as connecting teamed ports to more than one switch
to recover from a switch failure. Prior to the introduction of Dual Channel, HP Integrity Network
Adapter Teaming did not provide a team type that would accomplish both needs:
•
TLB can provide switch redundancy since it allows you to connect teamed ports from the
same team to one or more switches (refer to
Figure 4-18
). TLB also supports transmit load
balancing. However, TLB does not support receive load balancing.
Types of HP Integrity Network Adapter Teams
73