Basic Router Configuration

Objective: Implement initial settings on a router and end devices.

Introduction
Welcome to Basic Router Configuration!

Have you ever run a relay? The first person runs the first leg of the race and hands off the baton to
the next runner, who continues forward in the second leg of the race and hands off the baton to the
third runner, and on it goes. Routing packets is very similar to a relay. But if the first runner does not
know where to find the second runner, or drops the baton in the first leg, then that relay team will
most certainly lose the race.

Routing packets is very similar to a relay. As you know, routing tables are created and used by
routers to forward packets from their local networks on to other networks. But a router cannot
create a routing table or forward any packets until it has been configured. If you plan to become a
network administrator you definitely must know how to do this. The good news? It is easy! This
module has Syntax Checker activities so that you can practice your configuration commands and see
the output. There are also some Packet Tracer activities to get you started. Let’s go!
Configure Initial Router Settings
Basic Router Configuration Steps
Basic Router Configuration Example
In this example, router R1 in the topology diagram will be configured with initial settings.

All router access should be secured. Privileged EXEC mode provides the user with complete access to the device and
its configuration. Therefore, it is the most important mode to secure.

The following commands secure privileged EXEC mode and user EXEC mode, enable Telnet and SSH remote access,
and encrypt all plaintext (i.e., user EXEC and VTY line) passwords.
Packet Tracer - Configure Initial Router Settings
In this activity, you will perform basic router configurations. You will secure access to the CLI and console port using
encrypted and plaintext passwords. You will also configure messages for users logging into the router. These banners
also warn unauthorized users that access is prohibited. Finally, you will verify and save your running configuration.

Objectives
Part 1: Verify the Default Router Configuration
Part 2: Configure and Verify the Initial Router Configuration
Part 3: Save the Running Configuration File

Background
In this activity, you will perform basic router configuration tasks. You will secure access to the CLI and console
port using encrypted and plain-text passwords. You will also configure messages for users who are logging into
the router. These banners warn unauthorized users that access is prohibited. Finally, you will verify and save your
running configuration.

Instructions
Verify the Default Router Configuration
Establish a console connection to R1.
Choose a Console cable from the available connections.
Click PCA and select RS 232.
Click R1 and select Console.
Click PCA > Desktop tab > Terminal.
Click OK and press ENTER. You are now able to configure R1.

Enter privileged mode and examine the current configuration.

You can access all the router commands from privileged EXEC mode. However, because many of the privileged
commands configure operating parameters, privileged access should be password-protected to prevent
unauthorized use.
Enter privileged EXEC mode by entering the enable command.
Open a configuration window

Router> enable
Router#
Notice that the prompt changed in the configuration to reflect privileged EXEC mode.
Enter the show running-config command.
Router# show running-config
Questions:

What is the router’s hostname?

Type your answers here.
How many Fast Ethernet interfaces does the Router have?
Type your answers here.
How many Gigabit Ethernet interfaces does the Router have?
Type your answers here.
How many Serial interfaces does the router have?
Type your answers here.
What is the range of values shown for the vty lines?
Type your answers here.
Display the current contents of NVRAM.
Router# show startup-config
 startup-config is not present
Question:

Why does the router respond with the startup-config is not present message?
Close a configuration window

Configure and Verify the Initial Router Configuration

To configure parameters on a router, you may be required to move between various configuration modes. Notice
how the prompt changes as you navigate through the IOS configuration modes.

Configure the initial settings on R1.

Note: If you have difficulty remembering the commands, refer to the content for this topic. The commands are the
same as you configured on a switch.
Open a configuration window

a. Configure R1 as the hostname.

b. Configure Message of the day text: Unauthorized access is strictly prohibited.
c. Encrypt all plain text passwords.
Use the following passwords:
1) Privileged EXEC, unencrypted: cisco
2) Privileged EXEC, encrypted: itsasecret
3) Console: letmein

Verify the initial settings on R1.

Open a configuration window

Verify the initial settings by viewing the configuration for R1.

Question:

What command do you use?

answers here.
Exit the current console session until you see the following message:
R1 con0 is now available

Press RETURN to get started.

Press ENTER; you should see the following message:
Unauthorized access is strictly prohibited.

User Access Verification

Password:
Questions:

