CCNA 200-301 v1.1 reference — IP Connectivity

IPv6 static routing

IPv6 static routes with global unicast and link-local next hops, the interface argument link-local requires, and verification.

Objective 3.3v1.1 exam target

Quick Reference Handbook

Route forms and link-local next hops

IPv6 static route forms

Form	Syntax	When to use
Global-unicast next hop	`ipv6 route <prefix> <global-next-hop>`	Standard on multiaccess links — same logic as IPv4
Link-local next hop	`ipv6 route <prefix> <interface> <link-local-next-hop>`	When the next hop is fe80::* — the interface argument is REQUIRED
Exit interface only	`ipv6 route <prefix> <interface>`	Point-to-point links only
Host route	`ipv6 route <host>/128 <next-hop>`	Single-address precision

Because link-local addresses exist on every link and are ambiguous without a link context, IOS requires the exit interface whenever the next hop is fe80::*: ipv6 route 2001:db8:200::/64 gi0/1 fe80::2. This is a common exam and config-trap detail.

Two valid forms for one route

Prefix: 2001:db8:200::/64
Link: Ethernet to neighbor fe80::2 / 2001:db8:1::2

Global form: ipv6 route 2001:db8:200::/64 2001:db8:1::2 — clean recursive lookup.
Link-local form: ipv6 route 2001:db8:200::/64 gigabitethernet0/1 fe80::2 — interface required.
Both produce the same installed route; the link-local version makes the exit explicit.

Prefer global unicast next hops; use interface+link-local when the neighbor only advertises link-local.

Configuration and verification

IPv6 static routes

Route 2001:db8:200::/64 via next-hop 2001:db8:1::2 — Privileged EXEC → Global configuration

Cisco IOS / IOS XE

ipv6 unicast-routing enabled.

configure terminal
ipv6 route 2001:db8:200::/64 2001:db8:1::2
 end

Verify

show ipv6 route static
show ipv6 route 2001:db8:200::/64
ping ipv6 2001:db8:200::5

S route appears with the correct prefix and next-hop.
Reachability requires the next-hop itself to resolve via ND.

Changes device configuration.

$ show ipv6 route static (interpreted)

S 2001:DB8:200::/64 [1/0]Static route, AD 1.

via 2001:DB8:1::2Resolved global next hop.

S 2001:DB8:300::/64 [1/0]

via FE80::2, GigabitEthernet0/1Link-local next hop — note the interface qualifier.

Common mistakes

Specifying a link-local next hop without the interface — IOS rejects or misapplies it.
Forgetting ipv6 unicast-routing — routes install but nothing forwards.
Assuming IPv6 ND finds next hops across routers — next-hop resolution is link-local scope only.
Using exit-interface-only on multiaccess links — same ARP-style problem, worse with ND.

IPv6 static route installed but unreachable

Observation: The route is in show ipv6 route but traffic fails.

Hypotheses

Link-local next hop configured without interface
ND resolution failing for the next hop
Missing ipv6 unicast-routing

Check	Indicates
`show ipv6 route` detail	Confirm the next-hop and interface actually resolved.
`show ipv6 neighbors`	Next hop's MAC resolution proves L2 connectivity.
Return routes on the far side	Static IPv6 is one-directional just like IPv4.

Correction: Fix the next-hop form or ND path, and verify return routing.

Ping/traceroute IPv6 completes both ways.

On this page

Route forms and link-local next hops
Configuration and verification

Related resources

Practise this topic Source topic 33: IPv6 (Part 3 - Static Routing)Practise topic 33 deck

Sources

Cisco CCNA 200-301 v1.1 Exam Topics (official PDF) — reviewed 2026-11-02
Cisco — IPv6 Command Reference — reviewed 2026-11-02
RFC 8200 — IPv6 Specification — reviewed 2026-11-02

Targets CCNA 200-301 v1.1 objectives. Supplemental blocks are labeled beyond exam scope.