Hello
I was recently testing a replica failover with re-IP scenario and discovered that the replica had booted in DHCP mode. Also noticed on first logon that the server was installing a new hardware device. It seems that the re-IP occurred correctly (per the registry) but the now active network adapter is a "new" one with a new MAC and no networking configuration applied.
This seems to be discussed here: https://www.veeam.com/blog/mac-address- ... apter.html
And a workaround was mentionned for Veeam v5.
This is no small issue, how have others dealt with this situation?
It also has applicable concerns with certain software that uses the MAC address as an identifier for product licensing. Looking at my replicas only the NICs with manual MAC addresses have carried over, all the others have been renumbered. It was my understanding that replicas kept all characteristics of their source VM.
Patrick
-
- Novice
- Posts: 5
- Liked: 3 times
- Joined: Jun 06, 2017 3:49 pm
- Full Name: Patrick Zaloum
- Contact:
-
- VP, Product Management
- Posts: 7076
- Liked: 1510 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: Veeam Replica re-IP
Which OS do you use with what patch level? Which network card.
Windows 2012 had once an issue where the new network card is detected on a new PCI-E bus and lost it´s IP. Latest patch level should be installed to avoid this.
Windows 2012 had once an issue where the new network card is detected on a new PCI-E bus and lost it´s IP. Latest patch level should be installed to avoid this.
-
- Novice
- Posts: 5
- Liked: 3 times
- Joined: Jun 06, 2017 3:49 pm
- Full Name: Patrick Zaloum
- Contact:
Re: Veeam Replica re-IP
I've been able to replicate the behavior with Windows 2008r2 and a Windows 7, both latest patch level. Haven't attempted other OS's but that shouldn't be relevant.
-
- VP, Product Management
- Posts: 7076
- Liked: 1510 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: Veeam Replica re-IP
Windows 2008R2 was affected by the PCI-E (VMXnet3/E1000e) new ID bug as well.
There are 2 fixes that I am aware of:
http://support.microsoft.com/kb/2344941 for pre Update1
and
http://support.microsoft.com/kb/2550978 for post Update 1
There are 2 fixes that I am aware of:
http://support.microsoft.com/kb/2344941 for pre Update1
and
http://support.microsoft.com/kb/2550978 for post Update 1
Who is online
Users browsing this forum: Baidu [Spider], Bing [Bot], PetrM, Semrush [Bot] and 55 guests