4.4.9 Packet Tracer - Troubleshoot Inter-VLAN Routing – Physical Mode Answers

4.4.9 Packet Tracer - Troubleshoot Inter-VLAN Routing – Physical Mode Answers

Topology

4.4.9 Packet Tracer - Troubleshoot Inter-VLAN Routing - Physical Mode topology

Addressing Table

Device Interface IP Address Subnet Mask Default Gateway
R1 G0/0/1.3 10.3.0.1 255.255.255.0 N/A
G0/0/1.4 10.4.0.1 255.255.255.0
G0/0/1.13 10.13.0.1 255.255.255.0
S1 VLAN 3 10.3.0.11 255.255.255.0 10.3.0.1
S2 VLAN 3 10.3.0.12 255.255.255.0 10.3.0.1
PC-A NIC 10.4.0.50 255.255.255.0 10.4.0.1
PC-B NIC 10.13.0.50 255.255.255.0 10.13.0.1

VLAN Table

VLAN Name Interface Assigned
3 Management S1: VLAN 3
S2: VLAN 3
4 Operations S1: F0/6
7 ParkingLot S1: F0/2-4, F0/7-24, G0/1-2
S2: F0/2-17, F0/19-24, G0/1-2
8 Native N/A
13 Maintenance S2: F0/18

Objectives

  • Part 1: Evaluate Network Operation
  • Part 2: Gather Information, Create an Action Plan, and Implement Corrections

Background / Scenario

All the network devices in this Packet Tracer Physical Mode (PTPM) activity have been preconfigured to include intentional errors that are keeping the inter-VLAN routing from working. Your task is to evaluate the network, identify, and correct the configuration errors to restore full inter-VLAN connectivity. You may find errors with the configurations which are not directly related to inter-VLAN routing. These errors impact the ability of the network devices to perform this function.

Note: The design approach used in this activity is to assess your ability to configure and troubleshoot interVLAN routing only. This design may not reflect networking best practices.

Contents

Instructions

Part 1: Evaluate Network Operation

Requirements:

  • No VLAN 7 traffic is allowed on the trunks because there are no devices in VLAN 7.
  • VLAN 8 is the native VLAN.
  • All trunks are static.
  • End to end connectivity.

a. Use the laptop computer and appropriate cable to console into the network devices for testing and configuration purposes. The login password on all network devices is cisco and the enable password is class. You can click and drag the console connection from the console port of one device to another, but you will have to start a new terminal session.

b. Use the ping command to test the following criteria and record the results in the table below.

From To Ping Results
R1 S1 VLAN 3 (10.3.0.11) Unsuccessful
S2 VLAN 3 (10.3.0.12) Unsuccessful
PC-A (10.4.0.50) Unsuccessful
PC-B (10.13.0.50) Unsuccessful
S1 S2 VLAN 3 (10.3.0.12) Unsuccessful
PC-A (10.4.0.50) Unsuccessful
PC-B (10.13.0.50) Unsuccessful
S2 PC-A (10.4.0.50) Unsuccessful
PC-B (10.13.0.50) Unsuccessful
Ping outputs

R1# ping 10.3.0.11

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.3.0.11, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
R1# ping 10.3.0.12

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.3.0.12, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
R1# ping 10.4.0.50

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.4.0.50, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
R1# ping 10.13.0.50

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.13.0.50, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)

S1# ping 10.3.0.12

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.3.0.12, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
S1# ping 10.4.0.50

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.4.0.50, timeout is 2 seconds:
....
%CDP-4-NATIVE_VLAN_MISMATCH: Native VLAN mismatch discovered on FastEthernet0/1 (1), with S2 FastEthernet0/1 (8).

S1#.
Success rate is 0 percent (0/5)
S1# ping 10.13.0.50

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.13.0.50, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)

S2# ping 10.4.0.50

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.4.0.50, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
S2# ping 10.13.0.50

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.13.0.50, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)


Also check the IP settings of the two PCs:

C:\> ipconfig

FastEthernet0 Connection:(default port)

   Connection-specific DNS Suffix..:
   Link-local IPv6 Address.........: FE80::201:97FF:FE53:6188
   IPv6 Address....................: ::
   IPv4 Address....................: 10.4.0.50
   Subnet Mask.....................: 255.255.255.0
   Default Gateway.................: ::
                                     10.4.0.1

C:\> ipconfig

FastEthernet0 Connection:(default port)

   Connection-specific DNS Suffix..:
   Link-local IPv6 Address.........: FE80::2E0:F7FF:FEC9:9E76
   IPv6 Address....................: ::
   IPv4 Address....................: 10.13.0.50
   Subnet Mask.....................: 255.255.255.0
   Default Gateway.................: ::
                                     10.13.0.1

What we learned:

  • Every ping fails, from the router and from both switches, so the fault is in the trunks and subinterfaces that connect the VLANs, not in one end device.
  • During the tests S1 and S2 log %CDP-4-NATIVE_VLAN_MISMATCH: S1 F0/1 uses native VLAN 1, while S2 F0/1 uses native VLAN 8.
  • PC-A and PC-B have the correct addresses and gateways from the Addressing Table.

Part 2: Gather Information, Create an Action Plan, and Implement Corrections

