error al levantar ip virtuales en CENTOS

Forums: 

Tengo un servidor CENTOS con dos tarjetas externas eth1 LAN eth2 WAN

me puse a crear ip virtuales en eth1 con el siguientes esquema:
eth1 LAN0 197.200.100.1
eth1:1 LAN1 197.200.2.1
eth1:2 LAN2 197.200.3.1
eth1:3 LAN3 197.200.4.1
eth1:4 LAN4 197.200.5.1
eth1:6 LAN5 197.200.6.1

este proceso lo hice en el terminal cp ifcfg-eth1 ifcfg-eth1:0 y luego modificando los parametros en el archvio ifcfg-eth1:0

al momento se realizar un service network restart me sale el siguiente error:

[root@localhost ~]# service network reload
Interrupción de la interfaz eth1: [ OK ]
Interrupción de la interfaz eth2: [ OK ]
Interrupción de la interfaz de loopback: [ OK ]
Activación de la interfaz de loopback: [ OK ]
Activando interfaz eth1: RTNETLINK answers: File exists
Error al añadir la dirección 197.200.100.1 para eth1.
[ OK ]
Activando interfaz eth2: [ OK ]
[root@localhost ~]#

cual seria el error

ademas se desactiva la tarjetas de red en cada instante

gracias a un amigo me dijoq que hiciera un dmesg
este el resultado de eso:
En el terminal : dmesg
0000:06:00.0: tulip_stop_rxtx() failed
eth1: Setting full-duplex based on MII#1 link partner capability of 4de1.
0000:06:01.0: tulip_stop_rxtx() failed
eth2: Setting full-duplex based on MII#1 link partner capability of 45e1.
eth1: no IPv6 routers present
0000:06:00.0: tulip_stop_rxtx() failed
0000:06:01.0: tulip_stop_rxtx() failed
ADDRCONF(NETDEV_UP): __tmp1778408948: link is not ready
0000:06:00.0: tulip_stop_rxtx() failed
eth1: Setting full-duplex based on MII#1 link partner capability of 4de1.
0000:06:01.0: tulip_stop_rxtx() failed
eth2: Setting full-duplex based on MII#1 link partner capability of 45e1.
eth1: no IPv6 routers present
0000:06:00.0: tulip_stop_rxtx() failed
0000:06:01.0: tulip_stop_rxtx() failed
ADDRCONF(NETDEV_UP): __tmp1778408948: link is not ready
0000:06:00.0: tulip_stop_rxtx() failed
eth1: Setting full-duplex based on MII#1 link partner capability of 4de1.
0000:06:01.0: tulip_stop_rxtx() failed
eth2: Setting full-duplex based on MII#1 link partner capability of 45e1.
eth1: no IPv6 routers present
0000:06:00.0: tulip_stop_rxtx() failed
0000:06:01.0: tulip_stop_rxtx() failed
ADDRCONF(NETDEV_UP): __tmp1778408948: link is not ready
0000:06:00.0: tulip_stop_rxtx() failed
eth1: Setting full-duplex based on MII#1 link partner capability of 4de1.
0000:06:01.0: tulip_stop_rxtx() failed
eth2: Setting full-duplex based on MII#1 link partner capability of 45e1.
eth1: no IPv6 routers present
0000:06:00.0: tulip_stop_rxtx() failed
0000:06:01.0: tulip_stop_rxtx() failed
ADDRCONF(NETDEV_UP): __tmp1778408948: link is not ready
0000:06:00.0: tulip_stop_rxtx() failed
eth1: Setting full-duplex based on MII#1 link partner capability of 4de1.
0000:06:01.0: tulip_stop_rxtx() failed
eth2: Setting full-duplex based on MII#1 link partner capability of 45e1.
eth1: no IPv6 routers present
0000:06:00.0: tulip_stop_rxtx() failed
0000:06:01.0: tulip_stop_rxtx() failed
ADDRCONF(NETDEV_UP): __tmp1778408948: link is not ready
0000:06:00.0: tulip_stop_rxtx() failed
eth1: Setting full-duplex based on MII#1 link partner capability of 4de1.
0000:06:01.0: tulip_stop_rxtx() failed
eth2: Setting full-duplex based on MII#1 link partner capability of 45e1.
eth1: no IPv6 routers present
0000:06:00.0: tulip_stop_rxtx() failed
0000:06:01.0: tulip_stop_rxtx() failed
ADDRCONF(NETDEV_UP): __tmp1778408948: link is not ready
0000:06:00.0: tulip_stop_rxtx() failed
eth1: Setting full-duplex based on MII#1 link partner capability of 4de1.
0000:06:01.0: tulip_stop_rxtx() failed
eth2: Setting full-duplex based on MII#1 link partner capability of 45e1.
eth1: no IPv6 routers present
0000:06:00.0: tulip_stop_rxtx() failed
0000:06:01.0: tulip_stop_rxtx() failed
ADDRCONF(NETDEV_UP): __tmp1778408948: link is not ready
0000:06:00.0: tulip_stop_rxtx() failed
eth1: Setting full-duplex based on MII#1 link partner capability of 4de1.
0000:06:01.0: tulip_stop_rxtx() failed
eth2: Setting full-duplex based on MII#1 link partner capability of 45e1.
eth1: no IPv6 routers present
0000:06:00.0: tulip_stop_rxtx() failed
0000:06:01.0: tulip_stop_rxtx() failed
ADDRCONF(NETDEV_UP): __tmp1778408948: link is not ready
0000:06:00.0: tulip_stop_rxtx() failed
eth1: Setting full-duplex based on MII#1 link partner capability of 4de1.
0000:06:01.0: tulip_stop_rxtx() failed
eth2: Setting full-duplex based on MII#1 link partner capability of 45e1.
eth1: no IPv6 routers present
0000:06:00.0: tulip_stop_rxtx() failed
0000:06:01.0: tulip_stop_rxtx() failed
ADDRCONF(NETDEV_UP): __tmp1778408948: link is not ready
0000:06:00.0: tulip_stop_rxtx() failed
eth1: Setting full-duplex based on MII#1 link partner capability of 4de1.
0000:06:01.0: tulip_stop_rxtx() failed
eth2: Setting full-duplex based on MII#1 link partner capability of 45e1.
eth1: no IPv6 routers present
0000:06:00.0: tulip_stop_rxtx() failed
0000:06:01.0: tulip_stop_rxtx() failed
ADDRCONF(NETDEV_UP): __tmp1778408948: link is not ready
0000:06:00.0: tulip_stop_rxtx() failed
eth1: Setting full-duplex based on MII#1 link partner capability of 4de1.
0000:06:01.0: tulip_stop_rxtx() failed
eth2: Setting full-duplex based on MII#1 link partner capability of 45e1.
eth1: no IPv6 routers present
0000:06:00.0: tulip_stop_rxtx() failed
0000:06:01.0: tulip_stop_rxtx() failed
ADDRCONF(NETDEV_UP): __tmp1778408948: link is not ready
0000:06:00.0: tulip_stop_rxtx() failed
eth1: Setting full-duplex based on MII#1 link partner capability of 4de1.
0000:06:01.0: tulip_stop_rxtx() failed
eth2: Setting full-duplex based on MII#1 link partner capability of 45e1.
eth1: no IPv6 routers present
0000:06:00.0: tulip_stop_rxtx() failed
0000:06:01.0: tulip_stop_rxtx() failed
ADDRCONF(NETDEV_UP): __tmp1778408948: link is not ready
0000:06:00.0: tulip_stop_rxtx() failed
eth1: Setting full-duplex based on MII#1 link partner capability of 4de1.
0000:06:01.0: tulip_stop_rxtx() failed
eth2: Setting full-duplex based on MII#1 link partner capability of 45e1.
eth1: no IPv6 routers present
0000:06:00.0: tulip_stop_rxtx() failed
0000:06:01.0: tulip_stop_rxtx() failed
ADDRCONF(NETDEV_UP): __tmp1778408948: link is not ready
0000:06:00.0: tulip_stop_rxtx() failed
eth1: Setting full-duplex based on MII#1 link partner capability of 4de1.
0000:06:01.0: tulip_stop_rxtx() failed
eth2: Setting full-duplex based on MII#1 link partner capability of 45e1.
eth1: no IPv6 routers present
0000:06:00.0: tulip_stop_rxtx() failed
0000:06:01.0: tulip_stop_rxtx() failed
ADDRCONF(NETDEV_UP): __tmp1778408948: link is not ready
0000:06:00.0: tulip_stop_rxtx() failed
eth1: Setting full-duplex based on MII#1 link partner capability of 4de1.
0000:06:01.0: tulip_stop_rxtx() failed
eth2: Setting full-duplex based on MII#1 link partner capability of 45e1.
eth1: no IPv6 routers present
0000:06:00.0: tulip_stop_rxtx() failed
0000:06:01.0: tulip_stop_rxtx() failed
ADDRCONF(NETDEV_UP): __tmp1778408948: link is not ready
0000:06:00.0: tulip_stop_rxtx() failed
eth1: Setting full-duplex based on MII#1 link partner capability of 4de1.
0000:06:01.0: tulip_stop_rxtx() failed
eth2: Setting full-duplex based on MII#1 link partner capability of 45e1.
eth1: no IPv6 routers present
0000:06:00.0: tulip_stop_rxtx() failed
0000:06:01.0: tulip_stop_rxtx() failed
ADDRCONF(NETDEV_UP): __tmp1778408948: link is not ready
0000:06:00.0: tulip_stop_rxtx() failed
eth1: Setting full-duplex based on MII#1 link partner capability of 4de1.
0000:06:01.0: tulip_stop_rxtx() failed
eth2: Setting full-duplex based on MII#1 link partner capability of 45e1.
eth1: no IPv6 routers present
0000:06:00.0: tulip_stop_rxtx() failed
0000:06:01.0: tulip_stop_rxtx() failed
ADDRCONF(NETDEV_UP): __tmp1778408948: link is not ready
0000:06:00.0: tulip_stop_rxtx() failed
eth1: Setting full-duplex based on MII#1 link partner capability of 4de1.
0000:06:01.0: tulip_stop_rxtx() failed
eth2: Setting full-duplex based on MII#1 link partner capability of 45e1.
eth1: no IPv6 routers present
0000:06:00.0: tulip_stop_rxtx() failed
0000:06:01.0: tulip_stop_rxtx() failed
ADDRCONF(NETDEV_UP): __tmp1778408948: link is not ready
0000:06:00.0: tulip_stop_rxtx() failed
eth1: Setting full-duplex based on MII#1 link partner capability of 4de1.
0000:06:01.0: tulip_stop_rxtx() failed
eth2: Setting full-duplex based on MII#1 link partner capability of 45e1.
eth1: no IPv6 routers present
0000:06:00.0: tulip_stop_rxtx() failed
0000:06:01.0: tulip_stop_rxtx() failed
ADDRCONF(NETDEV_UP): __tmp1778408948: link is not ready
0000:06:00.0: tulip_stop_rxtx() failed
eth1: Setting full-duplex based on MII#1 link partner capability of 4de1.
0000:06:01.0: tulip_stop_rxtx() failed
eth2: Setting full-duplex based on MII#1 link partner capability of 45e1.
eth1: no IPv6 routers present
0000:06:00.0: tulip_stop_rxtx() failed
0000:06:01.0: tulip_stop_rxtx() failed
ADDRCONF(NETDEV_UP): __tmp1778408948: link is not ready
0000:06:00.0: tulip_stop_rxtx() failed
eth1: Setting full-duplex based on MII#1 link partner capability of 4de1.
0000:06:01.0: tulip_stop_rxtx() failed
eth2: Setting full-duplex based on MII#1 link partner capability of 45e1.
eth1: no IPv6 routers present
0000:06:00.0: tulip_stop_rxtx() failed
0000:06:01.0: tulip_stop_rxtx() failed
ADDRCONF(NETDEV_UP): __tmp1778408948: link is not ready
0000:06:00.0: tulip_stop_rxtx() failed
eth1: Setting full-duplex based on MII#1 link partner capability of 4de1.
0000:06:01.0: tulip_stop_rxtx() failed
eth2: Setting full-duplex based on MII#1 link partner capability of 45e1.
eth1: no IPv6 routers present
0000:06:00.0: tulip_stop_rxtx() failed
0000:06:01.0: tulip_stop_rxtx() failed
ADDRCONF(NETDEV_UP): __tmp1778408948: link is not ready
0000:06:00.0: tulip_stop_rxtx() failed
eth1: Setting full-duplex based on MII#1 link partner capability of 4de1.
0000:06:01.0: tulip_stop_rxtx() failed
eth2: Setting full-duplex based on MII#1 link partner capability of 45e1.
eth1: no IPv6 routers present
0000:06:00.0: tulip_stop_rxtx() failed
0000:06:01.0: tulip_stop_rxtx() failed
ADDRCONF(NETDEV_UP): __tmp1778408948: link is not ready
0000:06:00.0: tulip_stop_rxtx() failed
eth1: Setting full-duplex based on MII#1 link partner capability of 4de1.
0000:06:01.0: tulip_stop_rxtx() failed
eth2: Setting full-duplex based on MII#1 link partner capability of 45e1.
eth1: no IPv6 routers present
0000:06:00.0: tulip_stop_rxtx() failed
0000:06:01.0: tulip_stop_rxtx() failed
ADDRCONF(NETDEV_UP): __tmp1778408948: link is not ready
ADDRCONF(NETDEV_UP): eth1: link is not ready
ADDRCONF(NETDEV_UP): eth2: link is not ready
0000:06:00.0: tulip_stop_rxtx() failed
0000:06:01.0: tulip_stop_rxtx() failed
ADDRCONF(NETDEV_UP): __tmp1778408948: link is not ready
ADDRCONF(NETDEV_UP): eth1: link is not ready
ADDRCONF(NETDEV_UP): eth2: link is not ready
0000:06:00.0: tulip_stop_rxtx() failed
0000:06:01.0: tulip_stop_rxtx() failed
ADDRCONF(NETDEV_UP): __tmp1778408948: link is not ready
ADDRCONF(NETDEV_UP): eth1: link is not ready
ADDRCONF(NETDEV_UP): eth2: link is not ready
0000:06:00.0: tulip_stop_rxtx() failed
0000:06:01.0: tulip_stop_rxtx() failed
ADDRCONF(NETDEV_UP): __tmp1778408948: link is not ready
ADDRCONF(NETDEV_UP): eth1: link is not ready
ADDRCONF(NETDEV_UP): eth2: link is not ready
0000:06:00.0: tulip_stop_rxtx() failed
eth1: Setting full-duplex based on MII#1 link partner capability of 4de1.
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
0000:06:01.0: tulip_stop_rxtx() failed
eth2: Setting full-duplex based on MII#1 link partner capability of 45e1.
ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
eth2: no IPv6 routers present
eth1: no IPv6 routers present
ip_tables: (C) 2000-2006 Netfilter Core Team
Netfilter messages via NETLINK v0.30.
ip_conntrack version 2.4 (8192 buckets, 65536 max) - 228 bytes per conntrack
Removing netfilter NETLINK layer.
eth2: no IPv6 routers present
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[root@localhost ~]#

