Windows Server 2008 Failover Clusters: Networking (Part 1)

re: Windows Server 2008 Failover Clusters: Networking (Part 1)

M S Ali — Tue, 04 Sep 2012 13:32:24 GMT

What is the specification of tunnel between the cluster nodes' Microsoft Failover Cluster Virtual Adapters as we don't see any TCP connection between the nodes on the firewall in the Multisubnet MNS with Fileshare witness cluster.

re: Windows Server 2008 Failover Clusters: Networking (Part 1)

Dave — Mon, 25 Jun 2012 11:08:23 GMT

Hi can you advise me if dedicated hardware is required for heartbeat in a multisite cluster deployment for SQL2008R2? Or is this routed over the private LAN as it is unicast not broadcast?

re: Windows Server 2008 Failover Clusters: Networking (Part 1)

linsanity — Fri, 17 Feb 2012 06:35:18 GMT

HI Cluster Guru,

I have a question regarding the cluster's behavior:

If the Public Network is down let's say 8 hours due to the maintenance of the connected siwtch or the firewall, what is the cluster's reaction to this situation? all resources turn in failed state or remain intact? or others?

Thanks

re: Windows Server 2008 Failover Clusters: Networking (Part 1)

Alex Huntington — Wed, 11 May 2011 00:41:46 GMT

"When two different IP V4 address such as 192.168.1.11 / 255.255.255.0 and 10.10.1.11 / 255.255.255.0 are associated to a network adapter, only 192.168.1.0 is proposed when creating the cluster or a client endpoint, whatever the order is in the IP V4 properties, whatever the gateway is (192.168.1.1 or 10.10.1.1).

Any workaround to have 10.10.1.0 proposed ? "

I have found in a lab that using 10.10.1.0/24 subnet causes problem on the network adapter so in server manager that network will not show its IP address rather it will state (Multipul IP Addresses) even when there is only one 10.10.1.254 set on the adapter. As soon as i change the address out of the 10.10.1.0/24 subnet the problem is solved. Also with the 10.10.1.254 IP address on that adapter in RRAS the interface shows an APIPPA address 169.x.x.x rather than the 10.10.1.254 associated with the interface again If you change to 10.11.1.0/24 it works fine i have found or other IP subnet.

re: Windows Server 2008 Failover Clusters: Networking (Part 1)

Helen — Thu, 21 Apr 2011 16:30:03 GMT

My Failover Cluster Virtual Adapter has the mac address of my iscsi card (ndis 0) instead for my cluster adapter is there anthing i can do?

re: Windows Server 2008 Failover Clusters: Networking (Part 1)

Arnaud — Thu, 17 Feb 2011 08:58:07 GMT

When two different IP V4 address such as 192.168.1.11 / 255.255.255.0 and 10.10.1.11 / 255.255.255.0 are associated to a network adapter, only 192.168.1.0 is proposed when creating the cluster or a client endpoint, whatever the order is in the IP V4 properties, whatever the gateway is (192.168.1.1 or 10.10.1.1).

Any workaround to have 10.10.1.0 proposed ?

re: Windows Server 2008 Failover Clusters: Networking (Part 1)

PTD — Tue, 25 May 2010 14:34:31 GMT

I notice that you say that the cluster uses IPv6 under the covers for communication. I have been attempting to create a three node R2 cluster. I have assigned static IPv4 addresses as well as static FD00::/64 addresses to all NICs(8 total per machine, 4 dedicated to iSCSI, 2 dedicated to cluster, 1 dedicated to Hyper-V, and 1 shared between Hyper-V and Cluster).. Everything passes validation with the exception of a warning that my iSCSI SAN NICs have addresses on the same subnet(acceptable for MPIO).

I have opened up the firewall rules that the clustering service installation creates to all static IPv4 and IPv6 addresses on the nodes.

Still, the "forming cluster" step stalls and fails with a timeout error. Firewall logging reveals that attempts are being made to connect between nodes using the FE80:: IPv6 address of the cluster virtual adapter on the nodes. From node1's FE80:: to node2's FE:80::, etc...

I have even gone as far as using netsh to assign a fixed FD00:: address to the virtual adapter and opening the firewalls to that but it still uses with the FE80:: address.

If it is indeed tunneling, why do I see these connection attempts? Can you tell me if the FE80:: address assigned to the virtual adapter is constant or does it randomize like is required in RFC 3041? If it is constant, I may be able to work with that.

Opening up the firewalls to all FE80::/64 addresses is a least desireable action since it is likely that other less controlled machines will be located on the same FE80:: .link

re: Windows Server 2008 Failover Clusters: Networking (Part 1)

Windows Server Core Team — Tue, 16 Feb 2010 18:07:49 GMT

tonyr08: Config sounds fine. What's the validation warnings you are seeing?

re: Windows Server 2008 Failover Clusters: Networking (Part 1)

Windows Server Core Team — Tue, 16 Feb 2010 18:06:38 GMT

ichoudhury: I fixed the link, thanks for the heads up. No, you do not need to disable IPV6. Cluster uses IPV6 under the covers to determine best route(s) between cluster nodes.

re: Windows Server 2008 Failover Clusters: Networking (Part 1)

ichoudhury — Sun, 14 Feb 2010 05:27:54 GMT

Hi,

I could not jump to the link you provided above for IPv6, but I was able to hit modified address ...

http://technet.microsoft.com/en-us/network/bb530961.aspx

Also I was curious if ipv6 should be disabled if we are not yet ready for ipv6 from our networking standpoint.