Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Changing the Network Interface Card (NIC) in SafeSync for Enterprise (SSFE) 2.1

    • Updated:
    • 4 Feb 2016
    • Product/Version:
    • SafeSync for Enterprise 2.1
    • Platform:
    • iOS 9.2
Summary

SafeSync for Enterprise does not work correctly after changing the NIC.

When the vSphere VM or physical box changes the NIC device, the Ubuntu network-related configuration in SafeSync for Enterprise does not change automatically. This causes the OS of the VM to not recognize the new NIC, and the eth0 and eth1 mapping will fail. The eth0 and eth1 is linked to frontend0 and database0, so SafeSync will not work correctly.

Details
Public
To resume networking and NIC configuration mapping, do the steps below:
  1. Turn off the Master server and Slave server (if applicable).
  2. Go to the physical box or VM Settings (Master or Slave server), 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.
Premium
Internal
Rating:
Category:
Configure; Deploy; Install
Solution Id:
1113505
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.


Need More Help?

Create a technical support case if you need further support.