Just for the notes: I pushed a fix for populating the “Working with node” column properly. But still I don’t think this is causing @TheDiskDrive’s issue. Please post a picture of the error you see and we should be able to help.

@manoca A client does request an address form the DHCP server on PXE boot three times in the FOG world. First when the network PXE ROM comes up for initial PXE booting, second we load iPXE doing another DHCP request as it cannot properly take over the information from the first round and third we load the Linux kernel which is doing DHCP again.

I’d advise you to take a picture of the issue on screen so we really know exactly what you see! It’s a bit of a guess work otherwise.

@Aysientor Depending on the mono version that is installed with Ubuntu there still is a bug that I am working on fixing in the fog-client. Well actually I think this might be more a bug/change in the mono packages rather than a bug in our client. Anyhow we have a workaround for this. Find information on this here: https://forums.fogproject.org/topic/13070/client-not-authenticating

I’ll probably get to properly fix this and release a new fog-client version in the next days.

Added in dev-branch as well.

@kafluke See if you can add the new storage node definition into the DB manually. I know this is ugly but we ought to see if this is working.

shell> mysql -u root -p
Password:
...
mysql> use fog;
...
mysql> INSERT INTO nfsGroupMembers VALUES ('', 'Dallas Storage Node', '', 0, 1, '/images', '/opt/fog/snapins/ssl', '/images', '', '/opt/fog/snapins', 1, '192.168.X.Y', 10, 0, 'fog', 'password', '', 'ens160', 1, '/fog');
...

Make sure you use the correct IP address. Do not just copy & paste the command you see above. Most values are fine but definitely take a look at IP and maybe name…

@processor It’s a very simple code change that you might just want to manually add:

diff --git a/packages/web/lib/fog/group.class.php b/packages/web/lib/fog/group.class.php
index fa1d763..24b844f 100644
--- a/packages/web/lib/fog/group.class.php
+++ b/packages/web/lib/fog/group.class.php
@@ -525,7 +525,7 @@ class Group extends FOGController
                     $port = $defaultPort;
                 }
                 $MulticastSession = self::getClass('MulticastSession')
-                    ->set('name', $taskName)
+                    ->set('name', $taskName . ' - ' . $this->get('name'))
                     ->set('port', $port)
                     ->set('logpath', $Image->get('path'))
                     ->set('image', $Image->get('id'))

@Tom-Elliott Do you see any reason for not adding this? I am not exactly sure if the task name is being used anywhere else and changing it might cause an issue?!?

@kafluke So do you still see the deleted node in the mysql/mariadb output??

Please help us with some more context. Which node (name) did you delete?

@pdit said in FOG isolated setup question:

just wondering if it will start providing dhcp address to pxe client or do we have to configure that in fog (dhcp scope).

As I said, in installing FOG a DHCP server is being installed and configured fro you. Just give it a try.

@lister From the logs we see that the multicast task was only scheduled for a single host. This is totally fine, just wanted to ask if you intended to do so for testing or if you actually wanted to multicast with more clients?

The other thing I noticed in the logs “udp-sender --interface dev …”. I guess dev is not the right name for a netword device in Linux. Please check the settings in the web UI (FOG Configuration -> FOG Settings -> Multicast Settings -> UDPCAST INTERFACE and while you are at it, also check Storage -> DefaultMember -> Interface)

@manoca said in FOG-Client not booting up due to DHCP-reasons?:

Is it possible, that Windows Server 2016 DHCP-Server is not working correctly, when there are no free IP adresses to lease?

Yes I’d say so! PXE boot needs IP addresses to hand out to work properly.

@dijsil So do you still have an issue or is it all working now?

@dijsil In the above DHCP settings screenshot you have ipxe.efi as “066 Boot Server Host Name” while it should really be 192.168.0.58 I suppose.

I guess you know our wiki article: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

@plegrand I’d say keep on doing more tests. If you see some machines not joining the session then you might want to cancel it and restart the FOG server just to have a clean test setup on every run.

All the computers have 2 partitions and strangely the first partition is slower than the second : about 700MB/min rate

From my point of view this is another hint that it’s not as much a network/switch issue but more due to the clients actually deploying the data to disk. There might be some clients that have a dieing disk that might be causing the slowdown for all clients in one session. You know that with multicast the slowest link of the chain is dictates the overall speed! While it causes way less network traffic than unicast for a group of computers it has the caveat of being regulated by the slowest part speed-wise.

@Guillaume-IT As well take a look at the Storage Node definition while you are in the web UI and make sure to correct the interface information there.

@TaTa As Wayne said a package capture would be best so we really know what is going on. But I might as well try to guess here from the screenshot. You run DHCP proxy (dnsmasq) and we see it telling “BOOT SERVER IP: x.x.191.205” (which I suppose is the NEW FOG server IP) on the first DHCP request from the client. The second DHCP request from iPXE seems to be pointing to the OLD server (tftp://x.x.176.205). So either you have another DHCP proxy server in your network that is messing things up (don’t think so) or your dnsmasq config still has the old IP in it somewhere. Be aware that in the dnsmasq config there are usually several places where you need to change the IP!!

Hint: I think the great changeIP script does not handle dnsmasq config changes as this is not a standard setup.

@Mark-krikunov I am not exactly sure what you are asking. Have you installed FOG on a server in your network yet? Do you want to use it for image deployment at all or is it only used for running scripts on the clients? Reading your other post it sounds like you want to do imaging as well and want to automate the whole process. That’s fine, have you looked into the FOG API yet?

The other thing you can start with is the fog-client software that is usually used on the clients to execute scripts. There is a currently pending issue with the client on Linux but we have a rough fix for that: https://forums.fogproject.org/topic/13000/fog-client-on-centos-can-t-authenticate-not-working

I’d say, start playing with FOG, install a server and do some imaging to get to know the whole system. As well play with the fog-client.

@pdit If you told FOG to handle DHCP for you it will install a DHCP server software and also generate a config and start the service for you. The config file might be in /etc/dhcpd.conf or /etc/dhcp/dhcpd.conf or /etc/dhcp3/dhcpd.conf depending on the Linux OS you have.

I am wondering, have you changed the FOG server IP when moving it to the isolated network after the install? Please read those things: https://wiki.fogproject.org/wiki/index.php/Change_FOG_Server_IP_Address and https://github.com/FOGProject/fog-community-scripts/blob/master/updateIP/updateIP.sh

@mpatel For CentOS use the following:

dodhcp='Y'
bldhcp='1'
dhcpd='dhcpd'
packages='bc curl dhcp ...'

Then re-run the installer and see it do the work.

@TheDiskDrive I have looked into this again and I am still not sure I really get this. You said:

i’ve tried the deploy task to a 10 tablet group and this is not working i have this following error:
Invalid storage group

Where/when exactly do you get this error message? Please take a picture of the error on screen and post here!

When i launch the task and watching task progression ( in task management section) no working node is used

As I said before, the empty column in the web UI is not causing the problem from my point of view. I have just done another test and it deploys perfectly fine on my test systems.

@Guillaume-IT said in [CentOS 7 - FOG 1.5.5] Boot PXE:

I have 2 interfaces:

Who told you this is gonna work??