zNetLaB › Guided labs › Security
AAA — RADIUS for remote logins, local for the console
Security Advanced 4 devices 4 checked tasks 100 points Plan lab
Move the router’s logins to AAA. Remote sessions authenticate against the RADIUS server and fall back to the local database only if it cannot be reached; the console uses the local database on a list of its own, so a dead server can never lock you out of it. You build it in a browser, type real commands at each device, and every task below is
checked against the running configuration — so you find out it is wrong before anybody else does.
Open this lab in the simulator
The simulator runs in your browser with nothing to install. This lab is part of the full simulator: open it free for 7 days with a new account, then with a plan. It needs an account, which keeps your progress.
The scenario
Move the router’s logins to AAA. Remote sessions authenticate against the RADIUS server and fall back to the local database only if it cannot be reached; the console uses the local database on a list of its own, so a dead server can never lock you out of it.
Your role: a security engineer. Level: Advanced Done when: all 4 goals show as passed (100 points).
Network status
Devices: 1 router, 1 switch, 1 server, 1 PC, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. R1 starts with addresses (G0/0 10.0.0.1/24). RADIUS is a host with 10.0.0.100/24, gateway 10.0.0.1. Admin is a host with 10.0.0.20/24, gateway 10.0.0.1. SW starts with an empty configuration. Known problems
The network worked and now does not: the scenario above says what users report. The cause is a configuration fault, not a cable. Find it with show commands (interfaces, routes, neighbours, running-config) before you change anything; fix only what is wrong. Goals
AAA is enabled (20 pts) A RADIUS user can log in on the VTY lines (30 pts) The console authenticates the local user on its own list (25 pts) R1 reaches the RADIUS server (25 pts) The activity, in order
AAA is enabled Why: Each goal is a state the lab can check on the running device. Verify with: show running-config A RADIUS user can log in on the VTY lines Why: Each goal is a state the lab can check on the running device. Verify with: show running-config The console authenticates the local user on its own list Why: Each goal is a state the lab can check on the running device. Verify with: show running-config R1 reaches the RADIUS server Why: A ping needs a route in BOTH directions. This is the end-to-end proof that everything before it worked. Verify with: ping 10.0.0.100 Tips
Work in the order given: later goals depend on the earlier ones. After every change, run the verify command before moving on; do not guess. Stuck? Read the verify output first. It names the interface, neighbour or route that is wrong. Why this matters
Move the router’s logins to AAA. Remote sessions authenticate against the RADIUS server and fall back to the local database only if it cannot be reached; the console uses the local database on a list of its own, so a dead server can never lock you out of it.
What you will be able to do
AAA is enabled
A RADIUS user can log in on the VTY lines
The console authenticates the local user on its own list
R1 reaches the RADIUS server
The network
ISR 2911, Catalyst 2960-24TT, Server, PC — 4 devices in all, already cabled.
Gi0/0 10.0.0.1/24 Fa0/1 Fa0 Fa0/2 Fa0 Fa0/3 R1 SW RADIUS 10.0.0.100/24 · gw 10.0.0.1 Admin 10.0.0.20/24 · gw 10.0.0.1 Drawn from this lab: devices, cables, ports and the addresses already set. Device Model Address already set
R1 ISR 2911 configure it SW Catalyst 2960-24TT configure it RADIUS Server 10.0.0.100 / 255.255.255.0 gw 10.0.0.1 Admin PC 10.0.0.20 / 255.255.255.0 gw 10.0.0.1
Cabling
R1 Gi0/0 ↔ SW Fa0/1 RADIUS Fa0 ↔ SW Fa0/2 Admin Fa0 ↔ SW Fa0/3
What is configured at the start
These are already configured when the lab opens — including, where this is a troubleshooting lab, the fault itself:
R1 interface g0/0
ip address 10.0.0.1 255.255.255.0
no shutdown
exit
username backup secret Local123 Tasks, and how each one is checked
Every task is decided by reading the live network — a neighbour in FULL, a ping that succeeds, a line in the running configuration — not by looking for a keyword you typed. The same command shows you what the lab sees.
# Task Pts How to verify it yourself
1 AAA is enabled 20 Checked automatically against the device’s live state (aaaNewModel). 2 A RADIUS user can log in on the VTY lines 30 Checked automatically against the device’s live state (aaaLogin). 3 The console authenticates the local user on its own list 25 Checked automatically against the device’s live state (aaaLogin). 4 R1 reaches the RADIUS server 25 On R1: ping 10.0.0.100 must succeed.
Stuck? Ask the coach
Tell the coach what you see or what you tried. It gives you a hint, not the answer, the way a senior engineer would. Included with a free trial or any plan.
Ask the coach
Reference solution
Try it yourself first — the lab checks your work either way. This is one configuration that makes every task pass, device by device:
R1 aaa new-model
radius server RAD1
address ipv4 10.0.0.100 auth-port 1812
key R4diusKey
exit
aaa authentication login default group radius local
aaa authentication login CONSOLE local
line con 0
login authentication CONSOLE
exit
line vty 0 4
transport input telnet ssh
exit Where this is examined
This lab practises these topics in the zNetLaB certification courses:
AAA, passwords, VPN and wireless security — CCNA · Security Fundamentals Device access control, AAA, CoPP — CCNP Enterprise · ENCOR · Security AAA, uRPF, CoPP, IPv6 first-hop security — CCNP Enterprise · ENARSI · Infrastructure Security Access control: ACLs, AAA, remote access and VPNs — CompTIA Network+ · Network Security Authentication, authorisation and accounting — CompTIA Security+ · General Security Concepts Identity and access management — CompTIA Security+ · Security Operations AAA, RADIUS/TACACS+, 802.1X and identity services — CCNP Security Core · Secure Network Access, Visibility and Enforcement
Related labs
Where to start
The lessons all guided labs plans
CCNA®, CCNP® and Cisco® are trademarks of Cisco Systems, Inc. zNetLaB is not affiliated with or endorsed by Cisco.