@pilipp_edv said in general questions about storage / master storage nodes:

After that, I configured the windows DHCP servers in the other locations to point to the main FOG server.

FWIW: You can (should) point the remote dhcp server to the remote storage node so the clients doesn’t need to transfer the ipxe boot image across your wan. The storage node will instruct the clients to “check in” with the fog master node.

The part you are missing is the FOG server plugin “Location”. With the location plugin you first identify your different locations. Then assign storage nodes to the “location” then assign existing client computers to the location. As you full register new clients there will be an added prompt for location during registration. This plugin pulls all of the bits together to make the clients find the proper storage node.

@george1421

The problem was the IGMP Snooping as you suspected. Thank you for your help.

@aviel1540 Not sure I understand the question entirely.

You deploy image to machine After machine deploys, create a capture task for the machine When machine boots, it does an upload of it’s image. Once uploaded, then it boots to the OS?

You can just tell the machine to shutdown after the tasks are complete, so that you don’t have to wait 5 seconds. Sure you would have to physically generate the capture task, but this way would prevent the system from booting to the Newly deployed image.

@cornycopia After thinking about it, there’s a “general” port that’s used.

FOG Settings -> FOG_FTP_PORT

Granted this isn’t per server, but it is a choosable thing.

@youzersef I was remote to the physical host, but it seemed more like a blue screen in comparison to just “hanging”.

Anyways, I reinstalled FOG and cloned “stable” instead of “master” and got around that issue.

I’m going to make another post for another issue I’m facing with UEFI (would have updated sooner, but forms have been down).

@zeltron80 So what would this look like ? I just simply want another server option in the menu. Is it using your ‘exit’ => ‘exit’ to ‘exit’ => ‘chain tftp://xxx.xxx.xxx.xxx/menu.ipxe’ ?

@youzersef finally solved was a very simple think in the end of the installation I was pressing enter and after that I was opening the link that was a reason why was not working omg 😅
Now to work it’s work but it’s going slow to capture the image how I can get more faster ?

Re: AlmaLinux 8.9 NetInstall or ISO

I ended up piggy backing the ipxe setup from fogproject and loading netboot.xyz which is doing the trick.

Thank you.

@bkgoodman This can be set from the fog web ui. FOG has a concept of storage nodes and master nodes. Only master nodes can collect images, you can deploy images from both master nodes and storage nodes. Where storage nodes are deploy only.

While the following deals with synology nas devices the same info can reference other NFS aware devices. Your target system needs both nfs AND ftp enabled to be able to function as a FOG storage node.

https://forums.fogproject.org/topic/9430/synology-nas-as-fog-storage-node

@altitudehack This was a spam attempt that was missed. I’m working on clearing it out, and apologize

@Tom-Elliott
No, the node points to the master configurations.
installtype=‘S’
snmysqluser=‘fogstorage’
snmysqlpass=‘password’
snmysqlhost=‘ip_master’

using the fogproject/bin/installfog.sh

Checking if this node is registered…Done

Node being registered…Done

Ensuring node username and passwords match…Done

Setup complete

You still need to setup this node in the fog management
| portal. You will need the username and password listed
| below.

Management Server URL:
http://fog.test.test/fog/

You will need this, write this down!
IP Address: 172.17.0.2
Interface: eth0
Management Username: fogproject
Management Password: password

I redid the installation using the fogproject/bin/installfog.sh script and everything went well. I deleted the storage node from the master and ran the commands below again, it returned success but the storage node was not added to the master.

source /fogproject/lib/common/functions.sh
source /opt/fog/.fogsettings
registerStorageNode

To enter bios of the VM, use F2 key on boot, then you can disable secure boot

@george1421 Cool! After reinstalling FOG, ipxe.efi has file sizes now so the ASUS PC can PXE boot with ipxe.efi. Thank you very much!

@PCF24 Here is a quick and dirty script to reset all your hosts.
I tested it with two hosts and it is working for me. I don’t want to reset all my hosts.

You will have to paste your FOG server IP, FOG user api token, and FOG settings api token to the script.
You will also need to install jq in your FOG server.
Debian base: sudo apt install jq. RHEL based: sudo dnf install jq

#!/bin/bash server_ip="http://10.10.10.10" fog_user_token="PASTE_YOUR_USER_API_TOKEN_HERE" fog_api_token="PASTE_YOUR_FOG_SETTINGS_API_TOKEN_HERE" all_hosts=$(curl -S -s -X GET -H 'content-type: application/json' -H "fog-user-token: $fog_user_token" -H "fog-api-token: $fog_api_token" $server_ip/fog/host/ | jq '.hosts[]') all_ids=$(echo "$all_hosts" | jq '.id') all_ids=${all_ids//\"/} for host_id in $all_ids do curl -S -s -o /dev/null -H "fog-user-token: $fog_user_token" -H "fog-api-token: $fog_api_token" -X PUT -d '{"pub_key":""}' $server_ip/fog/host/$host_id/edit curl -S -s -o /dev/null -H "fog-user-token: $fog_user_token" -H "fog-api-token: $fog_api_token" -X PUT -d '{"sec_tok":""}' $server_ip/fog/host/$host_id/edit curl -S -s -o /dev/null -H "fog-user-token: $fog_user_token" -H "fog-api-token: $fog_api_token" -X PUT -d '{"sec_time":"0000-00-00 00:00:00"}' $server_ip/fog/host/$host_id/edit done

@george1421 Thank you for your quick reply.
I am currently trying to get the multicast cloning to work over several vlans as in your instructions.
I am using OPNsense instead of Pfsense. Unicast works without problems, but we have many of the same PCs and so multicast would make sense.
Part 2.7 would be relevant to check that I have not forgotten any ports.
Part 3.1 and 3.2 as I have never worked with an IGMP proxy.
During a short test, everyone stopped before cloning and waited. Would assume it was because of my wrong IGMP configuration as I didn’t see any blocked ports on the firewall.

@Tom-Elliott
Thanks, for all the input.
I’ll see if i can find some sensible solution for my setup.