Case Description: When the actual production environment, the server board is hung, the manufacturer changed a piece of the same model board, the network card is onboard, so the motherboard is equal to the NIC also changed. Then the problem comes and the NIC is all messed up. The NIC does not come up. Now I don't know what the reason is.
Analysis Process: Since the motherboard has been changed, but also the same model of the motherboard, drive problems can be excluded. The motherboard has4block NIC. Sequentially isEth0,eth1,eth2,eth3. Change the motherboard, withIfconfig–aCheck out more than a few network cards out of theEth4,eth5,eth6,eth7. However, in the configuration directory (/etc/sysconfig/network-scripts/), onlyEth0,eth1,eth2,eth3. Originally only usedeth2as a business network port,The configuration is also,but it's stillPingnot pass. The network card light is not bright, and then I think about it.Ifupand theIfdown,to view the port, the originaleth2Become aEth5, the solution is not to be baffled. Later Gao pointed, said try to clear the network card cache. And then it really was this cache prank.
The following commands are attached:
The first thing to see is the network card command
Ifconfig–a|more
Disabling and enabling network card commands
Ifup eth2 Ifdown eth2
Modify the NIC configuration.
Vi/etc/sysconfig/network-scripts/eth2
Configure Restart Network Service
Service Network Restart
5) In addition to the network card cache file. It's a good idea to back up before deleting.
Delete /etc/udev/rules.d/60-net.rules This file, restart OS just OK up.
Note: 60-net.rules On different systems The naming is not the same, roughly " Digital -*-net.rules " It's like this.
After replacing the motherboard, the network card cannot be used. A case of------Linux Clear network card cache