000031085 - Hyper-V Live Migration move of AM 8.1 SP1 breaks Ethernet Settings in Suse Linux

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000031085
Applies ToRSA Product Set: SecurID
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.1.0 SP1
Platform: Linux
Platform (Other): Hyper V on Windows 2012 or Windows 2012 R2 Server
O/S Version: Suse Linux
Product Name: RSA-0010810
Product Description: RSA-0010810
IssueLive Migration (move to another Hyper-V host) VM of AM 8.1 SP1 losses all network configuration and after reboot nothing worked and had to reconfigure IP address, mask, gateway and DNS.
Found the OS config /etc/sysconfig/network/ had new ethernet interrfaces  
They had to reboot then got menu to add an IP address and hostname, just like the initial setup. 
A move from one hyper-V host server to another is called Live Migration, Similar to Vmotion in VMWare
After reconfiguration, network settings showed Ethernet was called Eth22 eth22
CauseYour VM has a Dynamic MAC address on the Ethernet Network Interface Card, NIC, which changes after reboot or Live Migration, so the Linux VM loses its IP Network settings

ResolutionYou need a Static MAC address on the Ethernet Network Interface Card, NIC.  In order to change this you need to power down the Virtual Machine
Static MAC

Note: the article also says "Unlike most controls for networking, this must be set while the VM is powered off."
The thing that caught Engineering’s eye was that the article said, “Failing to set the MAC to be static can cause issues where the VM appears to go offline.  There is an example of this on the MS support site (KB976724).  In this scenario, SLES 10 SP2 live migrates, changes MAC address on the new host and then loses its IP configuration.  This is because the Linux distro binds the IP configuration to the MAC address.”
Live Migration (move to another Hyper-V host)  is supported, and was tested
WorkaroundDo not enable Crash or manual Live Migration, do not reboot
NotesOriginally thought this might be a “Static IP injection” problem requiring The network Management Service to be turned off in the Windows 2012 Server host.