SWICT Posted July 9, 2012 Posted July 9, 2012 Hi All, We have been using Fog (which has been working great) for the past few months, we recently transferred roles to a new 2008 DC and fog has stopped working. Ive added options 66 and 67 into the freshly installed DHCP scope but cant see where to change the settings in Fog itself, am I looking at reinstalling Fog from scratch? Any advice much appreciated Cheers
morganw Posted July 9, 2012 Posted July 9, 2012 I don't think you have to change any settings as long as the Fog server didn't used to be your DHCP server. If you've added any roles like WDS then this will probably hijack any PXE boots. What exactly happens when you network boot something?
SWICT Posted July 9, 2012 Author Posted July 9, 2012 Hey Thanks for the reply, from what I can remember there was an option on installation to point it to our old DHCP server? When I boot now it looks like it trys to get an address, fails and trys to boot from local disk? Cheers
morganw Posted July 9, 2012 Posted July 9, 2012 I don't think there are any options you would have to change. If whatever you boot fails to get an IP address then the problem is on your new DHCP server. Perhaps it's been configured to deny pxe-client boots, but with default settings and a valid scope it should just work. If you boot an operating system on the same PC does it get an IP address?
3s-gtech Posted July 9, 2012 Posted July 9, 2012 Check the configuration of /var/www/fog/commons/config.php (Debian based OS) I experienced the same thing when moving our IP address range, there are several files that will need updating but I can't remember the others for the life of me.
SWICT Posted July 9, 2012 Author Posted July 9, 2012 Thanks for all the advice thus far guys, Im running on Ubuntu so Ill check out the config file and see if there is anything obvious Ive just tested from xp running the command TFTP servername GET pxelinux.0 and that completes ok as well
morganw Posted July 9, 2012 Posted July 9, 2012 The fact you can get the pxelinux.0 file shows that as long as the client is given the correct information it will work. If you've just moved the DHCP server I don't think you'll need to modify any files on the Fog server.
SWICT Posted July 9, 2012 Author Posted July 9, 2012 To add to this after checking the configuration of /var/www/fog/commons/config.php The only reference I can find to the old server is the following line; "PXE_IMAGE_DNSADDRESS", "10.74.202.X" Ive changed this to reflect the new server ip restarted fog so we'll see what happens!
SWICT Posted July 9, 2012 Author Posted July 9, 2012 Ok hasnt made the slightest bit of difference, same behaviour as before When booting to an os the device pulls a valid DHCP address no problems both via wireless and wired Fog itself was working fine, anything else you guys can think of for me to check?
morganw Posted July 9, 2012 Posted July 9, 2012 What DHCP options have you got set? Also, did you specify option 066 with a hostname or did you use an IP address?
SWICT Posted July 9, 2012 Author Posted July 9, 2012 Have only got options 66 and 67 set in DHCP, option 60 doesnt exist In option 66 Ive specified the ip of the fog server, can login to the management interface just fine Cheers
morganw Posted July 9, 2012 Posted July 9, 2012 What happens on the client? Do you get TFTP timeout or something similiar, or does it not even try to connect to the TFTP server?
SWICT Posted July 9, 2012 Author Posted July 9, 2012 Its boots to PXE boot, looks like it fails to get a DHCP address and fog sits at booting from local disk, usually I would have the fog menu and be able to select the task etc No error as such or if it does it flashes up too quickly to see!
morganw Posted July 9, 2012 Posted July 9, 2012 and fog sits at booting from local disk ...so you see the Fog menu? That means the TFTP stuff is working correctly.
SWICT Posted July 9, 2012 Author Posted July 9, 2012 (edited) Not the usual menu Id expect to see, Ive attached some screenshots of what actually happens.......hope this makes it clearer [ATTACH=CONFIG]14573[/ATTACH] Edited July 9, 2012 by SWICT higher res
morganw Posted July 9, 2012 Posted July 9, 2012 What if you try a physical client instead of VMWare? I've never seen it do that before...
SWICT Posted July 9, 2012 Author Posted July 9, 2012 Same error, tried a couple of different nic cards too just too make sure Me neither
morganw Posted July 9, 2012 Posted July 9, 2012 I think it would do this if the pxelinux configuration file is missing all of the boot menu options. You could try re-writing this by modifying something in the user interface (like the menu timeout) and then save the changes. This should be somewhere like /tftpboot/pxelinux.cfg/default I don't run it anymore so I can't check anywhere. If the options are all in here but not getting to the client then it could be a file system permissions issue that stops the config file being sent to the client. As you have VMWare it might be worth just setting up a second Fog server from scratch and point to that to TFTP boot, just to see what happens with the boot menu. 1
SWICT Posted July 9, 2012 Author Posted July 9, 2012 Yeah Ive got a second VM building as we speak, dont want to spend hours on something when it might be quicker to just rebuild from scratch Ill take a look at the PXE menu tho, thanks for the suggestions....just strange how everything was working fine and now its broken!
3s-gtech Posted July 9, 2012 Posted July 9, 2012 Damn, wish I could remember the other settings location. It may be /opt/fog/.fogsettings I believe the reason it won't work is it's now looking at two locations for DHCP, across two files. It's not unified, and it is quite annoying! 1
SWICT Posted July 9, 2012 Author Posted July 9, 2012 Thanks Ill take a look whilst the other vm installs fog, would make sense I guess with regards to the two locations for dhcp!
SWICT Posted July 9, 2012 Author Posted July 9, 2012 Ok so doing a clean install works fine, I think Ill look at transferring everything across from the old box to the new box, thanks for all your input guys much appreciated
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now