FOG Failed to get IP via DHCP Error
-
I use FOG to image all of our Intel NUC devices at work. I just received 2 new NUC 12 Extreme devices which come with 2 NICs a 10GbE and 2.5GbE port. When I try to image these NUCs however I get the Failed to get IP via DHCP error.
The DHCP server for our FOG network is on our FOG server and I can see that the device has been given an IP address so it shouldn’t be a problem when trying to connect to FOG.
I am wondering if anyone can help me with this? I am unsure if it is because of the speed of the ports? because the other NUCs have only 1GbE ports on them.
I have tried configuring a static address on the NIC in the BIOS and have come up with the same issue.
-
@askiba So I have to ask you a few questions.
Can you get to the FOG iPXE menu?
If no then lets start by rebuilding iPXE: https://forums.fogproject.org/topic/15826/updating-compiling-the-latest-version-of-ipxe
If yes then when it fails to get IP address then FOS Linux is running. In this case make sure you update the FOS Linux kernel to 5.15.x version. This is done via the web ui ->FOG Configuraiton->Kernel update.
If your kernel is updated but it still doesn’t work then we need to debug the configuration.
Pick an interface on the nuc and get the mac address for it. If you are unsure which is which record all of the mac addresses.
Manually register the computer with FOG under web ui -> Host management.
Create a deploy task to the computer, but before you hit the schedule task button tick the debug check box then schedule the task.
pxe boot the target computer, it should jump into imaging right away. You should not see the fog ipxe menu at this point. After a few screens of text you need to clear with the enter key you will be dropped to the FOS Linux command prompt.
Key in the following commands, take a clear picture of the output and post it here.
lspci -nn | grep -i net
ip a s
grep -i firmware /var/log/messages
uname -a
Lets see what hardware you have installed in that system
-
@george1421 Thanks for the help! I updated the kernel, had to do it on the ubuntu server instead of the web ui but it worked and it found the device and installed the image!