Network automation lab 1 of 27
Your automation workstation: Bash, SSH keys and management ports
Set up the Linux workstation you will automate from: Bash files, pipes and environment variables, a syslog report, a port checker that tells SSH, HTTPS and NETCONF apart, SSH keys on IOS and IOS XE, and a backup script that runs without a password.
Run this lab
It needs Lite: its 3 nodes are set to 3 vCPU and 5,632 MB in total. That fits the free demo too.
In your workspace: Shared, then Network Automation - CCNA and CCNP Automation guided labs, then 01 - Your automation workstation - Bash SSH keys and management ports
- Level
- Beginner
- Time
- About 70 minutes
- Nodes need
- 3 vCPU, 5,632 MB
- Smallest plan
- Lite
The scenario
You've just joined Kestrel Freight's network team, which wants to stop configuring routers one SSH session at a time. Before any Python, you need a workstation you're fluent with: Bash, files and pipes, SSH that doesn't nag for passwords, and a clear picture of which management services each router offers. By the end of this lab your workstation will report on a syslog file, check management ports, and back up both routers with one command.
| Device | Role | Interface | Address |
|---|---|---|---|
| devbox | Automation workstation (Ubuntu desktop) | eth0 | 10.10.20.10/24 |
| r1 | Branch router, IOS 15.9 (IOSv) | Gi0/0 | 10.10.20.11/24 |
| xe1 | WAN router, IOS XE 17.3 (CSR 1000v) | Gi1 | 10.10.20.21/24 |
Topology: all three sit on the management LAN 10.10.20.0/24, so no gateway is needed between them. Device login: netops / NetOps-Lab1 (privilege 15).
What you’ll practise
- Manage files and directories, permissions and environment variables in Bash
- Turn a raw syslog file into a report with grep, awk, sort and uniq
- Check management ports (SSH 22, Telnet 23, HTTP 80, HTTPS 443, NETCONF 830) from the command line
- Log in to IOS and IOS XE with SSH, run one-shot commands and install an SSH public key on both
- Write a safe Bash script (shebang, set -euo pipefail, loops, exit codes) that backs up device configurations
The tasks
- Find your way around Bash
- Use environment variables
- Turn a syslog file into a report
- Check your addressing and reachability
- Check the management ports
- Log in with SSH and run one-shot commands
- Log in with a key instead of a password
- Back up both routers with one script
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
- devbox
eth0to Mgmt (network) - r1
Gi0/0to Mgmt (network) - xe1
Gi1to Mgmt (network)
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| devbox | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 1,024 MB |
| r1 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| xe1 | Cisco CSR 1000v | csr1000vng-universalk9.17.03.08a-serial | 1 vCPU, 4,096 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
Network Automation - CCNA and CCNP Automation guided labs.Open
01 - Your automation workstation - Bash SSH keys and management portsand 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 Network automation labs
Related labs in other courses
CloudLabBox is independent of Cisco. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.