Scribd
Upload
1K views2 pages

4.4.8 Packet Tracer - Troubleshoot Inter-VLAN Routing-OSCARMALDONADO

This document describes troubleshooting connectivity issues between PCs in different VLANs connected by a router. The objectives are to locate network problems, implement solutions, and verify connectivity. Upon examining the network, four issues were identified: 1) the default gateway for PC3 was incorrect; 2) VLAN assignments on router subinterfaces were incorrect; 3) router subinterface G0/1.10 was inactive; and 4) the switch port was configured as an access port instead of trunk. The recommended solutions are: 1) change the default gateway for PC3; 2) remove and reapply VLAN encapsulation on router subinterfaces; 3) enable subinterface G0/1.10; and 4) configure the switch port as a

Uploaded by

Oscar Maldonado
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
1K views2 pages

4.4.8 Packet Tracer - Troubleshoot Inter-VLAN Routing-OSCARMALDONADO

This document describes troubleshooting connectivity issues between PCs in different VLANs connected by a router. The objectives are to locate network problems, implement solutions, and verify connectivity. Upon examining the network, four issues were identified: 1) the default gateway for PC3 was incorrect; 2) VLAN assignments on router subinterfaces were incorrect; 3) router subinterface G0/1.10 was inactive; and 4) the switch port was configured as an access port instead of trunk. The recommended solutions are: 1) change the default gateway for PC3; 2) remove and reapply VLAN encapsulation on router subinterfaces; 3) enable subinterface G0/1.10; and 4) configure the switch port as a

Uploaded by

Oscar Maldonado
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

OSCAR MALDONADO---REDES II

Packet Tracer - Troubleshoot Inter-VLAN Routing


Addressing Table
Device Interface IP Address Subnet Mask Default Gateway VLAN

R1 G0/1.10 172.17.10.1 255.255.255.0 N/A VLAN 10


G0/1.30 172.17.30.1 255.255.255.0 N/A VLAN 30
PC1 NIC 172.17.10.10 255.255.255.0 172.17.10.1 VLAN 10
PC3 NIC 172.17.30.10 255.255.255.0 172.17.30.1 VLAN 30

Objectives
Part 1: Locate Network Problems
Part 2: Implement the Solution
Part 3: Verify Network Connectivity

Scenario
In this activity, you will troubleshoot connectivity problems caused by improper configurations related to
VLANs and inter-VLAN routing.

Instructions

Part 1: Locate the Network Problems


Examine the network and locate the source of any connectivity issues.

Commands you may find useful include:


R1# show ip interface brief
R1# show interface g0/1.10
R1# show interface g0/1.30
S1# show interface trunk
• Test connectivity and use the necessary show commands to verify configurations.
• Verify that all configured settings match the requirements shown in the Addressing Table.
• List all of the problems and possible solutions in the Documentation Table.
Documentation Table

 2013 - 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 1 of 2 www.netacad.com
Packet Tracer - Troubleshoot Inter-VLAN Routing

Problems Solutions

Dirección de PC3 que viene por defecto es Direccion incorrecta 172.17.10.1


incorrecta Direccion correcta 172.17.30.1
Se debe cambiar la dirección
La asignación d VLAN de la sub-interfaz se Utilizar no encapsulación dot1Q para
activa en R1. borrar Luego encapsulación dot1Q vlan #
para configurar las subinterfaces
correctas

La sub-interfaz G0 / 1.10 está inactiva y la Para habilitar G0 / 1.10 se utiliza el comando


interfaz G0 / 1 está activa no shutdown.

G0 / 1 en Switch1 está configurada como un Utilizar switchport mode trunk para cambiar la
puerto de acceso interfaz del modo de acceso.

Part 2: Implement the Solutions


Implement your recommended solutions.

Part 3: Verify Network Connectivity


Verify the PCs can ping each other and R1. If not, continue to troubleshoot until the pings are successful.

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

You might also like