HP Rx2620-2 Windows Integrity Network Adapter Teaming White Paper - Page 49

Switch A and Switch B is only a 100 Mbps link instead of 1000 Mbps. As a result, any device

Get HP Rx2620-2 - Integrity - 0 MB RAM PDF manuals and user guides
UPC - 829160435749
View all HP Rx2620-2 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 49 highlights

Figure 4-7 Upstream link failures cause server isolation HP NIC TEAMING IP= 1.1.1.1 NIC 1 Primary 50 USERS ACCESS TO SERVER C on so le Switch A C on so le Core Switch 250 USERS NO ACCESS TO SERVER External Network NO ACCESS TO SERVER NIC 2 Non-Primary Server Switch B C on so le 50 USERS NO ACCESS TO SERVER Router NO ACCESS TO SERVER In this case, the Fast Path mechanism, designed and developed by HP Engineering is an alternative solution. The Fast Path mechanism allows the teaming driver to passively monitor network connectivity on a per-teamed port basis with the Core Switch (designated as the Spanning Tree root switch). Teamed ports that receive Spanning Tree BPDU frames from a root switch with the highest Spanning Tree bridge priority are considered "eligible for use by the team. Any teamed port that receives a BPDU from a different root switch with a lower Spanning Tree bridge priority is considered "ineligible for use by the team" since the teamed port has been segregated from the main network segment. Therefore, Fast Path becomes another validation mechanism in addition to link loss, transmit path validation, receive path validation, and Active Path. There are also situations when upstream link failures can cause inefficient use of a server's teamed ports. For the first example, refer to Figure 4-8. In this example, Switch A has lost direct link with the Core Switch (in other words, Spanning Tree root switch). Spanning Tree eventually restores connectivity by unblocking the link between Switch A and Switch B. However, the link between Switch A and Switch B is only a 100 Mbps link instead of 1000 Mbps. As a result, any device connected to Switch A now only has access to 100 Mb worth of bandwidth to the core network. If the server's teamed port (in other words, NIC 1) connected to switch A is used as the team's Primary port, the maximum available receive bandwidth for the server is 100 Mb. However, if the same server used the teamed port (in other words, NIC 2) connected to Switch B as the team's Primary port, the maximum available receive bandwidth would be increased to 1000 Mb. Redundancy mechanisms that only test connectivity (for example, heartbeats, Active Path) will not detect this problem since connectivity with the core network still exists. A more granular mechanism needs to be implemented that can detect connectivity problems (bad versus good), and detect slower versus faster paths (good versus best). Types of HP Integrity Network Adapter Teams 49

  • 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
  • 104
  • 105
Figure 4-7 Upstream link failures cause server isolation
HP NIC
TEAMING
50 USERS
NO ACCESS TO SERVER
Router
NO ACCESS TO SERVER
50 USERS
ACCESS TO SERVER
250 USERS
NO ACCESS TO SERVER
Switch A
Switch B
Core Switch
IP=
1.1.1.1
NIC 2
Non-Primary
NIC 1
Primary
External
Network
NO ACCESS TO SERVER
Server
In this case, the Fast Path mechanism, designed and developed by HP Engineering is an alternative
solution. The Fast Path mechanism allows the teaming driver to passively monitor network
connectivity on a per-teamed port basis with the Core Switch (designated as the Spanning Tree
root switch). Teamed ports that receive Spanning Tree BPDU frames from a root switch with the
highest Spanning Tree bridge priority are considered “eligible for use by the team. Any teamed
port that receives a BPDU from a different root switch with a lower Spanning Tree bridge priority
is considered “ineligible for use by the team” since the teamed port has been segregated from
the main network segment. Therefore, Fast Path becomes another validation mechanism in
addition to link loss, transmit path validation, receive path validation, and Active Path.
There are also situations when upstream link failures can cause inefficient use of a server’s teamed
ports. For the first example, refer to
Figure 4-8
. In this example, Switch A has lost direct link with
the Core Switch (in other words, Spanning Tree root switch). Spanning Tree eventually restores
connectivity by unblocking the link between Switch A and Switch B. However, the link between
Switch A and Switch B is only a 100 Mbps link instead of 1000 Mbps. As a result, any device
connected to Switch A now only has access to 100 Mb worth of bandwidth to the core network.
If the server’s teamed port (in other words, NIC 1) connected to switch A is used as the team’s
Primary port, the maximum available receive bandwidth for the server is 100 Mb. However, if
the same server used the teamed port (in other words, NIC 2) connected to Switch B as the team’s
Primary port, the maximum available receive bandwidth would be increased to 1000 Mb.
Redundancy mechanisms that only test connectivity (for example, heartbeats, Active Path) will
not detect this problem since connectivity with the core network still exists. A more granular
mechanism needs to be implemented that can detect connectivity problems (bad versus good),
and detect slower versus faster paths (good versus best).
Types of HP Integrity Network Adapter Teams
49