IPv6 Addresses on Hosts: Cert Guide PT Labs for ICND1 Chapter 32

Static routes may be the exception for most networks, but they make a great learning tool for newbies. The ICND1 100-105 book’s Chapter 32 hits static IPv6 routes (along with connected routes). Come join the fun with some Packet Tracer files to support the examples from the chapter.

A Quick Note about the New CCNA

For those of you reading this post between when it was posted in August 2019, and the date Cisco released their newest CCNA exam (200-301) in February 2020, just a few notes.

• • • This post is about the examples in a chapter of the books about the CCNA R&S and CCENT exams that Cisco offered from 2016 through early 2020.
    • I plan to update this post (and similar posts in the series) for the chapters in the new books for the CCNA 200-301 exam.
    • In the mean time, there’s plenty of time to get your CCNA R&S certification before February 2020 – so dig in!
    • You can preorder the CCNA 200-301 Official Cert Guide, Volume 1 from Cisco Press or from Amazon. The links to order Volume 2 should be active soon.

  Advice before You Begin

  The big idea is pretty simple: Repeat the Examples in the Official Cert Guide as part of your lab practice for CCNA.

  To get your head around what kind of content is here in the blog for these labs, read both of these posts or at least the second post:

  • • • Intro to the Cert Guide PT Labs
      • Details of how to use Cert Guide PT Labs

  After reading those posts, you have the context, so onward to the details!

   

  What’s in This Post

  Intro to the Book Chapter: A brief description of the topics in that chapter of the book.

  Chapter Examples and .PKT File Reference: A section that lists the examples in the chapter, the .pkt files supplied, and reminders/notes about cases in which we don’t supply all three files for any one example.

  Tips and Exceptions: When we build the files, we come across items that we think might confuse you when trying the examples with PT. We write those notes in this section!

   

  Intro to the Book Chapter

  The flow is simple enough. The examples begin with a look at the routes that appear after configuring IPv6 interface addresses. Following that, it works through all the variations of static IPv6 routes, with different forwarding instructions and different destinations (subnets, hosts, default).

   

  Chapter Examples and .PKT File Reference

  Download this ZIP file to get all the .pkt files for this chapter: 

  This table tells you what files to expect in the ZIP, and which examples happen to use interface IDs that can be exactly replicated in PT:

  Example	Topology File	Initial Config	Ending Config	Exact Match of Interface IDs?
  32-1	Yes	Yes	Yes	Yes
  32-2	Use 32-1	Use 32-1	Use 32-1	Yes
  32-3	Use 32-1	Use 32-1	Use 32-1	Yes
  32-4	Yes	Yes	Yes	Yes
  32-5	Use 32-4	Yes	Yes	Yes
  32-6	Use 32-4	Use 32-5	Use 32-5	Yes
  32-7	Use 32-4	Use 32-5	Use 32-5	Yes
  32-8	Yes	Yes	Yes	Yes
  32-9	Use 32-8	Use 32-8	Use 32-8	Yes
  32-10	Use 32-8	Yes	Yes	Yes
  32-11	Use 32-10	Use 32-10	Use 32-10	Yes
  32-12	Yes	Yes	Yes	Yes
  32-13	Use 32-12	Use 32-12	Use 32-12	Yes
  32-14	Use 32-10	Use 32-10	Yes (A and B)	Yes
  32-15	Yes	Yes	Yes	Yes
  32-16	None	None	None	N/A
  32-17	None	None	None	N/A
  32-18	None	None	None	N/A
  32-19	None	None	None	N/A

   

  Reminders: Purpose of Each Type of .PKT File

  Topology File: The file contains all devices and cables in the associated figure along with any implied extra devices. The purpose: you never had to add a device or cable. It also contains a few configuration commands that do not affect the example, but help you navigate, for instance, it sets hostnames, passwords (always “cisco”), and interface descriptions.

  Initial Config: The file contains everything in the Topology file, plus all configuration listed or implied by the words and figures leading up to the example. That is, it attempts to match the state of the network just before the first line of the example.

  Ending Config: The file adds the configuration listed in the example to the Initial Config file – nothing more, nothing less.

  

   

  Table Lists “None” or Other Strange Terms?

  Some examples have all three types of PKT files, however, some Examples have no PT files, and some have a mix of fewer than three files. Here’s a reminder of why. You can check this earlier post for more background if you care to know more.

  Initial Config as “None”: If the table says “yes” for the Topology and Ending config, but not the Initial config, then the Topology file has all configuration needed at the beginning of the example.

  Ending Config as “None”: The Ending config will be shown as “None” when the example as printed in the book does not have any configuration commands.

  All Three Files as “None”:  We do not supply .pkt files for that example.

  Use x-y:  Use Example x-y’s ending config file because the example continues earlier example x-y.

   

  Tips and Exceptions

  This section lists our comments about using PT to do the examples. When we built the files, when we saw any behavior that we thought might make it more difficult to perform the example, we noted that fact so we could list it here, in case it might help you with the examples.

   

  Examples 32-6, 32-8, 32-9

  This example includes the show ipv6 route static command, which PT does not support. Use show ipv6 route instead.

   

  Example 32-10

  This example makes use of link local addresses that are created using EUI-64 rules. However, Packet Tracer does not conform to the same rules used by real gear for EUI-64 rules – see this post for a more detailed description.  For Example 32-10, note:

  The example shows the configuration of static routes with link-local next-hop addresses. The commands as listed in the example will not work in PT, because PT will be using different link-local addresses. So, use the show ipv6 interface s0/0/0 command on R1 and show ipv6 interface s0/0/1 on R2 to find the link-local addresses used in each case. They may be:

  • • • R1 s0/0/0 = FE80::290:21FF:FEEC:A501
      • R2 s0/0/1 = FE80::205:5EFF:FED5:601

  If so, the revised commands to match Example 32-10 will be:

  • • • On R1: ipv6 route 2001:db8:1111:2::/64 S0/0/0 FE80::205:5EFF:FED5:601
      • On R2: ipv6 route 2001:db8:1111:1::/64 S0/0/1 FE80::290:21FF:FEEC:A501

   

  Example 32-12

  The example and surrounding text/figures do not supply all the IPv6 addresses required to build a lab configuration that works, so the supplied PT files add some details. You may want to check the configuration of all the routers in the init file – the one that supplies all the configuration needed to begin the example – to see what we chose to use to make the lab work.

   

  Example 32-14

  Note that this one example shows two solutions to the same static route, so we supplied two ending PT files (A and B), one for each different solution.

  Of those, solution A happens to use a next-hop link-local address, which means PT will need different values than the example – see the notes above for Example 32-10 for details.

   

  Example 32-15

  Readers with older printings will note that there are errors associated with this example. Some parts of the figure and text use prefix 2001:DB8:1111:7::/64, while others use 3444:4:4:4::/64. The PT files show the use of 3444:4:4:4::/64.

  To test the lab, you need to disable and enable some interfaces. First, wait 30-60 seconds for OSPF in PT to converge. Router R1 should show the route over the GigE link. Then log in at router R2 and shutdown its G0/1 interface. That should cause R1’s OSPF-learned route to for 3444:4:4:4::/64 to fail, so that R1 adds its static route for that same prefix to R1’s routing table.