Why should every router have a message-of-the-day (MOTD) banner?

If you are not prompted for a password before reaching the user EXEC prompt, what console line command
did you forget to configure?
Type your answers here.
Enter the passwords necessary to return to privileged EXEC mode.
Questions:

Why would the enable secret password allow access to the privileged EXEC mode and the enable
password no longer be valid?
If you configure any more passwords on the router, are they displayed in the configuration file as plain text or
in encrypted form? Explain.
Type your answers here.
Close a configuration window

Save the Running Configuration File

Save the configuration file to NVRAM.
You have configured the initial settings for R1. Now back up the running configuration file to NVRAM to ensure
that the changes made are not lost if the system is rebooted or loses power.
Open a configuration window
 Questions:

What command did you enter to save the configuration to NVRAM?

Type your answers here.
What is the shortest, unambiguous version of this command?
answers here.

Optional: Save the startup configuration file to flash.

Although you will be learning more about managing the flash storage in a router in later chapters, you may be
interested to know that, as an added backup procedure, you can save your startup configuration file to flash. By
default, the router still loads the startup configuration from NVRAM, but if NVRAM becomes corrupt, you can
restore the startup configuration by copying it over from flash.
Complete the following steps to save the startup configuration to flash.
Open a configuration window

Examine the contents of flash using the show flash command:

R1# show flash
Questions:

How many files are currently stored in flash?

Type your answers here.
Which of these files would you guess is the IOS image?
Type your answers here.
Why do you think this file is the IOS image?
Type your answers here.
R1# copy startup-config flash
Destination filename [startup-config]
The router prompts you to store the file in flash using the name in brackets. If the answer is yes, then press
ENTER; if not, type an appropriate name and press ENTER.
Use the show flash command to verify the startup configuration file is now stored in flash.
Close a configuration window
End of document

Configure Router Interfaces

At this point, your routers have their basic configurations. The next step is to configure their interfaces. This is
because routers are not reachable by end devices until the interfaces are configured. There are many different types
of interfaces available on Cisco routers. For example, the Cisco ISR 4321 router is equipped with two Gigabit
Ethernet interfaces:

 GigabitEthernet 0/0/0 (G0/0/0)

 GigabitEthernet 0/0/1 (G0/0/1)

The task to configure a router interface is very similar to a management SVI on a switch. Specifically, it includes
issuing the following commands:

Note: When a router interface is enabled, information messages should be displayed confirming the enabled link.

Although the description command is not required to enable an interface, it is good practice to use it. It can be
helpful in troubleshooting on production networks by providing information about the type of network connected.
For example, if the interface connects to an ISP or service carrier, the description command would be helpful to
enter the third-party connection and contact information.
Note: The description-text is limited to 240 characters.

Using the no shutdown command activates the interface and is similar to powering on the interface. The interface
must also be connected to another device, such as a switch or a router, for the physical layer to be active.

Note: On inter-router connections where there is no Ethernet switch, both interconnecting interfaces must be
configured and enabled.

Configure Router Interfaces Example

In this example, the directly connected interfaces of R1 in the topology diagram will be enabled.

To configure the the interfaces on R1, use the following commands.

Note: Notice the informational messages informing us that G0/0/0 and G0/0/1 are enabled.
Verify Interface Configuration
There are several commands that can be used to verify interface configuration. The most useful of these is the show
ip interface brief and show ipv6 interface brief commands, as shown in the example.

Configuration Verification Commands

The table summarizes the more popular show commands used to verify interface configuration.

show ip interface brief

show ipv6 interface brief

show ip route

show ipv6 route

show interfaces
show ip interface

show ipv6 interface

Configure the Default Gateway
Default Gateway on a Host
If your local network has only one router, it will be the gateway router and all hosts and switches on your network
must be configured with this information. If your local network has multiple routers, you must select one of them to
be the default gateway router. This topic explains how to configure the default gateway on hosts and switches.

For an end device to communicate over the network, it must be configured with the correct IP address information,
including the default gateway address. The default gateway is only used when the host wants to send a packet to a
device on another network. The default gateway address is generally the router interface address attached to the
local network of the host. The IP address of the host device and the router interface address must be in the same
network.

