@Obsidian

What is the output of your replicator logs? Can you paste them here? You can go to your FOG site and go to the FOG Configuration Icon then the Log Viewer link on the left hand side. Be sure to select “Replicator” from the file menu.

@Junkhacker
This is what the default.ipxe has. We did modify the line beginning with “chain” to be the IP of our primary fog server and now our remote PCs can PXE boot as well as work using the registration/imaging capability of FOG.

!ipxe
cpuid --ext 29 && set arch x86_64 || set arch i386
params
param mac0 ${net0/mac}
param arch ${arch}
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:bootme
chain http://changedthisIP/fog/service/ipxe/boot.php##params

Can you please provide the details as to why this was the fix?

Thanks

@Junkhacker

I should add that the change to the default.ipxe file took me to the “Full Registration…” menu and allowed me to run through the prompts, but would not let me image a system. It wasn’t until i copied over the /var/www/html/fog/service/ipxe file over to the storage node that I was able to successfully image a system.

I’m going to document the exact steps to get a storage node setup at another branch office and have it image systems locally using the storage node instead of the master fog server. I should have this up by end of week.

@Obsidian

What is the output of your replicator logs? Can you paste them here? You can go to your FOG site and go to the FOG Configuration Icon then the Log Viewer link on the left hand side. Be sure to select “Replicator” from the file menu.

@Tom-Elliott
Yes all the nodes are on the same version as the main server. They had the files/folder in the path /var/www/html/fog/service/ipxe, but the clients booting from one of the storage nodes would not display the menu until we copied over the folder from the main server. We did make some modifications to the main server’s FOG_TFTP_PXE_KERNEL so that is why I had to copy it over to the clients.

@Tom-Elliott
I didn’t mean any offense by what I said.

@Junkhacker

I should add that the change to the default.ipxe file took me to the “Full Registration…” menu and allowed me to run through the prompts, but would not let me image a system. It wasn’t until i copied over the /var/www/html/fog/service/ipxe file over to the storage node that I was able to successfully image a system.

I’m going to document the exact steps to get a storage node setup at another branch office and have it image systems locally using the storage node instead of the master fog server. I should have this up by end of week.

@Junkhacker
This is what the default.ipxe has. We did modify the line beginning with “chain” to be the IP of our primary fog server and now our remote PCs can PXE boot as well as work using the registration/imaging capability of FOG.

!ipxe
cpuid --ext 29 && set arch x86_64 || set arch i386
params
param mac0 ${net0/mac}
param arch ${arch}
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:bootme
chain http://changedthisIP/fog/service/ipxe/boot.php##params

Can you please provide the details as to why this was the fix?

Thanks

@Wayne-Workman This doesn’t seem to work as flawlessly as described by Tom.

We had to add manually go into the MySQL database on the master fog server and allow access from the storage nodes as adding the storage node username and password into the FOG website configuration menu didn’t do anything. We were then able to get remote pcs to boot into the the local storage node’s PXE menu, but when we click on the “Perform Full Registration & Inventory” the remote pc just reboots and launches whatever pre-install OS there is instead of running the registration process.

@Wayne-Workman Apache is running:
service httpd status
httpd (pid 23626) is running…

Firewall is completely disabled and turned off with no rules set.

@Wayne-Workman That IP is for the site B storage node, which is now the master node for site B’s storage group. I can view the contents of the directory via CLI /var/www/html/fog/service/ipxe or /var/www/fog/service/ipxe which contain:
advanced.php bg.png boot.php bzImage bzImage32 grub.exe init_32.xz init.xz memdisk memtest.bin

If I go to the website http://10.63.10.107/fog/service/ipxe/boot.php there is nothing that shows up on my browser.

@Wayne-Workman

Hello Wayne,

I am aware of Tom and who he is and I greatly appreciate the work he has done with FOG as it has helped us out greatly.

I tried the solution suggested and the PXE/TFTP services are installed, however, the client systems are still getting the error “http://10.X.X.X.X/fog/services/ipxe/boot.php no such file or directory. Could not boot ipxe.org/2d12603b” then booting into their normal HD’s OS.

@ch3i I created a storage group for site B and added the new storage node to this new storage group. I clicked on the “Is Master Node” checkbox for Site B’s new storage node as well. I’m still getting the error mentioned above in that the host will begin the PXE boot and you can see the message about iPXE. Here is a screenshot:

@Bigredcherokee does the storage node contain all the images or are they using NFS to another host?