Scribd
Upload
251 views

2.9.2 Lab - Basic Switch and End Device Configuration

Uploaded by

CRISTIAN DAVID VIASUS VEGA
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
251 views

2.9.2 Lab - Basic Switch and End Device Configuration

Uploaded by

CRISTIAN DAVID VIASUS VEGA
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 8

Lab - Basic Switch and End Device Configuration

CRISTIAN DAVID VIASUS VEGA – EQUIPOS ACTIVOS - 2236876

Topology

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.

© 2013 - 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 1 of 8 www.netacad.com
Lab - Basic Switch and End Device Configuration

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

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.
b. Connect the two switches.
c. Connect the PCs to their respective switches.
d. Visually inspect network connections.

Step 2: Configure PC Hosts


a. Configure static IP address information on the PCs according to the Addressing Table.
b. Verify PC settings and connectivity.

© 2013 - 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 2 of 8 www.netacad.com
Lab - Basic Switch and End Device Configuration

Step 3: Configure and Verify Basic Switch Settings


a. Console into the switch. Enter the global configuration
b. Give the switch a name according to the Addressing Table.
Hostname S1 in config terminal
Hostname S2
c. Prevent unwanted DNS lookups.
no ip domain-lookup in config terminal

d. Enter local passwords. Use class as the privileged EXEC password and cisco as the password for
console access.
enable password cisco in line terminal
password secret class in privileged mode

© 2013 - 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 3 of 8 www.netacad.com
Lab - Basic Switch and End Device Configuration

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


S1> Int vlan1 192.168.1.1 255.255.255.0
No shutdown
S2> int vlan1 192.168.1.2 255.255.255.0
No shutdown
f. Enter a login MOTD banner to warn about unauthorized access.
banner motd #Se requiere permisos para ingresar#
g. Save the configuration.
The command is [copy run star or wr] in in privileged mode
h. Display the current configuration.
sh run
sh star

© 2013 - 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 4 of 8 www.netacad.com
Lab - Basic Switch and End Device Configuration

Muestra de las configuraciones guardadas en el Switch 1 (S1)

i. Display the IOS version and other useful switch information.


show version

j. Display the status of the connected interfaces on the switch.


sh ip int brief

Close Configuration Window.

k. Configure switch S2.

© 2013 - 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 5 of 8 www.netacad.com
Lab - Basic Switch and End Device Configuration

Muestra de la configuracion guardada, IOS Version & del estado de las interfaces del
Switch 2 (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.

© 2013 - 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 6 of 8 www.netacad.com
Lab - Basic Switch and End Device Configuration

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

Conexion de PC-A a Switch 1 (S1) y Switch 2 (S2)

Conexion de PC-B a Switch 1 (S1) y Switch 2 (S2)

Conexion de PC-B a PC-A

© 2013 - 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 7 of 8 www.netacad.com
Lab - Basic Switch and End Device Configuration

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

Porque los puertos FastEthernet están activos (UP) cuando los cables están conectados a los puertos en
este caso el Switch (S1, S2), sin embargo, los administradores pueden desactivado manualmente (DOWN).
En caso de lo contrario, los puertos están inactivos.

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

1) Dirección IP incorrecta ya sea porque haya quedado mal configurada la IP cuando se cambio el
segmento o rango de la misma.
2) Cando no activamos el puerto con la dirección desde la terminal, se considera inactivo por defecto
3) Medios desconectados por ejemplo un switch apagado o puertos administrativamente desactivados
4) El firewall detecta ese testeo de red y considera una intrusión así que impide el proceso de
comunicación

here.
End of Document

© 2013 - 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 8 of 8 www.netacad.com

You might also like