Free Play Labs – CCNA Vol 1 Chapter 7
The CCNA 200-301 exam expects that you know nothing about Cisco Command Line Interface (CLI) commands before beginning your journey. Cisco Packet Tracer is one of the many tools you can use to learn how to use the CLI, and this post can help you learn some of the most basic CLI commands on switches, as discussed in Chapter 7 of the CCNA 200-301 Official Cert Guide, Volume 1.
Confused? New to “Free Play” Labs?
The idea is simple: Many students would like to further explore the Examples in the Official Cert Guide. We remove the barriers so you can do just that with the free Cisco Packet Tracer simulator.
The details require some reading. To get your head around what kind of content is here in the blog for these labs, read:
Book: CCNA 200-301 OCG, Volume 1
Title: Configuring and Verifying Switch Interfaces
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 7 of the CCNA 200-301 Official Cert Guide, Volume 1 discusses a variety of switch configuration settings available from interface configuration mode on a LAN switch. The settings include speed and duplex, along with administrative settings to describe the interface and to set the interface to be enabled or disabled by default (no shutdown or shutdown). The chapter also discusses interface status codes and the typical scenarios that lead to one interface state or the other.
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
|.PKT Includes Initial State of Example?
|.PKT Also Includes Ending State of Example?
|Exact Match of Interface IDs?
Looking for Lab Instructions? Click the Button!
This example from the book does not happen to show the switch in the context of a figure. However, the output in the book shows two ports as being connected (up), so to reflect that same interface state in Packet Tracer, we added a second switch, with links between the local switch (Emma) and the second switch.
The example shows the output from the show interfaces status command, but the output from PT does not match real gear. In particular:
- PT’s output omits the description text from the “Name” column.
- PT’s VLAN column lists the correct access VLAN, but if the interface trunks, PT does not note that the interface trunks; real switches do.
- PT’s “Duplex” and “Speed” columns do not show the same status codes as real gear.
- PT’s list of ports in the “Port” column, and status value in the “Status” column, appear to be correct.
Although this example contains config, the point of the example is for the reader to enter the command shutdown, and observe the immediate effect of shutting down the interface.
Also, just as with Example 7-2, Example 7-4 does not refer to any figures because it shows a configuration command from a single switch. However, the output in the book shows the port (F0/1) as being connected (up) at the beginning of the example, so to reflect that same state in Packet Tracer, we added a second switch, with a link to SW1’s F0/1, so the port would be in a working state.
PT does not accept the command show running-config interface f0/2, as shown in the book example. Use show running-config and scroll to interface f0/2 instead.