asked on

Risks to deleting CNO on Hyper-v 2012 Failover Cluster?

I have a failover cluster- it is a 2-node Hyper-V Windows Server 2012, and one of the nodes had failed. I rebuilt the node, and have had weird issues seemingly related to the CNO ever since. One current problem is that failover doesn't work- I have to slow-migrate between nodes, which defeats most of the purpose of the cluster. The cluster consists of two nodes using a 10TB SAN for CSV. What risks to I run by deleting the cluster object and rebuilding it? I would do this off-hours of course, but I'm just curious what issues are likely to surface- I'll be doing this late at night, so I'd like to make sure I am as poised as possible with solutions in hand.
Thanks!

Philip Elder

How was the node removed from the cluster post death and how was it re-introduced?

Was Constrained Delegation set up on the DC(s) to allow the workloads to Live Migrate between them? If yes, was CD updated for the replacement node?

Steve

I recommend using the 'simulate failure' option as it carries no impact and has a cool little quirk:

If you perform enough 'simulated failures' within the network name section of WFCM (i.e. hit your configured failure limit, usually somewhere around 3-4) the option to 'repair' becomes available. This repair action performs a number of tasks including remediation of DNS/CNO items.

As the failures that have enabled the repair option were only simulated they can be done without impact and result in enabling
Doing it out of hours is still a good precaution though.

Worth a try before you take manual steps.

This question needs an answer!

Become an EE member today

7 DAY FREE TRIAL

Members can start a 7-Day Free trial then enjoy unlimited access to the platform.

View membership options

Learn why we charge membership fees

We get it - no one likes a content blocker. Take one extra minute and find out why we block content.