Simple Link Agregation no longer work :(

Seems Migrating existing interface with not used interface to create a new aggregation no longer work..

I've initially eth2 only active for web admin, then creating a new agregation using existing eth2 with eth3 creates lag0 fine but nothing is working [[:(]]

I can't connect to the webadmin and checking on the console it shows only eth3 and lag0 (lag0 with the right ip but no eth2 is up [[:(]] and if trying to ifconfig eth2 up does not help

and if I ifconfig lag0 down and ifconfig eth2 192.168.9.251 netmask 255.255.255.0 it is working again [:)]

thx

Parents

0 BuBU over 17 years ago

this still there into 7.190 !!!

initially all is working, I can access to the astaro webadmin, and console is like this (no lag setup, no default route but this is initial setup):

eth2 is the local webadmin iface:

then after updating to have lag=eth2+eth3 I have this asg ui:

then on the console:

but I'm not able to log and so...

if I do ethtool eth2 I see no link, then ifconfig eth2 up make link up but this still does not work ! (eth3 is also up link)
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
$_alex\$

0 _alex\ over 17 years ago in reply to BuBU

hey

do you have a link on the lag0 interface?

i just tried to reproduce your problem, but in my case it works fine.
i take a clean installation and set up eth1 as administrative interface. no other inferfaces defined. then i joined eth1 and eth2 to a link aggregation group. it works fine. is this the way you did?

/alex
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 BuBU over 17 years ago in reply to _alex\

Link detected lag0: no for ethtool lag0 [:(]

whereas link yes for both interface into the lag (eth2 and eth3)
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 BuBU over 17 years ago in reply to BuBU

and here is the bonding:
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 BuBU over 17 years ago in reply to BuBU

and here is the bonding:
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

0 BuBU over 17 years ago in reply to BuBU
and I just did:

ifconfig lag0 down
rmmod bonding0
ifconfig eth2 192.168.9.251 netmask 255.255.255.0

and the interface is working again [:(]
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

0 BuBU over 17 years ago in reply to BuBU

here is an extract from my dmesg:


eth0: link up, 100Mbps, full-duplex, lpa 0x05E1

eth1: link up, 100Mbps, full-duplex, lpa 0x05E1

eth2: link up, 100Mbps, full-duplex, lpa 0x05E1

SCSI subsystem initialized

Initializing USB Mass Storage driver...

usbcore: registered new driver usb-storage

USB Mass Storage support registered.

Ethernet Channel Bonding Driver: v3.0.1 (January 9, 2006)

bonding: Warning: miimon must be specified, otherwise bonding will not detect link failure, speed and duplex which are essential for 802.3ad operation

Forcing miimon to 100msec

bonding: MII link monitoring set to 100 ms

eth3: link up, 100Mbps, full-duplex, lpa 0x05E1

bonding: lag0: enslaving eth3 as a backup interface with an up link.

eth2: link up, 100Mbps, full-duplex, lpa 0x05E1

bonding: lag0: enslaving eth2 as a backup interface with an up link.