IPv4 Host name resolution on Failover Cluster Server 2008
[2008] [asa failover] [Cluster] [failover] [failover cluster] [Host'] [MSCS] [name] [pix failover] [Resolution] [server] [Windows]
Related:
- DNS Issues with DHCP in Windows Server 2008 Failover ClusterSymptom If you use DHCP in Windows Server 2008 Failover...
- MaxDB directories in UNIX clusters for failoverSymptom You want to run a MaxDB/SAP DB/liveCache instance in...
- Virtualization on WindowsSymptom You want to use an SAP system productively on...
- Virtualization on Windows: Enhanced monitoringSymptom You operate an SAP system with Microsoft Windows and...
- DB2-z/OS: Seamless JDBC Database Failover for SAP Java stackSymptom This SAP Note describes how to enable high availability...
- DB2-z/OS: DB2 Connect 9.1 JDBC Failover for SAP Java stackSymptom This SAP Note describes how to enable high availability...
- Virtualization on WindowsSymptom This note contains information about using an SAP system...
- Virtualization on Windows: Enhanced monitoringSymptom You operate an SAP system with Microsoft Windows on...
Symptom
The commandping -4
Applications that report IP addresses to other applications running on computers that do not belong to the cluster, might use this address. Therefore, the address cannot be used for general communication purposes, since it is not possible to connect to the applications at the address that they report.
Other terms
Failover Cluster, host name resolution, MSCS, Windows Server 2008
Reason and Prerequisites
Microsoft introduced with Failover Clustering in Windows Server 2008 a new network adapter for the internal cluster communication, named “Microsoft Failover Cluster Virtual Adapter”. The IP address of this adapter is located in a separate subnet (169.254.2…).
Normally, the IP address of this adapter is reported as first or second IP address in the list of available IP addresses. Unfortunately, you cannot administer the automatically created adapter using the network adapter administration. This means you cannot reorder the priority of the adapters in the existing network administration dialogs.
Solution
Check whetherping -4
If so, open and run a command prompt as administrator and run the following commands:
netsh interface ipv6 set prefix ::1/128 50 5
netsh interface ipv6 add prefix ::1/96 40 4
netsh interface ipv6 add prefix ::ffff:0:0/96 30 3
netsh interface ipv6 add prefix ::/0 20 2
netsh interface ipv6 add prefix ::ffff:169.254.0.0/112 10 1
Recheck withping -4
![[del.icio.us]](http://images.del.icio.us/static/img/delicious.small.gif){kind=small}