Difference between revisions of "Juniper ESI-LAG"
Jump to navigation
Jump to search
| Line 46: | Line 46: | ||
| | | | ||
|- | |- | ||
| − | | | + | |sw2 |
|switch 2 | |switch 2 | ||
|10.179.1.3/32 | |10.179.1.3/32 | ||
| − | |||
| − | |||
| | | | ||
| + | |10.193.0.107/24 | ||
| | | | ||
| − | |||
| − | |||
| − | |||
|- | |- | ||
|} | |} | ||
Revision as of 01:57, 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
Setup and configuration
| 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 | ||
| sw2 | switch 2 | 10.179.1.3/32 | 10.193.0.107/24 |