Lab R13: Locked out
Yesterday the administrator's PC reached both routers by SSH and the nightly copy of R1's configuration landed on R2. This morning nothing gets in. The servers that hold the company's accounts are switched off for maintenance all week, which nobody worried about, because every router is set to fall back to its own accounts. You still have both consoles. Find what was changed in the night and put each thing back the way the design on the diagram says, not merely into a state that lets you in.
What you will do
- Ticket 1: R1 refuses the connection
- Ticket 2: R1 refuses every account
- Ticket 3: R2 answers the wrong protocol
- Ticket 4: admin arrives as nobody
- Ticket 5: the nightly copy
- Save it
New in this lab: TACACS+, RADIUS, local, console, VTY, SSH, SCP.
How it is checked
Each of the 6 tasks is checked on the devices themselves as you finish it: the bench reads how the network is configured and what it does, not what you typed. The lab is done when all 6 pass.
The lessons it follows
It opens after these, and uses what they teach:
Open the lab benchIt needs a computer: phones and tablets are not supported.
