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 ~]#
Que tipo de tarjeta de red
Que tipo de tarjeta de red es ...???
A mi me ha dado problemas ese driver tulip ...
bye
:)
gracias por sus aportes,
gracias por sus aportes, sigo con el problema de que cada rato se desactivan solitas las tarjetas de red eth1 y eth2 y no sube toca hacerlo manualmente cada rato, lo mismo con la interfaces virtuales
Las tarjetas de red que utilizo son:
cnet ambas son cnet
La maquina donde esta instalado centos es :
Procesador intel C2D E8400 3.0GHz 6MB L2 1333GHz
Maimboard intel DG33PR S775,DDR2 1333GHZ
MEMORIA MARVISION DDR2 2GB
cual sera el problema que ocasiona que se desactive cada rato gracias por su ayuda
si probaste bien con las
si probaste bien con las interfaces virtuales?? yo tengo levantado conesas y jamaz me ha dado problema salvo cuando se reinicia el equipo (osea nunca)
que driver usan esas
que driver usan esas tarjetas...???
para mi estas repitiendo en
para mi estas repitiendo en nombre de la interface
rw-r--r-- 3 root root 209 feb 19 23:32 ifcfg-1:1
-rw-r--r-- 3 root root 186 feb 19 23:32 ifcfg-eth1:1
dentro de los ficheros para mi estas repitiendo los nombres del dispositivos
Saludos
Vamos Ecuador, si se puede
gracias nino pero me puedes
gracias nino pero me puedes explicar mejor su observación:
te comento y lo raro es que hago lo mismo en otra maquina es decir en la misma intefaces virtuales y no tengo ningun problema que se me desctivan cada rato, mi pregunta es prodra ser problema del hardware del computador.
por el mismo esquema de configuracion tengo habilitado y no tengo ningun problema en otro servidor.
Prueba una por una..
Yo también te sugiero que agregues las subinterfaces una por una, así puedes ver cual archivo es el que te falla.
Mueve los archivos de las subinterfaces a otro lado y reinicia el servicio de red, ahí deberían levantarse solo las principales. Luego vuelves a poner el archivo correspondiente a eth1:1 y vuelves a reiniciar el servicio de red, si no da error y se levanta sigues el mismo procedimiento con las otras subinterfaces.
Si te sale un error nos muestras el error y el contenido del archivo que acabas de agregar.
Saludos,
----
Edwin Boza
about.me/edwinboza
Páginas