MPLS Segment Routing Core for a EVE-NG virtual lab
NOTE - 11th April 2020: this project has become stale due to one thing and another - but still mostly useful and relevant.
Lab created from the example in the Juniper Day One book Configuring Segment Routing with Junos by Julian Lucek and Krzysztof Szarkowicz.
Now with added Salt! helped again by another Juniper Day One book authored by Peter Klimai and Mircea Ulinic's excellent Salt and automation resouces via his site and github page.
A set of initial lab configs is included in this repo for a post that will hopefully appear on Tech Snippets in the future (to include detail on using EVE-NG on the Google Compute Platform as well!).
At this time the EVE-NG server is in the Google Compute Platform as you get $300 worth of credit you can use as you please for 12 months. Azure gives you $250 but limited machine types and only for the first 30 days and Amazon doesn't have machines that support nested virtulization - so no good for EVE-NG.
- MPLS core is using ISIS as the IGP
- PE router images are all vMX QEMU Junos 17.3R3-S2.2
- R4 and R7 are the route reflectors
- CE vSRX site routers will be Junos v12.1x47-d15.4 QEMU images
- Juniper root user password is lab123
- Juniper lab user password is lab123
- Linux automation host root user password is root
- Linux automation host pfne user password is pfne
- Ansible has been used and I have created some low level playbooks to gather some information
- CumulusVX (Salt minion) cumulus user password is CumulusLinux!
- The pfne user has a local public SSH key to communicate with the network devices from the Linux automation server
- Initial folder holds the configs for the devices and also exports from EVE-NG of the initial setup (upto page 15 of the book)
- More comprehensive information on how to create the lab and other components here
EVE-NG lab topology:
NOTE: Forward Essentials no longer exists or availiable so :-( - EVE-NG lab topology in Forward Essentials (collector installed on the Linux automation box):
