iPXE boot Lenovo m725s
-
Trying to network boot some new workstations but receive the message no configuration methods succeeded followed by the URL to the ipxe article on DHCP timeout.
Able to boot legacy on the devices with undionly. Able to boot legacy and uefi ipxe.efi on laptops with the same model NIC. What am I missing?
Happy to provide additional information. -
@mcturnan87 Which version of FOG do you have? Please take a picture of the error on screen and post here.
-
@Sebastian-Roth We’re on FOG version 1.5.6
-
@mcturnan87 If you put an unmanaged switch between this computer and the building network does it work correctly?
From a working windows computer, if you go into the device driver for this network adapter what is the hardware ID for this network adapter (f.e. PCI\VEN_8086&DEV_15BB&CC_0200)?
-
@mcturnan87 Fairly sure this is a spanning tree issue. Try George’s suggestion.
-
@george1421 @Sebastian-Roth The switch I have both the FOG instance and the workstation plugged into is unmanaged (cisco sg100d-08). I’ve also tried on DLink umanaged switch (dLink dgs-1016d).
Hardware ID is PCI\VEN_10EC&DEV_8168&SUBSYS_314117AA&REV_0E
-
@mcturnan87 Please download an earlier version of iPXE (https://github.com/FOGProject/fogproject/raw/c3f2e63307033a8a6b0e1c4bda27a4d646c163d6/packages/tftp/ipxe.efi) and put that in
/tftpboot/directory on your FOG server. Rename the original file so you have a copy of that too. See if booting with that makes a difference.I think we’ve had another user the other day who had an issue with the lately updated iPXE UEFI binary as well.
-
@Sebastian-Roth I’ll give that a try at my next opportunity.
I failed to mention that FOG is not running DHCP, this is run by a Windows server. Vendor classes for efi/legacy booting have been configured on that server.
Would a switch with spanning tree between DHCP and fog/workstation throw this error as well?
-
@mcturnan87 said in iPXE boot Lenovo m725s:
Would a switch with spanning tree between DHCP and fog/workstation throw this error as well?
Depends on the switch model and network card but very likely yes.
I failed to mention that FOG is not running DHCP, this is run by a Windows server.
Good you mention this. Is this a failover setup with two DHCP servers? We have seen very strange issues when a DHCP cluster is not in sync.
-
@Sebastian-Roth Understood, I’ll verify our use of spanning tree in our network (new guy here, trying to bring the joy of imaging :D)
Only one DHCP server in the building, pretty small office.
-
Backed up original ipxe efi and downloaded one recommended. No change.
-
@mcturnan87 said in iPXE boot Lenovo m725s:
VEN_10EC&DEV_8168
That is one of those rotten realtek 8168 NIC adapters. I was looking into those about a month ago (already!!). If I remember right there was a change in the linux kernel around 4.10 where the linux kernel guys switched from a generic cdc driver to the realtek native driver. If I remember correctly the nic would init correctly but not communicate to the network. If we launched a debug install/deploy and then on FOS linux system look in the syslog there was an error regarding the init of that network adapter. I don’t happen to have a computer with that nic in it so I couldn’t debug it much more.
-
@george1421 The boot doesn’t get to the Linux kernel. It fails in iPXE already. See the picture below.
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
-
I had that problem on some notebook models.
In my case was the boot file.Changing the undionly.kkpxe that im using (on the standard boot files) by the realtek.kpxe it works.
Try the different boot files. Maybe some works.
Now my dnsmask and my isc dhcp deliver different file based on mac vendor bytes.
-
@Sebastian-Roth ok well dang, I assumed I saw the picture correctly. My mistake. (still may be an issue once we get past this).
As you said when we have issues here, its typically spanning-tree blocking the port.
-
@mcturnan87 said in iPXE boot Lenovo m725s:
sg100d-08
I looked at the specs for that sg100 and its supports 802.3az (green ethernet) so it may support spanning tree out of the box. Do you have a cheap unmanaged switch. Like a $20 amazon special?
-
@EduardoTSeoane This is UEFI though.
@mcturnan87 You can try using
realtek.efiinstead ofipxe.efi… -
@george1421 Noted. We do have the same NIC in our laptops and they are getting to the FOG ok. Haven’t tried a registration or deploy yet but I do get to the menu. Finger crossed we don’t hit the wall because they are 8168s.
@EduardoTSeoane We’re in an UEFI ~only environment. There is still some legacy but we’re moving away from it. Thanks for the input thought!
@Sebastian-Roth Confirmed spanning tree on our main switch stack. Will segregate our imaging network and set up FOGs dhcp. I’ll check back in soon.
-
@mcturnan87 said in iPXE boot Lenovo m725s:
Confirmed spanning tree on our main switch stack
Spanning tree can and should be used on your network, you just need to enable one of the fast spanning tree protocols like rstp, mstp, fast-stp or what ever your switch mfg calls it.
The cheap-o switches don’t support spanning tree at all, so as a test for this we temporarily insert one of these cheap switches between the pxe booting computer and the building switch to test.
And as always, is the firmware up to date on this HP system?
Haven’t tried a registration or deploy yet but I do get to the menu.
The fog menu is managed by iPXE (where you currently have the issue), beyond that then its FOS Linux.
-
@george1421 Set up an isolated network with just the FOG instance running DHCP, the workstation, and tried 3 different switches; the Cisco and Dlink I mentioned previously, as well as, a TPLink 6 port switch I found that appeared to be the ‘dumbest’ in the office. Received the same screen.
@Sebastian-Roth I tried realtek.efi, received same screen.
