Using fog with external dhcp pxe server
-
I have fog installed 1.2.0 and on my external dhcp server I have next-server “ip address” added when I reboot the system to fog and press F8 to start the fog install nothing happens no fog window and the system just boots as normal as if it does not recognize f8 being pressed.
As my dhcp server and dns server is not the same as the fog server do I need to install dnsmasq on the fog server?
I am using centos 6.
Also In the Fog menu “FOG PXE Boot Menu Configuration” I have ticked No Menu and Hide Menu, should this be ticked or No Tick?
Thanks for your help
-
Since this is not a standard FOG install, please explain a few things.
- What do you mean external dhcp server? Is this external in reference to the internet? (i.e. your fog server is connected to the internet?)
- What do you mean when i reboot “the system” to fog and press F8 to start fog… nothing happens? what is “the system” and what do you mean by “nothing happens” (such as nothingness of outer-space? Something must happen or you are not pressing the right key)
- DHCP Server and dns server not on fog. (That is ok). Dnsmasq is only used when you can’t change dhcp options 66 (next server) and 67 (boot file). Then you would use dnsmasq to supply these values.
- If you ticked no menu and hide menu then its possible that nothingness will be presented to you.
-
When I say external I mean its not on the fog server. We have a separate internal linux dhcp server and dns server.
I am pressing the right key I have set the key to be F8 in fog Boot key sequence. When I say nothing happens, exactly what I mean.
Our dhcp server is linux so I have not set option to 66 or 67 but I have set “next-server ip”. Maybe this is where I am going wrong as I would need to specify the bootfile, do you know how i set option 67 on a linux dhcp server? I do have a line for "filename “pxelinux.0"” but this boots my linux kickstart server . Would I need another line for the tftp boot file?
-
@limbooface Why are you using pxelinux.0?
It doesn’t exist for FOG 1.2.0, and even though it exists for what we have in development it doesn’t work very well.
YOu need to change the ‘filename’ to use undionly.kpxe or undionly.kkpxe
-
Where to start…
Dhcp options 66 and 67 are next-server and boot file. These need to point to your fog server for the target computer subnet scope. The next-server must be the IP address of the fog server and the bootfile is typically undionly.kpxe (or if you have problems undionly.kkpxe) and for an efi system you need ipxe.efi. pxelinux.0 should never be used with 1.2.0.
Here is a good guide for setting up linux dhcp. https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence
The F8 thing still has me a bit confused. What/where is the F8 coming into play? The typical boot menu option to select pxe booting is either F10 or F12.
-
TFTP Error file not found is the error I am getting
-
@limbooface said in Using fog with external dhcp pxe server:
Our dhcp server is linux so I have not set option to 66 or 67 but I have set “next-server ip”. Maybe this is where I am going wrong as I would need to specify the bootfile, do you know how i set option 67 on a linux dhcp server? I do have a line for "filename “pxelinux.0"” but this boots my linux kickstart server . Would I need another line for the tftp boot file?
For a single subnet scope you can not have two pxe boot servers. I would recommend that you upgrade to 1.3.0-rc4 and then with the iPXE menu editor chain load to your kickstart server if you still needed it.
-
@limbooface said in Using fog with external dhcp pxe server:
TFTP Error file not found is the error I am getting
Are you using dnsmasq somewhere on this subnet/broadcast domain?
-
ok thanks tftp server is being picked up but i am not seeing the fog menu in the logs i see
fog in.tftpd[14845]: tftp: client does not accept options
fog in.tftpd[14846]: Client 192.168.10.72 finished undionly.kpxe -
@limbooface Can you take a picture of the error with a mobile phone and post it here? There seems to be a disconnect somewhere.
-
Ok i have it working on my workstatons, on the vm servers that I am trying to image it does not show the fog screen and picks the tftp server and then reboots.
If i wish to create a image of a windows workstation Is that the upload option?, so upload to server.
Now if i am uploading a windows image from a workstation to a storage node does that storage node need to have a filesystem that windows will recognize like fat32? or will ext3 do?, as I thought it was only storing a iso so the format of the drive would not matter.