Skip to main content

Eclit Case Documentation

This is a lab to test your bgp/evpn skills, You have 15 business days to finish this.

The case will be reviewed at a remote meeting session upon your declaration about golden tickets. No manual config is allowed, everything should be deployed using ansible-playbooks

You can access the lab at:

http://gns3.netdev.com.tr:3080

There are other labs available, you will use the one with the name "network_case_eclit"

Facts

  • Jump server user pass ubuntu:ubuntu Warning internet facing instance, please do not forget to change password of ubuntu user
  • All ports except the managements ones are shut, be carefull, you can loop and loose the lab access
  • Spine management address : 192.168.10.11
  • Leaf-1 management address : 192.168.10.21
  • leaf-2 management address : 192.168.10.22
  • Leaf-3 management address : 192.168.10.23
  • Leaf-4 management address : 192.168.10.24
  • Leaf pairs are paired with dual links
  • switch username, password : admin:admin
  • Lab switches are Model Arista 4.26.0F vm instances
  • Ansible galaxy collection for arista documentation https://galaxy.ansible.com/ui/repo/published/arista/eos/
  • installation ansible-galaxy collection install arista.eos

Scenario

You will need to deliver the requirements listed below

  • Create a public github repository and by using branches develop the following task entries/features
  • Create a README.MD file with your details and some explanation about this lab
  • Push

Using ansible playbooks:

  • branch clos: Define a bgp/evpn clos topology you are free to chose between unnumbered/static addressing
  • branch mlag: Define MLAG peerlinks you are free to chose static or dynamic configuration
  • branch vlan: Define a vlan
  • branch userports: set ethernet1 ports as access members of defined vlan
  • branch telemetry: set monitoring details, credentials, descriptions

Monitoring:

  • Create a monitoring solution for this structure on jump server. Snmp is good, other solutions are preferred.

Golden tickets:

  1. vcs machines should be able to ping each other on same vlan between racks.
  2. A monitoring solution, it must update the operator about thresolds and outages. These updates must happen less than a minute when any sensor triggers.
  3. A solution brief, one pager.
Back to top