All- You are correct about ECMP, I encountered this 12+ months ago and forgot that specific details. Mark said he put the whole AE bundle into per packet mode [on a short LAN hop], which can also cause reordering [not just the LSP] if used incorrectly.
Yes, I've specifically disabled control word. For us, disabling control word avoid LSP contents being sticky to a single LAG member. It worked for us, in that it solved a congestion issue carrying a high bandwidth LSP mixed with internet traffic on a two link bundle. We are 100% Trio forwarding shop and avoid L3 ECMP [LACP only, with links having essentially the same latency characteristics]. YMMV, as I've been strongly reminded. -Michael > -----Original Message----- > From: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf > Of Mark Tinka > Sent: Friday, October 30, 2015 4:17 AM > To: Adam Vitkovsky <adam.vitkov...@gamma.co.uk>; Saku Ytti > <s...@ytti.fi> > Cc: juniper-nsp@puck.nether.net > Subject: Re: [j-nsp] Limit on interfaces in bundle > > > > On 30/Oct/15 11:06, Adam Vitkovsky wrote: > > > Yes I agree that control word should definitely be enabled across the > board, it’s necessary on Cisco anyways. > > Enabled by default in Junos. One would have to manually turn it off. > > Mark. > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
