service rhysd reload

Extreme Networks to Juniper LACP

Setting up a LAG between Extreme and Juniper switches isn’t hard

This example is between a Extreme Alpine x350 and a Juniper ex4200.

On the Extreme switch:

extreme
1
2
enable sharing <Master Port> grouping <port list> <type>
enable sharing 47 grouping 47,48 lacp

This will put ports 47 and 48 into a lacp trunk.

The lacp group will default to active which is fine. When you add vlans to the lacp trunk add them to the master port.

On the Juniper side:

Make sure your chassis has enough aggregated devices to allow for another.

juniper
1
set chassis aggregated-devices ethernet device-count 10
juniper
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
   ge-0/0/0 {
       ether-options {
           802.3ad ae2;
       }
   }
   ge-1/0/0 {
       ether-options {
           802.3ad ae2;
       }
   }
  ae2 {
       description "Lag link to Extreme switch";
       mtu 9216;
       aggregated-ether-options {
          lacp {
               active;
           }
       }
       unit 0 {
           family ethernet-switching {
               port-mode trunk;
           }
       }
   }

The above configuration added ge-0/0/0 and ge-1/0/0 into an lacp (802.3ad) interface called ae2 (aggregated ethernet 2). The Extreme x350’s I was using has a max MTU of 9216.. hence the MTU size.

Once up it will creating a single 2G interface. That will seamless drop to 1G if either interface dies.

Comments