Article ID: 197999
Article Last Modified on 2/22/2007
APPLIES TO
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows NT Server 4.0 Standard Edition
- Microsoft Windows NT Server 4.0 Enterprise Edition
- Microsoft Windows NT Load Balancing Service
This article was previously published under Q197999
SUMMARY
The limitations described in this article apply only when multicast cluster media access control address support is disabled and you are using only one network interface card in each cluster host.
MORE INFORMATION
If you disable multicast support and are only using unicast, you should install a dedicated network interface card (NIC) to handle cluster traffic to achieve optimum performance and the full range of networking functionality. Although it is possible to have a successful cluster installation with only one NIC, there are two limitations to this approach:
- Computers within the cluster will not be able to communicate among themselves with any networking protocol, not just TCP/IP. This can be a special problem if one or more of the clustered servers also act as primary and backup domain controllers.
- Networking traffic destined to individual servers within the cluster will generate additional networking overhead for all computers in the cluster.
These limitations may not be important for many installations. If the computers within the cluster are only accessed from outside the cluster (that is, there are no intracluster communications) and noncluster communications are infrequent (for example, short nightly updates of the Web server content to individual computers in the cluster), the use of a single networking card should be sufficient. Also, it is always possible to test and demo Windows NT Load Balancing Service (WLBS) using a single network card prior to installing additional cards for operational purposes.
Additional query words: Convoy unicast
Keywords: kbinfo KB197999
