[j-nsp] Aggregated Eth interface in L2VPN

[David Ball]

  Thanks Angel.  This is something that is configured on a global
level though.  Should I be concerned about this hashing being applied
to anything other than agg ethernet interfaces?  I don't currently
have specific hash-key statements for inet or mpls families (though I
use both), and I just want to ensure this isn't being applied anywhere
I don't want/need it to be.

David


On 19/12/2007, Angel Bardarov <angel.bardarov at btc-net.bg> wrote:
> Take a look at this link
> http://www.juniper.net/techpubs/software/junos/junos85/swconfig85-policy/id-10568390.html#id-10568390
>
> Angel
>
> David Ball wrote:
> >   I have 2 Gig links on different PICs added to an 802.3ad agg
> > ethernet bundle for a customer.  They're an L2VPN customer so we're
> > not maintaining MAC tables.  While they claim to have a Nortel switch
> > on their side with plenty of individual MACs behind it, we're still
> > only sending traffic to them over 1 of the 2 links in the bundle (ie.
> > 0bytes over the other link).  I've been unable to find detailed
> > information on exactly how the hashing is done for such a setup, and
> > wondered if anyone here could shed some light or could provide insight
> > as to how else I could investigate what MACs we're seeing from them
> > (which I didn't think was possible for l2vpns).  I believe it's done
> > based on src and dest MAC, but am unsure how.  The other side of the
> > L2VPN is another 2 x 1Gig agg bundle, again with a customer switch
> > with lots of MACs behind it.
> >
> > David
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
> >
> >
>