cancel
Showing results forĀ 
Search instead forĀ 
Did you mean:Ā 

MLAG algorithm when connected to Juniper Switches.

MLAG algorithm when connected to Juniper Switches.

Rod_Robertson2
Contributor
I have a customer who has a core of Extreme , and Juniper edge .

We seem to have an issue with Mlag.
The config looks OK , only thing different to my configuration is that the ISC is in its own VR, I do not see an issue with that ..

The problem that is being reported , is that the edge switches ( juniper when configured for AE0, the transfer of data is extremely slow.

Remove one of the mlag links and it all speeds up to an acceptable level.

We are not running LACP..

Juniper Edge config.

set interfaces ae0 description xe-uplinks-LAG set interfaces ae0 aggregated-ether-options minimum-links 1
set interfaces ae0 aggregated-ether-options link-speed 10g
set interfaces ae0 unit 0 family ethernet-switching port-mode trunk

set interfaces xe-0/1/0 ether-options 802.3ad ae0
set interfaces xe-0/1/1 ether-options 802.3ad ae0

Extreme config :

One side only ..

create vr "VR-MLAG-ISC"
create vlan "MLAG-ISC" vr VR-MLAG-ISC
configure vlan MLAG-ISC tag 6
configure vlan "MLAG-ISC" qosprofile QP5
configure vlan MLAG-ISC add ports 1:39 tagged
configure vlan MLAG-ISC ipaddress 10.10.10.1 255.255.255.252
disable iproute ipv4 compression vr VR-MLAG-ISC
disable iproute ipv6 compression vr VR-MLAG-ISC
create mlag peer "CL-MLAG"
configure mlag peer "CL-MLAG" ipaddress 10.10.10.2 vr VR-MLAG-ISC enable mlag port 1:43 peer "CL-MLAG" id 1
enable mlag port 1:44 peer "CL-MLAG" id 2
enable mlag port 1:45 peer "CL-MLAG" id 3
enable mlag port 1:46 peer "CL-MLAG" id 4
enable mlag port 1:47 peer "CL-MLAG" id 5
enable mlag port 1:48 peer "CL-MLAG" id 6

Ok this is more than I would configure normally for MLAG..(QOS IProute Compression )..

My main question is :

What hashing algorithm does Mlag use , its construction and can it be modified ,

I expect the issue to be the difference between Juniper and Extreme Algorithms ... well I hope it is , if this cannot be resolved , the customer will be returning to EAPS.

Many Thanks

Rod

1 ACCEPTED SOLUTION

Henrique
Extreme Employee
Hi Rod, I'm not sure if that will fix the issue. However, that change has fixed a similar problem last year.

I know this is mandatory when configuring LACP only, but it's a good option to try.

View solution in original post

20 REPLIES 20

Rod_Robertson2
Contributor
OK , if we have multiple VR 's , and of course the edge switch does not support vr's AKA X440's , are you implying that we should have an ISC per VR ?

So basically it does not matter what vr we use for the ISC .. normally I would just have the ISC in VR-Default.. it works as I have done this many times ..

We have 11 VR's on this PAir of X670 switches ..

The shared port is only needed if you are using LACP.

We have multiple VRs and only one ISC. On another 8800 pair we have the ISC in its own VR (because the rest of the vlans that were there moved to another BD pair)
I'd look at the "shared" part that Henrique mentioned.
GTM-P2G8KFN