IP Addressing: Cert Guide PT Labs for ICND1 Chapter 17
Today’s post moves into IPv4 routing and addressing with the ICND1 100-105 Official Cert Guide Chapter 17. As with the other recent posts, this post details some Packet Tracer (PT) files to use with the Examples in that chapter. Look below the fold for details!
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:
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
Chapter 11 of the ICND1 100-105 Official Cert Guide, “Operating Cisco Routers”, leads off the first book part (Part V) with significant CLI commands related to routers and routing. From a lab perspective, this chapter has only a few examples, given the nature of the content, with little work to do. It’s all about configuring interface IPv4 addresses and confirming that you added the configuration correctly.
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? |
| 17-1 | None | None | None | N/A |
| 17-2 | Yes | Yes | Yes | Yes |
| 17-3 | Use 17-2 | Use 17-2 | Use 17-2 | Yes |
| 17-4 | Use 17-2 | Use 17-2 | Use 17-2 | Yes |
| 17-5 | Use 17-2 | Use 17-2 | Use 17-2 | Yes |
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.
Example 17-2
This example focuses on R1, and the matching figure (17-6) does not specify the interface IP addresses for the WAN links on routers R2 and R3. For the purposes of this lab, we chose those IP addresses, which you can find in the Initial and Ending PT files.
I am a little confused by the packet tracer labs in your blog. are they meant to be for strictly observation? why not set up some objectives and let us try to see if we can successfully meet each criteria?
Austin
Hi Austin,
Sure, I wrote a post to answer your kind of question – the first post in the Packet Tracer Book lab series, which explains the rationale. https://blog.certskills.com/cgptl-01/
Check that out and follow up if it doesn’t answer your questions.
Also, check out the Config Lab series: 80-90 labs with criteria for you to perform.
Wendell
Hello,
Do any of these examples correspond to chapter 15 or a different chapter in the CCNA 200-301 OCG?
Thanks.
Hi Lucas,
ICND1 100-105 OCG chapter 17 does indeed significantly match new CCNA 200-301 Vol 1 chapter 15. That said, we’ve in process of re-building and releasing these kinds of posts for the new books. The CCNA 200-301 Vol 1 posts now run through Chapter 20. Check out the menu item “Hands On… Packet Tracer Labs 200-301 OCGs” for the list. Or https://blog.certskills.com/category/hands-on/pt-labs-200-301/