We recently had to restore an ISVA 10 virtual appliance. When the snapshot was applied, the networking was not working. We found that network interfaces listed in vmware, which are listed in the exact same order, are getting mapped to different 1.x interfaces within ISVA (we have 6 interfaces on this VM). We can see this because the mac address associated with the ISVA interfaces does not match what is in VMWare. So for example, ISVA interface 1.2 is mapped to interface 5 in VMWare.
Has anyone run across this? Is there any way to reorder the interfaces in ISVA? My only thought was to have the VM team shutdown the ISVA VM, remove all but the first interface, power on, then power off and add each additional interface back one at a time while powering cycling the VM each time. I don't know if this will trigger the underlying kernel to map them correctly or not.
I was hoping maybe there was some CLI command or something we could execute to get them mapping back correctly.
Any thoughts appreciated!
------------------------------
Matt Jenkins
------------------------------