Make the device API-ready

NetLab lab Advanced 4 tasks 30 points

Before a controller or Ansible can manage R1, it needs secure access. Set R1 up so automation over SSH will work:

Domain name example.com, 2048-bit RSA keys, SSH version 2.
A local user automation, privilege 15, secret Auto!Mate2026.
The vty lines use the local users and accept SSH only.

Then answer the questions about controller-based networking.

How it works: this is VulnTech NetLab, a network simulator running in your browser. Click a device in the diagram to open its console and type commands, just like on real equipment (? shows help, Tab finishes a word). Click a cable to inspect it. Tasks tick themselves off as you complete them; questions are answered in the box under each task. Your work is kept if you reload; Reset starts the network over.

Solution explanation

Automation tools and controllers reach devices over SSH (the southbound side), so SSH with key-based crypto and a real login is the foundation. Your own scripts call the controller's northbound REST API; the controller then uses the southbound API (NETCONF/RESTCONF/SSH) to program R1. SDN centralises the control plane; the devices keep forwarding (data plane).

Show solution

[R1]
enable
configure terminal
ip domain name example.com
crypto key generate rsa modulus 2048
ip ssh version 2
username automation privilege 15 secret Auto!Mate2026
line vty 0 4
login local
transport input ssh
end
[AUTO]
ssh -l automation 10.1.1.1
Auto!Mate2026
show privilege
exit