HYPER-V NETWORKING ISSUE!

[Koldov]

I'm desperately trying not to need to go into school this week but...

 

Working remotely and unfortunately it's nearly midnight and I've made my first 'serious' error!

 

I've manged to go from 2012R2 VMs to 2019 and Gen1 to Gen2 (although there have been a few scary moments and quite a few things I needed to deal with) I'd got up the nerve to do the host (2012R2 > 2019)...

 

Again there are a few things that aren't quite right, but the major issue was that during the 2019 install it seems to have installed new drivers for the NICs, it also seems to have renamed them somehow... luckily not a deal breaker for the host OS, but it killed the VM networking.

 

I thought I could deal with it but have gone round in circles...

 

Essentially the NICs were originally Broadcom #38 and Broadcom #39, now when the host OS installed new drivers, for some reason it renamed them QLogic #39 and QLogic #40 and the VSwitch wasn't attached to a physical NIC anymore!

 

What I thought was that I could just create a new VSwitch attached it to the renamed physical NIC but the choices in Hyper-V manager show the 'old' names (Broadcom #38 & Broadcom #39) and not the new names (QLogic #39 & QLogic #40) and I couldn't remove the old VSwitch.

 

After hours of research and not really finding anything similar, but eventually managing to delete the old VSwitch I tried to create a new one and stupidly unticked 'allow management OS' and then obviously chose the wrong one... Although I thought I chose the NIC not used by the host there must still be some link and once I hit 'apply' I was instantly disconnected...

 

So it's gone midnight and I'm going to have to do the 'walk of shame' into work tomorrow so I can work on the physical host and at least get that back up, the trouble is I don't even know how to fix the Hyper-V issue.

 

Why is Hyper-V manager still showing the old NIC names and is there anything I can do that doesn't involve me uninstalling and reinstalling the Hyper-V role...?

Edited December 21, 2022 by Koldov

[3s-gtech]

I can’t quite picture the issue you’re having, but I had to play some games with one of our hosts when I upgraded it from 2012 R2 to 2019 as I had to delete the NIC team before the upgrade. That affected the vswitch.

 

There was no special config or VLANs, but it was still a pain and getting traffic to pass properly again took a while.

 

What I’ll say is that it was massively, massively easier to fix connected locally. Don’t try to do this sort of thing locally unless you have iLO/iDRAC or are incredibly lucky!

 

Hope it goes okay today.

[Koldov]

Thanks!

 

Yeah I knew I was pushing my luck trying to do it remotely, but I'd done really well up to that point (although there were a few nail biting moments).

 

In fact apart from that one incident (which I have to admit was a click too far as it was getting late and I'd been on it solidly for hours) it was quite a success!

 

Just for completeness I managed to fix it by actually deleting the dedicated NIC in the host (the right one this time) and letting it reinstall. Then once I opened HyperV manager it was available with its new name to attach it to a VSwitch.