[j-nsp] Re: ae0 (802.3ad/LACP) against GSR?

[Josef Buchsteiner]

Friday, January 28, 2005, 10:13:45 AM, you wrote:

  
SY> On (2005-01-27 23:20 +0100), Niels Bakker wrote:

 >> > Cisco is running 12.0(27)S4, Juniper is running 7.0R2.
 >>
 >> that IOS may blow for link aggregation.  Perhaps try one of these:
 >>
 >> 12.0(25)S4
 >> 12.0(28)S1
 >> 12.0(30)S
 >>
 >> I have no personal knowledge how well lb-ph3 images work but they're
 >> supposedly the bee's knees.
 >>
 >> Best to follow-up to cisco-nsp :)

SY>   You were right, we upgraded to 12.0(30)S and IS-IS started to work.
SY>  I don't have anythin behind the lab juniper and I'm seeing egress
SY>  traffic from route engine always using only one physical interface, is
SY>  this expected behaviour, ie. is only transit traffic load-balanced?

     this  is  expected  behavior. traffic generated from the RE is in
     general  not  subject  to  the  route-lookup  as this is all done
     already in the host along with adding the L2 information therefor
     traffic will be send out on the first member link.

     thanks
     Josef

SY>   I've configured load-balance per-packet policy under forwarding-table.

SY>   Funny thing though, even with 12.0(27)S4 IS-IS worked if we had
SY>  3550 in between the boxes.

SY>  --
SY>    ++ytti
SY>  _______________________________________________
SY>  juniper-nsp mailing list juniper-nsp at puck.nether.net
SY> http://puck.nether.net/mailman/listinfo/juniper-nsp