Packet Tracer Labs – CCNA Vol 1 Chapter 24

Confused? New to “Packet Tracer Labs for OCGs”?

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

The details require some reading. To get your head around what kind of content is here in the blog for these labs, read:

• • Intro to the Cert Guide PT Labs

What’s in This Post

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

Download Link: Links to a ZIP; the ZIP holds all the .PKT files for this chapter.

Table of PKT files, by Example: A table that lists each example in the chapter, with the files supplied for each. Also lists a note about whether the PKT topology matches the book example exactly or not.

Tips: 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!

Chapter Intro

It almost seems too simple: Just configure a global unicast IPv6 address for each interface, using the ipv6 address interface subcommand. This chapter revolves around what happens when you configure that interface subcommand on each interface, but it takes a chapter because of a variety related happenings when you add that configuration:

• The router enables IPv6 on the interface.
• The router dynamically creates a link-local IPv6 address for the interface – an address that can be affected by other configuration.
• The router begins using different IPv6 multicast addresses depending on other IPv6 features on the router.

In addition to these base features, you have the option to ask the router to dynamically learn its IPv6 global unicast address, or to even avoid global unicast addresses altogether, relying solely on a link-local address for an interface.

As you can see from this brief introduction, IPv6 address configuration quickly moves from the process of assigning each router interface an address to the intricacies of IPv6. Enjoy!

Download the Packet Tracer ZIP File

One .PKT File – But Maybe Two (Duplicate) Toplogies

When building the content for this post, we review the examples in the book and decide whether it makes sense to supply a Packet Tracer (.pkt) file to match the example. If we choose to support an example by supplying a matching .pkt file, the .pkt file includes a topology that matches the example as much as possible. It also includes the device configurations as they should exist at the beginning of the example.

In some cases, the .pkt file shows two instances of the lab topology – one above and one below. We include two such topologies when the book example includes configuration commands, for these purposes:

• Top/Initial: The topology at the top has the configuration state at the beginning of the example.
• Bottom/Ending: The topology at the bottom adds the configuration per the example, so that it mimics the configuration at the end of the example.

Table of .PKT Files, by Example