Según parece pusiste toda la

Imagen de acl

Según parece pusiste toda la configuracion en ifcfg-eth1:0, lo cual no es correcto. Debes tener un archivo ifcfg-eth1:x por cada x de tus LANes.

Prueba primero con una sola y cuando te funcione, vas agregando de a pocos.

cuando le des a un service

Imagen de falcom

cuando le des a un service network restart primero asegurate de desconectar los cables de red, parece q es un bug de centos/RH al cambiar de ips o al agregar una nic virtual no los detecta

Creo es el parametro que

Imagen de damage

Creo es el parametro que tiene declarado en DEVICE dentro del ifcfg quizas no lo modifico y esta como eth1 en las otras virtuales.

TYPE=Ethernet
DEVICE=eth1:0
BOOTPROTO=none

TYPE=Ethernet
DEVICE=eth1:1
BOOTPROTO=none


Saludos.

gracias por sus aportes he

gracias por sus aportes he verificado el comentario de DEVICE que me dice damage y todo esta correcto:

# ADMtek NC100 Network Everywhere Fast Ethernet 10/100
DEVICE=eth0:1
BOOTPROTO=none
HWADDR=00:08:A1:C0:2F:40
ONBOOT=yes
TYPE=Ethernet
USERCTL=no
IPV6INIT=no
PEERDNS=yes
NETMASK=255.255.255.0
IPADDR=172.17.2.200
GATEWAY=192.168.15.254

