DHCP Failed : no configuration methods succedeed.



  • Hi,

    I’m using fog server 1.5.7 on ubuntu 16.04.3.

    We have a little issue with some intel cards : PCI-E Intel chips 82574 on Dell Optiplex 5050 and 5060.
    I get first an IP, the undionly.kpxe is downloaded but then I face the error :

    DHCP Failed : no configuration methods succedeed.

    IMG_20191112_094919.jpg

    In the pxe shell I tried to bind ip manually and then ping, but it seems finally the IP is already binded but
    the ping does not work.

    I tried all I had in mind without any success, I even disabled the integrated NIC did not helped.
    What make this thing strange is the same card works without any issue on another PC (Dell Optiplex 9020 for instance).

    I finally made it works using intel.kpxe instead of undionly.kpxe !

    Any idea on how to make it works with undionly.kpxe?

    Thanks by advance,

    Proc.


  • Moderator

    Well the simple answer is not the best one I’m afraid. Use the intel.kpxe or ipxe.kpxe boot loader/kernel. The undionly.kpxe boot loader uses the built in network card’s UNDI functions to work. This keeps the iPXE small and fast because it doesn’t need one of every driver in the world, all its needs is the UNDI (universal) driver. Well some firmware is not as compatible as others.

    So what can you do?

    1. First I would ensure the target computers have the latest firmware.
    2. Switch to uefi and then use the iPXE boot loader of ipxe.efi.
    3. Stay in bios mode and switch over to the ipxe.kpxe boot loader. Both the ipxe,efi and ipxe.kpxe us the internal iPXE drives (one of many) instead of the generic driver (undionly.kpxe) for all bios based computers.
    4. If you have a windows 2012 or later or a linux dhcp server then you can create filters to only send the intel.kpxe driver to these specific models of dell computers. (for those that may find this post later, Dell is one of the few vendors that embed a model specific UUID that ca be detected by the dhcp server). I have not done this bit before, but should be similar to what we have in the wiki.

  • Moderator

    @Foglalt Yes new thread please. We like to keep one issue per thread so not to confuse future readers.



  • @george1421 I was thinking about what is best. New thread or ask in between. I chose the later cos I only need a step-by-step “what happens in stages of fog imaging”, cos network support needs it to find the guilty part. My test revealed that the problem is not the fog itself in this case, but was the network devices in our network somewhere. Still suggets to open a new thread? If so, I will do to make things clear.


  • Moderator

    @Foglalt said in DHCP Failed : no configuration methods succedeed.:

    Now we have a very few hw what has such problem. At the moment we are scheduled to use network support time to figure out some other problem, what caused almost same issue (separated fog is working with stupid switch, but built in wired system it fails with exact same “errormessages”.

    You should start your own thread because your settings may be different.

    I think we might have a translation problem here. But I think I understand that if you place a dumb (unmanaged) switch between the target computer and the building network switch it works? If that is the case then you must get with your network support team. They need to configure the building network switch to use one of the fast spanning tree protocols like (Fast-STP, RSTP, MSTP, port fast or whatever your switch manufacturer calls it). That will fix the problem in the original picture.



  • We has problems of such, but was not able to filter out a proper method that worked. We had to find other methods (if possible, even sdd out, and into other machine, etc). Now we have a very few hw what has such problem. At the moment we are scheduled to use network support time to figure out some other problem, what caused almost same issue (separated fog is working with stupid switch, but built in wired system it fails with exact same “errormessages”. To make a solution closer, may I ask the Fog experts here?

    the detailed steps of fogging can be named 1 by 1? since ipxe boot to partclone section. Somewhere there is a solution for our hw, but our network support leaks somehow and misses the solution. Now we have outsourced methods, but we need to feed them with a many details, as possible.)

    Can I ask a humble favour to have the detailed information I need? step by step at fog vesion 1.4 to actual versions if we have differences at all. My knowledge is farm from hw or firmware based details of the process 😞



  • Using ipxe.kpxe instead of undionly.kpxe solved the issue. Thanks for your help.



  • Thank you! I keep you informed


  • Moderator

    @processor said in DHCP Failed : no configuration methods succeeded.:

    And at last, I’ll made 2k12 filters. (Which is barely already done in a kind of way)

    If you get to this point I’m willing to help with what I know regarding to host identification.



  • Hi george1421,

    Thanks for your clear answer.
    I’ll first update the machine bios, but Dell computers are less and less open so I’m pretty sure it won’t help.
    Then I’ll give a try to ipxe.kpxe hoping it’l be compatible with all intel hardware we have as broadcom.
    And at last, I’ll made 2k12 filters. (Which is barely already done in a kind of way)

    Bye


  • Moderator

    Well the simple answer is not the best one I’m afraid. Use the intel.kpxe or ipxe.kpxe boot loader/kernel. The undionly.kpxe boot loader uses the built in network card’s UNDI functions to work. This keeps the iPXE small and fast because it doesn’t need one of every driver in the world, all its needs is the UNDI (universal) driver. Well some firmware is not as compatible as others.

    So what can you do?

    1. First I would ensure the target computers have the latest firmware.
    2. Switch to uefi and then use the iPXE boot loader of ipxe.efi.
    3. Stay in bios mode and switch over to the ipxe.kpxe boot loader. Both the ipxe,efi and ipxe.kpxe us the internal iPXE drives (one of many) instead of the generic driver (undionly.kpxe) for all bios based computers.
    4. If you have a windows 2012 or later or a linux dhcp server then you can create filters to only send the intel.kpxe driver to these specific models of dell computers. (for those that may find this post later, Dell is one of the few vendors that embed a model specific UUID that ca be detected by the dhcp server). I have not done this bit before, but should be similar to what we have in the wiki.

Log in to reply
 

320
Online

7.4k
Users

14.5k
Topics

136.5k
Posts