/Juniper-JNCIP-DC

EVE-NG Lab for super spine EVPN-VXLAN deployment

GNU General Public License v3.0GPL-3.0

* README *
** JUNIPER JNCIP-DC EVPN/VXLAN & CONFIGS **

This series of configurations were configured for the JUNIPER JNCIP-DC examination topics. They may be used to assist in studies or for production deployment assistance.

HARDWARE | SOFTWARE SPECIFICATIONS

Virtualized Network Devices:

  • Vendor:: Juniper
  • Model:: vQFX
  • OS Version:: Junos: 18.4R1.8

Virtualization Platform::

  • Application: EVE-NG PROFESSIONAL
  • Version: 5.0.1-20-PRO, QEMU 2.4.0

System Hardware/Environment:

  • Host: EVE-NG Kernel: 4.20.17-eve-ng-ukms+ x86_64 (64 bit) Console: tty 2 Distro: Ubuntu 16.04 xenial
Machine Details:
  • System: LENOVO product: 30B5005XUS v: ThinkStation P510
  • Mobo: LENOVO model: 102F Bios: LENOVO v: S00KT40A date: 05/04/2017
  • CPU: Hexa core Intel Xeon E5-1650 v4 (-HT-MCP-) speed/max: 1809/4000 MHz
  • Graphics: Card: NVIDIA GP106GL [Quadro P2000], Display Server: N/A driver: N/A tty size: 160x46 Advanced
  • Network: Card: Intel Ethernet Connection (2) I218-LM driver: e1000e
  • Drives: HDD Total Size: 1024.2GB
Memory:
  • Array-1 capacity: 1 TB (check) devices: 8 EC: Multi-bit ECC
  • Device-1: DIMM_1 size: 8 GB speed: 2400 MHz type: DDR4
  • Device-3: DIMM_3 size: 8 GB speed: 2400 MHz type: DDR4
  • Device-5: DIMM_2 size: 16 GB speed: 2400 MHz type: DDR4

    • This lab is based on a bare metal install of the EVE-NG Community Edition. It may be run within VMWare Workstation and other hypervisors. Resource utilization, on above server specifications, for this lab/system:

    CPU: 17%
    MEM: 32%
    SWAP: 2%
    QEMU Nodes: 24
    VPCS Nodes: 12

    // CODE REQUIREMENTS \

    To obtain the JUNOS code, you will need to create an account at HTTPS://WWW.JUNIPER.NET. Virtual code contains certain restrictions and is regulated by the vendor.

    //// LAB DESCRIPTION \\\\

    This topology contains a CLOS network topology with super spine to show expansion of east-west traffic in a data center. It's deployment uses eBGP for the underlay, iBGP for the overlay, and EVPN/VXLAN to provide connectivity across the Layer 3 transport. In the underlay, eBGP may be substituted with nearly any routing protocol as long as you are able to advertise the loopback interfaces for use in the overlay.

    Lab Details:

    Management interfaces:

    • CSR1: 192.168.21.101
    • CSR2: 192.168.21.102
    • CSR3: 192.168.21.103
    • CSR4: 192.168.21.104
    • CSR5: 192.168.21.105
    • CSR6: 192.168.21.106
    • CSR7: 192.168.21.107
    • CSR8: 192.168.21.108
    • CSR9: 192.168.21.109
    • CSR10: 192.168.21.110
    • CSR11: 192.168.21.111
    • CSR12: 192.168.21.112

    Subnet IP Scheme:

    • WAN Links: 172.16.255.0/24 (Subdivide to /30)
    • Loopback Interfaces: 10.255.255.0/24 (Subdivide to /32)
    • VLANs: 192.168.0.0/16 (Subdivide to /24)

    BGP ASN Assignment:

    • OVERLAY ASN: 65100

    • UNDERLAY ASN:
    • CSR1: 65001
    • CSR2: 65002
    • CSR3: 65103
    • CSR4: 65104
    • CSR5: 65105
    • CSR6: 65106
    • CSR7: 65107
    • CSR8: 65208
    • CSR9: 65209
    • CSR10: 65210
    • CSR11: 65211
    • CSR12: 65212

    Lab User Accounts (username / password)

    • root / abc123
    • admin / abc123

    //// VENDOR GUIDES \\\\

    Juniper Support

    Juniper Learning Portal

    EVE-NG Documentation

    //// LAB IMAGE \\ Juniper-JNCIP-DC_Topology