So I think I’m done with theory, and now it’s time to practice some of the most important topics – firstly MC-LAG and EVPN. Unfortunately I don’t have access to real QFX5100 gear, so I’m using vMX and vQFX virtual appliances. I built my lab in GNS3 using my home PC with 4-core CPU and 32 GB of RAM. I’m using vMX v17 (v16 doesn’t support all required EVPN functionality), vQFX v15; and also vMX v14 in CE and MPLS PE…
For full configuration eample of EVPN-VXLAN to EVPN-MPLS stitching refer to MX Layer 2 VPNs Feature Guide, Chapter 28. First of all, you need to configure Logical Tunnel (lt-) interface for traffic between EVPN-VXLAN and EVPN-MPLS instances: interfaces lt-1/0/10 { esi { 36:36:36:36:36:36:36:36:36:36; all-active; } unit 3 { encapsulation ethernet-bridge; peer-unit 4; family bridge { …
Four Data Center InterConnect (DCI) options for EVPN-VXLAN service are described in detail in the Advanced Data Center Switching (ADCX) course materials. These options are: EVPN-VXLAN session over L3VPN-MPLS service; EVPN-VXLAN to EVPN-MPLS stitching; EVPN-VXLAN to EVPN-VXLAN stitching; EVPN-VXLAN session over dark fiber. First and last options are not so interesting – simple EVPN-VXLAN session between DC devices over direct IP connectivity or via L3VPN service. Basic L3VPN/MPLS stuff. But EVPN stitching is a slightly different story. Resembles Inter-AS VRF Option-A….
First note – QFX5100 series doesn’t support EVPN-VXLAN inter-VXLAN routing, and doesn’t support EVPN-MPLS at all. So all information in this post applicable only to MX devices. For EVPN-MPLS there is two types of IRB implementation: configuration of same MAC address on every IRB interface; default gateway MAC synchronization using EVPN default-gateway community. In EVPN-MPLS it is expected, that if IRB functionality necessary for this L2 domain, then IRB interfaces should be configured on every participating PE router. …
The general route target configured under vrf-target will be used by type 1 EVPN routes: MX: set routing-instances VS_VLAN100 vrf-target target:1:100 QFX: set switch-options vrf-target target:65000:2 If you configure vrf-target auto, then type 2 and type 3 EVPN routes will use the auto-derived per-VNI route target for export and import. Community numbers based on autonomous system number defined in routing-options stanza. MX: set routing-instances VS_VLAN100 switch-options vrf-target auto QFX: set switch-options vrf-target auto If you prefer…
The overall structure of QFX5100 EVPN-VXLAN configuration is almost identical to MX configuration, but QFX configuration statements are scattered across three different stanzas: switch-options, protocols evpn and vlans. First is the switch-options config: set switch-options vtep-source-interface lo0.0 set switch-options route-distinguisher 10.0.0.3:1 set switch-options vrf-import EVPN_VRF_IMPORT set switch-options vrf-target target:65000:2 set switch-options vrf-target auto ### depends on AS number in routing-options Vtep-source-interface and route-target policices are configured here. Configuration of vrf-import policy: set policy-options…
Basic config for EVPN-VXLAN service on Juniper MX. Important BGP configuration statements: set protocols bgp group EVPN_VXLAN family evpn signaling set protocols bgp group EVPN_VXLAN multipath Routing instance configuration: VS_VLAN100 { vtep-source-interface lo0.0; instance-type virtual-switch; route-distinguisher 1.255.255.0:100; vrf-import VS_VLAN100_IMP; vrf-target target:1:100; protocols { evpn { encapsulation vxlan; extended-vni-list 1100; …
Short notes about MX EVPN-MPLS configuration. Vlan-based configuration: routing-instances { EVPN-1 { instance-type evpn; vlan-id 100; interface ae0.100; routing-interface irb.100; route-distinguisher 11.11.11.11:1; vrf-target target:65000:1; protocols { evpn { default-gateway do-not-advertise; }…
For study of Juniper EVPN technology I recommend to read this materials (in this particular order): Juniper QFX10000 Series book; EVPN whitepaper; Advanced Data Center Switching (ADCX) course materials; EVPN Day One book; L3GW VMTO whitepaper; MX L2VPN Feature Guide; QFX EVPN/VXLAN Feature Guide. EVPN is definitely the core topic of JNCIE-DC lab, so I need to study all of this thoroughly. Firstly I need to read (and understand) all this stuff, and later on I plan to heavily practice all…
VXLAN with Multicast control plane is not explicitly stated in JNCIE-DC lab exam topics, so I not expect it on the exam. But anyway I decided to start Overlay topics from the simple case and later on continue to more advanced ones. Firstly, for Multicast VXLAN of course you need to configure Multicast protocol in the Underlay. Nothing complex, just basic PIM stuff: configure PIM interfaces and some kind of RP (static/local/anycast-RP). Configure VTEP source interface: set switch-options vtep-source-interface lo0.0 …