• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

IPXE Error: No configuration methods succeeded

Scheduled Pinned Locked Moved Solved
FOG Problems
5
16
15.2k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G
    Gary Kulovics
    last edited by Aug 3, 2016, 11:32 AM

    Hello All
    Am running Fog 1.3.0 RC 5
    SVN Reversion 5943
    Am trying to Image a Dell laptop and getting the following error message
    IPXE Error: No configuration methods succeeded

    Weird thing is yesterday afternoon all was working fine and this morning got that message have tried it on a couple of PC that were image yesterday and am getting the same error
    Please help

    Thanks
    Gary

    1 Reply Last reply Reply Quote 0
    • T
      Tom Elliott @Gary Kulovics
      last edited by Aug 3, 2016, 12:09 PM

      @Gary-Kulovics Sounds like something is handing out a different file.

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

      Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

      Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

      G 2 Replies Last reply Aug 3, 2016, 12:14 PM Reply Quote 0
      • T
        Tom Elliott
        last edited by Aug 3, 2016, 11:52 AM

        What file are you using? Can you try the ipxe.pxe or ipxe.efi file?

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

        1 Reply Last reply Reply Quote 0
        • G
          Gary Kulovics
          last edited by Aug 3, 2016, 12:05 PM

          Hi Tom
          Was using undionly.kkpxe Did change it to ipxe.pxe as you suggested but still getting the same error.Not sure what is going on

          Thanks
          Gary

          T 1 Reply Last reply Aug 3, 2016, 12:09 PM Reply Quote 0
          • T
            Tom Elliott @Gary Kulovics
            last edited by Aug 3, 2016, 12:09 PM

            @Gary-Kulovics Sounds like something is handing out a different file.

            Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

            Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

            Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

            G 2 Replies Last reply Aug 3, 2016, 12:14 PM Reply Quote 0
            • G
              Gary Kulovics @Tom Elliott
              last edited by Aug 3, 2016, 12:14 PM

              @Tom-Elliott Anyway to check that out?

              Gary

              G 1 Reply Last reply Aug 3, 2016, 12:42 PM Reply Quote 0
              • G
                george1421 Moderator @Gary Kulovics
                last edited by Aug 3, 2016, 12:42 PM

                @Gary-Kulovics A screen shot of the actually error would be helpful to know exactly where in the process its failing.

                What model of dell laptop are we talking about here?

                The network port where this target computer is plugged in, do you have spanning tree enabled on that switch port, if you do are you using one of the fast spanning tree protocols (port-fast, fast-stp, rstp, [or the other one I can’t remember immediately])?

                If you place once of those small unmanaged “cheapie” switches between the building switch and the target computer does it boot correctly?

                If your target computer is in bios (legacy) mode then you will want undionly-(k)kpxe. That has worked on every dell device I have in my fleet.

                Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                G 2 Replies Last reply Aug 3, 2016, 1:07 PM Reply Quote 0
                • G
                  Gary Kulovics @george1421
                  last edited by Aug 3, 2016, 1:07 PM

                  @george1421 0_1470229561322_WP_20160803_08_58_03_Pro.jpg

                  The models have tried it on are 5420 and the 5550
                  Have tried to image it from the switch that the server is on and still get that error and yes spanning tree is enabled with the correct protocols Am using the undionly.kkpxe file and everything worked fine yesterday not sure what happened overnight

                  Thanks
                  Gary

                  G 1 Reply Last reply Aug 3, 2016, 2:08 PM Reply Quote 0
                  • G
                    Gary Kulovics @george1421
                    last edited by Aug 3, 2016, 2:05 PM

                    @george1421 Have just tired the 5550 and changed the bios to UEFI with secure boot off and for some reason that worked Changed back to bios (legacy) mode and got the above problem So not sure what is going on. Any settings that can be changed?

                    Thanks
                    Gary

                    G 1 Reply Last reply Aug 3, 2016, 2:09 PM Reply Quote 0
                    • G
                      george1421 Moderator @Gary Kulovics
                      last edited by Aug 3, 2016, 2:08 PM

                      @Gary-Kulovics Ok from the screen shot, I can see that the iPXE kernel is getting to the target computer and its booting so that removes PXE, tftp, and the boot file from the equation.

                      Can you confirm that mac address d0:67:e5:3d:59:b4 is the mac address of the ethernet adapter in that laptop?

                      This error really points to an issue with spanning tree in that its not picking up its (the iPXE kernel) from dhcp. As I suggested before, if you could test this idea by putting a dumb switch between the building switch and the target computer. This dumb switch will keep the building switch port from transitioning during the booting process.

                      Just for some background here. The link light on the target computer will wink (momentarily turn off and then back on) as the target computer transitions between each stage of booting PXE Rom->iPXE Kernel and iPXE Kernel->FOS Kernel. If spanning tree is on and one of the fast protocols are not used, the switch will take up to 27 seconds to put the port into a forwarding state. The FOG booting process is so fast that it has already given up when the switch port decides to start forwarding traffic. This is what we generally see.

                      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                      G 1 Reply Last reply Aug 3, 2016, 2:48 PM Reply Quote 0
                      • G
                        george1421 Moderator @Gary Kulovics
                        last edited by Aug 3, 2016, 2:09 PM

                        @Gary-Kulovics said in IPXE Error: No configuration methods succeeded:

                        @george1421 Have just tired the 5550 and changed the bios to UEFI with secure boot off and for some reason that worked Changed back to bios (legacy) mode and got the above problem So not sure what is going on. Any settings that can be changed?

                        Luck of the draw? For uefi booting you need to change your boot file to ipxe.efi. This is the same kernel (more or less) as undionly.kpxe except it is compiled for uefi mode.

                        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                        1 Reply Last reply Reply Quote 0
                        • G
                          Gary Kulovics @george1421
                          last edited by Aug 3, 2016, 2:48 PM

                          @george1421
                          Hi George
                          Yes the MAC address is the correct
                          Have put a dumb switch between the building switch and the PC and still am getting the same error
                          Anyway we can slow down the Fog booting process?

                          Thanks Gary

                          1 Reply Last reply Reply Quote 0
                          • G
                            Gary Kulovics @Tom Elliott
                            last edited by Aug 4, 2016, 2:42 PM

                            @Tom-Elliott
                            Hi Tom
                            Looks like you were right
                            Installed Wireshark and found that a printer installed by Xerox was causing the problem Killed the port it was on and Fog is now working

                            Thanks guys for all your help

                            Thanks
                            Gary

                            Wayne WorkmanW 1 Reply Last reply Aug 5, 2016, 2:02 AM Reply Quote 1
                            • Wayne WorkmanW
                              Wayne Workman @Gary Kulovics
                              last edited by Aug 5, 2016, 2:02 AM

                              @Gary-Kulovics said in IPXE Error: No configuration methods succeeded:

                              Installed Wireshark and found that a printer installed by Xerox was causing the problem Killed the port it was on and Fog is now working

                              I’d like to hear more information about that. What was this printer doing? Can you share the packet capture?

                              Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
                              Daily Clean Installation Results:
                              https://fogtesting.fogproject.us/
                              FOG Reporting:
                              https://fog-external-reporting-results.fogproject.us/

                              G 1 Reply Last reply Aug 6, 2016, 11:30 PM Reply Quote 0
                              • G
                                Gary Kulovics @Wayne Workman
                                last edited by Aug 6, 2016, 11:30 PM

                                @Wayne-Workman Hi Wayne
                                The printer was (nobody knows why)responsing to the Fog sever request for the tftp boot file Xerox is in next week and hopefully they can shed some light on it Unfortunally did not take a capture of packets with wire shark if it happens again will do it Again thanks for all your help guys

                                Gary

                                1 Reply Last reply Reply Quote 0
                                • L
                                  larosejm
                                  last edited by Jul 17, 2017, 1:28 PM

                                  I get the same exact error, every time, for every machine and then after rebooting once, it works every time. This just happened all of a sudden. Wireshark doesn’t see any tftp servers.

                                  G 1 Reply Last reply Jul 17, 2017, 2:09 PM Reply Quote 0
                                  • G
                                    george1421 Moderator @larosejm
                                    last edited by Jul 17, 2017, 2:09 PM

                                    @larosejm I’d like you to start a new thread with this issue. This thread started with an older version of FOG. We need to capture your specific details as how you have fog setup and under what host OS (i.e. things that are specific to your setup).

                                    Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                                    1 Reply Last reply Reply Quote 0
                                    • 1 / 1
                                    • First post
                                      Last post

                                    194

                                    Online

                                    12.0k

                                    Users

                                    17.3k

                                    Topics

                                    155.2k

                                    Posts
                                    Copyright © 2012-2024 FOG Project