a. For each requirement that is not met, gather information by examining the running configuration and the routing tables to develop a hypothesis for what is causing the malfunction.

How to reach the devices

Connect the console cable from the laptop to the device you want to check (drag the cable to another device and open a new terminal session). Log in with cisco, then type enable and enter class. Follow the path of the traffic: R1 > S1 F0/5 > S1 F0/1 > S2 F0/1.

Problem 1: R1 – the native VLAN is set on the wrong subinterface
R1# show running-config | section interface GigabitEthernet0/0/1
interface GigabitEthernet0/0/1
 no ip address
 duplex auto
 speed auto
interface GigabitEthernet0/0/1.3
 encapsulation dot1Q 3
 ip address 10.3.0.1 255.255.255.0
interface GigabitEthernet0/0/1.4
 encapsulation dot1Q 4 native
 ip address 10.4.0.1 255.255.255.0
interface GigabitEthernet0/0/1.8
 encapsulation dot1Q 8
 no ip address
interface GigabitEthernet0/0/1.13
 encapsulation dot1Q 13
 ip address 10.13.0.1 255.255.255.0

What we learned:
The native keyword is on G0/0/1.4 (VLAN 4), but the switches use VLAN 8 as the native VLAN. R1 treats untagged frames as VLAN 4 and sends VLAN 4 traffic untagged, while the switches put untagged frames into VLAN 8.

Problem 2: S1 – F0/5 (link to R1) is an access port
S1# show interfaces fastethernet 0/5 switchport
Name: Fa0/5
Switchport: Enabled
Administrative Mode: static access
Operational Mode: static access
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: native
Negotiation of Trunking: Off
Access Mode VLAN: 3 (Management)
Trunking Native Mode VLAN: 1 (default)
Voice VLAN: none
Administrative private-vlan host-association: none
Administrative private-vlan mapping: none
Administrative private-vlan trunk native VLAN: none
Administrative private-vlan trunk encapsulation: dot1q
Administrative private-vlan trunk normal VLANs: none
Administrative private-vlan trunk private VLANs: none
Operational private-vlan: none
Trunking VLANs Enabled: All
Pruning VLANs Enabled: 2-1001
Capture Mode Disabled
Capture VLANs Allowed: ALL
Protected: false
Unknown unicast blocked: disabled
Unknown multicast blocked: disabled
Appliance trust: none

What we learned:
F0/5, the link to R1, is a static access port in VLAN 3. It cannot carry the tagged frames of VLANs 4, 8 and 13 to the R1 subinterfaces.

Problem 3: S1 – F0/1 (link to S2) has native VLAN 1 and an incomplete allowed list
S1# show interfaces trunk
Port        Mode         Encapsulation  Status        Native vlan
Fa0/1       on           802.1q         trunking      1

Port        Vlans allowed on trunk
Fa0/1       4,8,13

Port        Vlans allowed and active in management domain
Fa0/1       4,8

Port        Vlans in spanning tree forwarding state and not pruned
Fa0/1       4

What we learned:
Only F0/1 is a trunk (F0/5 is missing, Problem 2). Its native VLAN is 1 instead of 8, VLAN 3 is missing from the allowed list, and VLAN 13 is allowed but not active because it does not exist on S1 (Problem 5).


Key concept: the native VLAN must match on every trunk and on the router
On an 802.1Q trunk, frames of every VLAN carry a VLAN tag except those of the native VLAN, which cross the link untagged. Each end puts untagged frames it receives into its own native VLAN, so both ends must agree. Here S1 F0/1 used native VLAN 1 while S2 F0/1 used 8, and CDP reported it with %CDP-4-NATIVE_VLAN_MISMATCH. On a router-on-a-stick, the native VLAN is set on the subinterface with encapsulation dot1Q <vlan> native; it must be the same VLAN as on the switch trunk (VLAN 8), and only one subinterface can be native.

Problem 4: S2 – F0/1 (link to S1) is missing VLANs 3 and 13
S2# show interfaces trunk
Port        Mode         Encapsulation  Status        Native vlan
Fa0/1       on           802.1q         trunking      8

Port        Vlans allowed on trunk
Fa0/1       4,8

Port        Vlans allowed and active in management domain
Fa0/1       4,8

Port        Vlans in spanning tree forwarding state and not pruned
Fa0/1       4
S2# show vlan brief

VLAN Name                             Status    Ports
---- -------------------------------- --------- -------------------------------
1    default                          active
3    Management                       active
4    Operations                       active
7    ParkingLot                       active    Fa0/2, Fa0/3, Fa0/4, Fa0/5
                                                Fa0/6, Fa0/7, Fa0/8, Fa0/9
                                                Fa0/10, Fa0/11, Fa0/12, Fa0/13
                                                Fa0/14, Fa0/15, Fa0/16, Fa0/17
                                                Fa0/19, Fa0/20, Fa0/21, Fa0/22
                                                Fa0/23, Fa0/24, Gig0/1, Gig0/2
8    Native                           active
13   Maintenance                      active    Fa0/18
1002 fddi-default                     active
1003 token-ring-default               active
1004 fddinet-default                  active
1005 trnet-default                    active

