Robc0918
asked on
Windows Failover clustering network problem
I have been trying to figure this problem out for a few days now.
Environment
Windows Server 2008 R2
Two hyper V servers setup on CSV and Fail over clustering
Issue:
I connected both of our servers to a backup Storage area network - they connect to a switch. Failover cluster manager picked that network up and assigned it as a cluster network. There was a problem with the switch port configuration that caused it to be partitioned. I fixed that issue and changed the ethernet ports being used on the servers.
Since this change the Fail over cluster manager isn't picking up the new network and lists the old network as being down ( using the old ports). What this means is that now live migration does not and if one of the hosts failed the fail over part wouldn't work.
I have tried rebooting the Hosts. I have tried stopping and restarting the Cluster services on each node in the fail over manager. After all this the old network is still there listed as being down and its not picking up the new network on the new ports.
I had the old network set as disallow cluster communication.
My research has picked up nothing that might give me a solution to this problem.
Environment
Windows Server 2008 R2
Two hyper V servers setup on CSV and Fail over clustering
Issue:
I connected both of our servers to a backup Storage area network - they connect to a switch. Failover cluster manager picked that network up and assigned it as a cluster network. There was a problem with the switch port configuration that caused it to be partitioned. I fixed that issue and changed the ethernet ports being used on the servers.
Since this change the Fail over cluster manager isn't picking up the new network and lists the old network as being down ( using the old ports). What this means is that now live migration does not and if one of the hosts failed the fail over part wouldn't work.
I have tried rebooting the Hosts. I have tried stopping and restarting the Cluster services on each node in the fail over manager. After all this the old network is still there listed as being down and its not picking up the new network on the new ports.
I had the old network set as disallow cluster communication.
My research has picked up nothing that might give me a solution to this problem.
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Have you run the Failover Clustering verification utility, what does it fail on?
ASKER
Sorry, actually yes I ran those tests and they all passed.
I have a warning under validate IP tests but that is happening because I have adapters that aren't being used on these hosts.
This is an example of one of them.
Adapters Local Area Connection 17 and Local Area Connection on node server01.domain.com have IP addresses on the same subnet.
This may be intentional, since both adapters are currently Not Operational.
I have a warning under validate IP tests but that is happening because I have adapters that aren't being used on these hosts.
This is an example of one of them.
Adapters Local Area Connection 17 and Local Area Connection on node server01.domain.com have IP addresses on the same subnet.
This may be intentional, since both adapters are currently Not Operational.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I tried that initially and it didn't work. So your reminder prompted me to do something similar. The Network that was being reported was using the OLD ports. I disabled those ports instead and then re enabled them ( even though they weren't being used). Fail-over cluster manager then reported that the network was still down, but it now reported the correct Ethernet ports being used. SO I disabled those ports and then re enabled them. Now the fail over cluster manager reports that the network is up. It removed the old network and just labeled it as a cluster network. I renamed it and changed the properties and now everything works.