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

Network Fault Tolerance Only (NFT), Network Fault Tolerance Only with 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 18 highlights

Figure 3-4 Teaming types and functionality Basic Teaming Basic Teaming Advanced Teaming Basic Teaming Receive Load Balancing Transmit Load Balancing Switch Fault Tolerance* Network Fault Tolerance Only (NFT) Network Fault Tolerance Only with Preference Order Network Adapter Fault Tolerance Transmit Load Balancing with Fault Tolerance (TLB) Transmit Load Balancing with Fault Tolerance and Preference Order Switch-assisted Load Balancing with Fault Tolerance (SLB) 802.3ad Dynamic with Fault Tolerance Switch Fault Tolerance* Switch-assisted Dual Channel Load Balancing 802.3ad Dynamic Dual Channel Load Balancing *Switch Fault Tolerance means Team supports members connected to more than one switch. Network Fault Tolerance Only (NFT) Network Fault Tolerance (NFT) is the foundation of HP Integrity Network Adapter Teaming. In NFT mode, from two to eight teamed ports are teamed together to operate as a single virtual network adapter. However, only one teamed port-the Primary teamed port-is used for both transmit and receive communication with the server. The remaining adapters are considered to be standby (or secondary adapters) and are referred to as Non-Primary teamed ports. Non-Primary teamed ports remain idle unless the Primary teamed port fails. All teamed ports may transmit and receive heartbeats, including Non-Primary adapters. The fault-tolerance feature that NFT represents for HP Integrity Network Adapter Teaming is the only feature found in every other team type. It can be said that the foundation of every team type supports NFT. NFT is a basic feature of HP Integrity Network Adapter Teaming. Refer to "Basic Teaming Versus Advanced Teaming" for more information. Network Fault Tolerance Only with Preference Order Network Fault Tolerance Only with Preference Order is identical in almost every way to NFT. The only difference is that this team type allows the SA to prioritize the order in which teamed ports should be the Primary teamed port. This ability is important in environments where one or more teamed ports are more preferred than other ports in the same team. The need for ranking certain teamed ports better than others can be a result of unequal speeds, better adapter capabilities (for example, higher receive/transmit descriptors or buffers, interrupt coalescence, etc.), or preference for the team's Primary port to be located on a specific switch. NFT with Preference Order is a basic feature of HP Integrity Network Adapter Teaming. Refer to "Basic Teaming Versus Advanced Teaming" for more information. 18 Teaming Fundamentals for the First-Time 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
Figure 3-4 Teaming types and functionality
Basic Teaming
Network Fault
Tolerance Only with
Preference Order
Network Fault
Tolerance Only
(NFT)
Basic Teaming
Basic Teaming
Advanced Teaming
*Switch Fault Tolerance means Team supports members connected to more than one switch.
Transmit Load
Balancing with Fault
Tolerance
(TLB)
Transmit Load
Balancing with Fault
Tolerance and
Preference Order
Switch-assisted
Load Balancing with
Fault Tolerance
(SLB)
802.3ad Dynamic
with Fault Tolerance
802.3ad Dynamic
Dual Channel Load
Balancing
Switch-assisted Dual
Channel Load
Balancing
Switch Fault Tolerance*
Transmit Load Balancing
Receive Load Balancing
Network Adapter Fault Tolerance
Switch Fault Tolerance*
Network Fault Tolerance Only (NFT)
Network Fault Tolerance (NFT) is the foundation of HP Integrity Network Adapter Teaming.
In NFT mode, from two to eight teamed ports are teamed together to operate as a single virtual
network adapter. However, only one teamed port–the Primary teamed port–is used for both
transmit and receive communication with the server. The remaining adapters are considered to
be standby (or secondary adapters) and are referred to as Non-Primary teamed ports. Non-Primary
teamed ports remain idle unless the Primary teamed port fails. All teamed ports may transmit
and receive heartbeats, including Non-Primary adapters.
The fault-tolerance feature that NFT represents for HP Integrity Network Adapter Teaming is
the only feature found in every other team type. It can be said that the foundation of every team
type supports NFT.
NFT is a basic feature of HP Integrity Network Adapter Teaming. Refer to
“Basic Teaming Versus
Advanced Teaming”
for more information.
Network Fault Tolerance Only with Preference Order
Network Fault Tolerance Only with Preference Order is identical in almost every way to NFT.
The only difference is that this team type allows the SA to prioritize the order in which teamed
ports should be the Primary teamed port. This ability is important in environments where one
or more teamed ports are more preferred than other ports in the same team. The need for ranking
certain teamed ports better than others can be a result of unequal speeds, better adapter capabilities
(for example, higher receive/transmit descriptors or buffers, interrupt coalescence, etc.), or
preference for the team’s Primary port to be located on a specific switch.
NFT with Preference Order is a basic feature of HP Integrity Network Adapter Teaming. Refer
to
“Basic Teaming Versus Advanced Teaming”
for more information.
18
Teaming Fundamentals for the First-Time User