Views:
To resume networking and NIC configuration mapping, do the steps below:
  1. Turn off the Primary server and Secondary server (if applicable).
  2. Go to the physical box or VM Settings (Primary or Secondary fserver), then change the NIC.
    • For physical box, you need to get the MAC address (e.g. plug the NIC to a Windows machine, and then run ipconfig /all in command prompt).

      ipconfig results

    • For vSphere machine, open the VM Properties window to confirm the new NIC’s MAC address.

      Virtual Machine Properties

  3. Boot up the server that has the new NIC.
  4. Modify the configuration 70-persistent-net.rules. Do the following:
    1. Login to the server console and check the device information in this file: “root@appliance1: vim /etc/udev/rules.d/70-persistent-net.rules”.

      NIC Information

      The device’s configuration and MAC Address will be shown, and you will see the NAME="eth0" and NAME="eth1".

       
      If you see other devices’ information (like eth2, eth3, etc.), they are generated automatically when vSphere creates a new NIC or you have another NIC in your physical box. The names "eth2", "eth3", etc. cannot be used because the system only needs to use eth0 and eth1.
       
    2. Change the ATTR{address} to the MAC address which you got before, and make it the  same with the MAC address of the network interface card.
  5. Modify the configuration 99-osdp-net.rules. Do the following:
    1. Login to the server console and check the device information in this file: root@appliance1: vim /etc/udev/rules.d/99-osdp-net.rules.

      New NIC information

    2. Change the ATTR{address} to the MAC address which you get before, and make it the same with the MAC address of the network interface card.
  6. Restart the VM or the Physical box.
  7. Check network configuration. Use the following command:

    root@appliance1 : ifconfig

     
    The frontend0 and database0 will be mapped to the correct NIC device and the server will now work correctly.
    The file 99-osdp-net.rules records the frontend0 and databases0 information.
    Double check the eth0 and eth1's mac address is correct in this file:
    Path: root@appliance1: vim /etc/udev/rules.d/99-osdp-net.rules.