@george1421 @Tom-Elliott

Thanks for the help again!

@Fimlore Yes, only changing the “IP” to point at the relevant VLan’s. I’m sure there’s more stuff that would need to be worked out of course, but at least you can see it can be worked out. And I’m typically just a message away.

Also, with notepad++, you can change the formatting from Windows to Linux, to prevent these kind of issues

That did it! Thank you!

@george1421 yes this has been solved. Sorry for the delay I have been out the last few days

@Tom-Elliott yes

Nevermind disregard this post I switched out the adapter and now it is booting. thanks for your time.

@alh said:

To me it is not clear why at this stage (after we booted from the undionly.kpxe and therefore already found our desired boot server) one does not simply hard-code the IP of the FOG server here during installation?

The iPXE binaries are not being compiled on installation time but provided as binary. Therefore we can’t just hard-code the FOG server IP.

Update 1.4 RC 5 fixed the issue. Thanks for everyones help!

@aboushard After a client finishes deploying the image it sends a request to the FOG server to tell it “Job done”. I am wondering if this is happening in your case as well. Can you please take a look at the apache access and error log files just after the client finished. See my signature on where to find those logs.

@george1421 said in Storage nodes not deploying images:

@EuroEnglish AFAIK, multicast sessions are only hosted by the master server. Unless something has changed in the multicast bits only the master server sends out the image.

This has changed, the non-master storage nodes are now able to multicast too. It’s something Tom worked on maybe 6 months ago. It was so multicast wouldn’t go across the WAN link and conform to the settings set in Location Management.

You were absolutely correct. The Cisco switch was running regular Spanning tree. It has been modified to use the fast spanning tree and it worked like a charm!

@dylan123 As stated earlier, I got an instant “Failed to get IP via DHCP” error when I had just the dongle plugged directly in. I also am already using the “has_usb_nic=1” argument. Lastly. I have both the dongle MAC and the USB hub MAC listed in the host.

Hello,

I updated our Fog server to 1.3.5 and am happy to report success!
The image was deployed to the computer that was having the problem without any action.

How can I flag this post as solved?

Mind you, as an informative thing I suppose, the working branch already has the directory index fix.

@Tom-Elliott said in Cannot complete Capture on HP Detachable and HP Streaming laptops:

Multipartition Single Disk

Changing it to Multipartition Single Disk worked just great… I was able to deploy and capture those machine

Ok, i guess Ill just type them in again.

Just so you know Im not crazy, i pasted two lines in to a new xls from an old export and the one i did today, the orange is the missing tag.

0_1492026053382_upload-44406e12-4a1d-4372-9419-9e130e94a3c5 10-95-044-086 78:ac:c0:ae:61:56 4028 Hewlett-Packard HP Compaq 4000 Pro SFF PC
SE40-084-109 78:ac:c0:ae:61:56 Hewlett-Packard HP Compaq 4000 Pro SFF PC

@dloudon96 In fog images have 2 components.

Raw data files Database definitions (descriptors) of the image

You can copy (move) files between your old fog server and your new fog server no problem. You must recreate the image definitions in the database by hand on the new fog server. If you have the old fog server still running you can just copy and paste between the web GUIs.

FYI: If your old fog server is a 1.3.x you can export the database definitions from the web gui of the old fog server and import them into the new fog server.

@thanson These may help you:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_Downloading_-_Multicast
https://wiki.fogproject.org/wiki/index.php?title=Multicast

@brooksbrown Ok then turning your linux server into a router is pretty simple. You just have to turn on a linux kernel parameter to make it route between the interfaces.

The first thing you need to do is to get FOG imaging correctly. When you setup FOG did you tell it to use the eth1 as your imaging interface?

Also post your config file for the isc dhcp /etc/dhcp/dhcpd.conf

You may want to review this setup for isc dhcp server if you need to support both bios (legacy) and uefi systems: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

From the error, my bet is that your dhcp configuration is wrong and your dhcp option 66 doesn’t point to the IP address of your eth1 interface.

And finally turning your linux box into a router: http://www.yourownlinux.com/2013/07/how-to-configure-ubuntu-as-router.html

This is the kernel setting you need to enable in sysctl /etc/sysctl.conf

net.ipv4.conf.default.forwarding=1 net.ipv4.conf.all.forwarding=1

But again lets get fog imaging correctly.
If you did not pick the proper settings during fog server install, there is a hidden file that contains the settings in /opt/fog/.fogsettings just review that file to ensure the settings are correct. If you need to change something make the change there and rerun the installer.