Failover Clustering and Network Load Balancing Team Blog
Hi Cluster Fans,
In Windows Server 2008 and Windows Server 2008 R2 we have simplified how easy it is to create and use a Failover Cluster. For example, if we detect you are using DHCP in your datacenter, we will automatically assign the cluster as well as clustered applications and services a DHCP IP Address. This just makes configuration even easier since environment defaults are used, so less information is needed!
But what happens if you want to deploy just a single DHCP (or WINS) Server on your cluster? The recommendation is to use a static IP Address, so that the DHCP Server can always be reached, without requiring it to request a DHCP IP Address from a DHCP Server. If you use DHCP, you should always have multiple DHCP Servers in your environment for high-availability and redundancy, but even if you experience multiple simultaneous failures, you will still want them to come back online as quickly as possible by giving them statically assigned IP Addresses. If you only had only a single DHCP server which was using a DHCP address, this DHCP server may never come up.
The following steps will show how to configure a DHCP server with a static IP Address when DHCP is detected in the environment. First open the Windows Server 2008 R2 Failover Cluster Manager. Then launch the High-Availability Wizard by selecting the action, Configure a Service or Application for High-Availability. This wizard will ask just a few questions before giving you a clustered DHCP (or WINS) Server. First it asks for the application, feature, role or service to make highly-available. A DHCP Server is selected.
Second it asks for a friendly name for the DHCP server, this is the Network Name. If DHCP was not being used, a prompt for an IP Address would be show.
Finally shared cluster storage is selected. After confirming the information, a highly-available DHCP Server is created in very few simple steps.
Since a DHCP IP Address was used for the DHCP Server, we want to give it a static IP Address. First right-click the IPv4 Address and select Properties. Currently a DHCP IP Address is selected for use.
This is easily changed to use a statically assigned IP Address, 10.121.36.100.
Now after applying the changes and exiting, the DHCP is using the statically assigned IP Address.
You can use this method to change any type of IP Address this quick, including IPv6 or other statically assigned IPv4 and IPv6 Addresses.
Thanks,Symon PerrimanProgram Manager IIClustering & High-AvailabilityMicrosoft
With Windows 2003 we used to reserve the IP address on the DHCP server for all kinds of cluster resources like SQL IP/Name, Cluster IP/Name etc. But this reservation was done using a spoofed MAC address that would go something like 00020A.....
I am wondering if i can carry on that same practice with Windows 2008 R2 ? On the first few clustered resources i have used DHCP but i am trying to determine that if i can make a reservation using a spoofed address ? How do i determine the mac address of a cluster resource that is automatically assigned using DHCP ?
My Windows Server 2008 Cluster runs Exchange Server 2007 CCR mailbox, so I wonder if I need to change the IP address in one of the node as follows:
NIC 1 Server public IP
NIC 1 Exchange mailbox cluster service Virtual IP
NIC 1 MSCS virtual IP
Nic 2 Cluster Private network IP 1 (which receive the mailbox replication data from DR mailbox node)
Nic 2 Cluster Private network IP 2 (which send the mailbox replication data to DR mailbox node)
do I have to bring down both nodes or can I just change it on the node while it is become passive ?
The cluster Forum is the best place for questions like these, here's the link: