Fog Failing to image across the same VLAN

[CheekiBreekiHelsinki]

Hey,

I have been trying to capture an OS build from a VM on the same VM cluster and VLAN as the FOG server but for some reason it fails when I then run PXE for it to be picked up. I can ping and ssh into the aforementioned VM from the FOG server so traffic is definitely going across.

It has been picked up by other workstations we have on other VLAN’s so we know that FOG is otherwise functioning as intended. We have DHCP server option 03 disabled on the FOG ipxe and snponly policies.

Any reason why something on the same VLAN would be blocked or have difficulty performing deployments and captures?

Thanks!

[george1421]

@CheekiBreekiHelsinki you have some missing information needed in your first post.

1. What device is your dhcp server? (manufacturer and version)
2. Is it on the same subnet as the FOG server? You mentioned the VM and FOG server was on the same subnet.
3. What hypervisor are you using?
4. I assume when you say “run PXE” you are saying you are trying to pxe boot the VM?
5. Is the VM in bios or uefi mode?
6. What specifically do you have defined for dhcp option 66 and 67?

Lets start with those questions to see what’s next

[CheekiBreekiHelsinki]

Hey @george1421 , Thanks for the quick reply, sorry for the missing details.

1. What device is your dhcp server? (manufacturer and version)

DHCP (and DNS) is running on an Active Directory 10.0.20348.1668, Windows Server 2022 Standard

2. Is it on the same subnet as the FOG server? You mentioned the VM and FOG server was on the same subnet.

This applies to any machine I’ve tried to deploy to from fog, for example fog is on subnet 100, unless the target of the deploy is specifically on subnet 101 it will fail to boot into the PXE server. Even with a Workstation/VM on subnet 100 (exactly the same subnet as the fog server) it will without fail time out this will happen on any subnet other than 101. In our case VLANs will correspond to Subnets.

Any machine on the 101 subnet can pxe boot to fog to capture and deploy with no issue with both UEFI and BIOS.

3. What hypervisor are you using?

We have found that we will see this issue whether on a VM or a Workstation so this isn’t limited to the hypervisor in question.

4. I assume when you say “run PXE” you are saying you are trying to pxe boot the VM?

Yes, correct.

5. Is the VM in bios or uefi mode?

We have tried both with the same result for either.

6. What specifically do you have defined for dhcp option 66 and 67?

For the two DHCP Policies we have in place for fog we have the following options set for 66d and 67:

FOG snponly.efi policy
66: 10.2.100.103 (IP address of our fog server)
67: snponly.efi

FOG ipxe.efi
66: 10.2.100.103 (IP address of our fog server)
67: ipxe.efi