CloudLabBox
Try the free demo

Arista EOS lab 12 of 20

EOS day-2 operations with AEM and port mirroring

Run the day-2 toolkit a data-centre operations engineer uses on EOS: a quick health check, a SPAN session to a capture host, an event handler that reacts to an uplink going down, scheduled CLI snapshots, and a configuration session that rolls itself back unless confirmed.

Run this lab

It needs Lite: its 5 nodes are set to 5 vCPU and 5,632 MB in total. That fits the free demo too.

In your workspace: Shared, then Arista EOS guided labs, then 12 - EOS day-2 operations with AEM and port mirroring

Try it free for 30 minutesRun it on Lite from £3 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

Level
Intermediate
Time
About 60 minutes
Nodes need
5 vCPU, 5,632 MB
Smallest plan
Lite

The scenario

You're on the Northwind operations rota. The application team reports "slow and flaky" traffic between h1 (behind leaf1) and h2 (behind leaf2), and change control wants every risky change to undo itself if the engineer loses access. Use the EOS operations toolkit: check the switches' health, mirror h1's port to the probe capture host, have leaf1 record every change of its uplink automatically, collect regular counter snapshots, and practise a self-reverting change.

DeviceInterfaceNotes
leaf1Ethernet1trunk uplink to leaf2 Ethernet1
leaf1Ethernet3h1, VLAN 10
leaf1Ethernet4probe (capture host, mirror destination)
leaf2Ethernet3h2, VLAN 10
h1 / h2eth010.10.10.11/24 · 10.10.10.12/24

What you’ll practise

  • Run a repeatable health check from the CLI (version, memory, processes, errors, logs)
  • Mirror a port to a capture host with a monitor session and read the traffic with tcpdump
  • Write an event handler that runs a Linux action when an interface changes state
  • Schedule periodic CLI snapshots with the CLI scheduler and find their output files
  • Make a risky change inside a configuration session with a commit timer

The tasks

  1. A two-minute health check
  2. Mirror h1's port to the capture host
  3. React to events with an event handler
  4. Collect snapshots with the CLI scheduler
  5. A change that reverts itself

The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.

Topology and devices

The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.

Topology of EOS day-2 operations with AEM and port mirroring5 nodes, 4 links. Every link is listed as text below the diagram.leaf1leaf2h1h2probeEthernet3eth0Ethernet3eth0Ethernet4eth0Ethernet1Ethernet1
5 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • leaf1 Ethernet1 to leaf2 Ethernet1
  • leaf1 Ethernet3 to h1 eth0
  • leaf2 Ethernet3 to h2 eth0
  • leaf1 Ethernet4 to probe eth0
Nodes in EOS day-2 operations with AEM and port mirroring, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
leaf1Arista vEOSveos-4.33.1.1F1 vCPU, 2,048 MB
leaf2Arista vEOSveos-4.33.1.1F1 vCPU, 2,048 MB
h1Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB
h2Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB
probeAlpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder Arista EOS guided labs.

  3. Open 12 - EOS day-2 operations with AEM and port mirroring and start its nodes, then open Lab Tasks for the scenario and the steps.

The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.

More Arista EOS labs

All Arista EOS labs

Related labs in other courses

CloudLabBox is independent of Arista Networks. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.