On the cisco, mode on sets etherchannel not LACP (802.3ad). All static port channels, that is, that are not running LACP, remain in this mode. If you attempt to change the channel mode to active or passive before enabling LACP, the device returns an error message. You enable LACP on each channel by configuring the interface in that channel for the channel mode as either active or passive. When an LACP attempts to negotiate with an interface in the on state, it does not receive any LACP packets and becomes an individual link with that interface; it does not join the LACP channel group.
Eric -----Original Message----- From: Jonathan Lassoff [mailto:[email protected]] Sent: Wednesday, March 13, 2013 9:16 PM To: Eric Krichbaum Cc: snort bsd; juniper-nsp Subject: Re: [j-nsp] 3750 and 4200 On Wed, Mar 13, 2013 at 6:36 PM, Eric Krichbaum <[email protected]> wrote: > More likely, it's the forced "on" mode which disables LACP. Try it > with mode active. Will JunOS show the ae as down, then? [channel-group N mode on] with IOS just enables portchanneling unconditionally. Wouldn't that, in conjunction with a JunOS without an "lacp" stanza under the ifd / interface stanza (lacp passive) work just fine? I've mostly only been doing JunOS-JunOS LACP lately, though I've done it quite a bit with Cisco-Cisco in the past. LACP is worth running on your links if it works, IMO. Maybe try setting active on the JunOS and Cisco sides? ! interface Fa1/0/9 channel-group 10 mode active ! set interface ae1 aggregated-ether-options lacp active _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
