Nic startup failure caused by Linux cloning multiple solutions

Failure phenomena:

Recently cloned several Linux systems in the company test environment, after rebooting, the NIC Eth0 was missing.

So check the network card configuration, finally think of the following solutions, network card startup information:

650) this.width=650; "Src=" https://s3.51cto.com/wyfs02/M00/95/49/wKiom1kTzP-xnbOEAAAahswJVkk337.png-wh_500x0-wm_ 3-wmp_4-s_2254268613.png "title=" 1.png "alt=" Wkiom1ktzp-xnboeaaaahswjvkk337.png-wh_50 "/>

[Email protected] ~]# service network restart

Shutting down loopback insterface: [OK]

Bringing up loopback insterface: [OK]

Bringing up interface Eth0:device eth0 does no seem to be present,delaying initialization. [FAILED]

Method One:

[Email protected] ~]# Rm-rf/etc/udev/rules.d/70-persistent-net.rules

[[Email protected] ~]# Init 6

[Email protected] ~]# service network restart

Shutting down loopback insterface: [OK]

Bringing up loopback insterface: [OK]

Bringing Up interface eth0: [OK]

Method Two:

This is due to the fact that the files for the CentOS system are moved in the virtual machine (Vmware)

Cause reconfiguration, the MAC address of the NIC has changed, input ifconfig-a, cannot find eth0

Install a CentOS virtual machine, another copy, the network card will not start properly after booting

Error:

Device eth0 does not seem to be present,
Delaying initialization

Solve:

[Email protected] ~]# CD /etc/sysconfig/network-scripts/

[email protected] ~]# MV Ifcfg-eth0 ifcfg-eth1

[email protected] ~]# vim sysconfig/network-scripts/ifcfg-eth1

Modify Device= "Eth0"
For device= "Eth1"

[Email protected] ~]# service network restart

Method Three:

Operation before the failure:

The Dell Blade is CentOS6.3 operating system, the NIC identifies the EM1 and EM2, because the work requires a slot adjustment, and the blade is started

Failure phenomena:

After starting the network is not through, through the Idrac login route to see the default route is normal;

Restart Network Service:

[Email protected] ~]# service network restart

shutting down loopback insterface: [OK]Bringing up loopback insterface: [OK]bringing up interface Em1:device EM1 does no seem to be present,delaying initialization. [FAILED]

Analyze problems and resolve:

Before we mentioned the 70-persistent-net.rules file in other articles, we looked at:

[Email protected] ~]# Vim/etc/udev/rules.d/70-persistent-net.rules

# This file is automatically generated by The/lib/udev/write_net_rules # program, run by the persistent-net-generator.ru Les rules file. # # can modify it, as long as you keep each rule on a single # line, and the change is only the value of the Name= key.

# PCI Device 0x14e4:0x163a (BNX2) subsystem== "NET", action== "Add", drivers== "? *", attr{address}== "24:b6:fd:ab:76:1e", attr{type}== "1", kernel== "eth*", name= "eth1"

# PCI Device 0x14e4:0x163a (BNX2) subsystem== "NET", action== "Add", drivers== "? *", attr{address}== "24:b6:fd:ab:76:1c", attr{type}== "1", kernel== "eth*", name= "eth0"

The name is found to be incorrect, in turn the above red font eth0 changed to Em1,eth1 to EM2;

* Remember: The network card number is determined by the size of the MAC address, Mac smaller network card number;

As follows:

# PCI Device 0x14e4:0x163a (BNX2)

subsystem== "NET", action== "Add", drivers== "? *", attr{address}== "24:b6:fd:ab:76:1e", attr{type}== "1", kernel== "eth*" , name= "EM2"

# PCI Device 0x14e4:0x163a (BNX2) subsystem== "NET", action== "Add", drivers== "? *", attr{address}== "24:b6:fd:ab:76:1c", attr{type}== "1", kernel== "eth*", name= "Em1"

Save Exit ~!

[[Email protected] ~]# Init 6

Problem Solving!

Nic startup failure caused by Linux cloning multiple solutions