It's been a while since working on Win2000/Exchange 2000 Shared clusters, but I remember the Heartbeat NIC's being attached to a small HUB and then using host file entries to resolve the other Cluster Nodes to the corresponding Heartbeat NIC address. Is this still a typical configuration on X7 SCC clusters? I see no host file entries on the X7 hosts. Because when I ping/resolve a Cluster node it uses the Production NIC address. I'm just wondering if the Heatbeat NIC configuration is setup correctly. Thanks
The heartbeat (actually private is the good name) NIC si configured thru the cluster manager. You configure a NIC as private or shared (public and private) or public only. You can also configure the NIC priority. So, the cluster service use these settings (IP address) to determine which NIC to use and that's why you don't have to use host file. But maybe you confuse mscs cluster with NLB (which is often named network clustering). With NLB, in unicast mode, you should have to configure a host file to allow internal communication (though this is not mandatory anymore since Windows 2003 SP2). Regards Stephen Roux "Del" a écrit dans le message de news:%23dPEH42kIHA.1280@TK2MSFTNGP05.phx.gbl... > It's been a while since working on Win2000/Exchange 2000 Shared clusters, > but I remember the Heartbeat NIC's being attached to a small HUB and then > using host file entries to resolve the other Cluster Nodes to the > corresponding Heartbeat NIC address. > > Is this still a typical configuration on X7 SCC clusters? I see no host > file entries on the X7 hosts. Because when I ping/resolve a Cluster node > it uses the Production NIC address. I'm just wondering if the Heatbeat > NIC configuration is setup correctly. > > Thanks > > >
Thanks that confirms the KB I found and how we are configured. That's good http://support.microsoft.com/?id=258750 15. Complete the previous steps on all other nodes in the cluster. 16. Start Cluster Administrator. 17. Click the cluster name at the root of Administrator. On the File menu, click Properties. 18. On the Network Priority tab, verify that the private network is listed at the top. If it is not, use the Move Up button to increase its priority. 19. Click the private network, and then click Properties. 20. Click to select the Enable this network for cluster use check box. 21. Click Internal cluster communications only (private Network). "Stephen ROUX" wrote in message news:%23Xydjd$kIHA.4712@TK2MSFTNGP04.phx.gbl... > The heartbeat (actually private is the good name) NIC si configured thru > the cluster manager. You configure a NIC as private or shared (public and > private) or public only. You can also configure the NIC priority. > So, the cluster service use these settings (IP address) to determine which > NIC to use and that's why you don't have to use host file. > > But maybe you confuse mscs cluster with NLB (which is often named network > clustering). With NLB, in unicast mode, you should have to configure a > host file to allow internal communication (though this is not mandatory > anymore since Windows 2003 SP2). > > Regards > > Stephen Roux > > "Del" a écrit dans le message de > news:%23dPEH42kIHA.1280@TK2MSFTNGP05.phx.gbl... >> It's been a while since working on Win2000/Exchange 2000 Shared clusters, >> but I remember the Heartbeat NIC's being attached to a small HUB and then >> using host file entries to resolve the other Cluster Nodes to the >> corresponding Heartbeat NIC address. >> >> Is this still a typical configuration on X7 SCC clusters? I see no host >> file entries on the X7 hosts. Because when I ping/resolve a Cluster node >> it uses the Production NIC address. I'm just wondering if the Heatbeat >> NIC configuration is setup correctly. >> >> Thanks >> >> >> >
