thanks all for replies. both ends (physical are up now, with no lacp. as simple as just rebooted cisco switch.
really lacp isn't my concern at this moment. ________________________________ From: snort bsd <[email protected]> To: Jonathan Lassoff <[email protected]>; Eric Krichbaum <[email protected]> Cc: juniper-nsp <[email protected]> Sent: Thursday, 14 March 2013 10:16 AM Subject: Re: [j-nsp] 3750 and 4200 thanks. i don't think lacp is required for bundle links to work. i had done bundle links between cisco to cisco, juniper to juniper without lacp. i tried to avoid confusion of lacp between two switches before i know for sure two sides of links are working together. _dave ________________________________ From: Jonathan Lassoff <[email protected]> To: Eric Krichbaum <[email protected]> Cc: snort bsd <[email protected]>; juniper-nsp <[email protected]> Sent: Wednesday, 13 March 2013 10:15 PM 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 _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