For example, assume an IPv4 network topology consisting of a router interconnecting two separate LANs. G0/0/0 is
connected to network 192.168.10.0, while G0/0/1 is connected to network 192.168.11.0. Each host device is
configured with the appropriate default gateway address.

In this example, if PC1 sends a packet to PC2, then the default gateway is not used. Instead, PC1 addresses the
packet with the IPv4 address of PC2 and forwards the packet directly to PC2 through the switch.

What if PC1 sent a packet to PC3? PC1 would address the packet with the IPv4 address of PC3, but would forward
the packet to its default gateway, which is the G0/0/0 interface of R1. The router accepts the packet and accesses its
routing table to determine that G0/0/1 is the appropriate exit interface based on the destination address. R1 then
forwards the packet out of the appropriate interface to reach PC3.

The same process would occur on an IPv6 network, although this is not
shown in the topology. Devices would use the IPv6 address of the local router as their default gateway.
Default Gateway on a Switch

A switch that interconnects client computers is typically a Layer 2 device. As such, a Layer 2 switch does not require
an IP address to function properly. However, an IP configuration can be configured on a switch to give an
administrator remote access to the switch.

To connect to and manage a switch over a local IP network, it must have a switch virtual interface (SVI) configured.
The SVI is configured with an IPv4 address and subnet mask on the local LAN. The switch must also have a default
gateway address configured to remotely manage the switch from another network.

The default gateway address is typically configured on all devices that will communicate beyond their local network.

To configure an IPv4 default gateway on a switch, use the ip default-gateway ip-address global configuration
command. The ip-address that is configured is the IPv4 address of the local router interface connected to the switch.

The figure shows an administrator establishing a remote connection to switch S1 on another network.

In this example, the administrator host

would use its default gateway to send the packet to the G0/0/1 interface of R1. R1 would forward the packet to S1
out of its G0/0/0 interface. Because the packet source IPv4 address came from another network, S1 would require a
default gateway to forward the packet to the G0/0/0 interface of R1. Therefore, S1 must be configured with a
default gateway to be able to reply and establish an SSH connection with the administrative host.

Note: Packets originating from host computers connected to the switch must already have the default gateway
address configured on their host computer operating systems.

A workgroup switch can also be configured with an IPv6 address on an SVI. However, the switch does not require the
IPv6 address of the default gateway to be configured manually. The switch will automatically receive its default
gateway from the ICMPv6 Router Advertisement message from the router.
Packet Tracer - Connect a Router to a LAN

Addressing Table
Device Interface IP Address Subnet Mask Default Gateway

R1 G0/0 192.168.10.1 255.255.255.0 N/A

R1
G0/1 192.168.11.1 255.255.255.0 N/A

R1
S0/0/0 (DCE) 209.165.200.225 255.255.255.252 N/A
R2 G0/0 10.1.1.1 255.255.255.0 N/A

R2
G0/1 10.1.2.1 255.255.255.0 N/A

R2
S0/0/0 209.165.200.226 255.255.255.252 N/A
PC1 NIC 192.168.10.10 255.255.255.0 192.168.10.1
PC2 NIC 192.168.11.10 255.255.255.0 192.168.11.1
PC3 NIC 10.1.1.10 255.255.255.0 10.1.1.1
PC4 NIC 10.1.2.10 255.255.255.0 10.1.2.1

Objectives
Part 1: Display Router Information
Part 2: Configure Router Interfaces
Part 3: Verify the Configuration

Background
In this activity, you will use various show commands to display the current state of the router. You will then use
the Addressing Table to configure router Ethernet interfaces. Finally, you will use commands to verify and test
your configurations.
Note: The routers in this activity are partially configured. Some of the configurations are not covered in this course
but they are provided to assist you in using verification commands.

Display Router Information

Display interface information on R1.
Note: Click a device and then click the CLI tab to access the command line directly. The console password is
cisco. The privileged EXEC password is class.
Questions:

a. Which command displays the statistics for all interfaces configured on a router?
Type your answers here.
b. Which command displays the information about the Serial 0/0/0 interface only?
Type your answers here.
c. Enter the command to display the statistics for the Serial 0/0/0 interface on R1 and answer the following
questions:
1) What is the IP address configured on R1?
Type your answers here.
2) What is the bandwidth on the Serial 0/0/0 interface?
Te your answers here.
d. Enter the command to display the statistics for the GigabitEthernet 0/0 interface and answer the following
questions:
1) What is the IP address on R1?
Type your answers here.
 2) What is the MAC address of the GigabitEthernet 0/0 interface?