+++++++++++++++++

# ADMtek NC100 Network Everywhere Fast Ethernet 10/100
DEVICE=eth0:2
BOOTPROTO=none
HWADDR=00:08:A1:C0:2F:40
ONBOOT=yes
TYPE=Ethernet
USERCTL=no
IPV6INIT=no
PEERDNS=yes
NETMASK=255.255.255.0
IPADDR=172.17.3.200
GATEWAY=192.168.15.254

++++++++++++++++++++++
esta todo correcto:
el momento de hacer un service restart network

service network restart
Interrupción de la interfaz eth0: [ OK ]
Interrupción de la interfaz de loopback: [ OK ]
Deshabilitando el reenvio de paquetes IPv4: net.ipv4.ip_forward = 0
[ OK ]
Activación de la interfaz de loopback: [ OK ]
Activando interfaz eth0: SIOCADDRT: La red es inaccesible
SIOCADDRT: La red es inaccesible
SIOCADDRT: La red es inaccesible
[ OK ]
a que se refiere el mensaje de SIOCADDRT: la red es inacesible

gracias de antemano por los aportes

Estás repitiendo el GATEWAY

Imagen de acl

Estás repitiendo el GATEWAY en cada interfaz, y eso es incorrecto. Elimina eso. El mensaje de la red es inaccesible quiere decir que has intentado agregar una ruta a la tabla de enrutamiento cuyo gateway no puede alcanzar (porque no existe una entrada que te permita llegar a él en la tabla).

