CloudLabBox
Try the free demo

CCNP ENARSI lab 29 of 35

Device management: console, VTY, SSH, HTTPS, SCP and TFTP

Harden how a router is managed: console and VTY settings, login protection, SSH version 2 only, HTTPS instead of HTTP, an SCP server for configuration pulls, and TFTP backups, each proven from a real Linux management server.

Run this lab

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

In your workspace: Shared, then CCNP ENARSI 300-410 guided labs, then 29 - Device management - console VTY SSH HTTPS SCP and TFTP

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 70 minutes
Nodes need
2 vCPU, 1,536 MB
Smallest plan
Lite

The scenario

Shrike Freight's routers were set up years ago with Telnet, a plain HTTP server and the password cisco everywhere. An audit has failed the network. You'll bring R1 up to the company's management standard and prove each service from the management server SRV, a Linux host on the management LAN.

The standard:

  • Named admin accounts only (netops / Netops-Pass26, privilege 15); enable secret Enable-Pass26; no clear-text passwords.
  • Console and VTY sessions time out after 5 minutes; logins are blocked for 60 s after 3 failures in 30 s.
  • SSH version 2 only on VTY, from the management LAN only. No Telnet, no HTTP; HTTPS with local logins.
  • Configurations can be pulled over SCP and are backed up to TFTP on SRV.
DeviceInterfaceAddressNotes
R1Gi0/110.29.100.1/24management LAN
SRVeth010.29.100.100/24Linux management server: TFTP root /srv/tftp, helper scripts in /opt/lab

What you’ll practise

  • Harden console and VTY lines and protect logins against guessing
  • Enable SSH version 2 with RSA keys and remove Telnet
  • Replace the HTTP server with HTTPS using local authentication
  • Enable the IOS SCP server (and the AAA it needs) and pull a configuration over SCP
  • Back up the configuration to TFTP without prompts

The tasks

  1. Accounts, passwords and lines
  2. SSH version 2 only, from the management LAN
  3. HTTPS instead of HTTP
  4. Pull the configuration over SCP
  5. Back up to TFTP without prompts

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 Device management - console VTY SSH HTTPS SCP and TFTP2 nodes, 1 link. Every link is listed as text below the diagram.R1SRVGi0/1eth0
2 nodes, with the interface names each link uses.
Every link, as text
  • R1 Gi0/1 to SRV eth0
Nodes in Device management: console, VTY, SSH, HTTPS, SCP and TFTP, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
R1Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
SRVEVE-NG GUI server (Docker)eve-gui-server:latest1 vCPU, 1,024 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 CCNP ENARSI 300-410 guided labs.

  3. Open 29 - Device management - console VTY SSH HTTPS SCP and TFTP 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 CCNP ENARSI labs

All CCNP ENARSI 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.