Server Migration PXE Boot Issues
-
I created a WOL task and the hosts are non-responsive.
I PXE booted one of those hosts just now and got this message…
-
@Joe-Gill WOL was fixed in 1.4.4 as there was an issue with WOL not being cleared.
That said, the information seems conflicting. Are these systems on the same subnet as the FOG Server? If not, are you using WOL Broadcast plugin to steer the WOL traffic to the broadcast addresses of the network they’re to be booted to/from?
-
I will update to 1.4.4.
FOG server is on the same subnet as the hosts. I haven’t changed any of my addressing from old FOG server.
-
One thing that did change on this install is that I eliminated a password on our mysql database and I eliminated the FOG user on the server and FOG itself. I have gone through and done the best I could to change those things throughout FOG.
-
Well I updated to 1.4.4. I ran back through everything to make sure I had all my usernames and passwords changed on the server. I found a few that were not correct. That seems to have resolved the non-PXE boot issues…
The WOL issue is still there though. Now I task it and it doesn’t show up in tasks. But nothing happens on the hosts I’m tasking.
-
I just tried sending a Host a Wipe task w/ WOL. The host appeared in my task list like it should. WOL did not work. I manually powered on the host and it PXE booted into the task and started the task. So it appears everything functions except WOL.
-
@Joe-Gill This is not a problem with WOL or this would be reported ALL over the place. Something on your network is not sending the WOL Packets (or should I say not allowing the packets to start the device you’re hoping to turn on).
-
Sounds like it must be a setting on my VM. I’ll check it out and post a fix when I figure it out. The only things that have changed are the OS and the OS the VM is running in and the new enclosure. It must be one of those things.
Thanks!
-
You were correct! I apologize! I forgot we moved my test lab to a different switch. I can use WOL just fine now in one of my other labs on a different switch. Having the network admin adjust the port settings on that switch. I’m certain that’s the issue!
Everything else with our upgrade is working! Yay! Now I’m on Debian on upgraded hardware.
Thanks!!
-
We discovered the issue… DNS was not set properly on the FOG server… Don’t ask why this made a difference but when I reset things and restarted the server WOL works again. Ugh!
Settings on our switch ports were identical. So that was likely not the issue.
-
So it’s safe to solve?
-
Yes sir! Things are working well! I’ve multicasted several machines this afternoon without a hitch. Yay! Thanks!!
