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

    IPXE Issues

    Scheduled Pinned Locked Moved
    FOG Problems
    5
    15
    2.8k
    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.
    • J
      jaoyer @Junkhacker
      last edited by

      @Junkhacker

      3rd time’s the charm…try these:

      Picture 1: Failing using the old server address
      https://drive.google.com/open?id=0B6yrqHh_joc2d20tWEZzdWcwMVBhckk4V1dZb0Z4MlVvMkpr

      Picture 2: Failing with undionly.kpxe.INTEL with 5 “dots”
      https://drive.google.com/file/d/0B6yrqHh_joc2aENyMnJtRE16aFE/view?usp=sharing

      Picture 3: Working undionly.kpxe.INTEL
      https://drive.google.com/open?id=0B6yrqHh_joc2WnBhWUdEemFIQVNqZ1dybzk4RTlOeFFmSENn

      JunkhackerJ 1 Reply Last reply Reply Quote 0
      • JunkhackerJ
        Junkhacker Developer @jaoyer
        last edited by

        @jaoyer those worked. any luck with default.ipxe?

        signature:
        Junkhacker
        We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

        J 1 Reply Last reply Reply Quote 0
        • J
          jaoyer @Junkhacker
          last edited by

          @Junkhacker

          Copying the file over has worked consistently the last 5 times I booted a test machine, so I am fairly certain that that works. However, I am still concerned why it is pointing at the old server. It is my intention to decommission our old server at some point, and am afraid that it will still look to the old server for the default.ipxe file. To test this, I took our old fog server down so that it was completely shut off and booted my test machine . It was still looking for the the default.ipxe file on our old server even though it was down and it eventually timed out.

          https://drive.google.com/open?id=0B6yrqHh_joc2bWdYWkZobTlHSmV3TXQyNk9IcklnRG5YLTZv

          Is there any cache or anything that I have to clear out on our switches?

          How does the “next-server” part of the script work? Is it something as simple as giving the new server an address that comes before the old server?

          JunkhackerJ 1 Reply Last reply Reply Quote 0
          • JunkhackerJ
            Junkhacker Developer @jaoyer
            last edited by

            @jaoyer whatever is serving out options 66/67 dhcp options is providing the next-server address.

            signature:
            Junkhacker
            We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

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

              So option 66/67 of the DHCP server are set to point at the New fog server?

              The Old fogserver’s IP Address in the 66 option would cause the problem. YOu would need to update the option 66 to point at the new fog server.

              What’s the contents of:

              cat /tftpboot/default.ipxe
              

              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

              J 1 Reply Last reply Reply Quote 0
              • J
                jaoyer @Tom Elliott
                last edited by

                @Tom-Elliott

                Option 66 is set to the new server
                Option 67 I have set to either undionly.kpxe or undionly.kpxe.INTEL (I’ve tested both).

                0_1495130576562_dhcp capture.JPG
                Cat returns:

                #!ipxe
                cpuid --ext 29 && set arch x86_64 || set arch i386
                params
                param mac0 ${net0/mac}
                param arch ${arch}
                param platform ${platform}
                param product ${product}
                param manufacturer ${product}
                param ipxever ${version}
                param filename ${filename}
                isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
                isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
                :bootme
                chain http://10.40.22.67/fog/service/ipxe/boot.php##params

                Tom ElliottT 1 Reply Last reply Reply Quote 0
                • Tom ElliottT
                  Tom Elliott @jaoyer
                  last edited by

                  @jaoyer So is that the global options for options 66/67? Is it possible your lan is using “scoped” options to point lans where to get their options 66/67?

                  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

                  J 1 Reply Last reply Reply Quote 0
                  • J
                    jaoyer @Tom Elliott
                    last edited by

                    @Tom-Elliott

                    I think that fixed it. I do have split scope dhcp setup on two servers, and only changed the options on one of them. I changed them in both and it seems to be working fine now.

                    Feel free to call me an idiot 😄

                    As far as the updating issue going from 1.30RC10 to 1.40 (detailed in my 2nd response), should I create new thread?

                    Tom ElliottT Wayne WorkmanW 2 Replies Last reply Reply Quote 1
                    • Tom ElliottT
                      Tom Elliott @jaoyer
                      last edited by

                      @jaoyer Did you run the installer as sudo ./installfog.sh?

                      I might suggest rerunning the installer after gaining root first through sudo -i

                      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
                      • Wayne WorkmanW
                        Wayne Workman @jaoyer
                        last edited by

                        @jaoyer said in IPXE Issues:

                        As far as the updating issue going from 1.30RC10 to 1.40 (detailed in my 2nd response), should I create new thread?

                        Yes.

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

                        206

                        Online

                        12.1k

                        Users

                        17.3k

                        Topics

                        155.3k

                        Posts
                        Copyright © 2012-2024 FOG Project