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

    /Default.ipxe connection timeout on Dell only

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    9
    14
    8.1k
    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.
    • TrevelyanT
      Trevelyan
      last edited by

      What switches are you using?

      I had a similar issue which was down to portfast not being enabled on the relevant switchports. I only saw this happen after I upgraded to 1.2.0.

      1 Reply Last reply Reply Quote 0
      • cmlC
        cml Moderator
        last edited by cml

        I have a similar issue with one model of Dell laptops and solved it using this undionly.kpxe

        Debug is enabled on dhcp and tftp and the script drops to a shell if it fails to tftp, for further troubleshooting.

        The only modification is with the ipxescript:

        #!ipxe
        :netstart
        dhcp && goto netboot || goto netstart
        :netboot
        ping -c 1 ${next-server} || goto netstart
        chain tftp://${next-server}/default.ipxe || shell
        
        

        And here are all to pxe files created with that script. pxe-files.tar.gz

        –EDIT–

        Forgot to include my issue that this solves.

        We have Dell Inspiron 11z laptops that fail to get a DHCP address the first time iPXE issues the command. If the DHCP command is sent right after if succeeds and everything works normally.

        T 1 Reply Last reply Reply Quote 1
        • Tom ElliottT
          Tom Elliott
          last edited by

          You’ll likely find it simpler to just update to SVN/Trunk (if you can).

          The problem is specific to what that NIC is expecting to download from. It is expecting a specific parameter to get the default.ipxe file.

          Most systems work naturally when it is set to: /default.ipxe but there are a few quirks where the nic is EXPECTING tftp://${next-server}/default.ipxe

          Basically it’s expecting the implicit direction of protocol and where to get the 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 2
          • N
            need2 Moderator
            last edited by

            Also ensure your 7020s are on the latest BIOS release. I have seen a number of PXE issues in Dell systems that are on early editions of their BIOS, especially in 3020, 7020, and 9020s.

            Wayne WorkmanW 1 Reply Last reply Reply Quote 0
            • Wayne WorkmanW
              Wayne Workman @need2
              last edited by

              @need2 said:

              Also ensure your 7020s are on the latest BIOS release. I have seen a number of PXE issues in Dell systems that are on early editions of their BIOS, especially in 3020, 7020, and 9020s.

              The newer optiplexes (in my experience) auto update their bios. there’s a dell utility that, if installed, will keep it updated.

              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/

              1 Reply Last reply Reply Quote 1
              • ?
                A Former User @Tom Elliott
                last edited by

                @Tom-Elliott Thank you thank you! - I did some searching and came across this: https://wiki.fogproject.org/wiki/index.php/SVN#Install_Subversion_2 I followed the directions and now everything is working perfect.

                Thanks EVERYONE for all your assistance!

                1 Reply Last reply Reply Quote 1
                • T
                  Tyler W. Cox @cml
                  last edited by

                  @cml Thanks for the link to the debug undionly.kpxe it helped us solve our problem right away. Turns out we had a rogue DHCP server that was issuing a second lease after just before the hand-off to the default.ipxe file. That lease didn’t have an ip for the tftp server. As soon as we shut it down we got a successful boot!

                  george1421G 1 Reply Last reply Reply Quote 1
                  • george1421G
                    george1421 Moderator @Tyler W. Cox
                    last edited by

                    @Tyler-W.-Cox I’m a bit surprised that you had a second dhcp server running and you didn’t have IP conflicts or other random dhcp issues. But we are glad you got it worked out and have fog deployed successfully in your environment.

                    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!

                    Tfoote01T 1 Reply Last reply Reply Quote 1
                    • Tfoote01T
                      Tfoote01 @george1421
                      last edited by

                      @george1421

                      Not sure what the fix was, Second DHCP server? I’m running 1.4.4 and getting this same issue but I dont see anywhere what the fix was,

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

                        @tfoote01 The fix was to disable the rogue dhcp server that was giving conflicting information to the target computer ( in Tyler’s case )

                        If you are having a similar issue, please open a new thread with your specific details. We like to keep specific conditions to their own threads if possible.

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

                        143

                        Online

                        12.1k

                        Users

                        17.3k

                        Topics

                        155.3k

                        Posts
                        Copyright © 2012-2024 FOG Project