I have done this before on a Cisco switch but it’s been a while. Thought I share my notes on what commands are needed

# Vlan131 (fog server vlan) ip helper-address 192.168.158.255 # Vlan158 (fog client on a different vlan) ip directed-broadcast 101 # ip access-list extended 101 access-list 101 permit udp host 192.168.131.149 any eq 9 * NOTE in the ACL above 192.168.131.149 is the fog server ip address # forward udp ip forward protocol udp 9 (it might say discard) # On the switch the two vlans look something like this interface Vlan131 description fog server vlan ip address 192.168.131.1 255.255.255.0 ip helper-address 192.168.131.3 (my dhcp & dns server) ip helper-address 192.168.158.255 (fog client subnet broadcast address) end interface Vlan158 description fog client vlan ip address 192.168.158.1 255.255.255.0 ip directed-broadcast 101 (extended ACL) end

Hope it helps

Thanks @george1421,
I haven’t setup Fog yet so was looking for a step by step guide to getting it installed and configured.

I’ve gotten a very similar set up to what you want and have tried working.

You’ll need to either rebuild the FOG version of iPXE with the shim command enabled or use a stock version of iPXE with the default.ipxe script replaced with an autoexec.ipxe script (I haven’t tested this so you mileage may vary). Once you’ve done that you can just sign your iPXE binary with your sec boot key, and save it as grubx64.efi (or see this Shim Issue or this part of the foguefi install script if you use Dell PCs.)

Finally now when you netboot, provided you also have mokmanager (mmx64.efi) in the same folder, you’ll be prompted to install your secboot key and on next boot you’ll be able to boot. iPXE with secure boot on. You will also need to sign you bzImage etc and then modify your default.ipxe script to load the shim with the shim command, and then you’ll be able to boot into fog fully!

If anyone wants I can put together a more coherent guide and I’m happy to answer any questions you have on this.

Tom
I still get this error when I try to Create a New Image:
This page isn’t working
10.149.50.21 is currently unable to handle this request.
HTTP ERROR 500

Web searches says this is a server provider issue. Is there something in Fog Project that can be checked for me?

Hi @Tom-Elliott,

Currently both nodes are in the same storage group as I want to replicate images and snapins from the Master to the Normal storage Node. I read through some documentation and it seems this should still happen if they are in different storage groups. Is this true?

If so, I believe this second issue should be fixed.

@uzee FOG doesn’t change or really step into the target system during deployment. You CAN do this if you write a post install script that will get called once the target image is deployed to the target computer. In the case of a linux computer you could potentially set the target computer’s name here by updating the /etc/hostname file or anything else you can do with a bash script. The FOG Client can also be configured to make changes to the target computer or install applications based on instructions from the fog server. Its really identifying what you want to do and how much automation you want to script. Its all possible with FOG and a little creativity on your end. Since you already know Ubuntu (linux) bending FOG to what you want will be easier than coming strictly from a MS Windows background.

version is 1.5.10

I was not able to figure out capturing the image from a VM, I decided to use an actual desktop as the master/golden image. It made more sense as it would include the right hardware type, drivers, etc. I have captured the image finally. Now on to deployment

I’m having the exact same behavior.
Was working on the 27, 28 and 29.

Stopped working start of this week (2 september)
Added 3 storage nodes in between.
1a07ba58-be68-4007-a60c-5532e6c42e41-image.png

@Ryxn I checked and that nic has been in the linux kernel for several years.

And secondly when you checked for missing firmware the kernel wasn’t complaining about missing something.

Its a good thing you were able to get the error while in debug mode. Because that was going to be the next quest for you. To get the system when its behaving badly.

So when you get it into debug mode and its complaining about no nic lets do the following.

ip a s should show if the network interface has an ip address, I’m going to suspect no because it complained about it earlier in the boot process.

lspci -k -nn | more Look through this list until you find the entry. The number in the square brackets will be what you posted earlier. [8086&1502]. See if the nic is visible to the kernel. AND if it is it should mention what kernel driver its using. I’ll give you a for example using my laptop.

0000:00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection ( 13) I219-V [8086:15fc] (rev 20) Subsystem: Dell Ethernet Connection (13) I219-V [1028:0a22] Kernel driver in use: e1000e Kernel modules: e1000e

lastly if everything looks good, kernel sees the nic, there is a kernel driver assigned. Lets see if time fixes your problem.

When you ran the ip a s command it listed all of the network interfaces and if it has IP addresses. You will need to know the interface name for your network adapter. It may be something like eno1 or ens192, or something else. Get that device name.

Now run this command /sbin/udhcpc -i $iface --now replacing the whole word $iface with the device name listed from the ip command. This will tell the network adapter to again poll for an IP address from your dhcp server. If it picks up an IP address this time, then time does solve your problem and you will need to look into your network configuration and make sure that port-fast or fast-stp is enabled on your network port.

@george1421 Resolved: A 3rd party package in my router was intercepting my outbound FTP connections.

@aurfalien said in Mellanox ConnectX 3 imaging issues.:

So all good here.

Did FOS Linux have the driver enabled for that 10GbE card (i.e. were you able to image with FOG once you got past the iPXE menu)?

FWIW: For uefi mode snp.efi or snponly.efi should work if undionly.kpxe worked in bios mode. I’m saying it should because ConnectX3 is a somewhat older card (circa 2017/2018).

@Small0145 No, it’s not.

@Almeida BitLocker is enabled in your master ? If yes, you should disable it. Enable it only on the final computer.

We do have the BCD issue when enabling BitLocker on 24h2 image, we are running the same commands, but you are missing one.

You need to set device partition=C: for the recover from hibernate entry too. The annoying part is that its ID is dynamic.