Hyper-V Guest - Unidentified Network
-
To add to JB's recommendation, you might set the DC to boot a few mins before the others allowing it time to come up fully before the rest.
-
Yeah... I've tried all of the above, and the VMs still come up with Unidentified Network. I have a number of other HV Hosts configured the exact same way, and none of these have this problem.
I've rebooted the host several times, and had already changed NLA to delayed start on both the host and the guests.
At this point, I'm dissolving the team and removing the virtual switch, I'll then recreate the team and the virtual switch and reattach the guests, and see where I'm at.
-
Oh, and I have 2 DCs, so it should see one of them almost immediately
-
@pchiodo said in Hyper-V Guest - Unidentified Network:
Yeah... I've tried all of the above, and the VMs still come up with Unidentified Network. I have a number of other HV Hosts configured the exact same way, and none of these have this problem.
I've rebooted the host several times, and had already changed NLA to delayed start on both the host and the guests.
At this point, I'm dissolving the team and removing the virtual switch, I'll then recreate the team and the virtual switch and reattach the guests, and see where I'm at.
Well, that didn't pan out. Same problem...
-
Would you happen to have your DHCP server on that same HOST? Is the HOST set to a static or dynamic ip?
-
@Tim_G Ha, I completely missed these two lines:
"The host server is fine and has full connectivity.
These VMs are setup with static IPs and this particular LAN does not have a DHCP server."Ignore my above post.
-
OK, so now I have dissolved the team again, removed the virtual switch, configured one of the physical adapters with a static IP and then have created a new virtual switch with only the one NIC. So as it stands, the management NIC is NIC1 and the Virtual switch NIC is NIC2.
When I set the static on NIC2, it immediately connected to the network as normal.
As soon as I recreated the virtual switch, NIC 2 on the physical box changed to Unidentified network, and of course, the VM has the same issue.
So when NIC2 bound the host to the virtual, something went haywire.
Still struggling..... ugh
-
As soon as I remove the virtual switch, NIC2 comes back online, and can be pinged from the network. It appears this issue is on the host level.
-
Is it a Broadcom NIC? Is the firmware up to date? There are issues that are now resolved with Broadcom NICs if you update the firmware, if not, (on the host) you'll need to go in to the advanced properties of the NIC and disable Virtual Machine Queues:
Set-NetAdapterAdvancedProperty NIC1 -DisplayName “Virtual Machine Queues” -DisplayValue Disabled
Set-NetAdapterAdvancedProperty NIC2 -DisplayName “Virtual Machine Queues” -DisplayValue Disabled
Set-NetAdapterAdvancedProperty NIC3 -DisplayName “Virtual Machine Queues” -DisplayValue Disabled
Set-NetAdapterAdvancedProperty NIC4 -DisplayName “Virtual Machine Queues” -DisplayValue DisabledIf the above is all good or doesn't apply to you, have you:
- Set up the 3-NIC team FIRST
- Assign a static IP to the team
- Create a vSwitch in Hyper-V Manager, select the team NIC, UN-CHECK "Allow management operating system to share this network adapter".
- Assign above vSwitch (in #3 above) as the "Virtual Switch:" in your virtual machine's settings. You can reassign a VM's vNIC while it's running.
-
Disabling VMQ is much simpler and should always be disabled with Broadcom NICs.
Get-NetAdapterVmq | Disable-NetAdapterVmq -
VMQ has already been disabled. That was a standard when I loaded these boxes.
-
What was the last patch installed on the hypervisor?
-
@JaredBusch said in Hyper-V Guest - Unidentified Network:
Disabling VMQ is much simpler and should always be disabled with Broadcom NICs.
Get-NetAdapterVmq | Disable-NetAdapterVmqGenerally, you DO want to have VMQ enabled on your VM's Network Adapter, under Hardware Acceleration: "Enable virtual machine queue", and enabled on the HOST's network adapter. VMQ is not the issue. With VMQ enabled, you get even better performance (well, at least with 10gb speeds... probably not noticeable with 1gb). With VMQ disabled, the network load is on the Hosts CPU. VMQ off-loads it to the NIC, where it should be.
Where the problem lies, is with a select number of Broadcom NICs... specifically with the 57xx based chipsets. If you have one of the effected NICs, you should update the drivers, as it has now been resolved. If you can't update, then disable VMQ.
Here's the latest official Microsoft article regarding it:
-
I'm back to this problem. I moved the load from this server to another server so I could further investigate. I think I found the issue, but not a resolution.
In Device Manager, I still have two rogue entries:
Hyper-V Virtual Ethernet Adapter
Microsoft Hyper-V Network Switch Default MiniportBoth of these have the following error:
This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
An object ID was not found in the file
In PS the Get-VMNetworkAdapter - ManagementOS and Get-VMSwitch both come back with no results, yet they are listed in Device Manager. I can disable them in DM, but it does not resolve the issue. DM does not let me remove them, and Remove-VMSwitch and Remove-VMNetworkAdapter have no effect.
Any ideas?
-
@pchiodo said in Hyper-V Guest - Unidentified Network:
I'm back to this problem. I moved the load from this server to another server so I could further investigate. I think I found the issue, but not a resolution.
In Device Manager, I still have two rogue entries:
Hyper-V Virtual Ethernet Adapter
Microsoft Hyper-V Network Switch Default MiniportBoth of these have the following error:
This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
An object ID was not found in the file
In PS the Get-VMNetworkAdapter - ManagementOS and Get-VMSwitch both come back with no results, yet they are listed in Device Manager. I can disable them in DM, but it does not resolve the issue. DM does not let me remove them, and Remove-VMSwitch and Remove-VMNetworkAdapter have no effect.
Any ideas?
Reinstall Hyper-V Server. Something is hosed. Well I guess in your case it is Server 2012 DataCenter?
-
@JaredBusch That's really using a sledgehammer when a scalpel should be sufficient. I'd really like to find a resolution in case this comes up again. nuke and reload is a last resort IMHO.
-
@pchiodo said in Hyper-V Guest - Unidentified Network:
@JaredBusch That's really using a sledgehammer when a scalpel should be sufficient. I'd really like to find a resolution in case this comes up again. nuke and reload is a last resort IMHO.
Thanks for posting this - and while your hopefully found solution is a bit more useful considering that 2012 is still supported and sorta current, my wanting to fix my booting 2003 issue is along the same guise.
Sadly for both of us, it might not be worth the expense to our companies (in our time not working on other issues, if not in direct billing) versus just wiping and reinstalling.
-
@Dashrender I totally agree, and if this was a required production server, I'd be right on board. This particular server is not required for production, and I have moved its load to another Hyper-V server. Yes, I would like it back in the mix for load balancing and as a backup, but I still would like to take a little time to try and nail down the exact issue and solution before I just wipe it and reload.
-
@pchiodo said in Hyper-V Guest - Unidentified Network:
@Dashrender I totally agree, and if this was a required production server, I'd be right on board. This particular server is not required for production, and I have moved its load to another Hyper-V server. Yes, I would like it back in the mix for load balancing and as a backup, but I still would like to take a little time to try and nail down the exact issue and solution before I just wipe it and reload.
Right - but you missed the part about how this is possibly not beneficial to your company.
Like you, my 2003 server isn't in production either, I'm trying to make a CYA fully working/tested backup to put into the safety deposit box. Fixing the boot problem fully doesn't really help my company in any way since I have a usable solution for the boot issue. Fixing it takes me away from doing something of real value for my company, the same goes for you and solving this issue.
In the end, you and I both personally gain by having additional knowledge we didn't have before, but what we don't know is if that knowledge will have any outward value in the future. While your situation has a higher likeliness of having future value, people are still deploying Hyper-V 2012, and it's likely a very similar setup probably exists in Hyper-V 2016. My situation is completely different in that 2003 is old, does booting in a completely old manner - using P2V that's a mostly dead situation (very little P2Ving done anymore, most of it was already done), so I have very little chance of ever using this knowledge in the future.
-
@Dashrender said in Hyper-V Guest - Unidentified Network:
@pchiodo said in Hyper-V Guest - Unidentified Network:
@Dashrender I totally agree, and if this was a required production server, I'd be right on board. This particular server is not required for production, and I have moved its load to another Hyper-V server. Yes, I would like it back in the mix for load balancing and as a backup, but I still would like to take a little time to try and nail down the exact issue and solution before I just wipe it and reload.
Right - but you missed the part about how this is possibly not beneficial to your company.
Like you, my 2003 server isn't in production either, I'm trying to make a CYA fully working/tested backup to put into the safety deposit box. Fixing the boot problem fully doesn't really help my company in any way since I have a usable solution for the boot issue. Fixing it takes me away from doing something of real value for my company, the same goes for you and solving this issue.
In the end, you and I both personally gain by having additional knowledge we didn't have before, but what we don't know is if that knowledge will have any outward value in the future. While your situation has a higher likeliness of having future value, people are still deploying Hyper-V 2012, and it's likely a very similar setup probably exists in Hyper-V 2016. My situation is completely different in that 2003 is old, does booting in a completely old manner - using P2V that's a mostly dead situation (very little P2Ving done anymore, most of it was already done), so I have very little chance of ever using this knowledge in the future.
Agreed! In my particular case, I can see this happening again. We will likely not move off Server 2012 for the next 2-3 years depending on how fast our 3rd party apps adopt server 2016. This being the case, having a solution that takes minutes vs hours would be very valuable.
