@george1421 Thanks. The existing DHCPD server is not adminstrated by us. Its managed somewhere else by another group. I can reserve a certian segment of the range , but thats about it It sounds like maybe it will be simpler to have a separate FOG server in each subnet.

@george1421 ok I see. Yes, there is a separate DHCP server serving a separate range within that same subnet. So perhaps that will complicate things

Thanks @george1421
Well, we did not have a separate dhcp server in our environment when we setup FOG. So we used the same server. If this isn’t advisable we can probably move the service to another host

@george1421 said in FOG unable to PXE boot beyond the VLAN/subnet that the server is on:

FOG iPXE menu

So specifically on subnet A where the FOG server is located we see the FOG iPXE menu when any system boots to network card. Everything works great . On subnet B we don’t see the FOG iPXE menu when a system boots to ethernet.

The Fog server is a Ubuntu 18 system it is also the DHCPD server .I have not changed the option 66 or 67.

@george1421

Hi George, I am working with Rich in our lab. Specifically we havea group of VMs on the same VLAN and subnet as the FOG server . Each time we boot to legacy ethernet on those VMs we see the FOG client menu that rich descibe. Buuut , although we have set up IP helpers on the switch when we boot physical machines on a separate VLAN/Subnet we are not getting an IP and seeing the PXE boot.

FOG server is running on an Ubuntu server . I am not clear where to change the DHCP settings?

I too am interested in being able specifically to launch deploy task from a command prompt (even if it’s on the FOG server itself). It’s not ideal to just schedule a task on shutdown because I may need to shut down the machine several times before I re-image. Does any one have any other ideas ?