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

Transmit Load Balancing with Fault Tolerance and Preference Order

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

switches. This helps prevent switch uplink failure scenarios that leave team members in separate broadcast domains. • TLB teams that communicate with TCP/IP network devices via a router should use the Automatic, TCP port or, IP address-based load balancing algorithm (configured via the NCU). Transmit Load Balancing with Fault Tolerance and Preference Order Transmit Load Balancing with Fault Tolerance and Preference Order is exactly like Transmit Load Balancing with Fault Tolerance except that it allows the SA to rank teamed ports with a User Ranking. This user ranking (or preference) is used by the teaming driver as a criterion in deciding which teamed port should be the Primary port. Teamed ports are ranked higher or lower than each on the Team Controls tab on the Team Properties page. In addition, the User Ranking mechanism is listed in the Mechanism Priority list box on the Advanced Redundancy tab on the Team Properties page. The User Ranking mechanism is always ranked lower than any other advanced redundancy mechanisms (for example, Active Path or Fast Path). Otherwise, if User Ranking had a higher priority, the other advanced redundancy mechanisms would be effectively disabled. For all other aspects of this team type operation, refer to the section, "Transmit Load Balancing with Fault Tolerance (TLB)". Transmit Load Balancing with Fault Tolerance and Preference Order Applications Transmit Load Balancing with Fault Tolerance and Preference Order is mainly used in teaming configurations where one or more teamed ports are better than others. For example, a TLB team of a Gigabit network adapter and a Fast Ethernet adapter could utilize Preference order to rank the Gigabit adapter higher than the Fast Ethernet adapter. As long as the Gigabit adapter is in a good state, it will rank higher than the Fast Ethernet adapter and will be the team's Primary port. Switch-Assisted Load Balancing with Fault Tolerance (SLB) Switch-assisted Load Balancing (SLB) is an HP term that refers to an industry-standard technology for grouping multiple network ports into one virtual network port and multiple switch ports into one virtual switch port. HP's SLB technology works with multiple switch vendors' technologies. Compatible technologies include: HP ProCurve Port Trunking, Cisco Fast EtherChannel (FEC)/Gigabit EtherChannel (GEC) (Static Mode Only - no PAgP), IEEE 802.3ad Link Aggregation (Static Mode only - no LACP), Nortel's Multilink Trunking (MLT), and Extreme Network® Load Sharing. Therefore, SLB mode is sometimes referred to as Fast EtherChannel mode (FEC), Gigabit EtherChannel mode (GEC), 802.3ad Static mode, or Port Trunking. Note that SLB is not the same thing as Server Load Balancing (SLB) as used by some switch vendors (for example, Cisco). Switch-assisted Load Balancing operates independently of, and in conjunction with, Server Load Balancing. SLB incorporates most of the features of NFT and TLB, and adds the feature of load balancing received traffic. The major feature that TLB, NFT, and Dual Channel have and the SLB lacks is switch fault tolerance since all teamed ports in SLB teams (and 802.3ad Dynamic teams) are required to be connected to the same switch. In SLB mode, two to eight ports may be teamed together as a single virtual network port. The load-balancing algorithm used in SLB allows for the load balancing of the server's transmit and receive traffic (refer to Figure 4-17). 68 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
switches. This helps prevent switch uplink failure scenarios that leave team members in
separate broadcast domains.
•
TLB teams that communicate with TCP/IP network devices via a router should use the
Automatic, TCP port or, IP address-based load balancing algorithm (configured via the
NCU).
Transmit Load Balancing with Fault Tolerance and Preference Order
Transmit Load Balancing with Fault Tolerance and Preference Order is exactly like Transmit
Load Balancing with Fault Tolerance except that it allows the SA to rank teamed ports with a
User Ranking. This user ranking (or preference) is used by the teaming driver as a criterion in
deciding which teamed port should be the Primary port. Teamed ports are ranked higher or
lower than each on the Team Controls tab on the Team Properties page. In addition, the User
Ranking mechanism is listed in the Mechanism Priority list box on the Advanced Redundancy
tab on the Team Properties page. The User Ranking mechanism is always ranked lower than any
other advanced redundancy mechanisms (for example, Active Path or Fast Path). Otherwise, if
User Ranking had a higher priority, the other advanced redundancy mechanisms would be
effectively disabled.
For all other aspects of this team type operation, refer to the section,
“Transmit Load Balancing
with Fault Tolerance (TLB)”
.
Transmit Load Balancing with Fault Tolerance and Preference Order Applications
Transmit Load Balancing with Fault Tolerance and Preference Order is mainly used in teaming
configurations where one or more teamed ports are better than others. For example, a TLB team
of a Gigabit network adapter and a Fast Ethernet adapter could utilize Preference order to rank
the Gigabit adapter higher than the Fast Ethernet adapter. As long as the Gigabit adapter is in a
good state, it will rank higher than the Fast Ethernet adapter and will be the team’s Primary port.
Switch-Assisted Load Balancing with Fault Tolerance (SLB)
Switch-assisted Load Balancing (SLB) is an HP term that refers to an industry-standard technology
for grouping multiple network ports into one virtual network port and multiple switch ports
into one virtual switch port. HP’s SLB technology works with multiple switch vendors’
technologies. Compatible technologies include: HP ProCurve Port Trunking, Cisco Fast
EtherChannel (FEC)/Gigabit EtherChannel (GEC) (Static Mode Only – no PAgP), IEEE 802.3ad
Link Aggregation (Static Mode only – no LACP), Nortel’s Multilink Trunking (MLT), and Extreme
Network® Load Sharing. Therefore, SLB mode is sometimes referred to as Fast EtherChannel
mode (FEC), Gigabit EtherChannel mode (GEC), 802.3ad Static mode, or Port Trunking. Note
that SLB is not the same thing as Server Load Balancing (SLB) as used by some switch vendors
(for example, Cisco). Switch-assisted Load Balancing operates independently of, and in conjunction
with, Server Load Balancing.
SLB incorporates most of the features of NFT and TLB, and adds the feature of load balancing
received traffic. The major feature that TLB, NFT, and Dual Channel have and the SLB lacks is
switch fault tolerance since all teamed ports in SLB teams (and 802.3ad Dynamic teams) are
required to be connected to the same switch.
In SLB mode, two to eight ports may be teamed together as a single virtual network port. The
load-balancing algorithm used in SLB allows for the load balancing of the server’s transmit and
receive traffic (refer to
Figure 4-17
).
68
The Mechanics of Teaming for the Advanced User