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

Can I use HP Integrity Network Adapter Teaming in conjunction with Microsoft

Page 96 highlights

B.B.1.9 B.B.1.10 B.B.1.11 B.B.1.12 B.B.1.13 B.B.1.14 How do I uninstall HP Integrity Network Adapter Teaming? HP Integrity Network Adapter Teaming can be uninstalled by opening the properties page of any network interface under Network and Dial-up Connections (Microsoft UI). Select HP Network Teaming and Configuration and click the UNINSTALL button. Always dissolve any existing teams using the NCU before attempting an uninstall of HP Integrity Network Adapter Teaming. Why does having Spanning Tree turned on for the HP Integrity Network adapter team switch ports cause a problem sometimes? When link is lost on a port that has Spanning Tree enabled on it, Spanning Tree will isolate the port from communicating with the rest of the network for a certain time period. This time period can sometimes exceed a minute. This isolation period can cause communication loss, heartbeat failures, and undesired teaming failovers under certain conditions. Spanning Tree timeouts can also cause PXE boot failures. HP recommends bypassing the block, listen, and learn stages of Spanning Tree on switch ports connected to a server (for example, Cisco's PortFast). Is HP Integrity Network Adapter Teaming an industry-standard technology? The core of HP Integrity Network Adapter Teaming technology is an industry-standard technology used for grouping network ports together for fault tolerance and load balancing. However, some of the special mechanisms that HP uses to enhance network port teaming are unique to HP teaming technology. Can I use third party/non-HP network adapters with HP Integrity Network Adapter Teaming? No, only HP branded network adapters may be used. What does the Network Infrastructure Group need to do to help me deploy HP Integrity Network Adapter Teaming correctly? For all team types, the Network Infrastructure Group needs to know the following: • The VLAN IDs used on a particular team • Which group of ports constitutes a team. For each group, the following must be done: - All ports must be configured for the same VLANs, if any. - All ports must belong to the same broadcast domain/s. For SLB teams, they also need to know which group of ports constitutes a team. For each group, all ports in each team must be configured as a single-port trunk/Multilink Trunk/EtherChannel group. For 802.3ad Dynamic teams, they should only need to verify that LACP is enabled on the switch ports connecting to the server's teamed ports. For Dual Channel, they need to know which sets of teamed ports constitute Group A versus Group B. All the teamed ports in Group A should be configured on the switch as one port trunk and all the teamed ports in Group B should be configured on the switch as another port trunk. Can I use HP Integrity Network Adapter Teaming in conjunction with Microsoft Cluster Server? Yes, however, Microsoft may request that teaming be disabled before technical assistance is provided. If teaming can be disabled and the problem still occurs, it may be assumed that the problem is not affected by teaming. You may always contact HP for support and HP Support can help resolve the issue. Microsoft does not recommend using NIC teaming in private cluster networks because of delays that could occur in the transmission and receipt of heartbeat packets among the nodes. For public (or mixed) cluster networks, NIC teaming is acceptable. For more information about NIC teaming issues in clustered environments, see the following documents: 96 - Frequently Asked Questions

  • 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

B.B.1.9
How do I uninstall HP Integrity Network Adapter Teaming?
HP Integrity Network Adapter Teaming can be uninstalled by opening the properties
page of any network interface under Network and Dial-up Connections (Microsoft
UI). Select
HP Network Teaming and Configuration
and click the
UNINSTALL
button. Always dissolve any existing teams using the NCU before attempting an
uninstall of HP Integrity Network Adapter Teaming.
B.B.1.10
Why does having Spanning Tree turned on for the HP Integrity Network adapter
team switch ports cause a problem sometimes?
When link is lost on a port that has Spanning Tree enabled on it, Spanning Tree will
isolate the port from communicating with the rest of the network for a certain time
period. This time period can sometimes exceed a minute. This isolation period can
cause communication loss, heartbeat failures, and undesired teaming failovers under
certain conditions. Spanning Tree timeouts can also cause PXE boot failures. HP
recommends bypassing the block, listen, and learn stages of Spanning Tree on switch
ports connected to a server (for example, Cisco’s PortFast).
B.B.1.11
Is HP Integrity Network Adapter Teaming an industry-standard technology?
The core of HP Integrity Network Adapter Teaming technology is an
industry-standard technology used for grouping network ports together for fault
tolerance and load balancing. However, some of the special mechanisms that HP
uses to enhance network port teaming are unique to HP teaming technology.
B.B.1.12
Can I use third party/non-HP network adapters with HP Integrity Network Adapter
Teaming?
No, only HP branded network adapters may be used.
B.B.1.13
What does the Network Infrastructure Group need to do to help me deploy HP
Integrity Network Adapter Teaming correctly?
For all team types, the Network Infrastructure Group needs to know the following:
The VLAN IDs used on a particular team
Which group of ports constitutes a team. For each group, the following must
be done:
All ports must be configured for the same VLANs, if any.
All ports must belong to the same broadcast domain/s.
For SLB teams, they also need to know which group of ports constitutes a team. For
each group, all ports in each team must be configured as a single-port trunk/Multilink
Trunk/EtherChannel group.
For 802.3ad Dynamic teams, they should only need to verify that LACP is enabled
on the switch ports connecting to the server’s teamed ports.
For Dual Channel, they need to know which sets of teamed ports constitute Group
A versus Group B. All the teamed ports in Group A should be configured on the
switch as one port trunk and all the teamed ports in Group B should be configured
on the switch as another port trunk.
B.B.1.14
Can I use HP Integrity Network Adapter Teaming in conjunction with Microsoft
Cluster Server?
Yes, however, Microsoft may request that teaming be disabled before technical
assistance is provided. If teaming can be disabled and the problem still occurs, it
may be assumed that the problem is not affected by teaming. You may always contact
HP for support and HP Support can help resolve the issue.
Microsoft does not recommend using NIC teaming in private cluster networks
because of delays that could occur in the transmission and receipt of heartbeat packets
among the nodes. For public (or mixed) cluster networks, NIC teaming is acceptable.
For more information about NIC teaming issues in clustered environments, see the
following documents:
96
– Frequently Asked Questions