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

    MacPro6,1 PXE boot

    Scheduled Pinned Locked Moved
    Hardware Compatibility
    5
    25
    8.3k
    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.
    • C
      chief @george1421
      last edited by

      @george1421 I have moved the FOG server into the same VLAN and IP subnet. I have the DHCP set up as per the BIOS and UEFI co existence post. I am now getting PXE boot on windows, but it fails with a “No configuration methods succeeded”

      Capture

      The screenshot is from Virtualbox, but I’ve tested on phyical Dell laptops with same issue.

      george1421G 1 Reply Last reply Reply Quote 0
      • george1421G
        george1421 Moderator @chief
        last edited by george1421

        @chief Its been a few days now so lets make sure we are on the same page.

        You have the dhcp server (MS Windows??), the FOG server, and the PXE booting client all on the same vlan for testing.

        The target computer PXE boots, then the iPXE kernel is sent to the target computer. But now iPXE complains about “No configuration methods succeeded”

        If this is the case, my initial reaction is that this might be a spanning tree issue (assuming this happens on the dell computer).

        Why?, because the target computer pxe boots and the undionly.kpxe (or ipxe.efi) is sent to the target. computer. To do that the PXE rom must be able to talk to the dhcp server to get an IP address and boot file name. When the iPXE kernel launches it momentarily resets the network interface causing the link light to drop (wink) for a second. If spanning tree is enabled on that switch port and it is not configured for one of the fast STP protocols, the port won’t go into the forwarding state for 27 seconds. By then the iPXE kernel has given up stating “No configuration methods succeeded” or in english - “I can’t get a dhcp address on any network interface”.

        A quick check for a spanning tree issue is to place a dumb (unmanaged) switch between the target computer and the building network switch. If it boots into the FOG menu with the unmanaged switch in line then you need to speak to your networking group to confirm that one of the fast STP protocols are enabled. This is not a FOG issue but a networking issue.

        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!

        C 2 Replies Last reply Reply Quote 0
        • C
          chief @george1421
          last edited by

          @george1421 Thanks for help. Was off for a few days over the holiday period.

          Yes, Windows 2012r2 DHCP server. The FOG server and PXE client are on same VLAN/Subnet.

          Will test the network issues.

          1 Reply Last reply Reply Quote 1
          • C
            chief @george1421
            last edited by chief

            @george1421 Putting a dumb switch in between fixes the issue.
            We have Dell switches with portfast enabled and a bpdufilter. After a bit of googling, I think the bpdufilter should allow the dhcp through the switches.

            george1421G 1 Reply Last reply Reply Quote 0
            • george1421G
              george1421 Moderator @chief
              last edited by

              @chief Ok if you put a dumb switch in between the target computer and building switch and it resolved the problem. Then its probably one of the advanced protocols causing the issue.

              This is typically spanning tree being enabled and not using one of the fast stp protocols.

              Or you have green ethernet (802.3az) enabled on the building switch. We’ve seen this to be an issue with some realtek nics.

              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
              • 2
              • 2 / 2
              • First post
                Last post

              194

              Online

              12.0k

              Users

              17.3k

              Topics

              155.2k

              Posts
              Copyright © 2012-2024 FOG Project