# ifup eth0

Device eth0 does not seem to be present, delaying initialisation

To Solve this :
Delete networking interface rules file so that it can be regenerated and
reboot your CentOS system.

# rm /etc/udev/rules.d/70-persistent-net.rules
# reboot
New Mac address has been generated:

# This file was automatically generated by the

/lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.

# PCI device 0x8086:0x100e (e1000)

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="08:00:27:fe:c1:03", ATTR{type}=="1",
KERNEL=="eth*", NAME="eth0"
Now edit /etc/sysconfig/network-scripts/ifcfg-eth0,
Add

new

HWADDR generated or

remove it

Remove UUID

line

Restart the networking service

# service network restart
Shutting down interface eth0:
OK ]

Shutting down loopback interface:

OK ]

Bringing up loopback interface:

OK ]

Bringing up interface eth0: Determining if ip address

192.168.1.99 is already in use for device eth0...

OK

# ifconfig
eth0

Link encap:Ethernet

HWaddr 08:00:27:FE:C1:03

inet addr:192.168.1.99
Mask:255.255.255.0

Bcast:xxxxxxxx

inet6 addr: fe80::a00:27ff:fefe:c103/64 Scope:Link

UP BROADCAST RUNNING MULTICAST

MTU:1500

Metric:1

RX packets:4400 errors:0 dropped:0 overruns:0 frame:0

TX packets:129 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:387597 (378.5 KiB)
Enjoy!

TX bytes:19567 (19.1 KiB)

Bringing up interface eth0: Device eth0 does not seem to be present, delaying initialization
[FAILED]

Una vez se tenga este mensaje tan claro se procede a realizar lo siguiente:
1.
[root@ftp
eth1

Listar

los
~]#

dispositivos
ls
lo

registrados
/sys/class/net
sit0

y como se podrn dar cuenta por ningn lado aparece eth0..... Esto ocurre
debido a que la direccin de la NIC cambi y por ende nuestro Linux genera
una nueva interfaz que para este efecto es eth1
2. Ahora se procede a editar el archivo de Red persistente de udev.
[root@ftp ~]# cat /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.
# PCI device 0x1022:0x2000 (pcnet32) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:0c:29:0f:94:93", ATTR{type}=="1", KERNEL=="eth*",
NAME="eth0"
# PCI device 0x1022:0x2000 (pcnet32)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:0c:29:93:48:14", ATTR{type}=="1", KERNEL=="eth*",
NAME="eth1"

2. Vamos a editar el archivo anterior, realizando los siguientes paso:

- Cambios la direccin fsica (ATTR{address}) de eth0 por la de eth1
- Borramos la entrada relacionada con eth1 (las ltimas 3 lineas)
- Despus de realizar este ajuste, el archivo debi quedar algo como esto:
[root@ftp ~]# less /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.
# PCI device 0x1022:0x2000 (pcnet32) (custom name provided by external
tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",

ATTR{address}=="00:0c:29:93:48:14", ATTR{type}=="1", KERNEL=="eth*",

NAME="eth0"

- Guardamos los cambio.

3. Realizar el cambio en el archivo de configuracin en el archivo ifcfg-eth0 en la etiqueta
de HWADDR y colocamos la que asignamos en el paso anterior (00:0c:29:93:48:14).
4. Con lo anterior, estamos solo a un paso. Por ltimo le aplicamos un reboot y
si todo sali bien cuando la VM suba ya tendremos RED.