After a week of waiting (why this is taking so long? this wasn’t a particularly pleasant week), I finally got my number. Brand new JNCIE-DC #31 !!! The main note about the lab – time management is the most important thing on the exam. Don’t rush to the keyboard, read and understand all the tasks and it’s interdependencies. Have a plan regarding order of tasks – not all tasks can be completed in order in which they written. Don’t be…
How fast time flies! Tomorrow ( August 10) is my JNCIE-DC lab day. I spent last couple of days repeating my notes and labbing small optional topics like CoPP, ZTP, etc; and also familiar ones like CoS and MPLS L3VPN. Today is the rest day. Fly to Amsterdam, drink a couple of beers and go to bed. Fortunately I’ve been there before, so no worries about how to find Juniper office and be late for the exam. Plan for tomorrow: go…
Last big topic that I need to practice – Data Center Interconnect (DCI). Fortunately I pretty confident in my skills in the MPLS L3VPN area, so I think I shouldn’t spend much time for this topic. The most complex DCI option remains – EVPN stitching. In this topic I will show you my example of EVPN-VXLAN to EVPN-MPLS stitching (there is also option of EVPN-VXLAN to EVPN-VXLAN stitching, but configuration should be similar to my example). EVPN stitching concept is…
Firstly, QFX5100 series doesn’t support EVPN-VXLAN inter-VXLAN routing, so I practice all IRB related topics on vMX devices. vQFXs acts as a simple L2 EVPN gateways. This post continues the EVPN-VXLAN lab from the previous ones. Full vMX IRB interfaces configuration: alex@vMX1# show interfaces irb unit 100 { proxy-macip-advertisement; family inet { address 172.16.0.251/24 { virtual-gateway-address 172.16.0.254; } } …
This post continues the EVPN-VXLAN lab from the previous one. For now I configured the simplest possible variant of RT assignment – one vrf-target for all ES and VNI routes (vrf-target target:65000:1): alex@vQFX1# show switch-options service-id 1; vtep-source-interface lo0.0; route-distinguisher 11.11.11.11:1; vrf-target target:65000:1; ### This RT applies to ALL EVPN routes alex@vMX1# show routing-instances evpn { vtep-source-interface lo0.0; instance-type virtual-switch; interface ge-0/0/4.0; interface ae0.0; route-distinguisher 1.1.1.1:1; …
My EVPN-VXLAN lab topology: There is IP Fabric in DC1 (2 vMX and 2 vQFX), and 2 vMX_v14 to emulate CE devices. Each CE device connected to EVPN via LACP LAG ae0 (EVPN Active-Active ethernet segment on service side). vMX_old-1 also has sigle-homed interface ge-0/0/4 (just to show you the difference). Each CE device split into two logical systems for more convenient testing of routing functionality (global device context for Vlan100 and logical-system second for Vlan200). You could also use…