Changing Cluster Heart Beat IP

I have about 10 Windows 2008 failover cluster running in VMware. I noticed the cluster heart beat vlan used by the cluster is the same for each one. While there are no conflicts I would like to change it. Are there any problems in changing the cluster heartbeat IP?
LVL 21
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
this can be done with ease, but it depends on how you have currently configured your cluster heartbeats.

Check the properties of the cluster, check what traffic is allowed over each network interface. Because you can define the interfaces, to be used only for public, client, internal cluster traffic of both!

If you current Client/Public interface allow both type of traffic no issues, go head and change the cluster heart beat IP Addresses. However if your public/client interface only allows client/public traffic, you will need to make a temp change, before you make the IP change to Cluster Heartbeat, and then after change it back!

I hope that makes sense.

(or, and for this you will need to make friends with your Network Manager, is create a new VLAN for Cluster A, Cluster B etc)
compdigit44Author Commented:
Right now our clusters are setup with seperate public and private NIC's and all clusters seem to share the same vlAN / IP range which was setup long before I start at my current company. My questions is this setup OK or should all cluster have seperate heartbeat vLans??? I am concerned about IP conflicts in the future since all addresses are static and not currently in IPAM
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
We prefer to keep all our cluster heartbeats, private and isolated from each other, just like in the "old days" you would have a physical ethernet cable between two physical hosts.

We also standardize, on using the same IP Address (Private for Heartbeats), which you cannot do, if all your cluster hosts share the same network!
compdigit44Author Commented:
Thanks but is there any harm in the way we have it set now?
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
other, than idiots, that change the IP Addresses!

no, but it's not a private network!

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.