Prime VM NIC always renamed after reboot

[Mahmoud]

Hi,

whenever Cisco prime infra 3.4 rebooted (planned or unplanned) the VM loss the connectivity.

we have noticed that after restart the VM, the network interface name is changed (ex. from eth0 to eth1 or eth2--9 ) then the new interface has no IP assigned and we have to manually access shell and assign the IP to the newly created NIC.

any help for this issue

[Mahmoud]

Hi,

whenever Cisco prime infra 3.4 rebooted (planned or unplanned) the VM loss the connectivity.

we have noticed that after restart the VM, the network interface name is changed (ex. from eth0 to eth1 or eth2--9 ) then the new interface has no IP assigned and we have to manually access shell and assign the IP to the newly created NIC.

any help for this issue

[marce1000]

 - Which VM-hypervisor environment are you using , including version -> Meaning check Prime 3.4 release notes and/or compatibility requirements with VM setup has been checked.

 M.

[Mahmoud]

Hi

I am using hyper-v environment, I have checked the requirement and compatibility.

This is not a new installation , it was working fine for one year but this issue happened recently.

[marce1000]

     - What is the hyper-v version and on which windows/platform/hardware    +version(s) is it being used ?

 M.

[Mahmoud]

What is the hyper-v version

2016 build 14393

and on which windows/platform/hardware +version(s) is it being used ?

UCSB-5108

cisco prime : 3.4.0.0.348

[marce1000]

                     - What is the windows server version ?

 M.

[Mahmoud]

- What is the windows server version ?

2016

[marce1000]

 - Check if this article is useful :

                        https://access.redhat.com/solutions/514203

  M.