What we learned:
S2 F0/1 already uses native VLAN 8, but it allows only VLANs 4 and 8. VLAN 3 (management) and VLAN 13 (PC-B on F0/18) exist on S2 but cannot cross the trunk.

Problem 5: S1 – VLAN 13 does not exist
S1# show vlan brief

VLAN Name                             Status    Ports
---- -------------------------------- --------- -------------------------------
1    default                          active
3    Management                       active    Fa0/5
4    Operations                       active    Fa0/6
7    ParkingLot                       active    Fa0/2, Fa0/3, Fa0/4, Fa0/7
                                                Fa0/8, Fa0/9, Fa0/10, Fa0/11
                                                Fa0/12, Fa0/13, Fa0/14, Fa0/15
                                                Fa0/16, Fa0/17, Fa0/18, Fa0/19
                                                Fa0/20, Fa0/21, Fa0/22, Fa0/23
                                                Fa0/24, Gig0/1, Gig0/2
8    Native                           active
1002 fddi-default                     active
1003 token-ring-default               active
1004 fddinet-default                  active
1005 trnet-default                    active

What we learned:
S1 has VLANs 1, 3, 4, 7 and 8, but no VLAN 13. Even with VLAN 13 allowed on the trunks, S1 would drop PC-B traffic on its way to R1.

b. Create an action plan that you think will fix the issue. Develop a list of all the commands you intend to issue to fix the issue, and a list of all the commands you need to revert the configuration, should your action plan fail to correct the issue.

Hint: If you need to reset a switchport to default configuration, use the default interface interface name command.

As an example for F0/10:

S1(config)# default interface fastethernet 0/10

c. Execute your action plans one at a time for each criterion that fails and record the fix actions.

Fix 1: R1: Remove the native keyword from G0/0/1.4 and make G0/0/1.8 the native VLAN subinterface.

R1(config)# interface gigabitethernet 0/0/1.4
R1(config-subif)# encapsulation dot1Q 4
R1(config-subif)# ip address 10.4.0.1 255.255.255.0
R1(config-subif)# interface gigabitethernet 0/0/1.8
R1(config-subif)# encapsulation dot1Q 8 native
R1# show running-config | section interface GigabitEthernet0/0/1
interface GigabitEthernet0/0/1
 no ip address
 duplex auto
 speed auto
interface GigabitEthernet0/0/1.3
 encapsulation dot1Q 3
 ip address 10.3.0.1 255.255.255.0
interface GigabitEthernet0/0/1.4
 encapsulation dot1Q 4
 ip address 10.4.0.1 255.255.255.0
interface GigabitEthernet0/0/1.8
 encapsulation dot1Q 8 native
 no ip address
interface GigabitEthernet0/0/1.13
 encapsulation dot1Q 13
 ip address 10.13.0.1 255.255.255.0

What we learned:
G0/0/1.4 is now a normal tagged subinterface, and G0/0/1.8 is the native VLAN subinterface.

Fix 2: S1: Reset F0/5 (link to R1) and configure it as a static trunk with native VLAN 8.

S1(config)# default interface fastethernet 0/5
S1(config)# interface fastethernet 0/5
S1(config-if)# switchport mode trunk
S1(config-if)# switchport trunk native vlan 8
S1(config-if)# switchport trunk allowed vlan 3,4,8,13
S1# show interfaces fastethernet 0/5 switchport
Name: Fa0/5
Switchport: Enabled
Administrative Mode: trunk
Operational Mode: trunk
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: dot1q
Negotiation of Trunking: On
Access Mode VLAN: 1 (default)
Trunking Native Mode VLAN: 8 (Native)
Voice VLAN: none
Administrative private-vlan host-association: none
Administrative private-vlan mapping: none
Administrative private-vlan trunk native VLAN: none
Administrative private-vlan trunk encapsulation: dot1q
Administrative private-vlan trunk normal VLANs: none
Administrative private-vlan trunk private VLANs: none
Operational private-vlan: none
Trunking VLANs Enabled: 3-4,8,13
Pruning VLANs Enabled: 2-1001
Capture Mode Disabled
Capture VLANs Allowed: ALL
Protected: false
Unknown unicast blocked: disabled
Unknown multicast blocked: disabled
Appliance trust: none

What we learned:
F0/5 is now a static trunk with native VLAN 8 that allows VLANs 3, 4, 8 and 13 (VLAN 7 excluded).

Fix 3: S1: Set native VLAN 8 on F0/1 (link to S2) and allow VLANs 3, 4, 8, and 13.

S1(config)# interface fastethernet 0/1
S1(config-if)# switchport trunk native vlan 8
S1(config-if)# switchport trunk allowed vlan 3,4,8,13

Fix 4: S2: Allow VLANs 3, 4, 8, and 13 on F0/1 (link to S1).

S2(config)# interface fastethernet 0/1
S2(config-if)# switchport trunk allowed vlan 3,4,8,13
S2# show interfaces trunk
Port        Mode         Encapsulation  Status        Native vlan
Fa0/1       on           802.1q         trunking      8

Port        Vlans allowed on trunk
Fa0/1       3-4,8,13

Port        Vlans allowed and active in management domain
Fa0/1       3,4,8,13

