Arista EOS lab 1 of 20

EOS CLI and management access with safe change

Take two factory-fresh Arista leaf switches to a documented, secured baseline: learn the EOS command line, build an out-of-band management VRF with SSH, add role-based users, and make changes safely with configuration sessions and checkpoints.

Run this lab

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

In your workspace: Shared, then Arista EOS guided labs, then 01 - EOS CLI and management access with safe change

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
Beginner
Time
About 60 minutes
Nodes need
2 vCPU, 4,096 MB
Smallest plan
Lite

The scenario

Northwind Data is building a new data-centre pod. Two Arista leaf switches have just been racked in B12. They are still at factory settings: they call themselves localhost, the only account is admin with no password, and nothing can reach them except the console.

Before the fabric team arrives, you must give both switches a documented, secured management baseline on the out-of-band (OOB) network, and prove you can make and undo changes safely.

DeviceInterfaceAddressConnects to
leaf1Management1 (VRF MGMT)192.168.100.11/24OOB switch
leaf2Management1 (VRF MGMT)192.168.100.12/24OOB switch
leaf1Ethernet1(switch port)leaf2 Ethernet1
OOB servicesgateway, NTP192.168.100.1 (not built in this lab)–
OOB servicessyslog collector192.168.100.50 (not built in this lab)–

Topology: leaf1 Management1 and leaf2 Management1 share the OOB segment · leaf1 Ethernet1 — leaf2 Ethernet1.

What you’ll practise

  • Move between EOS command modes, use help and filter output with include, section and json
  • Name the switches, set time zone, DNS domain, NTP and logging towards the management network
  • Create role-based local users and authorise them for privileged EXEC
  • Put Management1 in a dedicated management VRF and enable SSH only there
  • Stage a change in a configuration session, review the diff and commit it
  • Save a configuration checkpoint, break the configuration and roll back with configure replace

The tasks

  1. Find your way around EOS
  2. Give each switch an identity
  3. Create role-based users
  4. Build the out-of-band management VRF
  5. Point time and logging at the OOB services
  6. Stage a change in a configuration session
  7. Checkpoint, break, roll back
  8. Save and compare

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 CLI and management access with safe change2 nodes and 1 network, 3 links. Every link is listed as text below the diagram.leaf1leaf2OOBManagement1Management1Ethernet1Ethernet1
2 nodes and 1 network, with the interface names each link uses.
Nodes in EOS CLI and management access with safe change, 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

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 01 - EOS CLI and management access with safe change 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.