Solved

Windows Failover clustering network problem

Posted on 2013-01-17
5
992 Views
Last Modified: 2013-01-18
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.
0
Comment
Question by:Robc0918
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 121
ID: 38788505
Have you run the Failover Clustering verification utility, what does it fail on?
0
 

Author Comment

by:Robc0918
ID: 38788930
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.
0
 
LVL 121

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 500 total points
ID: 38788987
Yes, that's a normal error, and completely acceptable, because you could be using MPIO to a SAN with the same subnet address.

I have seen weird things with clustering of late, try and disable the adapters and re-enable
0
 

Author Comment

by:Robc0918
ID: 38793046
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.
0
 
LVL 121
ID: 38793329
only a grade B?
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
Giving access to ESXi shell console is always an issue for IT departments to other Teams, or Projects. We need to find a way so that teams can use ESXTOP for their POCs, or tests without giving them the access to ESXi host shell console with a root …
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're looking for how to monitor bandwidth using netflow or packet s…
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…
Suggested Courses

632 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question