01-11-2013 10:46 AM - edited 03-07-2019 11:03 AM
I am having DHCP issues with HP7000 blades trunked to Nexus 5000. The 5000 is L2 up to a Nexus 7000 where it is L3 back down to the same 5000 where the DHCP server is. The blade sends out the DHCP DISCOVER, but I never see the packet propogate through to the other side out towards the DHCP server. Packet captures on Anue taps/Network Instruments shows a valid packet, but I notice it sends groups of 5 packets with 0 secondd. between each. I'm wondering if there is some type of broad-cast storm protection on the Nexus that may be interferring. I don't see anything in the nexus logs, and I do have the helper address on the L3. I can plu a laptop on a 2248 feeding into the same Nexus 5000 and get an address. Any ideas? I'm out!
interface Ethernet1/14
description FC8C7K11-S2P2
switchport mode trunk
switchport trunk allowed vlan 1200-1201,1800-1801
spanning-tree port type edge trunk
logging event port link-status
logging event port trunk-status
vpc orphan-port suspend
no shutdown
Thanks!
Mike.
02-27-2013 01:03 PM
Mike,
We have a topology similar to yours and had a similar issue with our 7k's after upgrading from IOS version 5.1 to 5.3. DHCP ran fine for several months and then out of nowhere we had sporadic DHCP issues across most of our Vlans. This caused a major disruption for over 2000 clients.
We could see all of the DHCP discovers arriving on the DHCP server whilst being relayed from the Nexus 7k's. We could see all of the offers being sent by the DHCP server, received on the Nexus 5k's and then forwarded to the 7k's. On the 7K's we could see these packets were not all being forwarded successfully.
We couldn't figure out why this was happening but after much digging and support from TAC we found that DHCP did not have its own class in COPP on the 7k's. We ended up updating the COPP configuration (ran copp strict) again to bring the new profiles of COPP to the 5.3 version. This did not get updated as ISSU does not upgrade the configuration with the new COPP automatically. This caused our packets to be not classified under a specific class. This meant they went under the radar from a forwarding behavior (in class default) which was our scavenger class. Updating the COPP configuration did the trick for us.
Now..... The trigger for our woes ended up being a host on our network that was sending a high volume of DHCP broadcast.
Due to these broadcast the COPP which is there to protect the CPU is active and dropping packets, only allowing a certain packet rate through. As COPP cannot differentiate between "good and bad" packets it was dropping between both sent to the CPU. Hence this cause some host to work but the majority not and sporadic issues across multiple Vlans with DHCP because of the excessive traffic being sent out by the source end host.
I hope this helps if not at least you got a good read and understanding of the misery we went through with this issue.
Good luck,
William
02-19-2019 04:44 AM
Hi Michael,
Do you have DHCP relay configured on the Nexus 7K switch?
Please check "bug" CSCve42732.
On the Nexus 7K, if you configure the "ip dhcp relay" command, then it will stop broadcasting DHCP DISCOVER packets on that VLAN.
To "fix" this, you'll need to either remove the ip dhcp relay command or to configure a dhcp relay for each DHCP server (even if the clients and the server are on the same broadcast domain).
Regards,
Vlad
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