CCNA lab 19 of 46

Static and floating static routes for IPv4 and IPv6

Connect a head office and a branch over a private WAN with an Internet backup, using every kind of static route in both IPv4 and IPv6, then fail the WAN and discover why static failover needs both ends to notice.

Run this lab

It needs Lite: its 5 nodes are set to 5 vCPU and 5,120 MB in total. That fits the free demo too.

In your workspace: Shared, then CCNA 200-301 guided labs, then 19 - Static and floating static routes for IPv4 and IPv6

Try it free for 30 minutesRun it on Lite from £3 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

Level
Intermediate
Time
About 60 minutes
Nodes need
5 vCPU, 5,120 MB
Smallest plan
Lite

The scenario

Ferrybridge Opticians has a head office (R1, LAN 10.19.1.0/24 and 2001:db8:19:1::/64) and a branch (R2, LAN 10.19.2.0/24 and 2001:db8:19:2::/64). They're joined by a private WAN link, and both also connect to the same ISP, which can carry traffic between the sites if the WAN fails. The routers are addressed but have no routes. The company doesn't want a routing protocol for two sites, so you'll do it all with static routes.

LinkR1R2ISP
Private WANGi0/0 10.0.12.1/30, 2001:db8:0:12::1Gi0/0 10.0.12.2/30, 2001:db8:0:12::2–
R1–ISPGi0/2 10.0.13.1/30, 2001:db8:0:13::1–Gi0/0 10.0.13.2, 2001:db8:0:13::2
R2–ISP–Gi0/2 10.0.23.1/30, 2001:db8:0:23::1Gi0/1 10.0.23.2, 2001:db8:0:23::2
LANsGi0/1 10.19.1.1/24, 2001:db8:19:1::1/64Gi0/1 10.19.2.1/24, 2001:db8:19:2::1/64Lo0 203.0.113.1, 2001:db8:ffff::1 ("Internet")
Cloud backup appliance––Lo1 198.51.100.10/32, 2001:db8:ffff:10::10/128

Link-locals: R1 fe80::1, R2 fe80::2, ISP fe80::3 on every interface. PC1 is 10.19.1.10, PC2 10.19.2.10; both will get IPv6 by SLAAC. The ISP already routes both LANs back to their own routers.

What you’ll practise

  • Configure IPv4 network routes with recursive, directly connected and fully specified next hops
  • Add default routes and a host route that overrides them
  • Build floating static routes as a backup path and test failover
  • Configure IPv6 network, host, default and floating static routes, including link-local next hops
  • Verify static routing with show commands and traceroute

The tasks

  1. Route between the sites over the WAN (IPv4)
  2. Send everything else to the ISP
  3. Steer one host with a host route
  4. Build the backup path with floating static routes
  5. Repeat it for IPv6
  6. Verify the whole design

The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.

Topology and devices

The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.

Topology of Static and floating static routes for IPv4 and IPv65 nodes, 5 links. Every link is listed as text below the diagram.R1R2ISPPC1PC2Gi0/1eth0Gi0/1eth0Gi0/2Gi0/0Gi0/2Gi0/1Gi0/0Gi0/0
5 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Nodes in Static and floating static routes for IPv4 and IPv6, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
R1Cisco IOSvvios-adventerprisek9-m.SPA.159-3.M61 vCPU, 1,024 MB
R2Cisco IOSvvios-adventerprisek9-m.SPA.159-3.M61 vCPU, 1,024 MB
ISPCisco IOSvvios-adventerprisek9-m.SPA.159-3.M61 vCPU, 1,024 MB
PC1VPCS hostBuilt in to EVE-NGCounted as 1 vCPU, 1,024 MB
PC2VPCS hostBuilt in to EVE-NGCounted as 1 vCPU, 1,024 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder CCNA 200-301 guided labs.

  3. Open 19 - Static and floating static routes for IPv4 and IPv6 and start its nodes, then open Lab Tasks for the scenario and the steps.

The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.

More CCNA labs

All CCNA labs

Related labs in other courses

CloudLabBox is independent of Cisco. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.