Type your answers.
3) What is the bandwidth (BW) of the GigabitEthernet 0/0 interface?
Type your answers here.

Display a summary list of the interfaces on R1.

Questions:

a. Which command displays a brief summary of the current interfaces, interface status, and the IP addresses
assigned to them?
Type your answers here.
b. Enter the command on each router and answer the following questions:
1) How many serial interfaces are there on R1 and R2?
Type your answers here.
2) How many Ethernet interfaces are there on R1 and R2?
Type your answers here.
3) Are all the Ethernet interfaces on R1 the same? If no, explain the difference(s).

Display the routing table on R1.

Questions:

a. What command displays the contents of the routing table?

Type your answers here.
b. Enter the command on R1 and answer the following questions:
1) How many connected routes are there (uses the C code)?
Type your answers here.
2) Which route is listed?
Type your answers here.
3) How does a router handle a packet destined for a network that is not listed in the routing table?

Configure Router Interfaces

Configure the GigabitEthernet 0/0 interface on R1.
a. Enter the following commands to address and activate the GigabitEthernet 0/0 interface on R1:
Open configuration window

R1(config)# interface gigabitethernet 0/0

R1(config-if)# ip address 192.168.10.1 255.255.255.0
R1(config-if)# no shutdown
%LINK-5-CHANGED: Interface GigabitEthernet0/0, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0, changed state
to up
b. It is good practice to configure a description for each interface to help document the network. Configure an
interface description that indicates the device to which it is connected.
R1(config-if)# description LAN connection to S1
c. R1 should now be able to ping PC1.
R1(config-if)# end
%SYS-5-CONFIG_I: Configured from console by console
R1# ping 192.168.10.10

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.10.10, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 0/2/8 ms
Configure the remaining Gigabit Ethernet Interfaces on R1 and R2.
a. Use the information in the Addressing Table to finish the interface configurations for R1 and R2. For each
interface, do the following:
1) Enter the IP address and activate the interface.
2) Configure an appropriate description.
b. Verify interface configurations.

Back up the configurations to NVRAM.

Question:

Save the configuration files on both routers to NVRAM. What command did you use?
Type your answers here.
Close configuration window

Verify the Configuration

Use verification commands to check your interface configurations.
a. Use the show ip interface brief command on both R1 and R2 to quickly verify that the interfaces are
configured with the correct IP address and are active.
Questions:

How many interfaces on R1 and R2 are configured with IP addresses and in the “up” and “up” state?
Type your answers here.
What part of the interface configuration is NOT displayed in the command output?
Type your answers here.
What commands can you use to verify this part of the configuration?
Type your answers here.
b. Use the show ip route command on both R1 and R2 to view the current routing tables and answer the
following questions:
Questions:

1) How many connected routes (uses the C code) do you see on each router?
Type your answers here.
2) How many OSPF routes (uses the O code) do you see on each router?
Type your answers here.
3) If the router knows all the routes in the network, then the number of connected routes and dynamically
learned routes (OSPF) should equal the total number of LANs and WANs. How many LANs and WANs
are in the topology?
Type your answers here.
4) Does this number match the number of C and O routes shown in the routing table?
Type your answers here.
Note: If your answer is “no”, then you are missing a required configuration. Review the steps in Part 2.

Test end-to-end connectivity across the network.

You should now be able to ping from any PC to any other PC on the network. In addition, you should be able to
ping the active interfaces on the routers. For example, the following tests should be successful:
From the command line on PC1, ping PC4.
From the command line on R2, ping PC2.
Note: For simplicity in this activity, the switches are not configured. You will not be able to ping them.
Log into Cisco Academy, Play videos 10.4.1, 10.4.2
Packet Tracer - Basic Device Configuration
End of document

Topology
You will receive one of three possible topologies.

Addressing Table
Device Interface IP Address Default Gateway

blank G0/0 blank N/A

blank N/A
Blank G0/0
blank N/A
Blank G0/0
Blank G0/1 blank N/A
blank N/A
Blank G0/1
blank N/A
Blank G0/1
Blank VLAN 1 blank blank
Blank VLAN 1 blank blank
Blank NIC blank blank

