Hello Paul and mtinka I´ve been reading that the load balancing in the bundle (balancing between physical interfaces in the same bundle) may be achieved using different criterias like source or destination IP ... but it seems is a global configurarion and dont understand why
do you have experience configuring load balancing schemes ? any hint would help Thanks a lot Alexi On Sun, Oct 25, 2009 at 4:41 PM, Paul Stewart <[email protected]> wrote: > Thanks - I didn't realize til after that the docs were for e-series. My > question was more geared on MX side of things. > > Appreciate it.. > > Paul > > > -----Original Message----- > From: Mark Tinka [mailto:[email protected]] > Sent: October 25, 2009 1:02 PM > To: [email protected] > Cc: Paul Stewart > Subject: Re: [j-nsp] 802.3ad Question > > On Sunday 25 October 2009 10:23:51 pm Paul Stewart wrote: > > > Just a quick question regarding 802.3ad... > > Not to be pedantic, but turns out it's now 802.1AX :-). > > > Is there a limit on number of members in the LAG bundle? > > I notice your reference was to a Juniper ERX platform. I can't tell you > much > here as I haven't worked with these before. > > But if you're looking at JUNOS-based routers, on the M120, M320, MX-series > and all T-series routing platforms, you can have up to 16 members per LAG > bundle. > > Chassis' not mentioned above will only support 8 members per bundle. > > Platforms can have up to 128 individual bundles, but you'll probably run > out > of ports before you get that far :-). > > > Does it matter if it’s Juniper à Cisco interconnect? > > LACP is the common denominator. > > Cheers, > > Mark. > > _______________________________________________ > 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
