17–QLogic Teaming Services
Application Considerations
310
83840-546-00 D
Teaming with Microsoft NLB
Teaming
does not
work in Microsoft’s Network Load Balancing (NLB) unicast
mode, only in multicast mode. Due to the mechanism used by the NLB service,
the recommended teaming configuration in this environment is Failover (SLB with
a standby NIC) as load balancing is managed by NLB.
Application Considerations
Teaming and Clustering
High-Performance Computing Cluster
Microsoft Cluster Software
In each cluster node, it is strongly recommended that customers install at least
two network adapters (on-board adapters are acceptable). These interfaces serve
two purposes. One adapter is used exclusively for intra-cluster
heartbeat
communications. This is referred to as the
private adapter
and usually resides on
a separate private subnetwork. The other adapter is used for client
communications and is referred to as the
public adapter
.
Multiple adapters may be used for each of these purposes: private, intracluster
communications and public, external client communications. All QLogic teaming
modes are supported with Microsoft Cluster Software for the public adapter only.
Private network adapter teaming is not supported. Microsoft indicates that the use
of teaming on the private interconnect of a server cluster is not supported
because of delays that could possibly occur in the transmission and receipt of
heartbeat packets between the nodes. For best results, when you want
redundancy for the private interconnect, disable teaming and use the available
ports to form a second private interconnect. This achieves the same end result
and provides dual, robust communication paths for the nodes to communicate
over.
For teaming in a clustered environment, customers are recommended to use the
same brand of adapters.