gracias ACL segui tus pasos

gracias ACL segui tus pasos quite los gateway a todos los eth1:X pero sigo con el problema despues de eso hice un service network restart y este el resultado.

[root@localhost networking]# cd devices
[root@localhost devices]# ls
ifcfg-1:1 ifcfg-eth1:0 ifcfg-eth1:2 ifcfg-eth1:4
ifcfg-eth1 ifcfg-eth1:1 ifcfg-eth1:3 ifcfg-eth2
[root@localhost devices]# ls -l
total 64
-rw-r--r-- 3 root root 209 feb 19 23:32 ifcfg-1:1
-rw-r--r-- 3 root root 233 feb 19 23:32 ifcfg-eth1
-rw-r--r-- 3 root root 186 feb 19 23:32 ifcfg-eth1:0
-rw-r--r-- 3 root root 186 feb 19 23:32 ifcfg-eth1:1
-rw-r--r-- 3 root root 186 feb 19 23:32 ifcfg-eth1:2
-rw-r--r-- 3 root root 186 feb 19 23:32 ifcfg-eth1:3
-rw-r--r-- 3 root root 186 feb 19 23:32 ifcfg-eth1:4
-rw-r--r-- 3 root root 236 feb 19 23:32 ifcfg-eth2
[root@localhost devices]# vi ifcfg-eth1:0
[root@localhost devices]# vi ifcfg-eth1:1
[root@localhost devices]# vi ifcfg-eth1:2
[root@localhost devices]# vi ifcfg-eth1:3
[root@localhost devices]# vi ifcfg-eth1:4
[root@localhost devices]# service network restart
Interrupción de la interfaz eth1: [ OK ]
Interrupción de la interfaz eth2: [ OK ]
Interrupción de la interfaz de loopback: [ OK ]
Activación de la interfaz de loopback: [ OK ]
Activando interfaz eth1: RTNETLINK answers: File exists
Error al añadir la dirección 197.200.100.1 para eth1.

