Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, October 26, 2012 4:55 PM
I recently build windows 2008 cluster and i found under Cluster Validation test , Networks --> Validate IP configuration section for Microsoft Failover Cluster Virtual Adapter I am seeing two ip address assgined to it. I verified the value with other windows 2008 cluster in my network. Is there any one can suggest why failover Cluster Virtual adapter got two ip address .
Please see the following Details i am seeing for Microsoft Failover Cluster Virutal adapter
Item |
Name |
|---|---|
Adapter Name |
Local Area Connection* 8 |
Adapter Description |
Microsoft Failover Cluster Virtual Adapter |
Physical Address |
02-50-56-BF-2F-C7 |
Status |
Not Operational |
IP Address |
169.254.1.193 |
Prefix Length |
16 |
IP Address |
169.254.227.106 |
Prefix Length |
16 |
Want to make sure cluster wont see any issues in future.
m
All replies (6)
Friday, October 26, 2012 5:49 PM
When you create a cluster, part of the configuration is specifying an IP address, known as a virtual IP (VIP), for use by the cluster. This address 'floats' between the nodes of the cluster, with the node owning the cluster name also owning the VIP. This is absolutely normal and is critical to the proper operation of the cluster.
What is incorrect in what you show is that the addresses are 169.254, or APIPA, addresses. This means that you have the system set up for DHCP, which is fine (though I prefer to have fixed IP addresses on my clusters), but you do not have DHCP servicing those NICs.
tim
Friday, October 26, 2012 6:18 PM
the issue above i am mentioning about is not for Cluster VIP, Its for Microsoft Failover Clusteradpater , this is available when you add failover clustering Feature in the server, and it will get 169.254.x.x adress and bounded to one of the available nic mac address.
My question is : Why Microsoft Failover Cluster adapter ( this is virutal adpater ) got Two ip address instead of one ? Server consists Primary , Secondary Nics available, cluster is already configured with Static ip address. the output i pased above thread from Cluster Validation report. Please See the screen shot again.
Please note I got three Nics attached to server NIC1,NIC2, Heartbeat
Adapter Name |
Local Area Connection* 8 |
Adapter Description |
Microsoft Failover Cluster Virtual Adapter |
Physical Address |
02-50-56-BF-2F-C7 |
Status |
Not Operational |
IP Address |
169.254.1.193 |
Prefix Length |
16 |
IP Address |
169.254.227.106 |
Prefix Length |
16 |
Item |
Name |
|---|---|
Adapter Name |
NIC1 |
Adapter Description |
Intel(R) PRO/1000 MT Network Connection |
Physical Address |
00-50-56-BF-2F-C5 |
Status |
Operational |
IP Address |
11.136.166.73 |
Prefix Length |
24 |
IP Address |
11.136.166.74 |
Prefix Length |
24 |
IP Address |
11.136.166.76 |
Prefix Length |
24 |
Item |
Name |
|---|---|
Adapter Name |
NIC2 |
Adapter Description |
Intel(R) PRO/1000 MT Network Connection #2 |
Physical Address |
00-50-56-BF-2F-C6 |
Status |
Operational |
IP Address |
11.66.166.32 |
Prefix Length |
24 |
Item |
Name |
|---|---|
Adapter Name |
Heartbeat |
Adapter Description |
Intel(R) PRO/1000 MT Network Connection #3 |
Physical Address |
00-50-56-BF-2F-C7 |
Status |
Operational |
IP Address |
172.16.166.73 |
Prefix Length |
24 |
Item |
Name |
|---|---|
Adapter Name |
Loopback Pseudo-Interface 1 |
Adapter Description |
Software Loopback Interface 1 |
Physical Address |
00-00-00-00-00-00-00-00 |
Status |
Operational |
IP Address |
::1 |
Prefix Length |
128 |
IP Address |
127.0.0.1 |
Prefix Length |
8 |
m
Friday, October 26, 2012 8:34 PM
Jeff wrote a good blog describing what the Failover Network Adapter is and how it functions - http://blogs.technet.com/b/askcore/archive/2009/02/13/what-is-a-microsoft-failover-cluster-virtual-adapter-anyway.aspx
Not sure why you are seeing two APIPA addresses on it - you should definitely be seeing one.
tim
Saturday, October 27, 2012 5:41 PM
Thats the reason i came to this forum to see if any one helps me to resolve the issue. I read the the article above already , but not helping me how to resolve the issue. I am not sure why i am seeing two APIPA Address on it.Any help is appreciated.
m
Saturday, October 27, 2012 9:04 PM
Cluster does not assign IP to this NIC. It relies in IP stack to auto-generate IP. Autogenerated IP starts from 169.*. I am not sure why you would get 2 IPs on this NIC. Is that reproducible even after rebooting the node? In any case I do not see why this would cause a problem.
Regards, Vladimir Petter, Microsoft Corporation
Monday, October 29, 2012 3:00 PM
Yes , i restarted the node, still i can see 2 ips assigned to Virtual network adapter, I just want to make sure this doesn't causes any issues for Clustering after server went to prodcution.
m