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

Fast Path, Summary of Fast Path's goals

Page 47 highlights

Figure 4-6 Active Path failover configuration: Community Address ARP Fast Path Fast Path is a mechanism used by HP Integrity Network Adapter Teaming to intelligently and proactively determine the best teamed ports to use to provide optimum network connectivity for the server. As with Active Path, Fast Path can determine if teamed ports have become segregated onto different broadcast domains (because of link loss on an upstream switch uplink, server network adapter ports that are connected to the wrong switch ports, VLAN misconfiguration on a switch, etc.) Also, Fast Path is used by HP Integrity Network Adapter Teaming to determine which teamed port is the optimal port to use as the team's Primary port among one or more teamed ports with validated connectivity to the preferred Spanning Tree root switch. Summary of Fast Path's goals: • To determine if the teamed ports have become segregated onto different broadcast domains (in other words, teamed ports see different Spanning Tree root switches) • To only use teamed ports with connectivity to the preferred Spanning Tree root switch for server data communication • To choose a single teamed port to be the team's Primary port (used for all receive traffic in NFT and TLB modes) that has access to the highest bandwidth links or least amount of switch hops from the team to the preferred Spanning Tree root switch Unlike Active Path, Fast Path is considered a "passive" mechanism because it does not actively transmit any frames; it only passively receives a specific type of frame, Spanning Tree Bridge Protocol Data Unit (BPDU), from the attached network(s) and uses the information to intelligently make decisions to meet its goals. The basic redundancy mechanisms used by HP Integrity Network Adapter Teaming are as follows: Types of HP Integrity Network Adapter Teams 47

  • 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 4-6 Active Path failover configuration: Community Address ARP
Fast Path
Fast Path is a mechanism used by HP Integrity Network Adapter Teaming to intelligently and
proactively determine the best teamed ports to use to provide optimum network connectivity
for the server. As with Active Path, Fast Path can determine if teamed ports have become
segregated onto different broadcast domains (because of link loss on an upstream switch uplink,
server network adapter ports that are connected to the wrong switch ports, VLAN
misconfiguration on a switch, etc.) Also, Fast Path is used by HP Integrity Network Adapter
Teaming to determine which teamed port is the optimal port to use as the team’s Primary port
among one or more teamed ports with validated connectivity to the preferred Spanning Tree
root switch.
Summary of Fast Path’s goals:
To determine if the teamed ports have become segregated onto different broadcast domains
(in other words, teamed ports see different Spanning Tree root switches)
To only use teamed ports with connectivity to the preferred Spanning Tree root switch for
server data communication
To choose a single teamed port to be the team’s Primary port (used for all receive traffic in
NFT and TLB modes) that has access to the highest bandwidth links or least amount of
switch hops from the team to the preferred Spanning Tree root switch
Unlike Active Path, Fast Path is considered a “passive” mechanism because it does not actively
transmit any frames; it only passively receives a specific type of frame, Spanning Tree Bridge
Protocol Data Unit (BPDU), from the attached network(s) and uses the information to intelligently
make decisions to meet its goals.
The basic redundancy mechanisms used by HP Integrity Network Adapter Teaming are as
follows:
Types of HP Integrity Network Adapter Teams
47