09-23-2019 01:01 AM
Hi All,
We have 4 sites, each site has its DHCP server, we changed that to be one DHCP server at the HQ office and all other sites will be assigned TCP/IP configuration from that one DHCP server.
On each site, we configured DHCP Relay "ip-helper address" on the core switch on each interface vlan, only one remote site worked fine and its clients are assigned TCP/IP configuration from the DHCP located at the HQ, but the other two sites are not obtaining.
I captured the packets at the core switch and found there is a packet with source IP (the interface vlan IP address) and destination IP (the DHCP Server IP address), but this packet is not reaching the DHCP server, found only discover packets on the capture with no offers.
I captured the packets at the router after the core switch but found nothing, even the discover packet is not appearing, we have DHCP snooping configured on the core and all its interfaces are configured with "ip dhcp snooping trust".
What could be the issue of preventing the discover packet from reaching the DHCP server, and by the way, I can ping the DHCP server from the core switch successfully.
Thanks,
Khaled
09-23-2019 01:12 AM
Hello,
what is the difference (if any) in the configuration between the 'working' site and the 'non-working' site ? If possible, post the configurations of the devices involved in both working and non-working sites...
09-23-2019 02:27 AM
09-23-2019 03:02 AM
Hello,
the working site has EIGRP enabled, the non working site does not. Where else in the path towards the DHCP server do you have EIGRP configured ? Since you are using iBGP, the EIGRP routes would be preferred.
It might be a good idea to post a schematic drawing of your topology so we can see what is connected to what...
09-23-2019 05:55 AM
Hi,
The core switch is connected to a CE router and there is iBGP between the core and the router, then to the MPLS network to the other site.
Regards,
Khaled
09-23-2019 02:49 AM
Hello
we have dhcp snooping on the core
Suggest you remove this from the core, Dhcp snooping should ONLY be applied on access layer switches NOT the core switch
Also check the switches to see if option 82 is enabled when you've enabled dhcp snooping I have found sometimes the dhcp sever isn't compatible with this option being applied to dhcp requests.
.
sh ip dhcp snooping
09-23-2019 05:52 AM
Hi,
As you saw, DHCP snooping is also enabled on the working site, and the output of the "show ip dhcp snooping" on both sites shows that all interfaces are trusted.
Regards,
Khaled
09-23-2019 08:25 AM
Hello
Either way snooping shouldn't be applied to the cores switches, it a layer 2 feature and should be applied only to the access layer
@eng.khaled.omar wrote:
I captured the packets at the core switch and found there is a packet with source IP (the interface vlan IP address) and destination IP (the DHCP Server IP address), but this packet is not reaching the DHCP server
What could be the issue of preventing the discover packet from reaching the DHCP server, and by the way, I can ping the DHCP server from the core switch successfully.
Would this include pinging the dhcp server sourced from each the L3 SVI address on the core?
09-23-2019 09:10 AM
09-23-2019 09:38 AM
Hello,
what are the access ports on the switches where the end clients are connected to configured like ? Do they have 'spanning-tree portfast' enabled ?
09-23-2019 09:47 AM
09-23-2019 10:10 AM
Hello,
the vtp mode on the non-working site switch is set to transparent, what is the vtp mode (show vtp status) on the working site switch ?
09-23-2019 10:54 AM
09-23-2019 11:11 AM
Set the vtp mode to 'server' as well on the non-working switch:
Switch(config)#vtp mode server
09-23-2019 10:34 AM
Hello
From working site and non working site do you get different paths?
traceroute 10.26.1.161 numeric
Also can you post the output from the below
access-list 110 permit udp any any
debug ip packet detail 110
debug ip dhcp server packet
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