We've configured DHCP relaying on 4 different contexts (we are PXE booting the machines to do initial setup).
It seemed to be working when we did the initially setup. Now we needed to add some new servers to the VLAN and have noticed a strange behaviour with the DHCP relaying agent. It seems to add a static arp entry for the first DHCP request. This has the unfortunate effect that subsequent DHCP offers for the same IP address never make it into the arp table on the context:
Admin/context33# sh arp | inc STATIC 192.168.33.211 00.21.5a.4a.6a.32 vlan33 STATIC 459 _ up 192.168.33.212 00.21.5a.4a.0a.dc vlan33 STATIC 437 _ up
Can we somehow disable this feature/bug? It's really annoying having to clear does arp entries everytime we have to add a new server.
Why do you have to delete them? Does the MAC change for an IP address?
We need to PXE bootstrap servers during the initial setup/installation. After the server is installed (OS) we configure it with a static ip address outside the DHCP scope and let it run.
The problem arises when we have to build a new server after the initial DHCPOFFER (from the first server) has expired. If the new server is offered the same ip address as the first server, but the ACE still has an arp entry for the first server.
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
Introduction Prepositioning is a powerful tools on the WAAS platform but
it is not always easy to figure out why your jobs are failing when
trying to retrieve the files.Here is a method that should help you to
figure out the reason why they are not succes...