[j-nsp] Aggregated Eth interface in L2VPN

[Alain Briant]

/ Hi david

Based on this:/

http://www.juniper.net/techpubs/software/junos/junos85/swconfig85-network-interfaces/id-12111969.html#id-12111969

This implementation uses the same load-balancing algorithm used for 
per-packet load balancing. For information about per-packet load 
balancing, see the /JUNOS Routing Protocols Configuration Guide/.
/The load ballancing algorithm is described here:/

http://www.juniper.net/techpubs/software/junos/junos85/swconfig85-routing/id-10480125.html#jN19E97

    * Source IP address
    * Destination IP address
    * Protocol
    * Source port number
    * Destination port number
    * Source interface index
    * Type of service (ToS)


/The distribution is based on level 3 parameters, since you're looking 
for level 2 ditribution I believe it won't do it for you

hope this help
regards
Alain
/
David Ball a écrit :

>  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
>
>
>  
>