Blank NIC blank blank

Blank NIC blank blank

Blank NIC blank blank

Blank NIC blank blank

Blank NIC blank blank

Blank NIC blank blank

blank NIC blank blank

Objectives
Complete the network documentation.
Perform basic device configurations on a router and a switch.
Verify connectivity and troubleshoot any issues.

Scenario
Your network manager is impressed with your performance in your job as a LAN technician. She would like you to
demonstrate your ability to configure a router that connects two LANs. Your tasks include configuring basic
settings on a router and a switch using the Cisco IOS. You will also configure IPv6 addresses on network devices
and hosts. You will then verify the configurations by testing end-to-end connectivity. You goal is to establish
connectivity between all devices.
Note: The VLAN1 interface on will not be reachable over IPv6.
In this activity you will configure the router, switch, and the PC hosts.
Note: Packet Tracer will not score some configured values, however these values are required to accomplish full
connectivity in the network.

Requirements
Provide the missing information in the Addressing Table.
Note: Some of the information is provided in the Packet Tracer instructions for your topology.
Name the router and the second switch. You will not be able to access the switch.
Use cisco as the user EXEC password for all lines.
 Use class as the encrypted privileged EXEC password.
Encrypt all plaintext passwords.
Configure an appropriate banner.
Configure IPv4 and IPv6 addressing for the switch according to the Addressing Table.
Configure IPv4 and IPv6 addressing for the switch according to the Addressing Table.
The hosts are partially configured. Complete the IPv4 addressing, and fully configure the IPv6 addresses
according to the Addressing Table.
Document interfaces with descriptions, including the VLAN 1 interface.
Save your configurations.
Verify connectivity between all devices. All devices should be able to ping all other devices with IPv4 and IPv6.
Troubleshoot and document any issues.
Implement the solutions necessary to enable and verify full end-to-end connectivity.
Note: Click Check Results button to see your progress. Click the Reset Activity button to generate a new set of
requirements.
End of document
Packet Tracer - Troubleshoot Default Gateway Issues

Addressing Table
Device Interface IP Address Subnet Mask Default Gateway

R1 G0/0 192.168.10.1 255.255.255.0 N/A

R1
G0/1 192.168.11.1 255.255.255.0 N/A
S1 VLAN 1 192.168.10.2 255.255.255.0 blank
S2 VLAN 1 192.168.11.2 255.255.255.0 blank
PC1 NIC 192.168.10.10 255.255.255.0 blank
PC2 NIC 192.168.10.11 255.255.255.0 blank
PC3 NIC 192.168.11.10 255.255.255.0 blank
PC4 NIC 192.168.11.11 255.255.255.0 blank

Objectives
Part 1: Verify Network Documentation and Isolate Problems
Part 2: Implement, Verify, and Document Solutions

Background
For a device to communicate across multiple networks, it must be configured with an IP address, subnet mask,
and a default gateway. The default gateway is used when the host wants to send a packet to a device on another
network. The default gateway address is generally the address of the router interface which is attached to the
local network that the host is connected to. In this activity, you will finish documenting the network. You will then
verify the network documentation by testing end-to-end connectivity and troubleshooting issues. The
troubleshooting method you will use consists of the following steps:
Verify the network documentation and use tests to isolate problems.
Determine an appropriate solution for a given problem.
Implement the solution.
Test to verify the problem is resolved.
Document the solution.
Throughout your CCNA studies, you will encounter different descriptions of the troubleshooting method, as well as
different ways to test and document issues and solutions. This is intentional. There is no set standard or template
for troubleshooting. Each organization develops unique processes and documentation standards (even if that
process is “we don’t have one”). However, all effective troubleshooting methodologies generally include the steps
above.
Note: If you are proficient with default gateway configurations, this activity might seem more involved than it
should be. You can, most likely, quickly discover and solve all the connectivity issues faster than following these
procedures. However, as you proceed in your studies, the networks and problems you encounter will become
increasingly more complex. In such situations, the only effective way to isolate and solve issues is to use a
methodical approach such as the one used in this activity.

Instructions

Verify Network Documentation and Isolate Problems

