Network card dropped from bond after restart
-
Problem description:
The network card in the bond is lost/dropped after the server is restarted.
Normal situation:

The network card drops from the bond after restarting:

Cause analysis:
There may be two reasons for this problem.Problem handling process:
1.Check the contents of the configuration file corresponding to the network card to see if DEVICE=eth0 is missingcat /etc/sysconfig/network-scripts/ifcfg-eth0
If it is missing, you need to add a new line DEVICE=eth0 to this configuration file, and then add the dropped network card from the new addition back to bond;echo "DEVICE=eth0" >> /etc/sysconfig/network-scripts/ifcfg-eth0 zs-nic-to-bond -a bond0 eth0Restart the server again to check that the network card in the bond group no longer drops.
systemctl restart network systemctl enable network- The NexaVM node system uses the network service. If NetworkManager is also running at the same time, the two will conflict, causing the network card to be lost after restarting;
Check the service running status:
systemctl status NetworkManager systemctl status network(The output shows that both services are in the running state)
If the NetworkManager service is running, you need to stop its service and disable it from starting automatically;systemctl stop NetworkManager systemctl disable NetworkManagerThen add the network card back to the bond group and restart the network network service to set it to start automatically;
zs-nic-to-bond -a bond0 eth0 systemctl restart network - The NexaVM node system uses the network service. If NetworkManager is also running at the same time, the two will conflict, causing the network card to be lost after restarting;
-
undefined nexus marked this topic as a regular topic