2008R2 cluster (yeah, I know) - Rename of vnetwork

[mjcp]

I've inherited a 2008R2 cluster which isn't able to move VMs. The vNET adaptor name is different between nodes so the moves fail.


The fix is straightforward enough: rename the vNET to match the other node(s). However... documentation is light on the fall out from this situation and its not something I have needed to do on a prod environment before.

Question:
Is a reboot required after the name change (either VM(s) or node(s) ) or just a refresh of VM config to pick up the new name?


Follow up Q:
If the latter (refresh only), will the guest VMs continue to function between name change and refresh? (already knowing that moves will not - that's what's getting fixed)


Cheers in advance!

M

[quackhandle]

I've inherited a 2008R2 cluster which isn't able to move VMs. The vNET adaptor name is different between nodes so the moves fail.


The fix is straightforward enough: rename the vNET to match the other node(s). However... documentation is light on the fall out from this situation and its not something I have needed to do on a prod environment before.

Question:
Is a reboot required after the name change (either VM(s) or node(s) ) or just a refresh of VM config to pick up the new name?


Follow up Q:
If the latter (refresh only), will the guest VMs continue to function between name change and refresh? (already knowing that moves will not - that's what's getting fixed)


Cheers in advance!

M

I would reboot everything and see what comes back up. Name changes and WSFC don't tend to play nice.

Any help here? :

Change the node names of a Windows cluster – SQLServerCentral

Step-by-Step: Configuring a 2-node multi-site cluster on Windows Server 2008 R2 – Part 1 – Clustering For Mere Mortals

qh

[mjcp]

I would reboot everything and see what comes back up. Name changes and WSFC don't tend to play nice.

Any help here? :

Change the node names of a Windows cluster – SQLServerCentral

Step-by-Step: Configuring a 2-node multi-site cluster on Windows Server 2008 R2 – Part 1 – Clustering For Mere Mortals

qh

Google Uni has a few results, but none for prod environments and therefore, has liberal use of reboots 'cos its windows and that's what we do ;-)


Re the above links - I need to rename the vNET, not the nodes and the 2nd has a step for renaming the vNETS as part of the setup (which whomever set these up, didn't do!) Annoyingly, you can validate the cluster without them matching and I guess testing the failover aspects didn't occur to the previous keepers!

Cheers! M

[CheeseSlice]

Not sure I can help, but you haven't said if its a Hyper-V cluster (sounds like it is one) and your vNET is the network defined in Hyper-V not at the WSFC level?

[mjcp]

Not sure I can help, but you haven't said if its a Hyper-V cluster (sounds like it is one) and your vNET is the network defined in Hyper-V not at the WSFC level?

It is a HV cluster.

Yes, the name inconsistency IS between the vNETs between the two nodes in Hyper-v.

Fortunately this site is quite a small environment, so removing from HA and lift/shift moves are do-able (and they haven't had functioning failover anyway, so not something they will miss!)... but would prefer 10 mins of rename and refresh vs a few hours of manual moves...

Cheers,
M