In Part 1 of this activity, complete the documentation and perform connectivity tests to discover issues. In addition,
you will determine an appropriate solution for implementation in Part 2.
Step 1: Verify the network documentation and isolate any problems.
Before you can effectively test a network, you must have complete documentation. Notice in the Addressing
Table that some information is missing. Complete the Addressing Table by filling in the missing default
gateway information for the switches and the PCs.
Test connectivity to devices on the same network. By isolating and correcting any local access issues, you can
better test remote connectivity with the confidence that local connectivity is operational.
A verification plan can be as simple as a list of connectivity tests. Use the following tests to verify local
connectivity and isolate any access issues. The first issue is already documented, but you must implement
and verify the solution during Part 2.
Testing and Verification Documentation

Test Successful? Issues Solution Verified

PC1 to PC2 No IP address on PC1 Change PC1 IP address blank

PC1 to S1 blank blank blank blank

PC1 to R1 blank blank blank blank

blank

blank blank blank blank

Blank

blank blank blank blank

Note: The table is an example; you must create your own document. You can use paper and pencil to draw a
table, or you can use a text editor or spreadsheet. Consult your instructor if you need further guidance.
Test connectivity to remote devices (such as from PC1 to PC4) and document any problems. This is frequently
referred to as end-to-end connectivity. This means that all devices in a network have the full connectivity
allowed by the network policy.
Note: Remote connectivity testing may not be possible yet, because you must first resolve local connectivity
issues. After you have solved those issues, return to this step and test connectivity between networks.

Determine an appropriate solution for the problem.

Using your knowledge of the way networks operate and your device configuration skills, search for the cause of
the problem. For example, S1 is not the cause of the connectivity issue between PC1 and PC2. The link lights
are green and no configuration on S1 would cause traffic to not pass between PC1 and PC2. So the problem
must be with PC1, PC2, or both.
Verify the device addressing to ensure it matches the network documentation. For example, the IP address for
PC1 is incorrect as verified with the ipconfig command.
Suggest a solution that you think will resolve the problem and document it. For example, change the IP address
for PC1 to match the documentation.
Note: Often there is more than one solution. However, it is a troubleshooting best practice to implement and
verify one solution at a time. Implementing more than one solution could introduce additional issues in a more
complex scenario.

Implement, Verify, and Document Solutions

In Part 2 of this activity, you will implement the solutions you identified in Part 1. You will then verify the solution
worked. You may need to return to Part 1 to finish isolating all the problems.

Implement solutions to connectivity problems.

Refer to your documentation in Part 1. Choose the first issue and implement your suggested solution. For
example, correct the IP address on PC1.

Verify that the problem is now resolved.

Verify your solution has solved the problem by performing the test you used to identify the problem. For example,
can PC1 now ping PC2?
If the problem is resolved, indicate so in your documentation. For example, in the table above, a simple
checkmark would suffice in the “Verified” column.
Verify that all issues are resolved.
If you still have an outstanding issue with a solution that has not yet been implemented, return to Part 2, Step 1.
If all your current issues are resolved, have you also resolved any remote connectivity issues (such as can PC1
ping PC4)? If the answer is no, return to Part 1, Step 1c to test remote connectivity.
End of document

Lab - Build a Switch and Router Network (You can practice these skills using the Packet Tracer or lab equipment, if available.)

[Title]
Topology

Addressing Table
Device Interface IP Address / Prefix Default Gateway

R1 G0/0/0 192.168.0.1 /24 N/A

N/A

R1 G0/0/0
2001:db8:acad::1/64
N/A

R1 G0/0/0
fe80::1

R1
G0/0/1 192.168.1.1 /24 N/A
N/A

R1 G0/0/1
2001:db8:acad:1::1/64
N/A

R1 G0/0/1
fe80::1
S1 VLAN 1 192.168.1.2 /24 192.168.1.1
PC-A NIC 192.168.1.3 /24 192.168.1.1

PC-A NIC
2001:db8:acad:1::3/64 fe80::1
PC-B NIC 192.168.0.3 /24 192.168.0.1

PC-B NIC
2001:db8:acad::3/64 fe80::1

Objectives
Part 1: Set Up the Topology and Initialize Devices
Part 2: Configure Devices and Verify Connectivity

