jfeyen Contributor.
Contributor.
1585 views

ZCM 2017 Update 2 - March Imaging Upgrade - UEFI PXE boot

Dear community,

In our organization we are using multiple installation platforms, depending on the OS and features we want on a laptop: Windows, Ubuntu ....
For this reason, we have a PXE boot loader system which redirects a administrator to either
- FOG installation system
- ZCM installation system
- or just plain load an iso over network

Before last week, this was all based on BIOS legacy system which we are converting to a EFI/UEFI based boot system based on DNSMASQ. This works well for all systems with exception of the ZCM system.
Explanation:

- ZCMserver is located in subnet1 having ip 10.1.254.178
- BootSelectorServer is located in subnet2 having ip 10.1.16.17


The bootselector server is based on a ubuntu 16.04 LTS with a DNSMASQ using following configuration


interface=eth0
bind-interfaces
dhcp-range=10.1.17.220,10.1.17.239,255.255.254.0,1h
dhcp-option=option:router,10.1.17.254
dhcp-option=option:ntp-server,10.1.16.5
dhcp-leasefile=/opt/dnsmasq/dnsmasq.leases
dhcp-sequential-ip
enable-tftp
tftp-root=/tftpboot

log-dhcp
port=0
dhcp-no-override


dhcp-vendorclass=BIOS,PXEClient:Arch:00000
dhcp-vendorclass=UEFI32,PXEClient:Arch:00006
dhcp-vendorclass=UEFI,PXEClient:Arch:00007
dhcp-vendorclass=UEFI64,PXEClient:Arch:00009

dhcp-boot=net:UEFI32,i386-efi/ipxe.efi,,192.168.112.24
dhcp-boot=net:UEFI,efi64/grubnetx64.efi.signed,,10.1.16.17
#dhcp-boot=net:UEFI64,efi64/grubnetx64.efi.signed,,10.1.16.17
dhcp-boot=net:UEFI64,efi/x86_64/nvlnbpx64.efi,,10.1.254.178
dhcp-boot=net:BIOS,bios/pxelinux.0,,10.1.16.17


When booting a server and performing a network boot, the DNSMASQ picks up the DHCP request, sets the UEFI64 tag and gives back the location of the ZCM server

Jun 11 09:28:19 PXESELECTOR001 dnsmasq-dhcp[6671]: 987456303 vendor class: PXEClient:Arch:00009:????:??????
Jun 11 09:28:19 PXESELECTOR001 dnsmasq-dhcp[6671]: 987456303 DHCPREQUEST(eth0) 10.1.17.220 00:50:56:86:b5:c1
Jun 11 09:28:19 PXESELECTOR001 dnsmasq-dhcp[6671]: 987456303 tags: UEFI64, eth0
Jun 11 09:28:19 PXESELECTOR001 dnsmasq-dhcp[6671]: 987456303 DHCPACK(eth0) 10.1.17.220 00:50:56:86:b5:c1
Jun 11 09:28:19 PXESELECTOR001 dnsmasq-dhcp[6671]: 987456303 requested options: 1:netmask, 2:time-offset, 3:router, 4, 5,
Jun 11 09:28:19 PXESELECTOR001 dnsmasq-dhcp[6671]: 987456303 requested options: 6:dns-server, 12:hostname, 13:boot-file-size,
Jun 11 09:28:19 PXESELECTOR001 dnsmasq-dhcp[6671]: 987456303 requested options: 15:domain-name, 17:root-path, 18:extension-path,
Jun 11 09:28:19 PXESELECTOR001 dnsmasq-dhcp[6671]: 987456303 requested options: 22:max-datagram-reassembly, 23:default-ttl,
Jun 11 09:28:19 PXESELECTOR001 dnsmasq-dhcp[6671]: 987456303 requested options: 28:broadcast, 40:nis-domain, 41:nis-server,
Jun 11 09:28:19 PXESELECTOR001 dnsmasq-dhcp[6671]: 987456303 requested options: 42:ntp-server, 43:vendor-encap, 50:requested-address,
Jun 11 09:28:19 PXESELECTOR001 dnsmasq-dhcp[6671]: 987456303 requested options: 51:lease-time, 54:server-identifier, 58:T1,
Jun 11 09:28:19 PXESELECTOR001 dnsmasq-dhcp[6671]: 987456303 requested options: 59:T2, 60:vendor-class, 66:tftp-server, 67:bootfile-name,
Jun 11 09:28:19 PXESELECTOR001 dnsmasq-dhcp[6671]: 987456303 requested options: 97:client-machine-id, 128, 129, 130, 131,
Jun 11 09:28:19 PXESELECTOR001 dnsmasq-dhcp[6671]: 987456303 requested options: 132, 133, 134, 135
Jun 11 09:28:19 PXESELECTOR001 dnsmasq-dhcp[6671]: 987456303 bootfile name: efi/x86_64/nvlnbpx64.efi
Jun 11 09:28:19 PXESELECTOR001 dnsmasq-dhcp[6671]: 987456303 next server: 10.1.254.178
Jun 11 09:28:19 PXESELECTOR001 dnsmasq-dhcp[6671]: 987456303 broadcast response
Jun 11 09:28:19 PXESELECTOR001 dnsmasq-dhcp[6671]: 987456303 sent size: 1 option: 53 message-type 5
Jun 11 09:28:19 PXESELECTOR001 dnsmasq-dhcp[6671]: 987456303 sent size: 4 option: 54 server-identifier 10.1.16.17
Jun 11 09:28:19 PXESELECTOR001 dnsmasq-dhcp[6671]: 987456303 sent size: 4 option: 51 lease-time 1h
Jun 11 09:28:19 PXESELECTOR001 dnsmasq-dhcp[6671]: 987456303 sent size: 4 option: 58 T1 30m
Jun 11 09:28:19 PXESELECTOR001 dnsmasq-dhcp[6671]: 987456303 sent size: 4 option: 59 T2 52m30s
Jun 11 09:28:19 PXESELECTOR001 dnsmasq-dhcp[6671]: 987456303 sent size: 4 option: 1 netmask 255.255.254.0
Jun 11 09:28:19 PXESELECTOR001 dnsmasq-dhcp[6671]: 987456303 sent size: 4 option: 28 broadcast 10.1.17.255
Jun 11 09:28:19 PXESELECTOR001 dnsmasq-dhcp[6671]: 987456303 sent size: 4 option: 42 ntp-server 10.1.16.5
Jun 11 09:28:19 PXESELECTOR001 dnsmasq-dhcp[6671]: 987456303 sent size: 4 option: 3 router 10.1.17.254

