Just Trying To Get Started
-
that is incorrect. for fog 1.0+ it should be undionly.kpxe
also, please update to the latest version of fog -
I made the change to my ltsp.conf file, restarted the dnsmasq service, and tried to pxe boot again, and I get the same failure. I will try updating FOG.
-
I tried running the FOGUpdater.sh in the installation folder, but it failed (unable to determine current version). Is there a better way to update?
-
if you download the current version and run the installer, it will detect the current install and update
-
So, I downloaded 1.1.2 and began the install. At the point in the install where I am asked to update the database schema, I tried and got a whole page of errors. See the attached file.
[url=“/_imported_xf_attachments/1/1110_Untitled Document 3.txt?:”]Untitled Document 3.txt[/url]
-
Edit your /opt/fog/.fogsettings
Edit the snmysqlhost (This should be the mysql host, if it’s local set this value to localhost)
Edit snmysqluser (This should be the user root, unless it’s a storage node in which it should be fogstorage)
Edit snmysqlpass (This should either be the password/or “” if blank for the root user, if it’s a node it should be the fogstorage password.)Re-run the installer.
-
Tom,
I am unable to find the /opt/fog/.fogsettings file to edit it.
My /opt/fog directory has no such files. Only four sub-directories exist here: log, service, snapins, & utils.
Please advise.
-
the file name is hidden
If you type:
[code]ls -lhart[/code] You should see the file. -
Thanks, Tom. Is my face red?!
FOG updated to 1.1.2 successfully.
undionly.kpxe edited into ltsp.conf file.
dnsmasq service restarted.
Same problem --> Still receiving pxe-m0f error.
-
what equipment is between the client and the server? have your switches been configured correctly for pxe booting?
-
We have properly PXE booted in the past for a very long time. Five years ago, our PXE booting would have involved our Novell imaging server. More recently than that, we have been using a Windows Deployment Services server (2008R2). As I am trying to deploy Windows 8.1, my WDS 2008R2 server won’t work, but it was deploying XP SP3 via PXE booting very well.
We run mostly Cisco switches, of varying ages.
-
Maybe you are needing more than this…
The client computer is attached to a generic Linksys hub in my office that receives intranet bandwidth from a wall panel (the wall panel is connected to another patch panel in my central rack that is connected to a stacked pair of Cisco Catalyst 3850 POE switches that are connected to the rest of my network via other hubs and switches of varying types and manufactures).
The generic Linksys hub that is getting intranet bandwidth from the infrastructure is also feeding bandwidth to 1) my client machine and 2) a smaller Linksys hub on the other side of my office. That smaller Linksys hub has my Ubuntu FOG machine connected to it.
I can touch both the client and hosts machines at the same time if I stretch:D
-
My DHCP server is a virtualized 2008R2 installation running on a VMWare ESX server in my central rack. That ESX server is connected to the network via a Cisco Catalyst 2960G switch which is connected to a Cisco Catalyst 3750 switch which is connected to my core switches mentioned above.
-
Maybe I sound ignorant by asking, but what if you actually just tried to use your existing DHCP server? Perhaps adding options 66/67 to a ‘sandbox’ scope or a scope that is easily accessible in your building. This would point to the Proxy DHCP service setup.
Also, I’ve experienced the whole PXE-M0F error if you’re not using the legacy PXE boot option. Would this happen to be a UEFI device? I know we’ve had to revert some of the newer laptops we deploy in our schools because it refuses to PXE boot.
-
[quote=“Phil Brackett, post: 32368, member: 24966”]My DHCP server is a virtualized 2008R2 installation running on a VMWare ESX server in my central rack. That ESX server is connected to the network via a Cisco Catalyst 2960G switch which is connected to a Cisco Catalyst 3750 switch which is connected to my core switches mentioned above.[/quote]
What happens when you run the tftp get commands from a machine within the network?
from a windows machine (preferably on the same switch you are working with), enable the tftp client in the Windows Add/Remove Programs and Features section of Control Panel.
Now open a command prompt and issue the following command where x.x.x.x is your ip address of your FOG server.
[code]
tftp x.x.x.x get undionly.kpxe[/code]Is Port Fast enabled on your switches? I use the 2960 in my environment as well, I don’t claim to be an expert but with the correct settings and dnsmasq I can pxe boot without issues. This is really the only setting I remember enabling other than IGMP Snooping, which I am told will not have an affect here.
-
Jaymes, the tftp attempt fails. I do have telnet access to all of my major switches, so if you can tell me how to check for Port Fast (my CLI is very rusty), I will look and see.
RLane, the client in question is a UEFI device, so I will try a legacy PXE boot to see if that works.
Thanks for the suggestions; more in a few minutes.
-
Okay, here’s some more info:
I checked the BIOS settings on the client (an HP Elitebook 8570p), and it is set-up for a legacy boot (I must have done that at some point in the past). However, in the System Configuration menu of the BIOS, there were three PXE boot options: 1) PXE NIC, 2) PXE IPV4, & 3) PXE IPV6. Only the first one was optioned. I optioned the other two, but still no joy.
Something interesting has changed though. Now, during PXE booting, I get the F8 menu and I choose network boot (as before) and the TFTP search seems to take a few seconds now. Previously, the PXE-M0F error appeared so fast that I had to video the process to see the error in slow-mo. Now, the TFTP search takes multiple seconds, and the periods after the TFTP are multiple before timing out. I don’t know if this makes a difference or not.
-
PXE Nic is likely the option you want. PXE IPv4 and PXE IPv6 is looking for UEFI files to boot which we don’t have right now.
The fact that you can’t tftp the files you need even in a windows box means either the networking is not allowing the passage of the tftp traffic, or tftpd-hpa service is not running.
-
This post is deleted! -
[quote=“Phil Brackett, post: 32399, member: 24966”]Okay, here’s some more info:
I checked the BIOS settings on the client (an HP Elitebook 8570p), and it is set-up for a legacy boot (I must have done that at some point in the past). However, in the System Configuration menu of the BIOS, there were three PXE boot options: 1) PXE NIC, 2) PXE IPV4, & 3) PXE IPV6. Only the first one was optioned. I optioned the other two, but still no joy.
Something interesting has changed though. Now, during PXE booting, I get the F8 menu and I choose network boot (as before) and the TFTP search seems to take a few seconds now. Previously, the PXE-M0F error appeared so fast that I had to video the process to see the error in slow-mo. Now, the TFTP search takes multiple seconds, and the periods after the TFTP are multiple before timing out. I don’t know if this makes a difference or not.[/quote]
Because the command failed I want you to verify that the tftp service is running, on the FOG server from the linux installation open a terminal and type the following command
[code]
sudo service tftpd-hpa restart[/code]This should cause the service to restart. After the service is restarted please try the command on the windows box again.
I use the CNA program provided by cisco to edit the settings of my switches after the initial set up. I recommend using this program as it is a GUI and you can back up and restore switch settings within it. I would verify that Port Fast is enabled on all your ports with the CNA program.
