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

[Anatoly_Machekh]

Neither works.

[Anatoly_Machekh]

Hi Henrique,

We have port-based at one node:

# sho sharing
Load Sharing Monitor
Config Current Agg Ld Share Ld Share Agg Link Link Up
Master Master Control Algorithm Group Mbr State Transitions
==============================================================================
2:1 1:1 LACP port 1:1 Y A 0
port 2:1 Y A 0
2:5 1:5 LACP port 1:5 Y A 0
port 2:5 Y A 0
2:6 1:6 LACP port 1:6 Y A 0
port 2:6 Y A 0
And custom (default) at the other end:

# sh sharing
Load Sharing Monitor
Config Current Agg Ld Share Ld Share Agg Link Link Up
Master Master Control Algorithm Group Mbr State Transitions
==============================================================================
2:1 1:1 LACP custom 1:1 Y A 0
custom 2:1 Y A 0
2:2 1:2 LACP custom 1:2 Y A 0
custom 2:2 Y A 0
2:21 1:21 LACP custom 1:21 Y A 0
custom 2:21 Y A 0

[Henrique]

Hi Anatoly,

What hashing algorithm are you using? XOR, CRC32?

Could you please share the "show sharing" output?

[Anatoly_Machekh]

Hello Community,

I have the same very problem on X670-G2. Our network looks like:

MPLS L3VPN on Juniper =LAG 2x10G= L2 domain =LAG 2x10G= MPLS L3VPN on Juniper

L2 domain consists of Extreme X670-G2 switches (stacks) with one VPLS instance.
We configured "l2vpn sharing" and multiple rsvp-te lsp between VPLS end nodes. Traffic is load-balanced between lsp.

Transport LSP : LSP_E1_E2_1 (Configured)
Next Hop I/F : VLAN12
Next Hop Addr : 172.22.127.10 Tx Label : 0x0043b
Tx Pkts : 1213508852 Tx Bytes : 3128993213097
Transport LSP : LSP_E1_E2_2 (Configured)
Next Hop I/F : VLAN12
Next Hop Addr : 172.22.127.10 Tx Label : 0x0043d
Tx Pkts : 598239828 Tx Bytes : 3528005632087
Transport LSP : LSP_E1_E2_3 (Configured)
Next Hop I/F : VLAN12
Next Hop Addr : 172.22.127.10 Tx Label : 0x0043f
Tx Pkts : 401710508 Tx Bytes : 3236292622542
Transport LSP : LSP_E1_E2_4 (Configured)
Next Hop I/F : VLAN12
Next Hop Addr : 172.22.127.10 Tx Label : 0x00441
Tx Pkts : 1034383499 Tx Bytes : 3032407107905

But on the end nodes traffic to Junipers is not load-balanced.
Any ideas how to do LAG load-balancing in this case?

[Julian_Eble]

Got an answer today, very sad by the way... 😞

"Engineering got back to me today, saying this a hardware limitation with Summit X670, X480 and X460.

There is no hardware provision(in terms of registers) to accomplish load sharing based on inner L3 fields in the MPLS terminated packet and the packets will be forwarded as per L2 hashing.

The above information is not mentioned in the concepts guide, hence a documentation CR# xos0061631 was created to update the document."