[ OK ]
Activando interfaz eth2:

Por que me sale ese mensaje de

no sera que te equivocaste

Imagen de nino1511

no sera que te equivocaste dentro del archivo
estas colocando una ip duplicada o el nombre del fichero no coincide, mira lo que pusiste aqui:
root@localhost networking]# cd devices
[root@localhost devices]# ls
ifcfg-1:1 ifcfg-eth1:0 ifcfg-eth1:2 ifcfg-eth1:4
ifcfg-eth1 ifcfg-eth1:1 ifcfg-eth1:3 ifcfg-eth2

ubicas ifcfg-1:1, dentro del fichero esta también asi?

yo te aconsejo que hagas esto service network stop
crees una a una las redes virtuales
y hagas un ifconfig
y dentro de esta ruta
/etc/sysconfig/network-scripts
que esten las redes virtuales y que coincidan con las que quieres crear
otra cosa no es que en tu script estas intentando crear una ip duplicada

Saludos

Vamos Ecuador, si se puede

y cuando reinicio con

y cuando reinicio con service network restart

solo se me vuelvo a activar la eth1 y la eth2 las eth1:X viruales no se activan

haciendo un ifconfig.
ifconfig
__tmp1036202298 Link encap:Ethernet HWaddr 00:1C:C0:23:39:DE
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:42277 errors:0 dropped:0 overruns:0 frame:0
TX packets:43523 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:20298242 (19.3 MiB) TX bytes:6473238 (6.1 MiB)
Memory:90380000-903a0000

eth1 Link encap:Ethernet HWaddr 00:08:A1:C0:3B:06
inet addr:197.200.100.1 Bcast:197.200.100.255 Mask:255.255.255.0
inet6 addr: fe80::208:a1ff:fec0:3b06/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:99734 errors:0 dropped:0 overruns:0 frame:0
TX packets:31154 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:10078718 (9.6 MiB) TX bytes:18118145 (17.2 MiB)
Interrupt:11 Base address:0x6c00

eth2 Link encap:Ethernet HWaddr 00:08:A1:C0:3B:18
inet addr:216.236.108.27 Bcast:216.236.108.31 Mask:255.255.255.248
inet6 addr: fe80::208:a1ff:fec0:3b18/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:42277 errors:0 dropped:0 overruns:0 frame:0
TX packets:43525 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:20298242 (19.3 MiB) TX bytes:6473562 (6.1 MiB)
Interrupt:10 Base address:0x8800

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1244 errors:0 dropped:0 overruns:0 frame:0
TX packets:1244 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2523120 (2.4 MiB) TX bytes:2523120 (2.4 MiB)

tengo solo esto
me toca subirle manualmente.

Páginas