Support ID# 03070080
A restored VM, instant recovery or full, has no network access. Our VMs have static MAC addresses, the restored VM has no network access until the MAC is set to dynamic and then back to static. It doesn't seem to matter if the same MAC is assigned, it will then work after doing this. We have tried removing and re-adding the NIC, this doesn't seem to work either.
I have retested this on our Hyper-V 2012R2 cluster and this problem does not exist so it seems to be a 2016 issue.
Support now clutching at straws suggesting we make sure the guest and hosts are patched to latest levels.
Is anyone able to verify if they can replicate this issue?
-
- Veeam Vanguard
- Posts: 629
- Liked: 251 times
- Joined: Sep 27, 2011 12:17 pm
- Full Name: Craig Dalrymple
- Location: Scotland
- Contact:
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: Restored VM has no network access on Hyper-V 2016
Craig,
Those restores, are they on the same host or a different host?
Those restores, are they on the same host or a different host?
-
- Veeam Vanguard
- Posts: 629
- Liked: 251 times
- Joined: Sep 27, 2011 12:17 pm
- Full Name: Craig Dalrymple
- Location: Scotland
- Contact:
Re: Restored VM has no network access on Hyper-V 2016
have tried both Mike, same issue
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: Restored VM has no network access on Hyper-V 2016
So. If you do Get-VM -Name "name" | Get-VMNetworkAdapter you will see a 000000000000 address?
The only time I saw this happen (from memory) is when you do a copy of a VM instead of a move (with an import). But that is a while ago, can't even remember the version of Hyper-V.
Second that I have heard off (but never encountered myself) is issues with static MAC addresses when you are using virtual switches with specific network options (I think VMQ was one of them) for a specific brand
The only time I saw this happen (from memory) is when you do a copy of a VM instead of a move (with an import). But that is a while ago, can't even remember the version of Hyper-V.
Second that I have heard off (but never encountered myself) is issues with static MAC addresses when you are using virtual switches with specific network options (I think VMQ was one of them) for a specific brand
-
- Veeam Vanguard
- Posts: 629
- Liked: 251 times
- Joined: Sep 27, 2011 12:17 pm
- Full Name: Craig Dalrymple
- Location: Scotland
- Contact:
Re: Restored VM has no network access on Hyper-V 2016
the Get-VM comes back with the correct MAC address. Will look at the other recommendations you mentioned. Cheers Mike
Who is online
Users browsing this forum: No registered users and 7 guests