Page 1 of 11
Challenge Lab
Basic Router Configuration
After completing this lab, you will be able to:
Erase and reload a router.
Perform basic IOS command line operations.
Perform basic router configuration.
Verify and test configurations using show commands, ping, and traceroute.
Create a startup configuration file.
Reload a startup configuration file.
In this exercise, you will open the Packet Tracer File titled Basic Router Configuration and
follow these lab instructions to work through the lab.
Below is the Address Table for the Network:
Default
Device Interface IP Address Subnet Mask Gateway
Fa0/0 10.0.0.1 255.255.0.0 N/A
Dallas S0/0/0 172.16.0.1 255.255.0.0 N/A
Fa0/0 192.168.0.1 255.255.255.0 N/A
Houston S0/0/0 172.16.0.2 255.255.0.0 N/A
PC1 FastEthernet 10.0.0.2 255.255.255.0 10.0.0.1
PC2 FastEthernet 192.168.0.2 255.255.255.0 192.168.0.1
Activity
Task 1: Erase and Reload the Routers.
1. Open the Dallas Router. Type in the following command to move from user-exec mode to
privileged-exec mode:
Router>enable
Router#
2. Erase the configuration. In a business environment, before redeploying a router, you must
first erase the startup-configuration. To clear the configuration, issue the erase startup-config
command. Confirm the objective when prompted by hitting Enter, and answer no if asked to
save changes. The result should look something like this:
Router#erase startup-config
Erasing the nvram filesystem will remove all files! Continue? [confirm]
Page 2 of 11
[OK]
Erase of nvram: complete
Router#
3. Reload the configuration. When the prompt returns, issue the reload command. Confirm the
objective when prompted by hitting Enter.
Would you like to enter the initial configuration dialog? [yes/no]: no
Press RETURN to get started!
Task 2: Understand Command Line Basics.
1. Type enable to return to privileged-exec mode. Enter an incorrect command and observe the
router response.
Router#comfigure terminal
^
% Invalid input detected at '^' marker.
Router#
Command line errors occur primarily from typing mistakes. If a command keyword is incorrectly
typed, the user interface uses the caret symbol (^) to identify and isolate the error. The ^ appears
at or near the point in the command string where an incorrect command, keyword, or argument
was entered.
2. Correct the previous command using arrow keys. If a command is entered incorrectly, and the
Enter key is pressed, the Up Arrow key on the keyboard can be pressed to repeat the last
command. Use the Right Arrow and Left Arrow keys to move the cursor to the location where
the mistake was made. Then make the correction. If something needs to be deleted, use the
Backspace key. Use the directional keys and the Backspace key to correct the command to
configure terminal, and then press Enter.
Router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#
3. Return to privileged EXEC mode with the exit command. Typing exit takes you back one
mode at a time.
Router(config)#exit
%SYS-5-CONFIG_I: Configured from console by console
Router#
4. Examine the commands that are available for privileged EXEC mode.
Page 3 of 11
A question mark, ?, can be entered at the prompt to display a list of available commands.
Router#?
Exec commands:
<1-99> Session number to resume
clear Reset functions
clock Manage the system clock
configure Enter configuration mode
connect Open a terminal connection
copy Copy from one file to another
debug Debugging functions (see also 'undebug')
delete Delete a file
dir List files on a filesystem
disable Turn off privileged commands
disconnect Disconnect an existing network connection
enable Turn on privileged commands
erase Erase a filesystem
exit Exit from the EXEC
logout Exit from the EXEC
no Disable debugging informations
ping Send echo messages
reload Halt and perform a cold restart
resume Resume an active network connection
setup Run the SETUP command facility
show Show running system information
--More--
Notice the --More-- at the bottom of the command output. The --More-- prompt indicates that
there are multiple screens of output. When a --More-- prompt appears, press the Spacebar to
view the next available screen. To display only the next line, press the Enter key. Press any
other key to return to the prompt.
5. View the rest of the command output by pressing the Spacebar. The remainder of the output
will appear where the --More-- prompt appeared previously.
telnet Open a telnet connection
traceroute Trace route to destination
undebug Disable debugging functions (see also 'debug')
vlan Configure VLAN parameters
write Write running configuration to memory, network, or terminal
6. Exit privileged EXEC mode with the exit command.
Router#exit
The following output should be displayed:
Router con0 is now available
Page 4 of 11
Press RETURN to get started.
7. Press the Enter key to enter user EXEC mode. The Router> prompt should be visible.
8. Type an abbreviated IOS command. IOS commands can be abbreviated, as long as enough
characters are typed for the IOS to recognize the unique command.
Enter only the character e at the command prompt and observe the results.
Router>e
% Ambiguous command: "e" (The ambiguous command error means that there is not enough of
the command type to differentiate it from other commands.)
Router>
Enter en at the command prompt and observe the results.
Router>en
Router#
The abbreviated command en contains enough characters for the IOS to distinguish the enable
command from the exit command.
9. Press the Tab key after an abbreviated command to use auto-complete. Typing an abbreviated
command, such as conf, followed by the Tab key completes a partial command name. This
functionality of the IOS is called auto-complete. Type the abbreviated command conf, press the
Tab key, and observe the results.
Router#conf
Router#configure
This auto-complete feature can be used as long as enough characters are typed for the IOS to
recognize the unique command.
10. Enter IOS commands in the correct mode. IOS commands must be entered in the correct
mode. For example, configuration changes cannot be made while in privileged EXEC mode.
Attempt to enter the command hostname DALLAS at the privileged EXEC prompt and observe
the results.
Router#hostname DALLAS
^
% Invalid input detected at '^' marker.
Page 5 of 11
Router#
Task 3: Perform Basic Configuration of Dallas Router.
1. Enter global configuration mode.
Router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#
2. Configure the router name as DALLAS. Enter the command hostname DALLAS at the
prompt.
Router(config)#hostname Dallas
Dallas(config)#
3. Disable DNS lookup with the no ip domain-lookup command. If this isn’t done, the router
will think you are trying to telnet into another device from privileged-exec mode every time you
type in a command wrong.
DALLAS(config)#no ip domain-lookup
DALLAS(config)#
4. Configure an EXEC mode password using the enable secret password command. Use class
for the password.
DALLAS(config)#enable secret class
DALLAS(config)#
The enable secret command is used to provide an additional layer of security over the enable
password command. The enable secret command provides better security by storing the enable
secret password using a non-reversible cryptographic function. The added layer of security
encryption provided is useful in environments where the password crosses the network or is
stored on a TFTP server. When both the enable password and enable secret passwords are
configured, the router expects the password as defined in the enable secret command. In this
case, the router ignores the password defined in the enable password command.
5. Remove the enable password. Because the enable secret is configured, the enable password
is no longer necessary. IOS commands can be removed from the configuration using the no form
of the command.
Page 6 of 11
DALLAS(config)#no enable password
DALLAS(config)#
6. Configure a message-of-the-day banner using the banner motd command.
DALLAS(config)#banner motd &
Enter TEXT message. End with the character '&'.
********************************
!!!AUTHORIZED ACCESS ONLY!!!
********************************
&
DALLAS(config)#
When does this banner display?
______________________________________________________________________________
_____
______________________________________________________________________________
_____
Why should every router have a message-of-the-day banner?
______________________________________________________________________________
_____
______________________________________________________________________________
_____
7. Configure the console password on the router. Use cisco as the password. When you are
finished, exit from line configuration mode.
DALLAS(config)#line console 0
DALLAS(config-line)#password cisco
DALLAS(config-line)#login
DALLAS(config-line)#exit
DALLAS(config)#
8. Configure the password for the virtual terminal lines. Use cisco as the password. When you
are finished, exit from line configuration mode.
DALLAS(config)#line vty 0 4
DALLAS(config-line)#password cisco
DALLAS(config-line)#login
DALLAS(config-line)#exit
DALLAS(config)#
9. Configure the FastEthernet 0/0 interface with the IP address 10.0.0.1/24.
DALLAS(config)#interface fastethernet 0/0
Page 7 of 11
DALLAS(config-if)#ip address 10.0.0.1 255.255.255.0
DALLAS(config-if)#no shutdown
%LINK-5-CHANGED: Interface FastEthernet0/0, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up
DALLAS(config-if)#
10. Use the description command to provide a description for this interface.
DALLAS(config-if)#description DALLAS LAN
DALLAS(config-if)#
11. Configure the Serial0/0/0 interface with the IP address 172.16.0.1 /24. Set the clock rate to
64000.
Note: Because the routers in the labs will not be connected to a live leased line, one of the
routers will need to provide the clocking for the circuit. This is normally provided to each of the
routers by the service provider. To provide this clocking signal in the lab, one of the routers will
need to act as the DCE on the connection. This function is achieved by applying the clock rate
64000 command on the serial 0/0/0 interface, where the DCE end of the null modem cable has
been connected.
DALLAS(config-if)#interface serial 0/0/0
DALLAS(config-if)#ip address 172.16.0.1 255.255.255.0
DALLAS(config-if)#clock rate 64000
DALLAS(config-if)#no shutdown
DALLAS(config-if)#
Note: The interface will not be activated until the serial interface on Houston Router is
configured and activated.
12. Use the description command to provide a description for this interface.
DALLAS(config-if)#description Link to HOUSTON
DALLAS(config-if)#
13. Use the end command to return to privileged EXEC mode.
DALLAS(config-if)#end
DALLAS#
14. Save the DALLAS configuration using the copy running-config startup-config command.
DALLAS#copy running-config startup-config
Building configuration...
[OK]
Page 8 of 11
DALLAS#
Task 4: Perform Basic Configuration of Router HOUSTON.
1. For HOUSTON, repeat Steps 1 through 10 from Task 6.
2. Configure the Serial 0/0/0 interface with the IP address 172.16.0.2/24.
HOUSTON(config)#interface serial 0/0/0
HOUSTON(config-if)#ip address 172.16.0.2 255.255.255.0
HOUSTON(config-if)#no shutdown
%LINK-5-CHANGED: Interface Serial0/0/0, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0, changed state to up
HOUSTON(config-if)#
3. Use the description command to provide a description for this interface.
HOUSTON(config-if)#description Link to DALLAS
HOUSTON(config-if)#
4. Configure the FastEthernet 0/0 interface with the IP address 192.168.0.1/24.
HOUSTON(config-if)#interface fastethernet 0/0
HOUSTON(config-if)#ip address 192.168.0.1 255.255.255.0
HOUSTON(config-if)#no shutdown
%LINK-5-CHANGED: Interface FastEthernet0/0, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up
HOUSTON(config-if)#
5. Use the description command to provide a description for this interface.
HOUSTON(config-if)#description HOUSTON LAN
HOUSTON(config-if)#
6. Use the end command to return to privileged EXEC mode.
HOUSTON(config-if)#end
HOUSTON#
7. Save the HOUSTON configuration using the copy running-config startup-config command,
HOUSTON#copy running-config startup-config
Building configuration...
[OK]
HOUSTON#
Page 9 of 11
Task 5: Configure IP Addressing on the Host PCs.
1. Configure the host PC1 that is attached to DALLAS with an IP address of 10.0.0.2/24 and a
default gateway of 10.0.0.1.
2. Configure the host PC2 that is attached to HOUSTON with an IP address of 192.168.0.2/24
and a default gateway of 192.168.0.1.
Task 6: Examine Router show Commands.
There are many show commands that can be used to examine the operation of the router. In both
privileged EXEC and user EXEC modes, the command show ? provides a list of available show
commands. The list is considerably longer in privileged EXEC mode than it is in user EXEC
mode.
1. The show running-config command is used to display the contents of the currently running
configuration file. From privileged EXEC mode on the DALLAS router, examine the output of
the show running-config command. If the –-More-- prompt appears, press the Spacebar to view
the remainder of the command output. Take a snip of the output and paste in a Word document.
DALLAS#show running-config
2. The show startup-config command displays the startup configuration file contained in
NVRAM. From privileged EXEC mode on the DALLAS router, examine the output of the show
startup-config command. If the –-More-- prompt appears, press the Spacebar to view the
remainder of the command output. Take a snip of the output and paste in a Word document.
3. The show interfaces command displays statistics for all interfaces configured on the router. A
specific interface can be added to the end of this command to display the statistics for only that
interface. From privileged EXEC mode on the DALLAS router, examine the output of the show
interfaces fastEthernet0/0 command. If the –-More-- prompt appears, press the Spacebar to
view the remainder of the command output. Take a snip of the output and paste in a Word
document.
DALLAS# show interfaces fastEthernet 0/0
4. The show version command displays information about the currently loaded software version
along with hardware and device information. From privileged EXEC mode on the DALLAS
router, examine the output of the show version command. If the –-More-- prompt appears, press
the Spacebar to view the remainder of the command output. Take a snip of the output and paste
in a Word document.
Page 10 of 11
DALLAS#show version
5. The show ip interface brief command displays a summary of the usability status information
for each interface. From privileged EXEC mode on the DALLAS router, examine the output of
the show ip interface brief command. If the –-More-- prompt appears, press the Spacebar to
view the remainder of the command output. Take a snip of the output and paste in a Word
document.
DALLAS#show ip interface brief
Task 7: Ping and Traceroute
1. The ping command is a useful tool for troubleshooting Layers 1 though 3 of the OSI model
and diagnosing basic network connectivity. This operation can be performed at either the user or
privileged EXEC modes. Using ping sends an Internet Control Message Protocol (ICMP) packet
to the specified device and then waits for a reply. Pings can be sent from a router or a host PC.
Take a snip of the output and paste in a Word document.
Use the ping command to test connectivity between the DALLAS router and PC1.
DALLAS#ping 10.0.0.2
Each exclamation point (!) indicates a successful echo. Each period (.) on the display indicates
that the application on the router timed out while it waited for a packet echo from a target. The
first ping packet failed because the router did not have an ARP table entry for the destination
address of the IP packet. Because there is no ARP table entry, the packet is dropped. The router
then sends an ARP request, receives a response, and adds the MAC address to the ARP table.
When the next ping packet arrives, it will be forwarded and be successful.
Repeat the ping from DALLAS to PC1.
DALLAS#ping 10.0.0.2
All of the pings are successful this time because the router has an entry for the destination IP
address in the ARP table.
Send an extended ping from DALLAS to PC1.
To accomplish this, type ping at the privileged EXEC prompt and press Enter. Fill out the rest
of the prompts as shown:
DALLAS#ping
Protocol [ip]:
Target IP address: 10.0.0.2
Repeat count [5]: 10
Datagram size [100]:
Timeout in seconds [2]:
Page 11 of 11
Extended commands [n]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 10, 100-byte ICMP Echos to 192.168.1.10, timeout is 2 seconds:
!!!!!!!!!!
Success rate is 100 percent (10/10), round-trip min/avg/max = 53/77/94 ms
DALLAS#
Send a ping from PC1 to DALLAS. Open the Command Prompt on PC1 and type ping
10.0.0.1.
Using traceroute.
The traceroute command is an excellent utility for troubleshooting the path that a packet takes
through an internetwork of routers. It can help to isolate problem links and routers along the way.
The traceroute command uses ICMP packets and the error message generated by routers when
the packet exceeds its Time-To-Live (TTL). This operation can be performed at either the user or
privileged EXEC modes. The Windows version of this command is tracert.
Use the traceroute command at the DALLAS privileged EXEC prompt to discover the path that a
packet will take from the DALLAS router to PC1. Take a snip of the output and paste in a Word
document.
DALLAS#traceroute 10.0.0.2
Use the tracert command at the Windows command prompt to discover the path that a
packet will take from PC1 to the Dallas Router.
C:\>tracert 10.0.0.1
Lab is complete. Practice setting up routers until you can do it in your sleep! LOL!
