Load Sharing VPLS end

[Julian_Eble]

Hello Community,

I'm having headache about the load-balance on Aggreation Ports.

Our scenery is a MPLS network who the end point are connected by Juniper Routers.
These connections are 10G (20g agg) and have one VLAN VPLS tagged end-by-end.
The traffic doesn't get balanced even when I change the hash-algorithm and the balance type.

Is there any problem using VPLS and LACP?
Extreme introduced the load-sharing VPLS but I think that useful just for the trunk LACP/MPLS, isn't?

Thanks,
Julian Eble

[Douglas_Machado]

Hello Julian,

I have the same problem and it occurs just with the egress traffic, from extreme(that ends the VPLS) to my router(in this case a Mikrotik CCR-1036).

[Julian_Eble]

There's no VPLS between Juniper and Extreme, only L2.
Juniper are doing the EDGE router with BGP and Extreme are our CORE MPLS

[Bill_Stritzinge]

Based on your layout...

Juniper =>20G LACP <= EXTREME CORE MPLS #VPLS# =>20G LACP => Juniper

How many VPLS tunnels are there? It would seem to me that because the tunnels would have the same source and destination mac (assuming multiple tunnels exist) that the hash would be limited to those pairs. If that is true, that would explain the lack of sharing across the links. In a traditional lag the hash would be able to take each stream and its source mac to apply the hash to and therefore being able to distribute efficiently, when the sources mac is small the distribution would be that way as well. Any idea how many source/destination mac pairs there are in that traffic?

Bill

[Bill_Stritzinge]

OK.. Can you please share the output from "show sharing"? If the interface is only L2 then the hash can only (will only) be done on the L2 hash (source mac/destination mac). How many streams?

[Julian_Eble]

In this case, just one tunnel, but the point is related to the end and then we're doing the pure L2.

I had a lab where just I simulated a traffic orignated by just one source and destionation mac, but multiples source and destionation IP's and protocols.

The traffic don't get hashed and are flowing just in one interface.