Topics created by cary1102

Make sure your firmware is up to date in this hardware. Its failing between the UEFI PXE rom hand off and iPXE starting. Typically when we’ve seen this in the past it was related to cruddy early generation firmware.

I know this is kind of old, but I had this same issue yesterday. I fixed it by running the installer and upgrading.

I think it would have been fixed by simply re-running the installer if I didn’t have to upgrade. I was only one version behind. I’ve notice most issues with Fog can be fixed this way.

@george1421 Thank you for the response. The issue was the switch. I put a “dummy” switch in place of my other one and it worked. I ended up enabling fastport on my other switch and success. Appreciate the help!

@Sebastian-Roth Thank you for your advice. What you said seemed to be my issue. All I did was uncomment option routers and replace the IP with my DHCP server IP. I can get into the FOG splash screen now. Thanks!

@cary1102 For that to work you need to push the router/gateway information to the clients in the 10.10.222.0 subnet. Add the following line so your config looks like this:

subnet 10.10.222.0 netmask 255.255.255.0 { option subnet-mask 255.255.255.0; option routers 10.10.222.XXX; ...

Put in the gateway IP address instead of XXX. I suppose you have a router/gateway that is making communication between the two different subnets possible?!?

You need to know that there might be other obstacles still in front of you. The clients use a couple different protocols like HTTP (easy), FTP and NFS to communicate with your FOG server and so the gateway needs to forward all those for the clients to be able to work properly.

I don’t know how we can possibly help you.

You haven’t told us what you’ve tried doing, what’s not working, or any thing. You give us, quite literally:

“I installed it, what do I do now?”

The best I can do is give you our User Guide, located here:
https://wiki.fogproject.org/wiki/index.php?title=FOGUserGuide

I have since messed with my setup and no longer have the error. Sorry but I did not get a screenshot of the warning.