Port        Vlans in spanning tree forwarding state and not pruned
Fa0/1       3,4,8,13

What we learned:
The S2 trunk now carries and forwards VLANs 3, 4, 8 and 13.

Fix 5: S1: Create VLAN 13.

S1(config)# vlan 13
S1(config-vlan)# name Maintenance
S1# show vlan brief

VLAN Name                             Status    Ports
---- -------------------------------- --------- -------------------------------
1    default                          active
3    Management                       active
4    Operations                       active    Fa0/6
7    ParkingLot                       active    Fa0/2, Fa0/3, Fa0/4, Fa0/7
                                                Fa0/8, Fa0/9, Fa0/10, Fa0/11
                                                Fa0/12, Fa0/13, Fa0/14, Fa0/15
                                                Fa0/16, Fa0/17, Fa0/18, Fa0/19
                                                Fa0/20, Fa0/21, Fa0/22, Fa0/23
                                                Fa0/24, Gig0/1, Gig0/2
8    Native                           active
13   Maintenance                      active
1002 fddi-default                     active
1003 token-ring-default               active
1004 fddinet-default                  active
1005 trnet-default                    active

What we learned:
VLAN 13 Maintenance now exists on S1.

Final verification

Note: Wait about 30 seconds (or click Fast Forward Time) so that spanning tree finishes converging on the trunks, then verify:

S1# show interfaces trunk
Port        Mode         Encapsulation  Status        Native vlan
Fa0/1       on           802.1q         trunking      8
Fa0/5       on           802.1q         trunking      8

Port        Vlans allowed on trunk
Fa0/1       3-4,8,13
Fa0/5       3-4,8,13

Port        Vlans allowed and active in management domain
Fa0/1       3,4,8,13
Fa0/5       3,4,8,13

Port        Vlans in spanning tree forwarding state and not pruned
Fa0/1       3,4,8,13
Fa0/5       3,4,8,13

Repeat the ping tests from Part 1:

R1# ping 10.3.0.11

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.3.0.11, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 0/0/1 ms
R1# ping 10.3.0.12

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.3.0.12, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
R1# ping 10.4.0.50

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.4.0.50, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 0/0/1 ms
R1# ping 10.13.0.50

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.13.0.50, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 0/0/1 ms

S1# ping 10.3.0.12

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.3.0.12, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
S1# ping 10.4.0.50

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.4.0.50, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/0/0 ms
S1# ping 10.13.0.50

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.13.0.50, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/1/5 ms

S2# ping 10.4.0.50

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.4.0.50, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
S2# ping 10.13.0.50

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.13.0.50, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)

Problem 6: S2 – the VLAN 3 interface stays up/down

After the five fixes, R1 and S1 reach both PCs, but nothing reaches S2 (10.3.0.12) and S2 cannot ping the PCs. Check the S2 interfaces:

S2# show ip interface brief
Interface              IP-Address      OK? Method Status                Protocol
FastEthernet0/1        unassigned      YES manual up                    up
FastEthernet0/2        unassigned      YES manual administratively down down
FastEthernet0/3        unassigned      YES manual administratively down down
FastEthernet0/4        unassigned      YES manual administratively down down
FastEthernet0/5        unassigned      YES manual administratively down down
FastEthernet0/6        unassigned      YES manual administratively down down
FastEthernet0/7        unassigned      YES manual administratively down down
FastEthernet0/8        unassigned      YES manual administratively down down
FastEthernet0/9        unassigned      YES manual administratively down down
FastEthernet0/10       unassigned      YES manual administratively down down
FastEthernet0/11       unassigned      YES manual administratively down down
FastEthernet0/12       unassigned      YES manual administratively down down
FastEthernet0/13       unassigned      YES manual administratively down down
FastEthernet0/14       unassigned      YES manual administratively down down
FastEthernet0/15       unassigned      YES manual administratively down down
FastEthernet0/16       unassigned      YES manual administratively down down
FastEthernet0/17       unassigned      YES manual administratively down down
FastEthernet0/18       unassigned      YES manual up                    up
FastEthernet0/19       unassigned      YES manual administratively down down
FastEthernet0/20       unassigned      YES manual administratively down down
FastEthernet0/21       unassigned      YES manual administratively down down
FastEthernet0/22       unassigned      YES manual administratively down down
FastEthernet0/23       unassigned      YES manual administratively down down
FastEthernet0/24       unassigned      YES manual administratively down down
GigabitEthernet0/1     unassigned      YES manual administratively down down
GigabitEthernet0/2     unassigned      YES manual administratively down down
Vlan1                  unassigned      YES manual administratively down down
Vlan3                  10.3.0.12       YES manual up                    down
S2# show running-config | section interface Vlan3
interface Vlan3
 ip address 10.3.0.12 255.255.255.0

What we learned:
The VLAN 3 interface has the correct address and is not shut down, but its line protocol is down. S2 therefore cannot send or receive any management traffic, even though the trunk now carries VLAN 3. This fault is not listed in the original Discrepancy Table and does not affect the completion score, but it breaks the requirement of end-to-end connectivity.


Key concept: when does a VLAN interface (SVI) come up?
A switch VLAN interface such as interface Vlan3 shows up/up only when the VLAN exists in the VLAN database and at least one port that carries that VLAN is up and forwarding (an access port in the VLAN, or a trunk that allows it). If no such port exists, the SVI stays up/down: the interface is enabled, but it cannot send or receive IP traffic. Before the fixes, VLAN 3 was not allowed on the S2 trunk, so Vlan3 on S2 had no forwarding port. Always check the Protocol column of show ip interface brief after changing trunks.

Fix 6: S2: Reset the VLAN 3 interface so that it comes up.

S2(config)# interface vlan 3
S2(config-if)# shutdown
S2(config-if)# no shutdown

%LINK-5-CHANGED: Interface Vlan3, changed state to administratively down

%LINK-3-UPDOWN: Interface Vlan3, changed state to down

%LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan3, changed state to up
S2# show ip interface brief
Interface              IP-Address      OK? Method Status                Protocol
FastEthernet0/1        unassigned      YES manual up                    up
FastEthernet0/2        unassigned      YES manual administratively down down
FastEthernet0/3        unassigned      YES manual administratively down down
FastEthernet0/4        unassigned      YES manual administratively down down
FastEthernet0/5        unassigned      YES manual administratively down down
FastEthernet0/6        unassigned      YES manual administratively down down
FastEthernet0/7        unassigned      YES manual administratively down down
FastEthernet0/8        unassigned      YES manual administratively down down
FastEthernet0/9        unassigned      YES manual administratively down down
FastEthernet0/10       unassigned      YES manual administratively down down
FastEthernet0/11       unassigned      YES manual administratively down down
FastEthernet0/12       unassigned      YES manual administratively down down
FastEthernet0/13       unassigned      YES manual administratively down down
FastEthernet0/14       unassigned      YES manual administratively down down
FastEthernet0/15       unassigned      YES manual administratively down down
FastEthernet0/16       unassigned      YES manual administratively down down
FastEthernet0/17       unassigned      YES manual administratively down down
FastEthernet0/18       unassigned      YES manual up                    up
FastEthernet0/19       unassigned      YES manual administratively down down
FastEthernet0/20       unassigned      YES manual administratively down down
FastEthernet0/21       unassigned      YES manual administratively down down
FastEthernet0/22       unassigned      YES manual administratively down down
FastEthernet0/23       unassigned      YES manual administratively down down
FastEthernet0/24       unassigned      YES manual administratively down down
GigabitEthernet0/1     unassigned      YES manual administratively down down
GigabitEthernet0/2     unassigned      YES manual administratively down down
Vlan1                  unassigned      YES manual administratively down down
Vlan3                  10.3.0.12       YES manual up                    up
S2# ping 10.3.0.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.3.0.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/0/1 ms
S2# ping 10.4.0.50

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.4.0.50, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 0/0/0 ms

What we learned:
The line protocol of Vlan3 comes up, and S2 reaches its gateway and PC-A. On real equipment an SVI normally comes up by itself as soon as a trunk forwards its VLAN; in this Packet Tracer file the interface had to be reset after the trunk was corrected.

Requirements check
Requirement Met? Evidence
No VLAN 7 traffic on the trunks ✔ S1 Fa0/1 and Fa0/5 allow only 3-4,8,13 (final check); S2 Fa0/1 allows only 3-4,8,13 (Fix 4)
VLAN 8 is the native VLAN ✔ Native vlan 8 on S1 Fa0/1, Fa0/5 and S2 Fa0/1; R1 encapsulation dot1Q 8 native on G0/0/1.8 (Fix 1)
All trunks are static ✔ Mode on on every trunk port in show interfaces trunk; S1 F0/5 Administrative Mode trunk (Fix 2)
End-to-end connectivity ✔ R1 and S1 reach both PCs (final pings); S2 reaches its gateway and PC-A after Fix 6; the PCs use the correct gateways (Part 1)

Device Running Configuration (Before Fix)

!====================================================================
!--- >>> ANNOTATED "BEFORE FIX" RUNNING-CONFIG - ROUTER R1
!--- >>> Lines prefixed "!--- >>>" are annotations added for the troubleshooting
!--- >>> write-up (cross-referenced to the Discrepancy Table) - they are NOT
!--- >>> part of the device's actual output. Everything else below is the
!--- >>> literal "show running-config" capture, unedited.
!====================================================================
R1# show running-config
Building configuration...

Current configuration : 1099 bytes
!
version 15.4
no service timestamps log datetime msec
no service timestamps debug datetime msec
service password-encryption
!
hostname R1
!
!
!
enable secret 5 $1$mERr$9cTjUIEqNGurQiFU.ZeCi1
!
!
!
no ip cef
no ipv6 cef
!
!
!
!
no ip domain-lookup
!
!
spanning-tree mode pvst
!
!
!
interface GigabitEthernet0/0/0
 no ip address
 duplex auto
 speed auto
 shutdown
!
interface GigabitEthernet0/0/1
 no ip address
 duplex auto
 speed auto
!
interface GigabitEthernet0/0/1.3
 encapsulation dot1Q 3
 ip address 10.3.0.1 255.255.255.0
!
interface GigabitEthernet0/0/1.4
 encapsulation dot1Q 4 native
 ip address 10.4.0.1 255.255.255.0
!--- >>> DISCREPANCY #1 (see Discrepancy Table): the "native" keyword is here,
!--- >>> on the VLAN 4 subinterface. VLAN 8 is the actual native VLAN
!--- >>> configured on both S1 and S2 ("switchport trunk native vlan 8") -
!--- >>> this misplacement breaks return traffic to PC-A.
!
interface GigabitEthernet0/0/1.8
 encapsulation dot1Q 8
 no ip address
!--- >>> This is where the "native" keyword SHOULD be (dot1Q 8 native) -
!--- >>> it's missing here. See DISCREPANCY #1.
!
interface GigabitEthernet0/0/1.13
 encapsulation dot1Q 13
 ip address 10.13.0.1 255.255.255.0
!
interface Vlan1
 no ip address
 shutdown
!
ip classless
!
ip flow-export version 9
!
!
!
banner motd ^C Authorized Users Only! ^C
!
!
!
!
line con 0
 password 7 0822455D0A16
 logging synchronous
 login
!
line aux 0
!
line vty 0 4
 password 7 0822455D0A16
 login
!
!
!
end

!====================================================================
!--- >>> ANNOTATED "BEFORE FIX" RUNNING-CONFIG - SWITCH S1
!--- >>> Lines prefixed "!--- >>>" are annotations added for the troubleshooting
!--- >>> write-up (cross-referenced to the Discrepancy Table) - they are NOT
!--- >>> part of the device's actual output. Everything else below is the
!--- >>> literal "show running-config" capture (terminal paging artifacts like
!--- >>> "--More--" have been removed for readability; the embedded CDP
!--- >>> syslog message is kept and called out explicitly below).
!====================================================================
S1# show running-config
Building configuration...

Current configuration : 2909 bytes
!
version 12.2
no service timestamps log datetime msec
no service timestamps debug datetime msec
service password-encryption
!
hostname S1
!
enable secret 5 $1$mERr$9cTjUIEqNGurQiFU.ZeCi1
!
!
!
no ip domain-lookup
!
!
!
spanning-tree mode pvst
spanning-tree extend system-id
!
interface FastEthernet0/1
 switchport trunk allowed vlan 4,8,13
 switchport mode trunk
!--- >>> DISCREPANCY #3 (see Discrepancy Table): no "switchport trunk native
!--- >>> vlan" line at all here (defaults to VLAN 1), and VLAN 3 is missing
!--- >>> from the allowed list. This exact mismatch produced the syslog
!--- >>> message the device itself logged during this session:
!--- >>>   %CDP-4-NATIVE_VLAN_MISMATCH: Native VLAN mismatch discovered on
!--- >>>   FastEthernet0/1 (1), with S2 FastEthernet0/1 (8).
!
interface FastEthernet0/2
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/3
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/4
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/5
 switchport access vlan 3
 switchport mode access
!--- >>> DISCREPANCY #2 (see Discrepancy Table): F0/5 is the uplink to R1
!--- >>> per the topology, but it's configured as a plain ACCESS port in
!--- >>> VLAN 3 instead of a trunk. This alone blocks VLAN 4/13/8 traffic
!--- >>> from ever reaching R1.
!
interface FastEthernet0/6
 switchport access vlan 4
 switchport mode access
!
interface FastEthernet0/7
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/8
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/9
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/10
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/11
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/12
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/13
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/14
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/15
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/16
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/17
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/18
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/19
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/20
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/21
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/22
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/23
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/24
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface GigabitEthernet0/1
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface GigabitEthernet0/2
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface Vlan1
 no ip address
 shutdown
!
interface Vlan3
 ip address 10.3.0.11 255.255.255.0
!
ip default-gateway 10.3.0.1
!
!--- >>> DISCREPANCY #5 (see Discrepancy Table): "show running-config" never
!--- >>> displays VLAN database entries (they live in vlan.dat). "show vlan
!--- >>> brief" on S1 confirms VLAN 13 does not exist there (only VLANs
!--- >>> 1, 3, 4, 7, 8), while S2 has VLAN 13 Maintenance on F0/18.
!
banner motd ^C Authorized Users Only! ^C
!
!
!
line con 0
 password 7 0822455D0A16
 logging synchronous
 login
!
line vty 0 4
 password 7 0822455D0A16
 login
line vty 5 15
 password 7 0822455D0A16
 login
!
!
!
!
end

!====================================================================
!--- >>> ANNOTATED "BEFORE FIX" RUNNING-CONFIG - SWITCH S2
!--- >>> Lines prefixed "!--- >>>" are annotations added for the troubleshooting
!--- >>> write-up (cross-referenced to the Discrepancy Table) - they are NOT
!--- >>> part of the device's actual output. Everything else below is the
!--- >>> literal "show running-config" capture, unedited.
!====================================================================
S2# show running-config
Building configuration...

Current configuration : 2949 bytes
!
version 12.2
no service timestamps log datetime msec
no service timestamps debug datetime msec
service password-encryption
!
hostname S2
!
enable secret 5 $1$mERr$9cTjUIEqNGurQiFU.ZeCi1
!
!
!
no ip domain-lookup
!
!
!
spanning-tree mode pvst
spanning-tree extend system-id
!
interface FastEthernet0/1
 switchport trunk native vlan 8
 switchport trunk allowed vlan 4,8
 switchport mode trunk
!--- >>> DISCREPANCY #4 (see Discrepancy Table): native VLAN 8 is already
!--- >>> correct here, but the allowed list is missing BOTH VLAN 3 and
!--- >>> VLAN 13 (only 4,8 are allowed). Missing VLAN 13 is the most severe
!--- >>> part of this: PC-B sits directly on S2, so without it PC-B's
!--- >>> traffic can never leave S2 toward S1/R1.
!
interface FastEthernet0/2
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/3
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/4
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/5
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/6
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/7
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/8
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/9
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/10
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/11
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/12
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/13
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/14
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/15
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/16
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/17
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/18
 switchport access vlan 13
 switchport mode access
!
interface FastEthernet0/19
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/20
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/21
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/22
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/23
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface FastEthernet0/24
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface GigabitEthernet0/1
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface GigabitEthernet0/2
 switchport access vlan 7
 switchport mode access
 shutdown
!
interface Vlan1
 no ip address
 shutdown
!
interface Vlan3
 ip address 10.3.0.12 255.255.255.0
!
ip default-gateway 10.3.0.1
!
banner motd ^C Authorized Users Only! ^C
!
!
!
line con 0
 password 7 0822455D0A16
 logging synchronous
 login
!
line vty 0 4
 password 7 0822455D0A16
 login
line vty 5 15
 password 7 0822455D0A16
 login
!
!
!
!
end

Discrepancy Table

# Device Error Evidence Fix
1 R1 Native VLAN flag placed on the wrong subinterface — G0/0/1.4 has encapsulation dot1Q 4 native instead of G0/0/1.8 Running-config shows encapsulation dot1Q 4 native under G0/0/1.4; both S1 and S2 configure switchport trunk native vlan 8, confirming VLAN 8 is the intended native VLAN, not VLAN 4 Under interface gigabitethernet 0/0/1.4, re-enter encapsulation dot1Q 4 (without native) and re-enter ip address 10.4.0.1 255.255.255.0; then apply encapsulation dot1Q 8 native under interface gigabitethernet 0/0/1.8. Only one subinterface per physical port can be native, so remove the flag from .4 first
2 S1 F0/5 (uplink to R1) is configured as an access port in VLAN 3 instead of a trunk Running-config shows switchport access vlan 3 / switchport mode access under FastEthernet0/5, but the topology requires this link to carry VLAN 3, 4, 8, and 13 to R1's subinterfaces default interface fastethernet 0/5 (per the lab's own hint) to clear the leftover access config, then rebuild it as switchport mode trunk, switchport trunk native vlan 8, switchport trunk allowed vlan 3,4,8,13
3 S1 F0/1 (uplink to S2) has no native VLAN set (defaults to VLAN 1) and its allowed-VLAN list is incomplete Running-config shows switchport trunk allowed vlan 4,8,13 with no switchport trunk native vlan line; the embedded syslog %CDP-4-NATIVE_VLAN_MISMATCH: ...FastEthernet0/1 (1), with S2 FastEthernet0/1 (8) directly confirms the mismatch Add switchport trunk native vlan 8 and change the allowed list to switchport trunk allowed vlan 3,4,8,13 — VLAN 3 is needed for S1/S2/R1 management reachability, VLAN 13 for PC-B's traffic; VLAN 7 stays excluded as required
4 S2 F0/1 (uplink to S1) is missing both VLAN 3 and VLAN 13 from the allowed list Running-config shows switchport trunk allowed vlan 4,8; native VLAN 8 is already correctly set here (S1 was the side missing it) Change the allowed list to switchport trunk allowed vlan 3,4,8,13, matching the corrected S1 side
5 S1 VLAN 13 was never created in S1's local VLAN database show vlan brief on S1 lists VLANs 1, 3, 4, 7, and 8 only; VLAN 13 (Maintenance) exists on S2 but not on S1, so PC-B traffic cannot transit S1 to R1 Add vlan 13 / name Maintenance — harmless to re-declare even if it already exists
6 S2 interface Vlan3 stays up/down after the trunk is corrected, so S2 cannot reach any device show ip interface brief shows Vlan3 10.3.0.12 ... up down; R1 and S1 cannot ping 10.3.0.12, and S2 cannot ping PC-A or PC-B, while all other tests succeed Under interface vlan 3, enter shutdown and then no shutdown; the line protocol comes up

Device Configs - Final

ROUTER R1

! ==============================================================
!--- 4.4.9 Packet Tracer - Troubleshoot Inter-VLAN Routing - Physical Mode
!--- FIX SCRIPT FOR ROUTER R1
!--- Usage: log in to R1 on the console (password "cisco"), type "enable" (password "class"), then paste this whole file at the R1# prompt. Every line beginning with "!" is a comment; IOS ignores it, so pasting a comment by accident is harmless.
!--- Troubleshooting lab: only the corrective commands from the Discrepancy Table.
! ==============================================================

configure terminal

! --------------------------------------------------------------
!--- Discrepancy #1: the native VLAN flag is on G0/0/1.4 instead of G0/0/1.8.
! --------------------------------------------------------------

