No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


FusionCompute V100R003C00 Network Communication Failure After A VM NIC Is Deleted and then Added

Publication Date:  2014-06-09 Views:  91 Downloads:  0
Issue Description
After a user deletes a network interface card (NIC) from a Linux VM and then adds it to the VM on the FusionCompute portal, the user fails to ping the gateway after logging in to the VM.
Alarm Information
Handling Process
1. Log in to the VM using VNC and delete persistent-net.rules in the /etc/udev/rules.d directory.
If the VM runs a SUSE operating system, delete 70-persistent-net.rules.

2. Restart the VM. 
Root Cause
After a NIC deleted and then added on the FusionCompute portal, the name of the new NIC is eth0. However, the name of the NIC you queried in the VM is eth1. 

Therefore, the configuration file of NIC eth0 cannot take effect for the new NIC.