200-301Lab

The core router came back knowing nothing

about 20 min
Exit
10.62.12.0/2410.62.0.0/30G0/1G0/110.62.0.4/30G0/2G0/210.62.13.0/24OPS10.62.12.20R110.62.12.1R2coreR310.62.13.1APP110.62.13.50
Ops on the left, the replaced core in the middle, the application site on the right.upshutno address
user EXEC

Start with enable, then configure terminal. Type a command, or use one below.

This is a simulated device. Output is computed from the topology, not from real hardware.

The core router R2 failed last night and the spare went in with the interface addresses and nothing else. R1 at Ops and R3 at the application site were not touched: each still sends everything it does not know to R2. This morning Ops cannot open the application server and the server team cannot reach Ops either.

Give R2 what it needs to carry traffic between the two sites in both directions, then save it.

Objectives

0 / 3

Checked against the configuration you build. Checking is free and unlimited.

  • Ops at 10.62.12.20 can reach the application server at 10.62.13.50 (not checked yet)

  • The application server can reach Ops at 10.62.12.20 (not checked yet)

  • The core router has saved the running configuration (not checked yet)

Your configuration is kept in this browser, so you can come back to it. Start over clears it.

The core router came back knowing nothing | CCNA lab | FirstTry