Difference between revisions of "Juniper Collapsed Spine with EVPN"

From ppwiki
Jump to navigation Jump to search
Line 27: Line 27:
 
|interface/IP
 
|interface/IP
 
|ae0 IP
 
|ae0 IP
 +
|ae0 interfaces
 +
|ae1 interfaces
 +
|ae2 interfaces
 +
|ae5 interfaces
 +
|ae6 interfaces
 
|mgmt
 
|mgmt
 
|AS
 
|AS
Line 37: Line 42:
 
|172.16.3.1/30
 
|172.16.3.1/30
 
|10.193.0.105/24
 
|10.193.0.105/24
 +
|
 
|64701
 
|64701
 
|-
 
|-
Line 45: Line 51:
 
|172.16.3.2/30
 
|172.16.3.2/30
 
|10.193.0.106/24
 
|10.193.0.106/24
 +
|
 
|64701
 
|64701
 
|-
 
|-
 
|sw1
 
|sw1
 
|switch 1
 
|switch 1
|10.179.1.4/32
 
 
|
 
|
 
|
 
|
|10.193.0.108/24
+
|
 +
|
 
|
 
|
 
|-
 
|-
 
|sw2
 
|sw2
 
|switch 2
 
|switch 2
|10.179.1.3/32
 
 
|
 
|
 
|
 
|
|10.193.0.107/24
+
|
 +
|
 
|
 
|
 
|-
 
|-

Revision as of 23:26, 18 October 2023

Goal

In this tutorial, We will be setting up a collapsed Spine EVPN/VXLAN with multi-homing.We will using two SRX's in cluster mode to route traffic between the 2 Tenants that we will configure. We will be using BGP for the underlay and overlay.

Prerequisites

For this tutorial we will be using:

- EVE-NG 2.0.3-112

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

- VSRX 3.0

- Debian VM's servers

Diagram

Setup and configuration

network info
Devices Role lo.0 IP interface/IP ae0 IP ae0 interfaces ae1 interfaces ae2 interfaces ae5 interfaces ae6 interfaces 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
sw2 switch 2
srx
srv1 Server1
srv2 Server2
srv3 Server3
srv4 Server4
srv5 Server5
srv6 Server6
srv7 Server7
srv8 Server8

core switch 1 configuration