Difference between revisions of "Juniper ESI-LAG"

From ppwiki
Jump to navigation Jump to search
Line 39: Line 39:
 
|64701
 
|64701
 
|-
 
|-
|qfxlsw27
+
|sw1
|leaf1
+
|switch 1
|10.179.0.5/32
+
|10.179.1.4/32
|172.16.1.50/30
 
|172.16.1.5/30
 
 
|
 
|
 +
|10.193.0.108/24
 
|
 
|
|10.193.0.80/24
 
|64601
 
|65032
 
 
|-
 
|-
|qfxlsw28
+
|ssw2
|leaf2
+
|switch 2
|10.179.0.6/32
+
|10.179.1.3/32
 
|172.16.2.1/30
 
|172.16.2.1/30
 
|172.16.2.5/30
 
|172.16.2.5/30
 
|
 
|
 
|
 
|
|10.193.0.81/24
+
|10.193.0.107/24
 
|64601
 
|64601
 
|65033
 
|65033
|-
 
|cr1
 
|core router
 
|10.179.0.7/32
 
|172.16.3.2/30
 
|172.16.3.6/30
 
|
 
|172.16.4.0/31
 
|10.193.0.86/24
 
|100
 
 
|-
 
|-
 
|}
 
|}

Revision as of 01:56, 27 February 2023

Goal

In this tutorial we are going to to setup ESI-LAG (Ethernet Switch Identifier - Link Aggregation Group). According to Juniper: "ESI link aggregation groups (ESI-LAGs) enable one or more client devices to form a logical link aggregation group (LAG) interface with the peers".

Prerequisites

For this tutorial I will be using :

- EVE-NG 2.0.3-112

- VQFX model: vqfx-10000 running JUNOS 19.4R1.10 for spines and leaves

- Debian VM's servers

Diagram

Esi-lag.png

Setup and configuration

network info
Devices Role lo.0 IP ae0 IP mgmt AS
cc1 core swtich1 10.179.1.1/32 172.16.3.1/30 10.193.0.105/24 64701
cc2 core switch2 10.179.1.2/32 172.16.3.2/30 10.193.0.106/24 64701
sw1 switch 1 10.179.1.4/32 10.193.0.108/24
ssw2 switch 2 10.179.1.3/32 172.16.2.1/30 172.16.2.5/30 10.193.0.107/24 64601 65033