Background / Scenario
This is a comprehensive lab to review previously covered IOS commands. In this lab, you will cable the equipment
as shown in the topology diagram. You will then configure the devices to match the addressing table. After the
configurations have been saved, you will verify your configurations by testing for network connectivity.
After the devices have been configured and network connectivity has been verified, you will use IOS commands to
retrieve information from the devices to answer questions about your network equipment.
This lab provides minimal assistance with the actual commands necessary to configure the router. Test your
knowledge by trying to configure the devices without referring to the content or previous activities.
Note: The routers used with CCNA hands-on labs are Cisco 4221 with Cisco IOS XE Release 16.9.4 (universalk9
image). The switches used in the labs are Cisco Catalyst 2960s with Cisco IOS Release 15.2(2) (lanbasek9
image). Other routers, switches, and Cisco IOS versions can be used. Depending on the model and Cisco IOS
version, the commands available and the output produced might vary from what is shown in the labs. Refer to the
Router Interface Summary Table at the end of the lab for the correct interface identifiers.
 Note: Ensure that the routers and switches have been erased and have no startup configurations. Consult with
your instructor for the procedure to initialize and reload a router and switch.
The default bias template used by the Switch Database Manager (SDM) does not provide IPv6 address
capabilities. Verify that SDM is using either the dual-ipv4-and-ipv6 template or the lanbase-routing template.
The new template will be used after reboot even if the configuration is not saved.
S1# show sdm prefer
Use the following commands to assign the dual-ipv4-and-ipv6 template as the default SDM template.
S1# configure terminal
S1(config)# sdm prefer dual-ipv4-and-ipv6 default
S1(config)# end
S1# reload

Required Resources
1 Router (Cisco 4221 with Cisco IOS XE Release 16.9.4 universal image or comparable)
1 Switch (Cisco 2960 with Cisco IOS Release 15.2(2) lanbasek9 image or comparable)
2 PCs (Windows with a terminal emulation program, such as Tera Term)
Console cables to configure the Cisco IOS devices via the console ports
Ethernet cables as shown in the topology
Note: The Gigabit Ethernet interfaces on Cisco 4221 routers are autosensing and an Ethernet straight-through
cable may be used between the router and PC-B. If using another model Cisco router, it may be necessary to use
an Ethernet crossover cable.

Instructions

Set Up Topology and Initialize Devices

Cable the network as shown in the topology.
Attach the devices shown in the topology diagram, and cable, as necessary.
Power on all the devices in the topology.

Initialize and reload the router and switch.

If configuration files were previously saved on the router and switch, initialize and reload these devices back to
their default configurations.

Configure Devices and Verify Connectivity

In Part 2, you will set up the network topology and configure basic settings, such as the interface IP addresses,
device access, and passwords. Refer to the Error! Reference source not found. and Error! Reference source
not found. at the beginning of this lab for device names and address information.

Assign static IP information to the PC interfaces.

Configure the IP address, subnet mask, and default gateway settings on PC-A.
Configure the IP address, subnet mask, and default gateway settings on PC-B.
Ping PC-B from a command prompt window on PC-A.
Note: If pings are not successful, the Windows Firewall may need to be turned off.
Question:

Why were the pings not successful?

Type your answers here.

Configure the router.

Console into the router and enable privileged EXEC mode.
Open configuration window

Enter configuration mode.

Assign a device name to the router.
 Disable DNS lookup to prevent the router from attempting to translate incorrectly entered commands as though
they were host names.
Assign class as the privileged EXEC encrypted password.
Assign cisco as the console password and enable login.
Assign cisco as the VTY password and enable login.
Encrypt the plaintext passwords.
Create a banner that warns anyone accessing the device that unauthorized access is prohibited.
Configure and activate both interfaces on the router.
Configure an interface description for each interface indicating which device is connected to it.
To enable IPv6 routing, enter the command ipv6 unicast-routing.
R1(config)# ipv6 unicast-routing
Save the running configuration to the startup configuration file.
Set the clock on the router.
Note: Use the question mark (?) to help with the correct sequence of parameters needed to execute this
command.
Close configuration window

Ping PC-B from a command prompt window on PC-A.

Note: If pings are not successful, the Windows Firewall may need to be turned off.
Question:

Were the pings successful? Explain.

Type your answers here.

Configure the switch.

In this step, you will configure the hostname, the VLAN 1 interface and its default gateway.
Open configuration window

