The identity router services will not start after reboot on Microsoft Hyper-V because Hyper-V sees that the NIC card configurations are changed from eth0 and eth1 to eth2 and eth3.
Cause
The Hyper-V virtual machine has a Dynamic MAC address on the Ethernet NIC, which changed after reboot or live migration. The IDR machine loses its network configurations as the Linux operating system binds the IP configurations to the MAC address.
Workaround
As a workaround, redeploy the IDR on Hyper-V and configure the MAC address settings to use a static MAC address rather than dynamic.