-------

On the ZCMServer you see an incoming connection and sending the TFTP file:
[DEBUG] [06/11/2018 09:28:20.000] [2083] [zmgtool] [4031] [] [zmgtool] [] [File sent to 10.1.17.220:1295 --> efi/x86_64/nvlnbpx64.efi] [] [] [] [Imaging]


But then the server just pops back to the main boot screen and nothing happens.

Anybody any thoughts please?

Thanks
Joeri
Kristof
Labels (1)
Tags (1)
0 Likes
4 Replies
Micro Focus Expert
Micro Focus Expert

Re: ZCM 2017 Update 2 - March Imaging Upgrade - UEFI PXE boo

I would suggest to testing in a lab w/o any 3rd party stuff in place to see if it works directly from ZCM.

If So.....LAN Trace to difference in the PXE Boot Details.....
Not sure I see where you are defining the Boot Parameters....that may be why it's not working...
0 Likes
jfeyen Contributor.
Contributor.

Re: ZCM 2017 Update 2 - March Imaging Upgrade - UEFI PXE boo

CRAIGDWILSON;2482330 wrote:
I would suggest to testing in a lab w/o any 3rd party stuff in place to see if it works directly from ZCM.

If So.....LAN Trace to difference in the PXE Boot Details.....
Not sure I see where you are defining the Boot Parameters....that may be why it's not working...


HI CRAIGDWILSON,

When pxe booting in the same VLAN as the ZENworks server it is working.

However in another VLAN it is not working.

Kr,

Joeri
Kristof
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: ZCM 2017 Update 2 - March Imaging Upgrade - UEFI PXE boo

Well...If on the Same VLAN then the devices may be responding to ZCM Server Proxy DHCP if that is running...vs your other solution.
Devices will respond to whoever responds 1st if multiple ones respond.
And may be responding to the ZCM ProxyDHCP Service that is not IP Relayed to Other Subnets....

There is not any configuration on ZCM PXE in regards to subnet handling....that is all handled by Router/Switch configuration....Most likely on same Subnet ZCM direct offering is winning and has the missing boot information details....

Examination of the Offer Packets on Working and Non-Working Subnets may help ID the configuration error....
0 Likes
jfeyen Contributor.
Contributor.

Re: ZCM 2017 Update 2 - March Imaging Upgrade - UEFI PXE boo

Hi Craigdwilson,

I got the DNSMASQ working as DHCP server which delivers the TFTP options for ZENworks in UEFI mode.

I had to add the following options to dnsmasq.conf

dhcp-option=net:UEFI64,vendor:PXEClient,1,192.168.54.56

dhcp-boot=net:UEFI64,efi/x86_64/nvlgrubx64.efi,192.168.54.56,192.168.54.56

Maybe it may help someone who wants to achieve the same.

Kr,

Joeri
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.