IPv6 Static Routes on VRP

IPv6 static routing in the HCIA toolkit

After you can address interfaces and explain ND/SLAAC, you still need reachability between prefixes. On Huawei VRP, the IPv6 counterpart of ip route-static is ipv6 route-static. H12-811 expects the command pattern, the verification command family, and the same design discipline you used for IPv4 statics: correct prefix length, reachable next hop, return path, and table verification.

IPv6 static routing does not reinvent longest match or preference theory. It applies those rules inside the IPv6 routing table. Your new failure modes are mostly IPv6-specific: forgetting ipv6 enable, using the IPv4 routing display, compressing addresses incorrectly in the command, or pointing a static at a link-local next hop without the right interface.

Prerequisites before the first static

Complete this checklist on each router in the path:

Example addressing on a simple two-router link plus LANs:

[R1] ipv6
[R1] interface GigabitEthernet0/0/0
[R1-GigabitEthernet0/0/0] ipv6 enable
[R1-GigabitEthernet0/0/0] ipv6 address 2001:db8:12::1/64
[R1] interface GigabitEthernet0/0/1
[R1-GigabitEthernet0/0/1] ipv6 enable
[R1-GigabitEthernet0/0/1] ipv6 address 2001:db8:1::1/64

[R2] ipv6
[R2] interface GigabitEthernet0/0/0
[R2-GigabitEthernet0/0/0] ipv6 enable
[R2-GigabitEthernet0/0/0] ipv6 address 2001:db8:12::2/64
[R2] interface GigabitEthernet0/0/1
[R2-GigabitEthernet0/0/1] ipv6 enable
[R2-GigabitEthernet0/0/1] ipv6 address 2001:db8:2::1/64

R1’s LAN is 2001:db8:1::/64; R2’s LAN is 2001:db8:2::/64; the interconnect is 2001:db8:12::/64.

Core command: ipv6 route-static

General form (conceptual):

ipv6 route-static <destination> <prefix-length> { <next-hop> | <interface> [ <next-hop> ] } [ preference <value> ]

Exam-standard example matching common HCIA wording:

[R1] ipv6 route-static 2001:db8:2:: 64 2001:db8:12::2
[R2] ipv6 route-static 2001:db8:1:: 64 2001:db8:12::1

Forms you should recognize

Global/ULA next hop (common in labs):

[R1] ipv6 route-static 2001:db8:2:: 64 2001:db8:12::2

Default route (::/0):

[R1] ipv6 route-static :: 0 2001:db8:12::2

Here destination :: with prefix-length 0 is the IPv6 default—parallel to 0.0.0.0 0.0.0.0 on IPv4.

Link-local next hop (operationally common in real IPv6):

[R1] ipv6 route-static 2001:db8:2:: 64 GigabitEthernet0/0/0 FE80::2

Because every interface can have an fe80:: address, outbound interface disambiguates which link the next hop lives on. Exam items may show either GUA next hops (clearer for beginners) or link-local next hops (more “real IPv6”).

Verification: the IPv6 table, not the IPv4 table

<Huawei> display ipv6 routing-table
<Huawei> display ipv6 routing-table protocol static
<Huawei> display ipv6 routing-table 2001:db8:2::10

Also verify underlay:

<Huawei> display ipv6 interface brief
<Huawei> ping ipv6 2001:db8:12::2
<Huawei> ping ipv6 2001:db8:2::1

If the next hop does not answer, fix addressing/ND before blaming the static syntax.

Removal

Use undo with matching parameters:

[R1] undo ipv6 route-static 2001:db8:2:: 64 2001:db8:12::2

Match destination, length, and next hop carefully—partial undo lines may not delete the intended route.

Longest match and preference still rule

Selection logic does not flip for IPv6:

1. Longest prefix match among covering IPv6 routes.
2. Preference among same-prefix candidates (lower better).
3. Cost/tie-breakers as applicable.

Floating IPv6 statics use the same preference knob as IPv4 statics: better (lower) preference primary, worse preference backup.

End-to-end lab narrative

Goal: Host on R1 LAN (2001:db8:1::10) pings host on R2 LAN (2001:db8:2::10).

1. Both hosts/routers have IPv6 enabled and on-link GUAs.
2. R1 has static to 2001:db8:2::/64 via 2001:db8:12::2.
3. R2 has static to 2001:db8:1::/64 via 2001:db8:12::1.
4. display ipv6 routing-table on each shows the remote LAN as Static.
5. ND resolves the interconnect next hops’ MACs.
6. Bidirectional pings succeed.

One-way ping almost always means a missing return static (or missing return dynamic route)—the same classic IPv4 static failure, now on the IPv6 RIB.

Default route design notes

Stub site R1 with a single exit to R2:

[R1] ipv6 route-static :: 0 2001:db8:12::2

R1 no longer needs a static per remote enterprise prefix if R2 (or the core) knows them. R2 still needs routes back to R1’s LANs—or a matching default/dynamic design. Default routes do not override more specific prefixes when those exist.

Comparison table: IPv4 vs IPv6 static on VRP

Memorizing this side-by-side chart converts IPv4 static skills into IPv6 static skills with minimal new theory.

Troubleshooting matrix

Operational best practices

1. Document every IPv6 static: prefix, length, next hop, interface, purpose.
2. Prefer consistent lab style (all GUA next hops or all link-local+interface).
3. Configure both directions in pure static designs.
4. Verify with IPv6 display commands and ping ipv6.
5. save after success if persistence is required.
6. Move to dynamic IPv6 routing (for example OSPFv3 in broader studies) when scale outgrows statics—HCIA still requires static mastery first.

Exam traps for IPv6 static routes

• Writing ip route-static for an IPv6 prefix.
• Using dotted masks (255.255.0.0) instead of prefix-length integers.
• Configuring ipv6 route-static 2001:db8:1::/64 … with Cisco-like slash in the wrong parameter position—know VRP’s destination then length form taught for HCIA: 2001:db8:1:: 64.
• Default as something other than ::/0 (:: with length 0).
• Looking at the IPv4 routing table to verify IPv6.
• Forgetting return routes.
• Assuming connected IPv4 routes somehow forward IPv6 (dual-stack tables are separate).
• Ignoring that next-hop GUA must be on a connected IPv6 subnet (or recursively reachable).

Mastery checklist

• ipv6 + ipv6 enable + ipv6 address complete before statics.
• Can write ipv6 route-static 2001:db8:2:: 64 2001:db8:12::2 from memory.
• Can write IPv6 default ipv6 route-static :: 0 <next-hop>.
• Verifies with display ipv6 routing-table / protocol static.
• Explains FE80 next-hop + interface requirement.
• Applies longest match and preference without IPv4/IPv6 confusion.

Chapter synthesis

IPv6 on HCIA-Datacom is a stack of skills: read and classify addresses, use ND/ICMPv6 instead of ARP/broadcast, choose SLAAC vs stateful vs stateless DHCPv6, and steer traffic with ipv6 route-static. If you can configure a dual-router lab with GUAs, confirm neighbors, and install bidirectional statics verified in display ipv6 routing-table, you have the operational core of this chapter for H12-811.