Case number: # 07015860
Veeam support team "gave up".
Issue:
- When we run VeeamSure procedure Fedora Linux VM's don't get an IP in Virtual Lab environment.
Veeam support suggestions was to go over steps below:
The following steps performed on production VM will resolve the issue:
1. Open PCI buses and devices list by command lspci -D and find the network card. You'll need this in point 2.
2. You should have a file /etc/udev/rules.d/70-persistent-net.rules which contains a line similar to the following:
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="04:01:07
Make a backup of this file(outside of the rules.d) and edit the original to:
SUBSYSTEM=="net", ACTION=="add", KERNELS=="0000:00:03.0", NAME="eth0"
- update KERNELS= value to the 1st column of lspci -D. This will assign interface to PCI bus address instead of MAC.
Comment out string with assignment to mac address as shown on the image.
3. Comment out string containing hardware address in eth0 config file /etc/sysconfig/network-scripts/ifcfg-eth0.
4. Reboot.
There is a problem that at step2, we don't have any files in "/etc/udev/rules.d/" in this folder.
Anyone ever managed or struggled with the same issue with Fedora Linux VM's and IP issue in Sure Lab?
Btw, Ubuntu VM in same enviroment does not have this issue. IP's are resolved sucessfully in VirtualLab.
Please advise.