Difference between revisions of "Juniper Collapsed Spine with EVPN"

From ppwiki
Jump to navigation Jump to search
Line 32: Line 32:
 
|ae6 interfaces
 
|ae6 interfaces
 
|mgmt
 
|mgmt
|AS
+
|local-as underlay
 +
|local-as overlay
  
 
|-
 
|-
Line 45: Line 46:
 
|xe-0/0/8
 
|xe-0/0/8
 
|10.193.0.105/24
 
|10.193.0.105/24
|64701
+
|65012
 
|-
 
|-
 
|cc2
 
|cc2
Line 51: Line 52:
 
|10.179.1.2/32
 
|10.179.1.2/32
 
|172.16.3.2/30
 
|172.16.3.2/30
||xe-0/0[10-11]
+
|xe-0/0[10-11]
|
+
|xe-0/0/0
|
+
|xe-0/0/1
|
+
|xe-0/0/9
|
+
|xe-0/0/8
 
|10.193.0.106/24
 
|10.193.0.106/24
|64701
+
|65013
 
|-
 
|-
 
|sw1
 
|sw1

Revision as of 23:43, 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 ae0 IP ae0 interfaces ae1 interfaces ae2 interfaces ae5 interfaces ae6 interfaces mgmt local-as underlay local-as overlay
cc1 core swtich1 10.179.1.1/32 172.16.3.1/3 xe-0/0[10-11] xe-0/0/0 xe-0/0/1 xe-0/0/9 xe-0/0/8 10.193.0.105/24 65012
cc2 core switch2 10.179.1.2/32 172.16.3.2/30 xe-0/0[10-11] xe-0/0/0 xe-0/0/1 xe-0/0/9 xe-0/0/8 10.193.0.106/24 65013
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