troubleshooting Question

vSphere 4 Failover Cluster Shutdown Problem

Avatar of MiniBazzer
MiniBazzerFlag for United Kingdom of Great Britain and Northern Ireland asked on
18 Comments1 Solution3286 ViewsLast Modified:
I have recently started at an organisation which has a fairly new virtualised installation. I have taken over from someone else who is in the process of moving to another department in the organisation, so knowledge can be obtained as to the history of the system.

I have a system which consists of two clusters - one Production and one Disaster Recovery. Each cluster is based on it's own set of system hardware - seperate Blade Centre's, SAN's etc etc. I can provide more information on this, if it helps to resolve the issue. :)

My issue is this...

We had a requirement to shutdown the Disaster Recovery hardware over the weekend due to some power work that was occuring. As the system as a whole is in a state where it is running on Production, I thought that we would be able to take the DR system down without much of a hiccup. Okay, the system wouldnt be visable in the Client and vCentre might complain about not being able to communicate. We also run DoubleTake, so thought that it might also complain about not being able to replicate. But generally we expected the system to run without much of an issue.

However, this was not the case. Shortly after shutting down DR, we started getting calls about machines being unable to connect to the system. Rebooting seemed to fix this, so we thought all was well. About an hour or so later, more machines were experiencing issues and even our own machines couldnt connect. We decided to reboot the network switches but to no avail. We then bought the network switches back online in the DR system, thinking that if there was a network config issue in the switches, this would resolve the issue. But no. The last thing to do was bring the BladeCentre back online and boot up the servers. Once everything was back up and running again (after a few minutes) the issue resolved itself.

This therefore would suggest that there is some sort of issue with the vSphere Cluster being down that caused our network outage problems, but we're puzzled as to how. If someone is able to shed any light, I would be most appreciative.

Cheers, Simon
Join our community to see this answer!
Unlock 1 Answer and 18 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 18 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros