hp8000-8300elite Issues.

Troye Johnson · Jul 11, 2017, 2:58 PM

Just want to think anyone who is able to help in advance.

I am still having the issue where I need to replace the ipxe.krn file in the /tftpboot folder. if I do not replace the file I get the following error.

When I replace the file I loose the ability to customize the menu.

george1421 · Jul 11, 2017, 9:01 AM

Your tag line says you are running FOG 1.3.4 on centos is that correct?

What precisely do you have configured for dhcp option 67 {boot-file}? I will give you a hint that ipxe.krn, ipxe.lkrn, and pxelinux.0 is the WRONG answer.

quinniedid · Jul 11, 2017, 3:12 PM

@Troye-Johnson If you have that PC registered, would you try adding in the Host Kernel Arguments: acpi=off

You can find that by going to Host Management and selecting the individual host and applying that option.

I have found that to be a big deal with these HP workstations.

Troye Johnson · Jul 11, 2017, 3:26 PM

I just updated My tag line been a while since I posted.

@quinniedid I will give that a try, I think I tried it before but it wont hurt to try it again.

@george1421 I am using pxelinux.0 since it has been the only method that worked with these machines currently. I am using dnsmasq here is a copy of the config that has worked so far.

# Sample configuration for dnsmasq to function as a proxyDHCP server,
# enabling LTSP clients to boot when an external, unmodifiable DHCP
# server is present.
# The main dnsmasq configuration is in /etc/dnsmasq.conf;
# the contents of this script are added to the main configuration.
# You may modify the file to suit your needs.

# Don't function as a DNS server:
port=0

# Log lots of extra information about DHCP transactions.
log-dhcp

# Dnsmasq can also function as a TFTP server. You may uninstall
# tftpd-hpa if you like, and uncomment the next line:
# enable-tftp

# Set the root directory for files available via FTP.
tftp-root=/tftpboot

# The boot filename.
dhcp-boot=pxelinux,,192.168.1.172

# rootpath option, for NFS
#dhcp-option=17,/images

# kill multicast
dhcp-option=vendor:PXEClient,6,2b

# Disable re-use of the DHCP servername and filename fields as extra
# option space. That's to avoid confusing some old or broken DHCP clients.
dhcp-no-override

# PXE menu.  The first part is the text displayed to the user.  The second is the timeout, in seconds.
pxe-prompt="Press F8 for boot menu", 3

# The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
# Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI
# This option is first and will be the default if there is no input from the user.
pxe-service=X86PC, "Boot from fog", pxelinux

# A boot service type of 0 is special, and will abort the
# net boot procedure and continue booting from local media.
pxe-service=X86PC, "Boot from local hard disk", 0

# If an integer boot service type, rather than a basename is given, then the
# PXE client will search for a suitable boot service for that type on the
# network. This search may be done by multicast or broadcast, or direct to a
# server if its IP address is provided.
# pxe-service=x86PC, "Install windows from RIS server", 1

# This range(s) is for the public interface, where dnsmasq functions
# as a proxy DHCP server providing boot information but no IP leases.
# Any ip in the subnet will do, so you may just put your server NIC ip here.
# Since dnsmasq is not providing true DHCP services, you do not want it
# handing out IP addresses.  Just put your servers IP address for the interface
# that is connected to the network on which the FOG clients exist.
# If this setting is incorrect, the dnsmasq may not start, rendering
# your proxyDHCP ineffective.
dhcp-range=192.168.1.10,proxy,255.255.0.0

george1421 · Jul 11, 2017, 9:51 AM

@Troye-Johnson OK using dnsmasq isn’t a problem at all.

I can offer 2 suggestions here to make your life a bit easier, well OK 3.

Upgrade dnsmasq to version 2.76 or newer if you need to support both uefi and bios systems in the same environment.
pxelinux.0 will not work, no way with FOG 1.3.x and newer (I even question fog 1.2.0, but that is a moot point). Change the boot file pxelinux to undionly in 2 locations and then create a symbolic link from undionly.kpxe to undionly.0 in the /tftpboot directory.
Upgrade to centos 7 and start over.

Tom Elliott · Jul 11, 2017, 9:49 AM

@Troye-Johnson said in hp8000-8300elite Issues.:

# The boot filename.
dhcp-boot=pxelinux,,192.168.1.172

And

# The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
# Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI
# This option is first and will be the default if there is no input from the user.
pxe-service=X86PC, "Boot from fog", pxelinux

This appears to be the problem.

Troye Johnson · Jul 11, 2017, 7:33 PM

@george1421 & @Tom-Elliott

I have tried to change both of those boot files to undionly with symlink and it will not get past the tftpboot screen. It keeps saying the file cannot be found. My dnsmasq Version is “Dnsmasq version 2.48” and when I do a yum upgrade and update it says everything is up to date and I cannot seem to find instructions on installing 2.76 on centos 6.5. I could be over looking it. The only method I have been able to get working to get computers imaged is using the pxelinux.0 file with pxelinux.cfg

DEFAULT vesamenu.c32
LABEL fog
	MENU DEFAULT
	kernel ipxe.krn dhcp && chain http://${next-server}/fog/service/ipxe/boot.php?mac=${net0/mac}
PROMPT 0
TIMEOUT 01```

george1421 · Jul 11, 2017, 1:50 PM

@Troye-Johnson Ugh, only getting bits of the picture little by little is not helpful.

You are using a syslinux menu from somewhere. What / why is this setup?

george1421 · Jul 11, 2017, 8:58 PM

@Troye-Johnson said in hp8000-8300elite Issues.:

If you want to maintain the syslinux menu for some reason. You might be able to do this.

DEFAULT vesamenu.c32
LABEL fog
	MENU DEFAULT
	kernel ipxe.krn dhcp && chain tftp://<fog_server_ip>/default.ipxe
PROMPT 0
TIMEOUT 01

You just need to ensure that ipxe.krn from the latest version of fog is installed on your selinux pxe boot server. And in this case you will want pxelinux.0 as your pxe boot file.

If you are doing this all on the FOG server then I would again have to question why you are using syslinux, I would ignore the mess and pxe boot right into iPXE as the fog developers intended. I understand there may be business reasons to use syslinux as if you have a custom pxe boot menu you need to use.

Quazz · Jul 13, 2017, 8:28 AM

@Troye-Johnson Please post the output of

ls -lah /tftpboot

here

Instead of a symlink, you can also try to simply copy the undionly.kpxe to undionly.0

Troye Johnson · Jul 17, 2017, 2:26 PM

Ok sorry guys just got back from an unexpected vacation and now I am back to trying to get this working as it should.

Troye Johnson · Jul 17, 2017, 2:28 PM

@Quazz

drwxr-xr-x   6 fog  root 4.0K Jul 11 15:26 .
dr-xr-xr-x. 26 root root 4.0K Jul 11 15:11 ..
drwxr-xr-x   2 fog  root 4.0K Oct 20  2016 10secdelay
-rw-r-xr-x   1 fog  root  868 Jun 20 16:07 boot.txt
-rw-r-xr-x   1 fog  root  428 Jun 20 16:07 default.ipxe
drwxr-xr-x   2 fog  root 4.0K Aug  1  2016 i386-7156-efi
drwxr-xr-x   2 fog  root 4.0K Aug  1  2016 i386-efi
-rw-r-xr-x   1 fog  root 195K Jun 20 16:07 intel7156.efi
-rw-r-xr-x   1 fog  root 222K Jun 20 16:07 intel.efi
-rw-r-xr-x   1 fog  root  94K Jun 20 16:07 intel.kkpxe
-rw-r-xr-x   1 fog  root  94K Jun 20 16:07 intel.kpxe
-rw-r-xr-x   1 fog  root  94K Jun 20 16:07 intel.pxe
lrwxrwxrwx   1 root root   18 Jul 11 12:03 ipxe.0 -> /tftpboot/ipxe.efi
-rw-r-xr-x   1 fog  root 921K Jun 20 16:07 ipxe7156.efi
-rw-r-xr-x   1 fog  root 971K Jun 20 16:07 ipxe.efi
-rw-r-xr-x   1 fog  root 848K Jun 20 16:07 ipxe.iso
-rw-r-xr-x   1 fog  root 341K Jun 20 16:07 ipxe.kkpxe
-rw-r-xr-x   1 fog  root 341K Jun 20 16:07 ipxe.kpxe
-rw-r--r--   1 root root 316K Jul 28  2016 ipxe.krn
-rw-r-xr-x   1 fog  root 340K Jun 20 16:07 ipxe.krn.latest
-rw-r-xr-x   1 fog  root 334K Nov  8  2016 ipxe.krnold
-rw-r-xr-x   1 fog  root 334K Aug  1  2016 ipxe.krn.old
-rw-r-xr-x   1 fog  root 337K Mar 15 17:04 ipxe.krn.older
-rw-r-xr-x   1 fog  root 334K Nov 15  2016 ipxe.krn.org
-rw-r-xr-x   1 fog  root 341K Jun 20 16:07 ipxe.pxe
-rw-r-xr-x   1 fog  root 121K Jun 20 16:07 ldlinux.c32
-rw-r-xr-x   1 fog  root 184K Jun 20 16:07 libcom32.c32
-rw-r-xr-x   1 fog  root  26K Jun 20 16:07 libutil.c32
-rw-r-xr-x   1 fog  root  26K Jun 20 16:07 memdisk
-rw-r-xr-x   1 fog  root  29K Jun 20 16:07 menu.c32
lrwxrwxrwx   1 fog  root   14 Aug  1  2016 pxelinux.0 -> pxelinux.0.old
-rw-r-xr-x   1 fog  root  43K Jun 20 16:07 pxelinux.0.old
drwxr-xr-x   2 fog  root 4.0K Aug  1  2016 pxelinux.cfg
-rw-r-xr-x   1 fog  root 195K Jun 20 16:07 realtek7156.efi
-rw-r-xr-x   1 fog  root 221K Jun 20 16:07 realtek.efi
-rw-r-xr-x   1 fog  root  95K Jun 20 16:07 realtek.kkpxe
-rw-r-xr-x   1 fog  root  95K Jun 20 16:07 realtek.kpxe
-rw-r-xr-x   1 fog  root  95K Jun 20 16:07 realtek.pxe
-rw-r-xr-x   1 fog  root 194K Jun 20 16:07 snp7156.efi
-rw-r-xr-x   1 fog  root 220K Jun 20 16:07 snp.efi
-rw-r-xr-x   1 fog  root 194K Jun 20 16:07 snponly7156.efi
-rw-r-xr-x   1 fog  root 221K Jun 20 16:07 snponly.efi
lrwxrwxrwx   1 root root   23 Jul 11 12:03 undionly.0 -> /tftpboot/undionly.kpxe
-rw-r-xr-x   1 fog  root  94K Jun 20 16:07 undionly.kkpxe
-rw-r-xr-x   1 fog  root  94K Jun 20 16:07 undionly.kpxe
-rw-r-xr-x   1 fog  root  94K Jun 20 16:07 undionly.pxe
-rw-r-xr-x   1 fog  root  30K Jun 20 16:07 vesamenu.c32

This was the result

Troye Johnson · Jul 17, 2017, 2:32 PM

@george1421 said in hp8000-8300elite Issues.:

maintain the syslinux menu for some reason. You might be able to do this.
DEFAULT vesamenu.c32

hey, @george1421

I only did it this way because it was the only way I was able to get it to work. I have tried various different methods to get it to work without the syslinux menu but for some reason all of the other methods have failed me. I have dnsmasq installed on the fog server and we are also dealing with crossing subnets all of our servers are on the .1 subnet while all of the workstations are on the .11 subnet. I have no issues when imaging with my current setup but it does involve me replacing the ipxe.krn everytime I upgrade the fog server to the latest one from the ipxe.iso.

george1421 · Jul 17, 2017, 2:39 PM

@Troye-Johnson Well if you don’t “need” syslinux stuff, lets regroup and get FOG working as it was intended.

So you have dnsmasq running. Can you post the configuration of your dnsmasq file?

The first step is to get imaging working on the same subnet as the fog server, then we will work with the other subnets.

Troye Johnson · Jul 17, 2017, 2:47 PM

@george1421
Here is the dnsmasq config file I was using.

# Sample configuration for dnsmasq to function as a proxyDHCP server,
# enabling LTSP clients to boot when an external, unmodifiable DHCP
# server is present.
# The main dnsmasq configuration is in /etc/dnsmasq.conf;
# the contents of this script are added to the main configuration.
# You may modify the file to suit your needs.

# Don't function as a DNS server:
port=0

# Log lots of extra information about DHCP transactions.
log-dhcp

# Dnsmasq can also function as a TFTP server. You may uninstall
# tftpd-hpa if you like, and uncomment the next line:
# enable-tftp

# Set the root directory for files available via FTP.
tftp-root=/tftpboot

# The boot filename.
dhcp-boot=pxelinux,,192.168.1.172

# rootpath option, for NFS
#dhcp-option=17,/images

# kill multicast
dhcp-option=vendor:PXEClient,6,2b

# Disable re-use of the DHCP servername and filename fields as extra
# option space. That's to avoid confusing some old or broken DHCP clients.
dhcp-no-override

# PXE menu.  The first part is the text displayed to the user.  The second is the timeout, in seconds.
pxe-prompt="Press F8 for boot menu", 3

# The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
# Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI
# This option is first and will be the default if there is no input from the user.
pxe-service=X86PC, "Boot from fog", pxelinux

# A boot service type of 0 is special, and will abort the
# net boot procedure and continue booting from local media.
pxe-service=X86PC, "Boot from local hard disk", 0

# If an integer boot service type, rather than a basename is given, then the
# PXE client will search for a suitable boot service for that type on the
# network. This search may be done by multicast or broadcast, or direct to a
# server if its IP address is provided.
# pxe-service=x86PC, "Install windows from RIS server", 1

# This range(s) is for the public interface, where dnsmasq functions
# as a proxy DHCP server providing boot information but no IP leases.
# Any ip in the subnet will do, so you may just put your server NIC ip here.
# Since dnsmasq is not providing true DHCP services, you do not want it
# handing out IP addresses.  Just put your servers IP address for the interface
# that is connected to the network on which the FOG clients exist.
# If this setting is incorrect, the dnsmasq may not start, rendering
# your proxyDHCP ineffective.
dhcp-range=192.168.1.10,proxy,255.255.0.0

# This range(s) is for the private network on 2-NIC servers,
# where dnsmasq functions as a normal DHCP server, providing IP leases.
# dhcp-range=192.168.0.20,192.168.0.250,8h

# For static client IPs, and only for the private subnets,
# you may put entries like this:
# dhcp-host=00:20:e0:3b:13:af,10.160.31.111,client111,infinite

george1421 · Jul 17, 2017, 2:48 PM

@Troye-Johnson Can you also run this command from the fog server linux console dnsmasq -v and post the results here.

Also do you need or plan to support both uefi and bios (legacy) mode computers?

Troye Johnson · Jul 17, 2017, 2:50 PM

@george1421
Yes at lease until we get new computers in a year or two.

 dnsmasq -v
Dnsmasq version 2.48  Copyright (C) 2000-2009 Simon Kelley
Compile time options IPv6 GNU-getopt DBus no-I18N DHCP TFTP "--bind-interfaces with SO_BINDTODEVICE"

This software comes with ABSOLUTELY NO WARRANTY.
Dnsmasq is free software, and you are welcome to redistribute it
under the terms of the GNU General Public License, version 2 or 3.

george1421 · Jul 17, 2017, 2:58 PM

@Troye-Johnson OK you have a little work ahead of you. But in the end we will get this working for you.

Your version of dnsmaq is quite (very) old. We are going to go ahead and compile a newer version of dnsmaq for you. Version 2.76 is the first version that dynamically supported both uefi and bios firmware. So I’m going to recommend you fist update to 2.76 by compiling it yourself. Don’t worry I have a tutorial for that. It was written using ubuntu so I may need to spin up a centos 6.5 system to document the process using centos. There may be just enough different that it may cause you a problem. Once we get your dnsmasq updated then you can use the config file found in that tutorial and move away from that whole .0 file issue.

https://forums.fogproject.org/topic/8725/compiling-dnsmasq-2-76-if-you-need-uefi-support

I’ll report back when I have the centos 6.5 instance up and running and the tutorial tweaked.

Troye Johnson · Jul 17, 2017, 3:45 PM

@george1421

Ok so I started from scratch and got it to work in a vm using the steps from here “https://wiki.fogproject.org/wiki/index.php?title=Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server#DNSMASQ_settings_for_iPXE” Now while it worked in a vm when doing it from a workstation hp compaq elete 8300 ultra-slim desktop I get a “please enter tftp server:” error.

george1421 · Jul 17, 2017, 9:49 AM

@Troye-Johnson said in hp8000-8300elite Issues.:

please enter tftp server

This is telling us that the dhcp server is not setting dhcp option 66. If you manually enter the FOG server IP address I suspect you will see the fog ipxe menu

I have centos 6.5 installed and I’m just applying the updates to bring it to your current release. After that I’ll get the tutorial updated for compiling dnsmasq 2.76 (it WILL be worth your effort to upgrade).

hp8000-8300elite Issues.

149

12.0k

17.3k

155.2k