LACP isn't a requirement (and as we can see it is not configured on the foundry), so if I remove the LACP line and set the channel mode to 'on' instead of 'active' would that work sufficiently? I could have sworn I had it working in the lab without LACP...
If I can make the changes on the Cisco that would be best (disable LACP, ect), because the Foundry is at a remote site and I do not have direct console access. For now I have the 2nd link shut on the Cisco side and traffic is at least no longer being interrupted. -- Randy ---------- Original Message ----------- From: Eric Helm <[email protected]> To: [email protected] Sent: Thu, 28 Jan 2010 15:01:23 -0600 Subject: Re: [f-nsp] (no subject) > You have Dynamic (LACP) configured on the Cisco side and Static trunk > configured on the Foundry side. You should configure LACP on the Foundry > as well. Do not use the "trunk ethe 1 to 2" command to configure LACP: > > int eth 1 to 2 > link-aggregate passive > > /Eric > _______________________________________________ > foundry-nsp mailing list > [email protected] > http://puck.nether.net/mailman/listinfo/foundry-nsp ------- End of Original Message ------- _______________________________________________ foundry-nsp mailing list [email protected] http://puck.nether.net/mailman/listinfo/foundry-nsp
