Fog Trunk no longer PXE booting
-
Build 6213
Was working prior without issue. DHCP Option 66/67 both set
As noted, it’s odd because this was working without issue
This is what happens when i’m pxe booting now…
I need help please I can’t figure out why this is occuring it was working fine before.
-
Just for sanity sake, please type in the fog servers IP address here. What I’m interested in is does it boot properly post this error message.
For this error message resolution we will probably need a pcap file of the communications here. Because within the ipxe kernel its getting the IP address but its not getting the dhcp options for {boot-server} or possibly {bootfile}. Or you have a dhcpPROXY that is giving extra information.
The other noteworthy thing is that you might want to upgrade to latest on the trunk build. Your release is a bit behind the times.
-
Another nice thing to know would be the OS the fog server is running on.
-
See below for screen caps of what happens when i try to boot. and fog trunk is installed on Ubuntu 14.04LTS
-
I also forgot to note that i’ve ssh’d to the server and verified that the default.kpxe file is there.
-
@eldiablo909 do you mean default.ipxe?
-
@Tom-Elliott Yes… that’s what i meant, sorry sleepless night last night
-
@eldiablo909 so it’s a 192.168 dhcp server handing out information to a 10.0 network?
-
@Tom-Elliott yes, i had it on the same network prior but it was doing the same thing so i decided to try using windows DHCP vs my firewall.
-
This often happens when there are two DHCP servers running on the same network.
-
@Quazz I don’t have another DHCP server on either the 10.80. or the 192.168. network.
-
@eldiablo909 We see that the first round of DHCP seems to work out because the Intel
PXE boot ROM is able to grab an ip, get next-server/filename info and load the iPXE binary. One thing I notice here is the DHCP server IP address being totally different to the client IP and gateway address. This does not have to be an issue. It’s just a bit unusual and I wanted to point this out in case…Version 6213 might not be the very latest but from what I see in the repo we haven’t changed the embedded iPXE script since then. So upgrading to the very latest won’t help I reckon!
From the message you see it seems like your DHCP server does not send next-server (option 66) on the second DHCP round (when iPXE is asking). Possibly your DHCP server decided to not like the DHCP options send by iPXE/gPXE/Etherboot anymore (e.g. option 175).
About the TFTP error. Make sure the TFTP server is running on your FOG server. I remember there have been issues with this on ubuntu.
service tftp-hpa restart. As well follow this: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_TFTP -
@eldiablo909 I think we are back to requiring a pcap file so we can see what is going on… on the wire. Make sure tcpdump is installed on your FOG server then run the following command
tcpdump -w output.pcap port 67 or port 68 or port 69Next pxe boot the client computer. You will get the question for the fog server IP enter it and take it to the final error where you can’t go any more. Then post the pcap file here. We’ve instructed tcpdump to only capture broadcast bootp and tftp requests.
-
@george1421 What about the “router” setting in the DHCP server?
-
@Tom-Elliott Ok, we fixed it… we looked at the pcap dump here and found it was one of my colleagues and his sonicwall pulling a sarah palin and went rogue. Issue resolved.
Again my hats off to you guys and the community thank you so much!
