Here's my setup (pardon the poorly done ASCII art):
[eth1:Astaro220: eth0]------[fa0/0:cisco2950:fa0/24]----.
'-------------------------[fa0/0:cisco2960:fa0/24]----'
|
|
[my computer]
so i have eth0 of my astaro jacked into fa0/0 of my first cisco (the 2950) and i have eth1 of my astaro jacked into fa0/0 of my second cisco (the 2960).. the 2960 and 2950 are crosslinked on their respective port fa0/24.
I go into the Link Aggregation window and check eth1 as the interface to LAG.. and I set eth0 as the link to convert.
then i enable the LAG.
... then i loose all connectivity on that subnet! When I look at the dashboard I have LAG0 (the LAG i created) such that the state is up but the link is down.
I can't figure out what, if anything, I am doing wrong. Any ideas??
Thanks!
greg.
PS. Here is the output from the dmesg log:
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
bonding: lag0: enslaving eth5 as a backup interface with a down link.
e100: eth6: e100_watchdog: link up, 100Mbps, full-duplex
bonding: lag0: enslaving eth6 as a backup interface with an up link.
bonding: lag0: link status definitely down for interface eth6, disabling it
e100: eth0: e100_watchdog: link down
e100: eth4: e100_watchdog: link down
e100: eth7: e100_watchdog: link down
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
e100: eth4: e100_watchdog: link up, 100Mbps, full-duplex
e100: eth7: e100_watchdog: link up, 100Mbps, full-duplex
bonding: lag0: Warning: No 802.3ad response from the link partner for any adapters in the bond
bonding: lag0: Warning: No 802.3ad response from the link partner for any adapters in the bond
bonding: lag0: Warning: No 802.3ad response from the link partner for any adapters in the bond
e100: eth5: e100_watchdog: link up, 100Mbps, full-duplex
bonding: lag0: link status definitely up for interface eth5.
net_enable_timestamp [ping]: netstamp_needed=1
net_disable_timestamp [swapper]: netstamp_needed=0
net_enable_timestamp [ping]: netstamp_needed=1
net_disable_timestamp [swapper]: netstamp_needed=0
bonding: lag0: Removing an active aggregator
bonding: lag0: Warning: No 802.3ad response from the link partner for any adapters in the bond
bonding: lag0: Removing an active aggregator
bonding: lag0: released all slaves
e100: eth5: e100_watchdog: link up, 100Mbps, full-duplex
e100: eth6: e100_watchdog: link up, 100Mbps, full-duplex
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
e100: eth5: e100_watchdog: link up, 100Mbps, full-duplex
bonding: lag0: enslaving eth5 as a backup interface with an up link.
e100: eth6: e100_watchdog: link up, 100Mbps, full-duplex
bonding: lag0: enslaving eth6 as a backup interface with an up link.
bonding: lag0: link status definitely down for interface eth6, disabling it
e100: eth0: e100_watchdog: link down
e100: eth4: e100_watchdog: link down
e100: eth7: e100_watchdog: link down
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
e100: eth4: e100_watchdog: link up, 100Mbps, full-duplex
e100: eth7: e100_watchdog: link up, 100Mbps, full-duplex
bonding: lag0: Removing an active aggregator
bonding: lag0: Warning: No 802.3ad response from the link partner for any adapters in the bond
bonding: lag0: Removing an active aggregator
bonding: lag0: released all slaves
e100: eth5: e100_watchdog: link up, 100Mbps, full-duplex
This thread was automatically locked due to age.
