Help Center/ Storage Disaster Recovery Service/ FAQs/ Synchronous Replication (for Installed Base Operations)/ What Can I Do When the EIP Cannot Be Pinged After I Perform a Switchover for a Protection Group Containing a SUSE Server?
Updated on 2024-05-07 GMT+08:00
View PDF
Share

What Can I Do When the EIP Cannot Be Pinged After I Perform a Switchover for a Protection Group Containing a SUSE Server?

Symptom

The production site server in a protection group runs the SUSE OS. After users enable protection and perform a switchover for the protection group, the EIP of the server cannot be pinged.

Root Cause

After the switchover, the server NIC name may already change. If the NIC has an EIP bound, the EIP cannot be pinged.

Handling Method

After the switchover, delete the /etc/udev/rules.d/70-persistent-net.rules file on the DR site server and then restart it. The procedure is as follows.

  1. Log in to the DR site server.

    1. Log in to the management console and click Elastic Cloud Server under Computing.
    2. In the server list, select the DR site server.
    3. Locate the row containing the server and click Remote Login in the Operation column.

      Log in to the server as prompted.

  2. Run the following command to delete the file:

    rm /etc/udev/rules.d/70-persistent-net.rules

  3. Run the following command to restart the DR site server:

    reboot