Once you have a basic understanding of IPv6 and configuring IPv6 interfaces you can then build networks using static routes! This lab will discuss and demonstrate the configuration and verification of IPv6 static routing.
If you completed Labs 12-1 – The Basics of Internet Protocol Version 6 (IPv6) and Lab 12-2 – Configuring IPv6 Interface Addressing then you should have a solid foundational understanding IPv6. Now its time to move into IPv6 routing technologies.
The IPv6 routing technologies that will be discussed and demonstrated in the Free CCNA Workbook includes IPv6 static routing, RIPng (Routing Information Protocol next generation) and OSPFv3 (Open Shortest Path First version 3).
You will learn two types of IPv6 static routes in this lab which are the standard administrative static routes where you have the ability to set the administrative distance following the route statement as well as default static routes used as a last resort route if no particular route exist for a destination of incoming traffic.
Before you can configure IPv6 routing on a Cisco router you must first enable the Cisco router to route IPv6 by executing the command ipv6 unicast-routing in global configuration mode.
IPv6 static routing is much like IPv4 static routing so if you need to review IPv4 static routing then take a look back at Lab 6-1 – Configuring Static Routing.
Unlike IPv4 static routing, with IPv6 you have the ability to use either the global unicast address or link-local address as the next hop in the static route statement. When working with IPv6 dynamic routing protocols which will be discussed in the next 2 labs, the next hop will be the neighbors link-local IPv6 address and not their global unique assigned ipv6 address. However when configuring a static route with a link-local IPv6 address as the next hop you must specify the egress interface. For all intensive purposes, using either/or will achieve the same desired effect.
When configuring an IPv6 static route you’ll use the ipv6 route X:X:X:X::/X X:X:X:X::X whereas the first IPv6 address in the static route statement is the network and the 2nd IPv6 address is the next hop in the transit path to reach that network. You also have the ability to assign the IPv6 static route an administrative distance the same way you would assign administrative distance to an IPv4 static route by following the route statement with an administrative distance (1-254). Keep in mind the administrative distance of 255 is considered “unreachable”. An example of an IPv6 static route using an administrative distance of 224 is; ipv6 route 2001:ABC:123:FADE::0/64 2001:ABAD:BEEF:1234::1 224. Keep in mind when using an IPv6 link-local address as the next hop you must specify the egress (exiting) interface. I.e; ipv6 route 2001:ABC:123:FADE::0/64 Serial0/1 FE80::C800:10FF:FE1C:8 224.
Looking back at 12-1, you’ll see in the chart provided that the “unspecified” network is represented as ::/0. This is the same concept as the IPv4 0.0.0.0/0 address. You can configure an IPv6 static default route by using ::/128 as the destination network followed by the next-hop. I.e; ipv6 route ::/128 2001:ABAD:BEEF:1234::1 200
In this lab you will configure a static route on R1 to reach R2’s Loopback0 network using R2’s Serial0/1 IPv6 link-local address as the next-hop then configure a default IPv6 route on R2 using R1’s Serial0/1 IPv6 link-local address as the next-hop.
Familiarize yourself with the following new command(s);
|ipv6 route x:x:x:x::0/1-128 egress-interface x:x:x:x:x:x:x:x||This command when executed in interface configuration mode sets an IPv6 address on the specified interface. The syantax is ipv6 route network egress interface next-hop ipv6 address.|
The following logical topology shown below is used in this lab;
Objective 1. – Configure a static route with the administrative distance of 200 on R1 pointing towards R2’s Serial0/1 link-local IPv6 address to reach the network assigned to R2’s loopback0 interface.
To configure this static route statement you must first obtain the IPv6 link-local address of R2’s Serial0/1 interface as shown below;
R2>enable R2#show ipv6 interface Serial0/1 Serial0/1 is up, line protocol is up IPv6 is enabled, link-local address is FE80::C800:10FF:FE1C:8 No Virtual link-local address(es): Description: ### LINK TO FRAME RELAY SWITCH ### Global unicast address(es): 2001:ABAD:BEEF:1221::2, subnet is 2001:ABAD:BEEF:1221::/64 Joined group address(es): FF02::1 FF02::1:FF00:2 FF02::1:FF1C:8 MTU is 1500 bytes ICMP error messages limited to one every 100 milliseconds ICMP redirects are enabled ICMP unreachables are sent ND DAD is enabled, number of DAD attempts: 1 ND reachable time is 30000 milliseconds (using 17988) R2#
Once you’ve obtained R2’s IPv6 link-local address you can now configure the static route statement on R1 as shown below;
R1>enable R1#configure terminal Enter configuration commands, one per line. End with CNTL/Z. R1(config)#ipv6 unicast-routing R1(config)#ipv6 route 2001:ABAD:BEEF:2002::0/64 Serial0/1 FE80::C800:10FF:FE1C:8 R1(config)#end R1#
Objective 2. – Configure a default static route on R2 pointing towards R1’s Serial0/1 globally unique IPv6 unicast address to reach all unknown networks including the network assigned to R1’s loopback0 interface.
R2#configure terminal Enter configuration commands, one per line. End with CNTL/Z. R2(config)#ipv6 route unicast-routing R2(config)#ipv6 route ::/0 2001:ABAD:BEEF:1221::1 R2(config)#end R2#
Objective 3. – Verify that R2’s Loopback0 has IPv6 communication to R1’s Loopback0 network using ping.
R2#ping 2001:ABAD:BEEF:1001::1 source Loopback0 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2001:ABAD:BEEF:1001::1, timeout is 2 seconds: Packet sent with a source address of 2001:ABAD:BEEF:2002::1 !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 8/37/68 ms R2#