Centos configuration eth0 Prompt device does not seem to be present

Source: Internet
Author: User

Centos configuration eth0 prompt device does not seem to be present

I. failure Phenomena:

[Email protected] ~]# service network restart

S Hutting down loopback insterface:                                                          [   ok ]

Bringing up loopback insterface: [OK]

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

Workaround:

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

[[email protected] ~] # Reboot .....------.

[Email protected] ~]# service network restart

S Hutting down loopback insterface:                                                            [   ok  ]

B Ringing up loopback insterface:                                                                 [   ok  ]

B ringing up interface eth0: [OK]

[Email protected] ~]#

Two. Another approach

This is caused by the move of the CentOS system files in the virtual machine (Vmware), resulting in reconfiguration, the MAC address of the NIC has changed, input ifconfig-a, cannot find eth0

·······

Install a CentOS virtual machine, and another copy, boot after the network card does not start normally, error: Device eth0 does not seem to be present,
Delaying initialization

FIX: # Mv/etc/sysconfig/network-scripts/ifcfg-eth0
Sysconfig/network-scripts/ifcfg-eth1

Vim
Sysconfig/network-scripts/ifcfg-eth1

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


Can remove UUID, physical address

Then reboot the boot Nic and try

Three. A little deeper than the first

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] ~]# Vi/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] ~] #reboot

..................


This article is from the IT Network blog, so be sure to keep this source http://531572034.blog.51cto.com/4383413/1828044

Centos configuration eth0 Prompt device does not seem to be present

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.