02-01-2024 11:28 AM
Hoping the community can help me here. I am fairly comfortable and familiar with Cisco and networking concepts, but this one is stumping me.
I have a 2960 switch that is third down the line from the layer 3 Meraki controller. Here are the interfaces down the path to the switch in question:
interface GigabitEthernet1/0/1
description TO US-SFC-MDF
switchport trunk encapsulation dot1q
switchport mode trunk
srr-queue bandwidth share 1 30 35 5
priority-queue out
mls qos trust cos
macro description cisco-switch
auto qos trust
spanning-tree link-type point-to-point
ip dhcp snooping trust
end
interface GigabitEthernet1/0/24
description To US-SFC-IDF8-AS1
switchport trunk encapsulation dot1q
switchport trunk native vlan 999
switchport mode trunk
srr-queue bandwidth share 1 30 35 5
priority-queue out
mls qos trust cos
macro description cisco-switch
auto qos trust
spanning-tree link-type point-to-point
ip dhcp snooping trust
end
interface GigabitEthernet1/0/26
description TO US-SFC-MPOE-CS1
switchport trunk native vlan 999
switchport mode trunk
srr-queue bandwidth share 1 30 35 5
priority-queue out
mls qos trust cos
macro description cisco-switch
auto qos trust
spanning-tree link-type point-to-point
ip dhcp snooping trust
end
interface GigabitEthernet1/0/27
description TO US-SFC-IDF9-AS1
switchport trunk native vlan 999
switchport mode trunk
srr-queue bandwidth share 1 30 35 5
priority-queue out
mls qos trust cos
macro description cisco-switch
auto qos trust
spanning-tree link-type point-to-point
end
interface GigabitEthernet1/0/25
description TO US-SFC-IDF8-AS1
switchport trunk native vlan 999
switchport mode trunk
srr-queue bandwidth share 1 30 35 5
priority-queue out
mls qos trust cos
macro description cisco-switch
auto qos trust
spanning-tree link-type point-to-point
end
interface GigabitEthernet1/0/21
description FLS_Digital_Lines
switchport access vlan 13
switchport mode access
ip device tracking maximum 65535
spanning-tree portfast
end
As you can see, each of the interfaces down the chain has trunking enabled, native VLANs match, and ALL VLANs are allowed to pass through. The end interface, g1/0/21 on IDF9 is of course set as access mode, with only VLAN 13 allowed. Plugging a device into this port 21 fails to snag a DHCP address from the MX. Screenshots of the relevant info on the MX for additional context:
Any guidance on this configuration? Am I missing something? I cannot for the life of me get any end device to pull an IP from ANY VLAN, let alone VLAN 13 as needed.
Thank you!
02-01-2024 11:35 AM
You enable ip dhcp snooping
So you need to add below command in global
No ip dhcp snooping inforomation option
MHM
02-01-2024 11:39 AM
Thanks for the reply. I have DHCP snooping set as TRUST option, is that not correct? You're saying I simply need to disable DHCP snooping entirely?
02-01-2024 11:43 AM
No
Only disable SW from add op82 to dhcp packet.
This op82 will make some problems in dhcp server when assign IP.
Add only below in global
No ip dhcp snooping inforomation option
MHM
02-01-2024 12:25 PM
Get the ip dhcp snopping on every interface upstream/downstream and ip dhcp snooping vlan vlan-list across all catalyst switches
02-01-2024 10:56 PM
Hello
Some of those trunks have dhcp-snooping trust enabled but others dont, So I would expect to see this on at least the uplink towards the meraki MX, also between the MX it directly attached switch that needs to be a trunk port also with snooping trusted if you have enabled it through your switch estate.
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