Activity 2 :
Topology
Objectives
Part 1: Verify the Default Switch
Configuration
Part 2: Configure a Basic Switch
Configuration
Part 3: Configure a MOTD Banner
Part 4: Save Configuration Files to
NVRAM
Part 5: Configure S2
Background
In this activity, you will perform basic
switch configurations. You will secure access to the command-line interface (CLI)
and console ports using encrypted and plain text passwords. You will also learn
how to configure messages for users logging into the switch. These banners are
also used to warn unauthorized users that access is prohibited.
Part 1: Verify the Default Switch Configuration
Step 1:
Enter privileged EXEC mode.
You can access all switch 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.
The privileged EXEC command set includes
those commands contained in user EXEC mode, as well as the configure command
through which access to the remaining command modes are gained.
- Click S1 and then the CLI tab.
Press Enter.
- Enter privileged EXEC mode by
entering the enable command:
Switch> enable
Switch#
Notice that the prompt changed in the
configuration to reflect privileged EXEC mode.
Step 2:
Examine the current switch
configuration.
- Enter the show running-config command.
Switch# show
running-config
- Answer the following questions:
1)
How many FastEthernet
interfaces does the switch have?
2)
How many Gigabit
Ethernet interfaces does the switch have?
3)
What is the range of values
shown for the vty lines?
4)
Which command will display the
current contents of non-volatile random-access memory (NVRAM)?
5) Why does
the switch respond with startup-config is not present?
Part 2: Create a Basic Switch Configuration
Step 1:
Assign a name to a switch.
To configure parameters on a switch, you
may be required to move between various configuration modes. Notice how the
prompt changes as you navigate through the switch.
Switch# configure
terminal
Switch(config)# hostname S1
S1(config)# exit
S1#
Step 2:
Secure access to the console
line.
To secure access to the console line,
access config-line mode and set the console password to letmein.
S1# configure
terminal
Enter configuration commands, one per line. End
with CNTL/Z.
S1(config)# line
console 0
S1(config-line)# password letmein
S1(config-line)# login
S1(config-line)# exit
S1(config)# exit
%SYS-5-CONFIG_I: Configured from console by
console
S1#
Why is the login command required?
Step 3:
Verify that console access is
secured.
Exit privileged mode to verify that the console
port password is in effect.
S1# exit
Switch con0 is now available
Press RETURN to get started.
User Access Verification
Password:
S1>
Note: If the switch did not prompt you for a password, then you did not configure
the login parameter in Step 2.
Step 4:
Secure privileged mode access.
Set the enable password to c1$c0.
This password protects access to privileged mode.
Note:
The 0 in
c1$c0 is a zero, not a capital O.
This password will not grade as correct until after you encrypt it in Step 8.
S1> enable
S1# configure
terminal
S1(config)# enable
password c1$c0
S1(config)# exit
%SYS-5-CONFIG_I: Configured from console by
console
S1#
Step 5:
Verify that privileged mode
access is secure.
- Enter the exit command again to log out of the switch.
- Press <Enter> and you will now be asked for a password:
- The first password is the
console password you configured for line
con 0. Enter this password to return to user EXEC mode.
- Enter the command to access
privileged mode.
- Enter the second password you
configured to protect privileged EXEC mode.
- Verify your configurations by
examining the contents of the running-configuration file:
S1# show running-config
Notice how the console and enable
passwords are both in plain text. This could pose a security risk if someone is
looking over your shoulder.
Step 6:
Configure an encrypted password
to secure access to privileged mode.
The enable
password should be replaced with the newer encrypted secret password using
the enable secret command. Set the enable
secret password to itsasecret.
S1(config)# enable
secret itsasecret
Note: The enable secret
password overrides the enable
password. If both are configured on the switch, you must enter the enable secret password to enter
privileged EXEC mode.
Step 7:
Verify that the enable secret password
is added to the configuration file.
- Enter the show running-config command again to verify the new enable secret password is configured.
Note:
You can abbreviate show running-config as
- What is displayed for the enable secret password?
- Why is the enable secret password displayed differently from what we configured?
Step 8:
Encrypt the enable and console
passwords.
As you noticed in Step 7, the enable secret password was encrypted,
but the enable and console passwords were still in plain
text. We will now encrypt these plain text passwords using the service password-encryption command.
S1(config)# service
password-encryption
If you configure any more passwords on
the switch, will they be displayed in the configuration file as plain text or
in encrypted form? Explain.
Part 3: Configure a MOTD Banner
Step 1:
Configure a message of the day (MOTD)
banner.
The Cisco IOS command set includes a
feature that allows you to configure messages that anyone logging onto the
switch sees. These messages are called message of the day, or MOTD banners.
Enclose the banner text in quotations or use a delimiter different from any
character appearing in the MOTD string.
S1(config)# banner
motd "This is a secure system. Authorized Access Only!"
%SYS-5-CONFIG_I: Configured from console by
console
1)
When will this banner be
displayed?
2)
Why should every switch have a MOTD
banner?
Part 4: Save Configuration Files to NVRAM
Step 1:
Verify that the configuration
is accurate using the show run command.
Step 2:
Save the configuration file.
You have completed the basic
configuration of the switch. 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.
S1# copy
running-config startup-config
Destination filename [startup-config]?[Enter]
Building configuration...
What
is the shortest, abbreviated version of the copy running-config startup-config command?
Step 3:
Examine the startup
configuration file.
Which
command will display the contents of NVRAM?
Are all
the changes that were entered recorded in the file?
You have completed the configuration on
S1. You will now configure S2. If you cannot remember the commands, refer to
Parts 1 to 4 for assistance.
Configure S2 with the following
parameters:
b. Protect access to the console using the letmein password.
c. Configure an enable password of c1$c0
and an enable secret password of itsasecret.
d. Configure a message to those logging into the switch with the
following message:
Authorized access only. Unauthorized access
is prohibited and violators will be prosecuted to the full extent of the law.
e. Encrypt all plain text passwords.
f. Ensure that the configuration is correct.
g. Save the configuration file to avoid loss if the switch is powered
down.
 |
