Open the lab

[ YOUR LAB FILE ]

Download the starting topology, then work through the lesson in SwitchLab.

Download SwitchLab Lab (.swlab)

  1. Save the .swlab file without renaming its extension.
  2. Open SwitchLab. Import and export controls currently require a desktop-width window. On a smaller screen, Tools → Fit brings the topology into view.
  3. Select Import Sandbox (folder icon), choose the downloaded file, and confirm the device and cable counts below.
  4. Select a device, then choose Open device on desktop or its name in the bottom bar on smaller screens. Select CLI for switches/routers or Desktop → Terminal for PCs. Enter enable only when the prompt ends in >.
  5. Follow this page beside the simulator. Use a free account to export your work. Reimport the original download to restart; export any work you want to keep first.

Prerequisites

  • Complete the focused lessons for the features used in this scenario.
  • For campus policy scenarios, complete VLANs, trunks, IPv4, OSPF and ACL lessons first.

Follow the CCNA study path · Browse all SwitchLab labs

Topology

Migrate a Routed Site from Static Routes to OSPF: starting network imported into the SwitchLab sandbox.
Starting topology captured in SwitchLab. Select the image to view it at full size.

4 devices · 3 links

Scenario

Both sites work with static routes. During an approved maintenance window, migrate them to single-area OSPF and remove the superseded static entries. A brief interruption during the transition is acceptable; the final handoff must prove dynamic routing.

Objectives

  • Implement or restore the approved network design without breaking required control paths.
  • Verify configuration, end-to-end behavior and completed-network persistence.
  • Produce an operational handoff with evidence and a deterministic reset path.

CCNA blueprint

200-301 v1.1 objectives — this lab covers the following specific skills, not every subtopic in the domain.

  • 1.6 — Apply and verify the scenario’s IPv4 addressing.
  • 3.4 — Configure or repair single-area OSPF.

Starting information

  • PC1 uses 10.10.10.0/24 through R1 g0/0=10.10.10.1; PC2 is 10.20.20.20/24 through R2 g0/0=10.20.20.1.
  • The g0/1 transit is 10.0.12.1/30 on R1 and 10.0.12.2/30 on R2. Preserve all cables and router addresses.
  • OSPF process 1 uses area 0 and router IDs 1.1.1.1 / 2.2.2.2; advertise the transit and both LANs while keeping g0/0 passive.
HostIPv4 addressMaskGateway
PC110.10.10.10255.255.255.010.10.10.1
PC210.20.20.20255.255.255.010.20.20.1
RouterInterfaceIPv4 addressMask
R1g0/010.10.10.1255.255.255.0
R1g0/110.0.12.1255.255.255.252
R2g0/010.20.20.1255.255.255.0
R2g0/110.0.12.2255.255.255.252
Device / portDevice / port
PC1 / eth0R1 / g0/0
R1 / g0/1R2 / g0/1
PC2 / eth0R2 / g0/0

Tasks

  1. Record working bidirectional traffic and the existing static-route sources before the change.
  2. Configure OSPF with the approved plan and remove the two superseded static routes.
  3. Verify FULL neighbors and remote OSPF routes; ensure no static route is masking a missing advertisement.
  4. Repeat both traffic directions, save/export/reload and document the migration and rollback using the original starter file.

Useful commands

show ip ospf neighbor
show ip route
show running-config
copy running-config startup-config

Progressive hints

Hint 1

Break the end-to-end path into host settings, local VLAN carriage, gateway reachability, route selection and any access policy.

Hint 2

Use a working control at each layer. Do not remove security controls or add broad routes just to make one ping succeed.

Hint 3

Compare each affected host, interface and route against the approved plan; use the earlier focused lessons for the exact command patterns.

Verification

  • The final network matches every approved addressing, VLAN, routing and policy requirement above.
  • Every required positive path succeeds and every forbidden path remains blocked.
  • Completed export/reload retains the result; reimporting the starter restores the original exercise.

Solution / walkthrough

Show Solution

Use enable only from a > prompt; if already at #, begin with configure terminal.

R1

Apply the approved OSPF process and keep the LAN passive; verify remote routes are learned dynamically.

enable
configure terminal
no ip route 10.20.20.0 255.255.255.0 10.0.12.2
router ospf 1
router-id 1.1.1.1
network 10.10.10.0 0.0.0.255 area 0
network 10.0.12.0 0.0.0.3 area 0
passive-interface g0/0
exit
end
copy running-config startup-config

R2

Apply the approved OSPF process and keep the LAN passive; verify remote routes are learned dynamically.

enable
configure terminal
no ip route 10.10.10.0 255.255.255.0 10.0.12.1
router ospf 1
router-id 2.2.2.2
network 10.20.20.0 0.0.0.255 area 0
network 10.0.12.0 0.0.0.3 area 0
passive-interface g0/0
exit
end
copy running-config startup-config

Run every verification check above after the changes. A saved configuration alone does not prove packet delivery.

Previous lab

Connect Departmental VLANs through Routed Gateways

Related labs

Related articles and tools

Next recommended lab

Small Office Deployment