03-19-2023 03:51 PM
Why does a 2960 switch drop packets from a layer 3 switch, with the message "switch does not have the Vlan indicated on the IEEE 802.1q frame tag. It drops the frame" in packet tracer, all vlans and inter vlan routing was configured?
Solved! Go to Solution.
03-19-2023 10:02 PM
OK I was able to take a look. After seeing the full configs and setup I don't think that will work. Apologies I gave you some wrong information based on some assumptions. I have attached the PT file configured a bit differently.
The reason it wasn't processing the packet is because the switch is using a trunk port (to allow all VLANs to get an IP from it) but the server doesn't know how to process VLAN tags so it drops it. It needs its own subnet. Also you configured the .193 address as the helper which is the DG of the DHCP server. You need the IP of the DHCP server itself.
Changes I made:
Configured the DHCP server port on SW3 as an access port assigned to VLAN 40.
Configured the helper address of 192.168.1.195
PC0 was able to get an IP address after that. I ahve attached the PT file.
I aslo fixed a couple other things. The connection between R0 and the MLS was not in the same subnet. You were using a /30 but the interfaces IPs were in different /30 networks. I made them the same. Also your OSPF config on the MLS was configured wrong (if you were trying to advertise those VLAN subnets). You were activating OSPF on interfaces that didnt exist.
For example you had:
network 192.168.2.0 0.0.0.63 area 0
when the interface was the 192.168.1. subnet. I added the .1 interfaces but left the .2 interfaces if you want to check it out
Hope that helps
-David
03-19-2023 04:07 PM
Hello,
Can you provide the vlan database, trunk configurations, and screenshots of the error or what it shows that its dropping packets?
-David
03-19-2023 04:55 PM
03-19-2023 04:30 PM
share the config of SW and R
03-19-2023 05:27 PM
I shared it below, it's the layer 3 switch
03-19-2023 04:58 PM
03-19-2023 05:07 PM - edited 03-19-2023 05:08 PM
Did you also create the VLAN 40 on the L3 switch. If you just created the SVI it does NOT automatically create the L2 instance which is needed to complete the path.
You didn't provide any VLAN database for wither switch and you don't have a PCA. You have a PC0 and a PC1 so not sure which one it is.
On the L3 switch make sure the command is entered:
conf t
vlan 40
YOu will also need to do this for all other VLANs that need communication from the other switches
Show the vlan database on the L2 and the L3 switch if that didn't solve your issue:
show vlan
Please also show the trunk interface (to make sure its allowed on the interface).
-David
03-19-2023 05:18 PM
03-19-2023 05:46 PM
I think you switched some things. From your first couple of pictures you show that SW3 drops the traffic due to no VLAN but you say its from PC0. PC0 is connected to switch 0 with VLAN 10. PC0 shouldn't even be reaching switch 3.
Can you check all your access switches to ensure the correct VLAN is on them and configured on the access ports attached to the PCs.
From your picture Switch0 should be all VLAN 10 with PC0, and Switch3 should be all VLAN 40 with PC1 connected. Please verify this is correct.
-David
03-19-2023 05:55 PM
Yes, Switch0 is VLAN 10 with PC0, and Switch3 is VLAN 40 with PC1 connected. Switch 3 is the one who drops the packets.
03-19-2023 05:59 PM
The Dhcp server is also on switch three, the layer 3 uses the helper address and forwards the packet to switch 3 which drops it
03-19-2023 06:04 PM - edited 03-19-2023 06:05 PM
Can you create VLAN 10 on Switch 3. And also make the port connected to the DHCP server a trunk port and make sure VLAN 10 (and all other VLANS) are allowed.
If the DHCP server is on SW 3 then it will just get to the L3 switch and be sent on the trunk port to Switch 3. I dont think it hits the SVI because it doesn't need to.
-David
03-19-2023 06:22 PM
03-19-2023 06:25 PM
Are DHCP services turned on on the server. Have you assigned a pool for VLAN 10? Can you show the screenshots of the server and what networks you have configured on there for DHCP. It should be 192.168.1.0 255.255.255.192.
03-19-2023 06:36 PM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide