2.9.

2 Lab – Basic Switch and End Device Configuration

Addressing Table

Device Interface IP Address Subnet Mask

S1 VLAN 1 192.168.1.1 255.255.255.0

S2 VLAN 1 192.168.1.2 255.255.255.0

PC-A NIC 192.168.1.10 255.255.255.0

PC-B NIC 192.168.1.11 255.255.255.0

Objectives

 Set Up the Network Topology

 Configure PC Hosts

 Configure and Verify Basic Switch Settings

Background / Scenario
In this lab, you will build a simple network with two hosts and two switches. You will also configure basic
settings including hostname, local passwords, and login banner. Use show commands to display the
running configuration, IOS version, and interface status. Use the copy command to save device
configurations.

You will apply IP addressing for this lab to the PCs and switches to enable communication between the
devices. Use the ping utility to verify connectivity.

Note: The switches used are Cisco Catalyst 2960s with Cisco IOS Release 15.0(2) (lanbasek9 image).
Other switches and Cisco IOS versions can be used. Depending on the model and Cisco IOS version, the
commands available and output produced might vary from what is shown in the labs.

Note: Make sure that the switches have been erased and have no startup configurations. Refer to
Appendix A for the procedure to initialize and reload a switch.

Required Resources

 2 Switches (Cisco 2960 with Cisco IOS Release 15.0(2) lanbasek9 image or comparable)

 2 PCs (Windows with 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 Ethernet ports on the 2960 switches are autosensing and will accept either a straight-through
or a cross-over cable for all connections. If the switches used in the topology are other than the 2960
model, then it is likely that a cross-over cable will be needed to connect the two switches.

Instructions

Step 1: Set Up the Network Topology

In this step, you will cable the devices together according to the network topology.

a. Power on the devices.

Power on all devices in the topology. The switches do not have a power switch; they will power on as
soon as you plug in the power cord.

b. Connect the two switches.

Connect one end of an Ethernet cable to F0/1 on S1 and the other end of the cable to F0/1 on S2. You
should see the lights for F0/1 on both switches turn amber and then green. This indicates that the
switches have been connected correctly.

c. Connect the PCs to their respective switches.

Connect one end of the second Ethernet cable to the NIC port on PC-A. Connect the other end of the
cable to F0/6 on S1. After connecting the PC to the switch, you should see the light for F0/6 turn amber
and then green, indicating that PC-A has been connected correctly.
Connect one end of the last Ethernet cable to the NIC port on PC-B. Connect the other end of the cable
to F0/18 on S2. After connecting the PC to the switch, you should see the light for F0/18 turn amber and
then green, indicating that the PC-B has been connected correctly.

d. Visually inspect network connections.

After cabling the network devices, take a moment to carefully verify the connections to minimize the
time required to troubleshoot network connectivity issues later.

Step 2: Configure PC Hosts

a. Configure static IP address information on the PCs according to the Addressing Table.

In PC-A, navigate to the Control Panel. In the Category view, under the Network and Internet heading,
click View Network status and tasks > click Change adapter settings

Right-click the desired network adaptor and select Properties.

Select the Internet Protocol Version 4 (TCP/IPv4) and click Properties.

Select Use the following IP address. Enter the IP address for PC-A (192.168.1.10) and subnet mask
(255.255.255.0) as listed in the IP addressing table. You can leave default gateway blank at this time
because there is no router attached to the network. Click OK to continue. Click Close to exit the
Properties window.

Repeat the previous steps to assign the IP address information for PC-B.

b. Verify PC settings and connectivity.

From PC-A, open a Command Prompt to verify the PC settings and connectivity using the ipconfig /all
command at the prompt.
To test the connectivity to PC-B, enter ping 192.168.1.11 at the prompt. The ping should be successful. If
not, troubleshoot as necessary.

Step 3: Configure and Verify Basic Switch Settings

a. Console into the switch. Enter the global configuration mode.

Establish a console connection to the switch from PC-A using Tera Term.

You can access all switch commands in privileged EXEC mode. 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. Enter privileged EXEC mode by entering the
enable command.

The prompt changed from Switch> to Switch# which indicates privileged EXEC mode.
Use the configuration terminal command to enter configuration mode.

The prompt changed to reflect global configuration mode.

b. Give the switch a name according to the Addressing Table.

Use the hostname command to change the switch name to S1.

c. Prevent unwanted DNS lookups.

To prevent the switch from attempting to translate incorrectly entered commands as though they were
hostnames, disable the Domain Name System (DNS) lookup.

d. Enter local passwords. Use class as the privileged EXEC password and cisco as the password for
console access.

To prevent unauthorized access to the switch, configure passwords.

e. Configure and enable the SVI according to the Addressing Table.

A login banner, known as the message of the day (MOTD) banner, should be configured to warn anyone
accessing the switch that unauthorized access will not be tolerated.

The banner motd command requires the use of delimiters to identify the content of the banner
message. The delimiting character can be any character as long as it does not occur in the message. For
this reason, symbols, such as the #, are often used.

g. Save the configuration.

Use the copy command to save the running configuration to the startup file on non-volatile random
access memory (NVRAM).

h. Display the current configuration.

The show running-config command displays the entire running configuration, one page at a time. Use
the spacebar to advance paging. The commands configured in Steps a – h are highlighted below.
i. Display the IOS version and other useful switch information.

Use the show version command to display the IOS version that the switch is running, along with other
useful information. Again, you will need to use the spacebar to advance through the displayed
information.
j. Display the status of the connected interfaces on the switch.

To check the status of the connected interfaces, use the show ip interface brief command. Press the
spacebar to advance to the end of the list.
k. Configure switch S2.

Repeat the previous steps for Switch S2. Make sure the hostname is configured as S2.

l. Record the interface status for the following interfaces.

Interface S1 Status S1 Protocol S2 Status S2 Protocol

F0/1 Up Up Up Up

F0/6 Up Up Down Down

F0/18 Down Down Up Up

VLAN 1 Up Up Up Up

m. From a PC, ping S1 and S2. The pings should be successful.

n. From a switch, ping PC-A and PC-B. The pings should be successful.

Reflection Question

Why some FastEthernet ports on the switches are up and others are down?

The FastEthernet ports are up when cables are connected to the ports unless they were manually
shutdown by the administrators. Otherwise, the ports would be down.

What could prevent a ping from being sent between the PCs?

Wrong IP address, media disconnected, switch powered off or ports administratively down, firewall.