Static IP Routing: Cert Guide PT Labs ICND1 Chapter 18

certskills
By certskills May 22, 2019 09:05

Labs really do help, and labbing what you saw in book examples can even help. Do the labs, and then try and explore beyond the book. Today’s post launches from Chapter 18 of the ICND1 Official Cert Guide.  Enjoy!

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

While Chapter 17 of the ICND1 100-105 Official Cert Guide had only a few examples, Chapter 18, “Configuring IPv4 Addresses and Static Routes” has many.  This chapter is the first chapter in the book that gets into detail about configuring IPv4 addresses and the resulting connected and local routes. The chapter also goes into some detail about IPv4 static routes, with many examples on those features.

 

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 ID?
18-1  None  None  None N/A
18-2  None  None  None N/A
18-3  Yes  Yes  Yes Yes
18-4  Yes  Yes  Yes Yes
18-5  None  None  None N/A
18-6  Yes  Yes  Yes Yes
18-7 None None Use 18-6 Yes
18-8 Yes Yes Yes Yes
18-9 None None Use 18-8 Yes
18-10 None None None N/A
18-11 Yes Yes Yes Yes
18-12 Yes Yes Yes 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.

 

Examples 18-3, 18-4

Both examples focus on the router configurations. However, note that the initial PKT files pre-configure the switch port with the switchport mode trunk command, so that both the router and switch use trunking on that link.

 

Example 18-6

In our testing, the PT 2960 switch did not support layer 3 switching, so we used a PT 3560 switch. Note that the PT 3560 switch does not require a command like sdm prefer lanbase-routing to enable IP routing.

 

Example 18-7

You can still perform this example in PT, but note that you will see some minor differences. Note that the output on the PT 3560 switch does not include the Local routes shown in Example 18-7, but it does include the connected routes, due to the PT 3560 being a (simulated) older switch with older software. More recent layer 3 switches would include the Local routes.

 

Example 18-8

Be aware that we have seen some incorrect error messages when performing this example in PT. That is, the router in PT gives an error message that a real router would not. For example:

 

Example 18-10

The example requires the use of the permanent keyword on the command ip route 172.16.2.0 255.255.255.0 172.16.4.2 permanent, and PT does not support it today.

 

Example 18-12

This example uses the topology in book figure 18-15; note that some printings list the figure reference as 18-16. FYI.

 

IP Addressing: Cert Guide PT Labs for ICND1 Chapter 17
certskills
By certskills May 22, 2019 09:05
Write a comment

No Comments

No Comments Yet!

Let me tell You a sad story ! There are no comments yet, but You can be first one to comment this article.

Write a comment
View comments

Write a comment

Comment; Identify w/ Social Media or Email

Subscribe

Subscribe to our mailing list and get interesting stuff and updates to your email inbox.

Thank you for subscribing.

Something went wrong.

Search

Categories