Re: [c-nsp] Cisco to Juniper LAG/LACP - Juniper not sending traffic over both links.

2012-10-06 Thread Mark Tinka
On Friday, September 07, 2012 03:11:20 AM Aaron wrote:

 Maybe this is stating the obvious, but when I've used
 ip-src-dst type hashing I've gotten the granularity I've
 desired.  This is with cisco devices, so sorry I can't
 speak to what juniper allows.

The issue I've had with Juniper EX3200/4200 switches was 
their inability to load share non-IP traffic, particularly 
MPLS-based flows. This was in a scenario where the devices 
were running as core switches.

Once I replaced the Juniper switches with ME3600X's (which 
actually didn't load share based on MPLS for the code at the 
time, just earlier this year), load sharing was achieved. 
Moreover, the routers to which the switches were load 
sharing were Junipers.

Not sure about your situation - whether you're connecting to 
the provider's Juniper switches or routers (the Juniper M- 
and MX-series routers don't suffer from this problem), or 
whether you have non-IP traffic crossing the links. 

Cheers,

Mark.


signature.asc
Description: This is a digitally signed message part.
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

[c-nsp] Cisco to Juniper LAG/LACP - Juniper not sending traffic over both links.

2012-09-06 Thread Joseph Jackson
Hey networkers,

I have 3 sites connected to a service providers MPLS network.  Two of
those sites (Dallas and LA) are configured as etherchannel/LACP ports
with 2 1gig uplinks in them.  On our end we have Catalyst 6506-E
switches the provider side is Juniper gear (I don't have model info).
The issue I am seeing is that on our side we are sending traffic out
of both interfaces and appear to be load balancing correctly.  The
provider (juniper) side is only sending traffic inbound to us over 1
of the links and not using the full etherchannel to load balance in
coming bandwidth.  On the LA end the juniper routers are seeing two
mac addresses learned on that etherchannel - one mac is the SVI and
one mac is one of the member ports.  The Dallas side is only seeing
one mac address.  The service provider is telling me that their
hardware is working correctly and that the hashing algorithm on the
juniper boxes is deciding that only one link should receive traffic.
Anyone else see this issue or can provide any tips.

Thanks!

Joseph
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


Re: [c-nsp] Cisco to Juniper LAG/LACP - Juniper not sending traffic over both links.

2012-09-06 Thread Joseph Jackson
Just got word from the provider.  They are using the default hashing
algorithm which is based on mac address.

On Thu, Sep 6, 2012 at 4:33 PM, Andrew Miehs and...@2sheds.de wrote:
 Which hashing algorithm are the using? One based on MAC address will do 
 exactly as you are describing.

 Andrew

 Sent from a mobile device

 On 07/09/2012, at 6:58, Joseph Jackson recou...@gmail.com wrote:

 Hey networkers,

 I have 3 sites connected to a service providers MPLS network.  Two of
 those sites (Dallas and LA) are configured as etherchannel/LACP ports
 with 2 1gig uplinks in them.  On our end we have Catalyst 6506-E
 switches the provider side is Juniper gear (I don't have model info).
 The issue I am seeing is that on our side we are sending traffic out
 of both interfaces and appear to be load balancing correctly.  The
 provider (juniper) side is only sending traffic inbound to us over 1
 of the links and not using the full etherchannel to load balance in
 coming bandwidth.  On the LA end the juniper routers are seeing two
 mac addresses learned on that etherchannel - one mac is the SVI and
 one mac is one of the member ports.  The Dallas side is only seeing
 one mac address.  The service provider is telling me that their
 hardware is working correctly and that the hashing algorithm on the
 juniper boxes is deciding that only one link should receive traffic.
 Anyone else see this issue or can provide any tips.

 Thanks!

 Joseph
 ___
 cisco-nsp mailing list  cisco-nsp@puck.nether.net
 https://puck.nether.net/mailman/listinfo/cisco-nsp
 archive at http://puck.nether.net/pipermail/cisco-nsp/
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/