Difference between revisions of "Juniper EVPN-VXLAN & DCI"
Jump to navigation
Jump to search
(→Site A) |
(→Site A) |
||
Line 45: | Line 45: | ||
|10.193.0.79/24 | |10.193.0.79/24 | ||
|- | |- | ||
− | | | + | |qfxlsw27 |
|leaf1 | |leaf1 | ||
|10.179.0.5/32 | |10.179.0.5/32 | ||
Line 53: | Line 53: | ||
|10.193.0.80/24 | |10.193.0.80/24 | ||
|- | |- | ||
− | | | + | |qfxlsw28 |
|leaf2 | |leaf2 | ||
|10.179.0.6/32 | |10.179.0.6/32 |
Revision as of 20:19, 15 August 2022
Goal
In this tutorial we are going to setup 2 sites: Site A and site B and connect both sites together using a MPLS backbone. Both sites will be configured using EVPN-VXLAN centrally Routed Bridging (CRB).
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
- VMX running Junos: 18.2R1.9 for the core routers
- Debian VM's servers
Diagram
Setup and configuration
Site A
Devices | Role | lo.0 IP | xe-0/0/0 IP | xe-0/0/1 IP | xe-0/0/2 IP | mgmt |
qfxssw27 | spine1 | 10.179.0.1/32 | 172.16.1.49/30 | 172.16.2.2/30 | 172.16.3.1/30 | 10.193.0.78/24 |
qfxssw28 | spine2 | 10.179.0.2/32 | 172.16.1.6/30 | 172.16.2.6/30 | 172.16.3.5/30 | 10.193.0.79/24 |
qfxlsw27 | leaf1 | 10.179.0.5/32 | 172.16.1.50/30 | 172.16.1.5/30 | 10.193.0.80/24 | |
qfxlsw28 | leaf2 | 10.179.0.6/32 | 172.16.2.1/30 | 172.16.2.5/30 | 10.193.0.81/24 |