| Assessment Result 2 |
Activity 3 :
Topology
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
configurations. You will secure access to the CLI and console port using
encrypted and plain text 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.
Part 1: Verify the Default Router Configuration
Step 1:
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.
Step 2:
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.
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
- Answer the following questions:
What
is the router’s hostname?
How
many Fast Ethernet interfaces does the Router have?
How
many Gigabit Ethernet interfaces does the Router have?
How
many Serial interfaces does the router have?
What
is the range of values shown for the vty lines?
- Display the current contents of
NVRAM.
Router# show
startup-config
startup-config is not present
Why does the router respond
with the startup-config is not present message?
Part 2: 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 router.
Step 1:
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.
- R1 as the hostname.
- Use the following passwords:
1)
Console: letmein
2)
Privileged EXEC, unencrypted: cisco
3)
Privileged EXEC, encrypted: itsasecret
- Encrypt all plain text
passwords.
- Message of the day text: Unauthorized
access is strictly prohibited.
Step 2:
Verify the initial settings on
R1.
- Verify the initial settings by
viewing the configuration for R1. What command do you use?
- 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:
Why should every router have a
message-of-the-day (MOTD) banner?
If you are not prompted for a password,
what console line command did you forget to configure?
- Enter the passwords necessary
to return to privileged EXEC mode.
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.
Part 2: Save the Running Configuration File
Step 1:
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.
What command did you enter to save the
configuration to NVRAM?
What
is the shortest, unambiguous version of this command?
Which command displays the contents of
the NVRAM?
- Verify that all of the
parameters configured are recorded. If not, analyze the output and determine
which commands were not done or were entered incorrectly. You can also click Check Results in the instruction
window.
Step 2:
Optional bonus: 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 now 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.
- Examine the contents of flash
using the show flash
command:
R1# show
flash
How
many files are currently stored in flash?
Which
of these files would you guess is the IOS image?
Why do you think this file is the IOS
image?
- Save the startup configuration
file to flash using the following commands:
R1# copy
startup-config flash
Destination filename [startup-config]
The router prompts 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.
 |
| Assessment Result 3 |
Activity 4
Topology
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 are provided to assist you
in using verification commands.
Part 1: Display Router Information
Step 1:
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.
- Which command displays the
statistics for all interfaces configured on a router?
- Which command displays the
information about the Serial 0/0/0 interface only?
- 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?
2)
What is the bandwidth on the
Serial 0/0/0 interface?
- 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?
2)
What is the MAC address of the GigabitEthernet
0/0 interface?
3)
What is the bandwidth on the GigabitEthernet
0/0 interface?
Step 2:
Display a summary list of the
interfaces on R1.
- Which command displays a brief
summary of the current interfaces, statuses, and IP addresses assigned to them?
- Enter the command on each
router and answer the following questions:
1)
How many serial interfaces are
there on R1 and R2?
2)
How many Ethernet interfaces
are there on R1 and R2?
3)
Are all the Ethernet interfaces
on R1 the same? If no, explain the
difference(s).
Step 3:
Display the routing table on R1.
- What command displays the
content of the routing table?
- Enter the command on R1 and answer the following questions:
1) How
many connected routes are there (uses the C code)?
Which
route is listed?
1)
How does a router handle
a packet destined for a network that is not listed in the routing table?
Part 2: Configure Router Interfaces
Step 1:
Configure the GigabitEthernet
0/0 interface on R1.
- Enter the following commands to
address and activate the GigabitEthernet 0/0 interface on R1:
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
- It
is good practice to configure a description for each interface to help document
the network information. Configure an interface
description indicating to which device it is connected.
R1(config-if)# description LAN connection to S1
- 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
Step 2:
Configure the remaining Gigabit
Ethernet Interfaces on R1 and R2.
- 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.
- Verify interface
configurations.
Step 3:
Back up the configurations to
NVRAM.
Save
the configuration files on both routers to NVRAM. What command did you use?
Part 3:
Verify the Configuration
Step 1:
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
active.
How many interfaces on R1 and R2 are configured with IP addresses and in the “up” and “up” state?
What
part of the interface configuration is NOT displayed in the command output?
What commands can you use to verify this
part of the configuration?
- Use the show ip route command on both R1
and R2 to view the current
routing tables and answer the following questions:
1)
How many connected
routes (uses the C code) do you see
on each router?
2)
How many EIGRP routes (uses the
D code) do you see on each router?
3)
If the router knows all the
routes in the network, then the number of connected routes and dynamically
learned routes (EIGRP) should equal the total number of LANs and WANs. How many
LANs and WANs are in the topology?
4)
Does this number match the
number of C and D routes shown in the routing table?
Note: If your answer is
“no”, then you are missing a required configuration. Review the steps in Part 2.
Step 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 should 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.
 |
| Assessment Result 4 |