Re: DHCP Stopped Working
Jeff Schroeder wrote:
On Thu, Dec 4, 2008 at 9:38 PM, Ole Ersoy <ole.ersoy(a)gmail.com>
wrote:
> Hi,
>
> I had dhcp working fine. Then after rebooting the cobbler client in order to try
another install attempt, I noticed that my voice over IP device had stolen the IP that the
cobbler client wants. So I reconfigured dhcpd.conf to use a different IP for the cobbler
client. Now the cobbler client times out when attempting to get a lease.
>
> I tried uninstalling and reinstalling dhcp and then starting with a clean
configuration, but there's still no love. I also tried looking at the log and
there's no logged requests for a dhcp lease.
>
>
cobbler system report --name $system_name
Take a look at the netboot line and it is probably set to false. After
you kickstart a server, it turns the netboot flag to false to keep
from accidentally rekickstarting it again.
Try:
cobbler system edit --name $system_name --netboot 1 && cobbler sync.
Then reboot the box again.
FYI -- Toggling the netboot enabled flag should have no affect on the
DHCP config. You can use cobbler system records to manage DHCP for
systems that never get installed by cobbler.
> Any ideas on how to reset this?
>
Also take a look at the file: /tftpboot/pxelinux.cfg/$mac-address
before and after the sync as it contains the boot configuration.
I think he's reporting a DHCP problem which is before the stage where
the bootloader talks to the TFTP server.