Unable to PXE boot after office move



  • Server
    • FOG Version: 1.3 RC?
    • OS: Centos 7
    Client
    • Service Version:
    • OS: 10
    Description

    Hi,
    After an office move and what I believe to be an identical setup my machines are failing to PXE boot with ‘connection reset’ alt text

    From this machine I am struggling to boot with I am able to ping my fog server. The machine is also getting an IP address from the fog server, however when I type the url for the fog management into a browser on the machine I get the page cannot be displayed which suggests that my fog server may be operating on some level but not fully? I cannot log in to the management system to get the RC version apologies.

    Sorry for my lack of knowledge but I am unsure where to begin troubleshooting.

    Thanks as always,
    Tom


  • Moderator

    @TomBagley It’s good to hear the tool worked for you and that your issues are solved.



  • @Wayne-Workman I changed the IP address to conform to our new networking structure and ran the tool which worked a charm. My Fog server has now sprung into life and is functioning as it was before the move so it must have been a network setting at our end that was causing the malfunction to begin with!

    Thanks for the help as always really appreciate it.

    Tom



  • @Wayne-Workman Thanks Wayne I will try that and let you know.


  • Moderator

    @TomBagley said in Unable to PXE boot after office move:

    I’m able to PXE boot if I roll back my Fog Server to a checkpoint when I first completed the build which does suggest I’ve changed something inadvertently.

    Well that’s weird. First thing I’d recommend on the current version (not the rolled back one) is re-running the fog installer.

    If the IP hasn’t changed at all, running the tool wouldn’t help anything.



  • Hi,

    I’m able to PXE boot if I roll back my Fog Server to a checkpoint when I first completed the build which does suggest I’ve changed something inadvertently.

    I’ve only updated one image since this checkpoint so if it sounds sensible I’ll look to export the newest image, roll the server back and then import the newer image.

    Tom



  • Hi,
    Thanks for the responses. I have left the IP address the same although there is a wish to rebuild and change it to fit inline with our new network structure so that script is going to be extremely useful to me.

    Having said that there’s a possibility it was changed from it’s usual IP and then back to it so do you feel it’s still worth running the updateIP tool?

    Tom


  • Moderator

    If the fog server’s IP changed - first make sure it doesn’t change again. Do that with either a DHCP reservation or a static address. After that, there’s a tool I put together in this repository that will update the IP address in all the places on your FOG server for you: https://github.com/FOGProject/fog-community-scripts It’s the updateIP one. You would clone that entire project with git clone just as you would for the fog repository.


  • Moderator

    Did you change the IP address of your fog server during/after the office move?
    Did you make any modifications to the fog server during/after the office move?

    The boot.php page (needed to boot) is supplied by the apache web server FOG uses. This is the same web server that hosts the management pages. So its logical if the management pages do not display, neither will pxe boot be working.


Log in to reply
 

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.