• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 904
  • Last Modified:

shut down Hyper-V cluster

This is a lab not in production.

We've been testing the Hyper-V cluster recently.  two Windows 2008 R2 SP1 servers are running Hyper-V in a cluster (2 SAN)

Another Hyper-V is in standalone.

One DC is in the cluster

One DC is running on the standalone Hyper-V

One DC is running on a physical server.

The goal was to see if we can also power it on (after the shut down) in the event that a DC goes down.  So we moved all FSMO roles on the DC in the cluster (which of cource can't be brought online before the cluster is online)

We shuted down all VM and servers,

Then we powered on the DC from the physical server.  Then the standalone Hyper-V.  we couldn't login to the domain at first.

We powered on the other DC running on the standalone Hyper-V.

It looks like AD has some trouble to run without the DC that had all the FSMO roles.  

Then we powered on the Hyper-V cluster.  The cluster failed to go online.  it couldn't resolve the cluster name (but the IP was online)  Besides, it looks like one of the Hyper-v that had all the disks (SAN) online was the one having the problem.  

As soon as we shut it down, the disks ownership has been transfered to the other Hyper-V and everything went back online.

As far as I understand.  It can take more time to bring all AD ressources online when the DC that holds all FSMO roles is down.  Is that true?

Besides, when one of the Hyper-V in the cluster is having trouble to reach the DNS, the cluster cannot be used from the IP only.  But I can be wrong here.  Please let me know

The disks (SAN) owned by a Hyper-V server will not be available if this server is having problem to communicate with the DNS, although all other DC are also running the DNS,

Thanks for your feedback
2 Solutions
Krzysztof PytkoSenior Active Directory EngineerCommented:
Ok, that's not true. FSMO holders are not so important according to DC boot up process. To be able to log in in a domain at least one Global Catalog server is required and at least one DNS server. Make sure that both DCs are GC and have DNS role installed.

Then DNS settings in NIC properties are important. To be able to resolve all necesarry SRV DNS records, you need to specify in this case primary and alternate DNS servers on both Domain Controllers. Please check that order

For DC1
Primary: DC2
Alternate: its IP address
3rd: (loopback interface)

And accordingly to these settings, configure the second DC.

Please test this scenario, please and let me know if it works now.

In addition to having a working domain controller with DNS, I also find it useful to have a working DHCP server, especially when the Hyper-V nodes use DHCP. ( Learned that the hard way :-)

FMSO roles aren't needed, but it can take several minutes for AD to come up on a DC, and of course your cluster nodes need to point to a running DNS server. With those changes, you should be able to completely shut down your environment and bring it back up.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now