!--- Remove "native" from the VLAN 4 subinterface first (only one native subinterface is allowed per port) and re-enter its IP address.
interface gigabitethernet 0/0/1.4
 encapsulation dot1Q 4
 ip address 10.4.0.1 255.255.255.0
 exit

!--- Make VLAN 8 the native VLAN, matching "switchport trunk native vlan 8" on the switches.
interface gigabitethernet 0/0/1.8
 encapsulation dot1Q 8 native
 exit

end

! --------------------------------------------------------------
!--- Save the configuration to NVRAM. (Press Enter when prompted for the destination filename.)
! --------------------------------------------------------------
copy running-config startup-config


! ==============================================================
!--- Verification:
!---   show interfaces gigabitethernet 0/0/1.8  -> "Native VLAN" shown for VLAN 8
!---   ping 10.3.0.11 / 10.3.0.12 / 10.4.0.50 / 10.13.0.50  -> successful
! ==============================================================

SWITCH S1

! ==============================================================
!--- 4.4.9 Packet Tracer - Troubleshoot Inter-VLAN Routing - Physical Mode
!--- FIX SCRIPT FOR SWITCH S1
!--- Usage: log in to S1 on the console (password "cisco"), type "enable" (password "class"), then paste this whole file at the S1# prompt. Every line beginning with "!" is a comment; IOS ignores it, so pasting a comment by accident is harmless.
!--- Troubleshooting lab: only the corrective commands from the Discrepancy Table.
! ==============================================================

configure terminal

! --------------------------------------------------------------
!--- Discrepancy #2: F0/5 (to R1) is an access port in VLAN 3.
! --------------------------------------------------------------

!--- Reset the port to defaults (lab hint), then build a static trunk with native VLAN 8; VLAN 7 is excluded.
default interface fastethernet 0/5
interface fastethernet 0/5
 switchport mode trunk
 switchport trunk native vlan 8
 switchport trunk allowed vlan 3,4,8,13
 exit

! --------------------------------------------------------------
!--- Discrepancy #3: F0/1 (to S2) has no native VLAN and an incomplete allowed list.
! --------------------------------------------------------------

!--- Native VLAN 8 clears the CDP native VLAN mismatch with S2; VLAN 3 (management) and VLAN 13 (PC-B) are added, VLAN 7 stays excluded.
interface fastethernet 0/1
 switchport trunk native vlan 8
 switchport trunk allowed vlan 3,4,8,13
 exit

! --------------------------------------------------------------
!--- Discrepancy #5: VLAN 13 does not exist in the S1 VLAN database (confirmed with show vlan brief).
! --------------------------------------------------------------

!--- PC-B traffic (VLAN 13) must transit S1 to reach R1, so the VLAN must exist here.
vlan 13
 name Maintenance
 exit

end

! --------------------------------------------------------------
!--- Save the configuration to NVRAM. (Press Enter when prompted for the destination filename.)
! --------------------------------------------------------------
copy running-config startup-config


! ==============================================================
!--- Verification:
!---   show interfaces trunk  -> Fa0/1 and Fa0/5 on, trunking, native VLAN 8, VLANs 3,4,8,13
!---   show vlan brief        -> VLAN 13 Maintenance present
!---   ping 10.3.0.12 / 10.4.0.50 / 10.13.0.50  -> successful
! ==============================================================

SWITCH S2

! ==============================================================
!--- 4.4.9 Packet Tracer - Troubleshoot Inter-VLAN Routing - Physical Mode
!--- FIX SCRIPT FOR SWITCH S2
!--- Usage: log in to S2 on the console (password "cisco"), type "enable" (password "class"), then paste this whole file at the S2# prompt. Every line beginning with "!" is a comment; IOS ignores it, so pasting a comment by accident is harmless.
!--- Troubleshooting lab: only the corrective commands from the Discrepancy Table.
! ==============================================================

configure terminal

! --------------------------------------------------------------
!--- Discrepancy #4: F0/1 (to S1) is missing VLAN 3 and VLAN 13.
! --------------------------------------------------------------

!--- Match the corrected S1 side (adds VLAN 3 management and VLAN 13 PC-B); native VLAN 8 is already set on this port.
interface fastethernet 0/1
 switchport trunk allowed vlan 3,4,8,13
 exit

! --------------------------------------------------------------
!--- Discrepancy #6: interface Vlan3 stays up/down after the trunk change.
! --------------------------------------------------------------

!--- Reset the SVI so that its line protocol comes up (needed in this Packet Tracer file after the trunk is corrected).
interface vlan 3
 shutdown
 no shutdown
 exit

end

! --------------------------------------------------------------
!--- Save the configuration to NVRAM. (Press Enter when prompted for the destination filename.)
! --------------------------------------------------------------
copy running-config startup-config


! ==============================================================
!--- Verification:
!---   show interfaces trunk  -> Fa0/1 on, trunking, native VLAN 8, VLANs 3,4,8,13
!---   show ip interface brief -> Vlan3 10.3.0.12 up/up
!---   ping 10.3.0.1 / 10.4.0.50 / 10.13.0.50  -> successful
! ==============================================================

Download Packet Tracer (.pka) file:

Subscribe
Notify of
guest

4 Corrections & Clarifications