Answers: IPv6 Static Routes 3

By certskills August 17, 2016 09:10

This most recent lab asked you to configure a bunch of static IPv6 routes on the same router. Some had the exact same destination subnet, and some created host routes that overlapped with other static routes. And all were assigned different administrative distance values. Which ones would you expect to see in the router’s IPv6 routing table? Take a look at today’s answer post after taking your own attempt at configuring the lab per the original lab post.



Figure 1: Router Triangle Topology


Example 1: R1 Config



This lab is focused with two primary goals in mind. First, to further practice in using IPv6 static routes to remote networks using both networks and host routes. Second, to highlight some of the differences in forwarding behavior when using multiple different administrative distances.

There are two major things you need to keep in mind when determining which route will be used to a network: First, is this the most specific route to the destination? Second, if so, does this route have the lowest administrative distance? Keep in mind that the order of these two questions is very important.

For this lab, you were tasked with configuring five different static IPv6 routes. Three of these routes offer different paths to R5’s LAN subnet. The requirements tell you to use three different administrative distances. Those three routes are:

  1. The first route to configure for R5’s LAN uses R2 as a next hop and an administrative distance of 50; the LAN between R1 and R2 uses the 3000:1:2::/64 network with R2 being configured with the 3000:1:2::2 address as the next hop address. The command to configure this route would be ipv6 route 2000::/64 3000:1:2::2 50.
  2. The second route to configure for R5’s LAN uses R3 as a next hop and an administrative distance of 40; the LAN between R1 and R3 uses the 3000:1:3::/64 network with R3 being configured with the 3000:1:3::2 address as the next hop address. The command to configure this route would be ipv6 route 2000::/64 3000:1:3::2 40.
  3. The third and final route to configure for R5’s LAN uses R4 as a next hop and an administrative distance of 60; the LAN between R1 and R4 uses the 3000:1:4::/64 network with R4 being configured with the 3000:1:4::2 address as the next hop address. The command to configure this route would be ipv6 route 2000::/64 3000:1:4::2 60.

Ask yourself at this point, which of these routes would be preferred when selecting a path from R1 to R5’s LAN?

The other two routes requested in for this lab are host routes for PC2 and PC4 which potentially alter the routing behavior of R1. The first was a host route for PC2 using R2 as a next hop and an administrative distance of 100. The command to configure this route would be ipv6 route 2000::102/128 3000:1:2::2 100. The second was a host route for PC4 using R4 as a next hop and an administrative distance of 110; the command to configure this route would be ipv6 route 2000::104/128 3000:1:4::2 110. Note that the use of the /128 prefix length is the IPv6 equivalent of using the subnet mask.

Ask yourself now, will either of these host routes alter the routing behavior of traffic from R1 to PC2 and PC4? The answer is yes, this is because each of these routes will be more specific than the previous three routes for the 2000::/64 subnet. R5 only considers the administrative distance if the destination of the route is exactly the same.

The two host routes cause R5 to forward packet of those two hosts over those specific routes:

  • Traffic destined for PC2 will always go through R2 assuming the interface is still operational.
  • Traffic destined for PC4 will always go through R4 assuming that interface is still operational.

Just to complete the idea, Example 2 lists router R1’s routing table after adding the configuration in this lab. It shows only one of the three static routes to subnet 2000:://64, the one with 3000:1:3::2 as next hop, with administrative distance 40. Why? Because those three routes have the exact same destination (2000::/64), but different administrative distance values, so router R1 adds only the router that has the best AD. However, for the two host routes, the destination of each route is unique, so the AD values of 100 and 110 were not needed by R1 to choose between multiple static routes to the same destination.

Example 2: R1 IPv6 Routing Table


Answers: SNMPv2c Secured with ACLs
SNMPv3 1
By certskills August 17, 2016 09:10
Write a comment


  1. Wendell info August 18, 16:58

    This is test comment 2

    Reply to this comment
  2. Wendell info August 18, 17:09

    this is test comment 3

    Reply to this comment
  3. Borradacho September 23, 05:49

    Just want to say thanks a lot for the great job! Now I’m moving through the OCG ICND1 book with the help of your tasks and labs. I don’t like posting comments, because often the tasks and answers are enough clear for me. But this time I do this in order you to know that your work is highly appreciated. Great book, great blog.
    Keep on writing!

    Reply to this comment
  4. Adrian January 9, 13:30

    I don’t understand why in the routing table last two static routes are repeated (lines 14-21).
    Amazing work Wendell! Thank you!

    Reply to this comment
    • CCENTSkills January 12, 15:36

      You’re welcome! Glad you’re enjoying the blog. I’m looking forward to creating some new content this year!

      On your question… copy/paste error. You’re thinking correctly, the second pair was unnecessarily repeated. Thanks for letting me know! I just removed them.

      Reply to this comment
  5. Mansoor May 27, 14:55

    Hi Wendall,

    Appreciate your work for this blog. These labs are great for practice and your explanations are precise.

    Reply to this comment
  6. Ari July 18, 03:13

    dont we have to create any route back for r1

    Reply to this comment
    • CCENTSkills July 25, 10:30

      Hi Ari,
      The lab is designed so that the other routers (those other than R1) won’tneed any static routes. Note that all the IPv6 subnets are connected to at least one of the “other” routers, so the fact that they all run EIGRP for IPv6 should take care of advertising routes to all the subnets in the figure.

      Reply to this comment
  7. Peter September 12, 13:27

    I couldn’t get this one to work with 2911 routers in PT. Firstly, the routers silently ignored all the EIGRP interface commands, and inserted a ‘shutdown’ in the EIGRP config which could not be removed. Then, the static routes in R1 were accepted and showed up in the config, but ‘sh ipv6 routes’ only showed L and C routes.

    Strangely, static route exercises 1 and 2 worked fine.

    Are these issues deliberate restrictions in PT or are they likely to be bugs? Or am I still doing something wrong (hard to imagine what with such straightforward exercises)?

    Reply to this comment
    • Peter September 12, 16:13

      #redface I put it together in a different order and it worked. So probably a user error. However, in the problem statement you might want to review the test instructions, which say to ping each PC from the others. Since they are all on the same subnet that’s not terribly revealing. Traceroutes from R1 show different paths, so you might want to put that in the instructions instead, or perhaps add a PC connected through R1 to ping/trace the others (although that would make a fairly busy network even busier).

      Reply to this comment
  8. Chris March 16, 12:19

    Hi Wendell, at the bottom of page 591 in Vol 1, should that not be R3 in example 25-12? It reads R2 in the second box.

    Reply to this comment
View comments

Write a comment

Leave a Reply to Adrian Cancel reply