Console into the switch and enable privileged EXEC mode.

Enter configuration mode.
Assign a device name to the switch.
Disable DNS lookup to prevent the router from attempting to translate incorrectly entered commands as though
they were host names.
Configure and activate the VLAN interface on the switch S1.
Configure the default gateway for the switch S1.
Save the running configuration to the startup configuration file.

Verify connectivity end-to-end connectivity.

From PC-A, ping PC-B.
From S1, ping PC-B.
All the pings should be successful.
Close configuration window

Display Device Information

In Part 3, you will use show commands to retrieve interface and routing information from the router and switch.
Display the routing table on the router.
Use the show ip route command on the router R1 to answer the following questions.
Open configuration window
Questions:

What code is used in the routing table to indicate a directly connected network?
Type your answers here.
How many route entries are coded with a C code in the routing table?
Type your answers here.
What interface types are associated to the C coded routes?
Type your answers here.
 Use the show ipv6 route command on router R1 to display the IPv6 routes.

Display interface information on the router R1.

Use the show ip interface g0/0/1 to answer the following questions.
Questions:

What is the operational status of the G0/0/1 interface?

Type your answers here.
What is the Media Access Control (MAC) address of the G0/1 interface?
Type your answers here.
How is the Internet address displayed in this command?
Type your answers here.
For the IPv6 information, enter the show ipv6 interface interface command.

Display a summary list of the interfaces on the router and switch.

There are several commands that can be used to verify an interface configuration. One of the most useful of these
is the show ip interface brief command. The command output displays a summary list of the interfaces on the
device and provides immediate feedback to the status of each interface.
Enter the show ip interface brief command on the router R1.
R1# show ip interface brief

To see the IPv6 interface information, enter the show ipv6 interface brief command on R1.
R1# show ipv6 interface brief
Close configuration window

Enter the show ip interface brief command on the switch S1.

Open configuration window

S1# show ip interface brief

Close configuration window

Reflection Questions
If the G0/0/1 interface showed that it was administratively down, what interface configuration command would you use
to turn the interface up?
Type your answers here.
What would happen if you had incorrectly configured interface G0/0/1 on the router with an IP address of 192.168.1.2?
Type your answers here.

Router Interface Summary Table

Router Model Ethernet Interface #1 Ethernet Interface #2 Serial Interface #1 Serial Interface #2

Fast Ethernet 0/0 Fast Ethernet 0/1

1800 (F0/0) (F0/1) Serial 0/0/0 (S0/0/0) Serial 0/0/1 (S0/0/1)
Gigabit Ethernet 0/0 Gigabit Ethernet 0/1
1900 (G0/0) (G0/1) Serial 0/0/0 (S0/0/0) Serial 0/0/1 (S0/0/1)
Fast Ethernet 0/0 Fast Ethernet 0/1
2801 (F0/0) (F0/1) Serial 0/1/0 (S0/1/0) Serial 0/1/1 (S0/1/1)
Fast Ethernet 0/0 Fast Ethernet 0/1
2811 (F0/0) (F0/1) Serial 0/0/0 (S0/0/0) Serial 0/0/1 (S0/0/1)
Gigabit Ethernet 0/0 Gigabit Ethernet 0/1
2900 (G0/0) (G0/1) Serial 0/0/0 (S0/0/0) Serial 0/0/1 (S0/0/1)
Gigabit Ethernet 0/0/0 Gigabit Ethernet 0/0/1
4221 (G0/0/0) (G0/0/1) Serial 0/1/0 (S0/1/0) Serial 0/1/1 (S0/1/1)
Gigabit Ethernet 0/0/0 Gigabit Ethernet 0/0/1
4300 (G0/0/0) (G0/0/1) Serial 0/1/0 (S0/1/0) Serial 0/1/1 (S0/1/1)

Note: To find out how the router is configured, look at the interfaces to identify the type of router and how many
interfaces the router has. There is no way to effectively list all the combinations of configurations for each router class.
This table includes identifiers for the possible combinations of Ethernet and Serial interfaces in the device. The table
does not include any other type of interface, even though a specific router may contain one. An example of this might
be an ISDN BRI interface. The string in parenthesis is the legal abbreviation that can be used in Cisco IOS commands
to represent the interface.
End of Document