Nft Network Adapter Failure Recovery; Nft Applications - HP Rx2620-2 - Integrity - 0 MB RAM Manual

NFT Network Adapter Failure Recovery

For Network Fault Tolerance Only (NFT) teams, there are two operating modes: Normal Mode
and Manual Mode. Normal mode is the default mode that NFT operates in. If the user desires
to manually force a failover, the Manual Mode button on the Team Controls tab on the Team
Properties can be used.
• Manual Mode: This mode for NFT is used for user-initiated failovers (manual failovers).
When used, Manual Mode allows an NFT team to automatically failover during events that
normally cause a failover (for example, a cable is unplugged on the Primary port of an NFT
team). However, Manual Mode also allows the team to manually failover with the click of
a button. Manual mode is normally used for troubleshooting purposes (for example, using
an analyzer to take an inline network trace). Manual Mode is a temporary mode.
• Normal Mode: The second mode available for NFT is Normal Mode. In this mode, an NFT
team will initiate a failover from the Primary port to an operational Non-Primary port
whenever a failover event occurs (refer to "Failover events") on the Primary port. When the
failover occurs, the two ports swap MAC addresses so the team remains known to the
network by the same MAC address. If the old Primary port is restored, it becomes a
Non-Primary port for the team but no MAC address changes are made unless there is another
failover event on the Primary port.
NOTE:
Non-Primary ports are already in standby mode. The only consequence of a failed
Non-Primary port is the possibility of the Primary port failing and the team becoming
unavailable to the network because both teamed ports are in a failed state. If there are three
or more network ports in a team and two ports fail, the team is still available via the third
port.

NFT Applications

NFT is deployed in environments that only require fault tolerance and do not require transmit
or receive throughput greater than the capacity of the Primary port (for example, a server that
56 The Mechanics of Teaming for the Advanced User
Failures of Non-Primary ports do not trigger any type of recovery because
is the preferred root Fast Path also can choose the best
teamed port from a set of teamed ports that all have
validated connectivity to the main network segment. As a
result, Fast Path can initiate a failover from one teamed
port operating as the Primary port to another non-Primary
teamed port for either of two reasons. The first failover is
caused by a teamed port losing connectivity with the main
network segment, in which case the team will label the
teamed port as Split LAN and will disable the teamed port
for use by the team. The second failover occurs when the
team discovers that a non-Primary port has better
connectivity to the root switch than the current Primary
port. In this case, the roles are switched, and the original
Primary port remains a functioning member of the team
in a non-Primary role.
If all teamed ports lose connectivity with all root switches
(in other words, no team members are receiving BPDUs),
no failover will occur since one teamed port is no better
than another with regard to the Fast Path mechanism. The
team will operate as if Fast Path was disabled except that
all teamed ports will be labeled as Fast Path Degraded and
the team will be in a degraded state.