Lab Practice 4: Performing an Initial Router Configuration
Topology Diagram
Addressing Table
Lab Objectives
Upon finishing this lab you will be able to;
Configure the router host name.
Configure passwords.
Configure banner messages.
Verify the router configuration.
Scenario
In this lab activity, you will create a network that is like the one shown in the Topology Diagram. Begin
by cabling the network as shown in the Topology Diagram. You will use the Cisco IOS CLI to apply an
initial configuration to a router, including host name, passwords, a message-of-the-day (MOTD) banner,
and other basic settings. Use the IP addresses that are provided in the Topology Diagram to apply an
addressing scheme to the network devices. When the network configuration is complete, examine the
routing tables to verify that the network is operating properly.
Task 1: Cable the Network.
Cable a network that is like the one in the Topology Diagram. The output used in this lab is from 1841
routers. You can use any current router in your lab if it has the required interfaces as shown in the
topology. Be sure to use the appropriate type of Ethernet cable to connect from host to switch, switch
to router, and host to router. Be sure to connect the serial DCE cable to router R1 and the serial DTE
cable to router R2.
Answer the following questions:
What type of cable is used to connect the Ethernet interface on a host PC to the Ethernet interface on a
switch? Straight through
What type of cable is used to connect the Ethernet interface on a switch to the Ethernet interface on a
router? Straight through
What type of cable is used to connect the Ethernet interface on a router to the Ethernet interface on a
host PC? Cross over
Task 2: Perform Basic Configuration of Router R1.
Step 1: Establish a HyperTerminal session to router R1.
Step 2: Enter privileged EXEC mode.
Router>enable
Router#
Step 3: Enter global configuration mode.
Router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#
Step 4: Configure the router name as R1.
Enter the command hostname R1 at the prompt.
Router(config)#hostname R1
R1(config)#
Step 5: Disable DNS lookup.
Disable DNS lookup with the no ip domain-lookup command.
R1(config)#no ip domain-lookup
R1(config)#
Why would you want to disable DNS lookup in a lab environment?
_______________________________________________________________________________
_______________________________________________________________________________
What would happen if you disabled DNS lookup in a production environment?
_______________________________________________________________________________
Task 3: Configure privileged mode and secret passwords
Configure the privileged mode and secret passwords.
a. In global configuration mode, set the password to;
R1(config)#enable password cisco
Set an encrypted privileged password to cisco123 using the secret command.
R1(config)#enable secret cisco123
Task 4: Configure console password.
a. In global configuration mode, switch to line configuration mode to specify the console line.
R1(config)#line console 0
b. Set the password to cisco, require that the password be entered at login, and then exit line
configuration mode.
R1(config-line)#password cisco
R1(config-line)#login
R1(config-line)#exit
R1(config)#
Task 5: Configure password for the virtual terminal lines to allow Telnet access to the router.
a. In global configuration mode, switch to line configuration mode to specify the vty lines.
R1(config)#line vty 0 4
b. Set the password to cisco123, require that the password be entered at login, exit line
configuration mode, and then exit the configuration session.
R1(config-line)#password cisco
R1(config-line)#login
R1(config-line)#exit
R1(config)#
Task 6: Configure password encryption and Message of the Day (MOTD) banner
a. Currently, the line passwords and the enable password are shown in clear text when you show the
running configuration. Verify this now by entering the show running-config command. To avoid the
security risk of someone looking over your shoulder and reading the passwords, encrypt all clear
text passwords.
R1(config)#service password-encryption
b. Use the show running-config command again to verify that the passwords are encrypted. To
provide a warning when someone attempts to log in to the router, configure a MOTD banner.
R1(config)#banner motd $Authorized Access Only!$
c. Test the banner and passwords. Log out of the router by typing the exit command twice. The banner
displays before the prompt for a password.
d. Save the running configuration to the startup configuration.
R1(config)#end
R1#copy run start
Task 7: Configure FastEthernet 0/0 interface
Configure the FastEthernet0/0 interface with the IP address 192.168.1.1/24.
R1(config)#interface fastethernet 0/0
R1(config-if)#ip address 192.168.1.1 255.255.255.0
R1(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
R1(config-if)#
Task 8: Configure the Serial0/0/0 interface.
Step 1: Configure the Serial0/0/0 interface with the IP address 192.168.2.1/24. Set the clock rate to
64000. R1(config-if)#interface serial 0/0/0
R1(config-if)#ip address 192.168.2.1 255.255.255.0
R1(config-if)#clock rate 64000
R1(config-if)#no shutdown
R1(config-if)#
Note: The interface will be activated until the serial interface on R2 is configured and activated
Step 2: Return to privileged EXEC mode.
Use the end command to return to privileged EXEC mode.
R1(config-if)#end
R1#
Step 3: Save the R1 configuration.
Save the R1 configuration using the copy running-config startup-config command.
R1#copy running-config startup-config
Building configuration... [OK]
R1#
What is a shorter version of this command? _______________________
Task 9: Perform Basic Configuration of Router R2.
Step 1: For R2, repeat steps undertaken under Task 2 to 6 for R1.
Step 2: Configure the Serial 0/0/0 interface.
Configure the Serial 0/0/0 interface with the IP address 192.168.2.2/24.
R2(config)#interface serial 0/0/0
R2(config-if)#ip address 192.168.2.2 255.255.255.0
R2(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
R2(config-if)#
Step 3: Configure the FastEthernet0/0 interface.
Configure the FastEthernet0/0 interface with the IP address 192.168.3.1/24.
R2(config-if)#interface fastethernet 0/0
R2(config-if)#ip address 192.168.3.1 255.255.255.0
R2(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
R2(config-if)#
Step 4: Return to privileged EXEC mode.
Use the end command to return to privileged EXEC mode.
R2(config-if)#end
R2#
Step 5: Save the R2 configuration.
Save the R2 configuration using the copy running-config startup-config command.
R2#copy running-config startup-config
Building configuration... [OK]
R2#
Task 10: Configure IP Addressing on the Host PCs.
Step 1: Configure the host PC1.
Configure the host PC1 that is attached to R1 with an IP address of 192.168.1.10/24 and a default
gateway of 192.168.1.1.
Step 2: Configure the host PC2.
Configure the host PC2 that is attached to R2 with an IP address of 192.168.3.10/24 and a default
gateway of 192.168.3.1.
Task 11: Verify and Test the Configurations.
Step 1: Verify that routing tables have the following routes using the show ip route command.
You will notice that both R1 and R2 have two routes. Both routes are designated with a C. These are the
directly connected networks that were activated when you configured the interfaces on each router. If
you do not see two routes for each router as shown in the following output, proceed to Step 2.
R1#show ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static
route
o - ODR, P - periodic downloaded static route
Gateway of last resort is not set
C 192.168.1.0/24 is directly connected, FastEthernet0/0
C 192.168.2.0/24 is directly connected, Serial0/0/0
------------------------
R2#show ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static
route
o - ODR, P - periodic downloaded static route
Gateway of last resort is not set
C 192.168.2.0/24 is directly connected, Serial0/0/0
C 192.168.3.0/24 is directly connected, FastEthernet0/0
Step 2: Verify interface configurations.
Another common problem is router interfaces that are not configured correctly or not activated. Use the
show ip interface brief command to quickly verify the configuration of each router’s
interfaces. Your output should look similar to the following:
If both interfaces are up and up, then both routes will be in the routing table. Verify this again by using
the show ip route command.
Step 3: Test connectivity.
Test connectivity by pinging from each host to the default gateway that has been configured for that
host.
From the host attached to R1, is it possible to ping the default gateway? __________
From the host attached to R2, is it possible to ping the default gateway? __________
If the answer is no for any of the above questions, troubleshoot the configurations to find the error
using the following systematic process:
1. Check the PCs.
Are they physically connected to the correct router? (Connection could be through a switch or
directly.) ____________
Are link lights blinking on all relevant ports? ____________
2. Check the PC configurations.
Do they match the Topology Diagram? ____________
3. Check the router interfaces using the show ip interface brief command.
Are the interfaces up and up? ____________
If your answer to all three steps is yes, then you should be able to successfully ping the default
gateway.
Step 4: Test connectivity between router R1 and R2.
From the router R1, is it possible to ping R2 using the command ping 192.168.2.2? ____________
From the router R2, is it possible to ping R1 using the command ping 192.168.2.1? ____________
If the answer is no for the questions above, troubleshoot the configurations to find the error using the
following systematic process:
1. Check the cabling.
Are the routers physically connected? ____________
Are link lights blinking on all relevant ports? ____________
2. Check the router configurations.
Do they match the Topology Diagram? ____________
Did you configure the clock rate command on the DCE side of the link? ____________
3. Check the router interfaces using the show ip interface brief command. Are the
interfaces “up” and “up”? ____________
If your answer to all three steps is yes, then you should be able to successfully ping from R2 to R1 and
from R2 to R3.
Task 12: Reflection
Step 1: Attempt to ping from the host connected to R1 to the host connected to R2.
This ping should be unsuccessful.
Step 2: Attempt to ping from the host connected to R1 to router R2.
This ping should be unsuccessful.
Step 3: Attempt to ping from the host connected to R2 to router R1.
This ping should be unsuccessful.
What is missing from the network that is preventing communication between these devices?
________________________________________________________________________________
________________________________________________________________________________
Task 13: Documentation
On each router, capture the following command output to a text (.txt) file and save for future reference.
show running-config
show ip route
show ip interface brief
