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
- 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.
| Device | Interface | Address | Connects to |
|---|---|---|---|
| leaf1 | Management1 (VRF MGMT) | 192.168.100.11/24 | OOB switch |
| leaf2 | Management1 (VRF MGMT) | 192.168.100.12/24 | OOB switch |
| leaf1 | Ethernet1 | (switch port) | leaf2 Ethernet1 |
| OOB services | gateway, NTP | 192.168.100.1 (not built in this lab) | – |
| OOB services | syslog collector | 192.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
- Find your way around EOS
- Give each switch an identity
- Create role-based users
- Build the out-of-band management VRF
- Point time and logging at the OOB services
- Stage a change in a configuration session
- Checkpoint, break, roll back
- 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.
Every link, as text
- leaf1
Management1to OOB (network) - leaf2
Management1to OOB (network) - leaf1
Ethernet1to leaf2Ethernet1
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| leaf1 | Arista vEOS | veos-4.33.1.1F | 1 vCPU, 2,048 MB |
| leaf2 | Arista vEOS | veos-4.33.1.1F | 1 vCPU, 2,048 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
Arista EOS guided labs.Open
01 - EOS CLI and management access with safe changeand 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
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.