Saget25
New Member.
1368 views

Configuring PXE for UEFI Zenworks 2017 U3a

We are currently having problems with UEFI PXE service.

It does work in legaxy mode but we have not managed to make it work in UEFI mode.

Is there something to configure on the router ?
IP Helper stuff ?
If so, what do we need ?

If i take a look at the novell-proxydhcp.log we have that kind of information when we try to boot uefi pxe... but nothing happend on the client :

[DEBUG] [05/09/2019 12:57:37.000] [13769] [zmgtool] [13769] [] [zmgtool] [] [Boot File 64 bit efi/x86_64/nvlnbpx64.efi] [] [] [] [Imaging]
[DEBUG] [05/09/2019 12:57:37.000] [13769] [zmgtool] [13769] [] [zmgtool] [] [DHCP_OFFER sent to 255.255.255.255:68] [] [] [] [Imaging]
[DEBUG] [05/09/2019 12:57:37.000] [13769] [zmgtool] [13769] [] [zmgtool] [] [Received packet on 0.0.0.0:68] [] [] [] [Imaging]
[DEBUG] [05/09/2019 12:57:37.000] [13769] [zmgtool] [13769] [] [zmgtool] [] [Boot File 64 bit efi/x86_64/nvlnbpx64.efi] [] [] [] [Imaging]
[DEBUG] [05/09/2019 12:57:37.000] [13769] [zmgtool] [13769] [] [zmgtool] [] [DHCP_OFFER sent to 255.255.255.255:68] [] [] [] [Imaging]
[DEBUG] [05/09/2019 12:57:41.000] [13769] [zmgtool] [13769] [] [zmgtool] [] [Received packet on 0.0.0.0:68] [] [] [] [Imaging]
[DEBUG] [05/09/2019 12:57:41.000] [13769] [zmgtool] [13769] [] [zmgtool] [] [Boot File 64 bit efi/x86_64/nvlnbpx64.efi] [] [] [] [Imaging]
[DEBUG] [05/09/2019 12:57:41.000] [13769] [zmgtool] [13769] [] [zmgtool] [] [DHCP_OFFER sent to 255.255.255.255:68] [] [] [] [Imaging]
[DEBUG] [05/09/2019 12:57:41.000] [13769] [zmgtool] [13769] [] [zmgtool] [] [Received packet on 0.0.0.0:68] [] [] [] [Imaging]
[DEBUG] [05/09/2019 12:57:41.000] [13769] [zmgtool] [13769] [] [zmgtool] [] [Boot File 64 bit efi/x86_64/nvlnbpx64.efi] [] [] [] [Imaging]
[DEBUG] [05/09/2019 12:57:41.000] [13769] [zmgtool] [13769] [] [zmgtool] [] [DHCP_OFFER sent to 255.255.255.255:68] [] [] [] [Imaging]
[DEBUG] [05/09/2019 12:57:49.000] [13769] [zmgtool] [13769] [] [zmgtool] [] [Received packet on 0.0.0.0:68] [] [] [] [Imaging]
[DEBUG] [05/09/2019 12:57:49.000] [13769] [zmgtool] [13769] [] [zmgtool] [] [Boot File 64 bit efi/x86_64/nvlnbpx64.efi] [] [] [] [Imaging]
[DEBUG] [05/09/2019 12:57:49.000] [13769] [zmgtool] [13769] [] [zmgtool] [] [DHCP_OFFER sent to 255.255.255.255:68] [] [] [] [Imaging]
[DEBUG] [05/09/2019 12:57:49.000] [13769] [zmgtool] [13769] [] [zmgtool] [] [Received packet on 0.0.0.0:68] [] [] [] [Imaging]
[DEBUG] [05/09/2019 12:57:49.000] [13769] [zmgtool] [13769] [] [zmgtool] [] [Boot File 64 bit efi/x86_64/nvlnbpx64.efi] [] [] [] [Imaging]
[DEBUG] [05/09/2019 12:57:49.000] [13769] [zmgtool] [13769] [] [zmgtool] [] [DHCP_OFFER sent to 255.255.255.255:68] [] [] [] [Imaging]

For the moment we have option 66 configured on the SuSe OES DHCP server.

we tried with option 60 and 67 but no luck...

Any idea ?

Thank you !
Labels (1)
0 Likes
12 Replies
Micro Focus Expert
Micro Focus Expert

Re: Configuring PXE for UEFI Zenworks 2017 U3a

https://www.novell.com/documentation/zenworks-2017-update-2/pdfdoc/zen_cm_preboot_imaging/zen_cm_preboot_imaging.pdf
See Bottom of Page 61 into Page 62.

You need to configure the IP Helper Address for the the ZCM Proxy DHCP Services, which should be running on your Imaging Server.
Let the ZCM Proxy DHCP Server offer up the appropriate boot files vs your General Purpose DHCP Server.

Option 66 should Not be configured on your Suse OES DHCP Server, that will no longer work.....
It was never supported, but did work.
Now it will no longer work.
0 Likes
Saget25
New Member.

Re: Configuring PXE for UEFI Zenworks 2017 U3a

CRAIGDWILSON;2499484 wrote:
https://www.novell.com/documentation/zenworks-2017-update-2/pdfdoc/zen_cm_preboot_imaging/zen_cm_preboot_imaging.pdf
See Bottom of Page 61 into Page 62.

You need to configure the IP Helper Address for the the ZCM Proxy DHCP Services, which should be running on your Imaging Server.
Let the ZCM Proxy DHCP Server offer up the appropriate boot files vs your General Purpose DHCP Server.

Option 66 should Not be configured on your Suse OES DHCP Server, that will no longer work.....
It was never supported, but did work.
Now it will no longer work.


Is this required if the pxe devices are on the same vlan/network than the zcm server ?

It is really strange for the moment it does work one out of 30 times…

Thank you craig !
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Configuring PXE for UEFI Zenworks 2017 U3a

If they are on same subnet then no.....

The ZCM ProxyDHCP Server will look at the device's hardware as well as imaging work and then assign the appropriate boot loader.
One for Legacy BIOS
Another for UEFIO
And an array of others depending on if this particular device maybe doing WinPE and then may get varying flavors.

Lots of Intelligence on the ZCM Proxy-DHCP Server.

However, even in a UEFI Only Linux Boot Always the Boot Strap loader will not work correctly if not delivered by our Proxy DHCP Server.
I don't know the TECHNICAL Reasons for that, I just know it's the case from other folks who always delivered the file via their DHCP servers and tried to go UEFI.

In the real world however, that should not be a limitation because there is going to be a wide variety of devices needing different bootstraps and a static DHCP entry will not work in the end.
0 Likes
Saget25
New Member.

Re: Configuring PXE for UEFI Zenworks 2017 U3a

CRAIGDWILSON;2499489 wrote:
If they are on same subnet then no.....

The ZCM ProxyDHCP Server will look at the device's hardware as well as imaging work and then assign the appropriate boot loader.
One for Legacy BIOS
Another for UEFIO
And an array of others depending on if this particular device maybe doing WinPE and then may get varying flavors.

Lots of Intelligence on the ZCM Proxy-DHCP Server.

However, even in a UEFI Only Linux Boot Always the Boot Strap loader will not work correctly if not delivered by our Proxy DHCP Server.
I don't know the TECHNICAL Reasons for that, I just know it's the case from other folks who always delivered the file via their DHCP servers and tried to go UEFI.

In the real world however, that should not be a limitation because there is going to be a wide variety of devices needing different bootstraps and a static DHCP entry will not work in the end.


Ok.

Well many ressources at my office tried to make the UEFI PXE Boot work, we also had a consultant looking into this
and also Moises Morales at MicroFocus and we have not progressed.

Maybe the UEFI process is simply flawed…

We even tried with a VMWARE vm to boot and it is not stable…. but we have a little more success with the UEFI pxe boot

At this point our boss asked us to use USB pendrive to boot to our WinPE environment 😞

i find this a little disappointing.

If you have other ideas let me know.

PS: We also tried with a Zenworks 2017 Update 4 brand new server with a new zone to host the PXE and still working once every 30 times at best.
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Configuring PXE for UEFI Zenworks 2017 U3a

Your initial post you even stated that you were using DHCP to deliver the Boot File.
That can't work.
That was not even our documented process going back 20 years.

Moises may have not realized you were setup that way...


anto28;2499490 wrote:
Ok.

Well many ressources at my office tried to make the UEFI PXE Boot work, we also had a consultant looking into this
and also Moises Morales at MicroFocus and we have not progressed.

Maybe the UEFI process is simply flawed…

We even tried with a VMWARE vm to boot and it is not stable…. but we have a little more success with the UEFI pxe boot

At this point our boss asked us to use USB pendrive to boot to our WinPE environment 😞

i find this a little disappointing.

If you have other ideas let me know.

PS: We also tried with a Zenworks 2017 Update 4 brand new server with a new zone to host the PXE and still working once every 30 times at best.
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Configuring PXE for UEFI Zenworks 2017 U3a

The reason why it likely EVER works is luck for the Draw....
Your DHCP Server is send the Boot File....
Looks like your ZCM Proxy Server is sending a File.
Whoever gets there 1st wins.

The GOOD NEWS however....
Is you are due a Refund from your Consultant!!! LOL!!!!!!
0 Likes
Saget25
New Member.

Re: Configuring PXE for UEFI Zenworks 2017 U3a

Would like to but... don'T think they will haha 😉
0 Likes
Saget25
New Member.

Re: Configuring PXE for UEFI Zenworks 2017 U3a

We didnt had those option setuped... you mean option 60, 66, 67 ?

We tried enabling them to see if it would help... but it didn't do anything so we disabled them.

Our setup :

ZCM Server with Preboot services enabled
Microfocus OES DHCP
Everything is in the same IP Range, devices and servers too..

But still does not work unless we boot legacy
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Configuring PXE for UEFI Zenworks 2017 U3a

#1 - Find the SR# on which you were working with Moises.....We can use that for reference for what is happening.
#2 - PXE Boot a Vmware Workstation using UEFI and run wireshark so it captures all the PXE Traffice to see what is happening.

Sounds as if your OES DHCP Server is handing out imaging details.
That LAN Trace would help confirm where stuff is coming from.

There may even be some rogue server nobody knows about.
I recall when I was a Navy Contractor eons ago, some bored Gov't worker setup his own DHCP server during a night shift.
Talk about a fun morning until we figured out what happened 🙂
0 Likes
Saget25
New Member.

Re: Configuring PXE for UEFI Zenworks 2017 U3a

Yeah i thought about the rogue DHCP...

Thats why we even removed the voice VLAN in the area where we deploy images to be certain that nothing else would answer.

If we monitor the dhcpd.log and the novell-proxydhcp.log we see that there is activity in both while workstation are trying to boot UEFI PXE.

From what we see... the proxydhcp sends the boot filename... but then nothing else happens...

Yeah, i could try again with Moises to see if he has more ideas
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Configuring PXE for UEFI Zenworks 2017 U3a

Getting the LAN Trace will be Key....
VMware Workstation is the Easiest way to do that.
If you have that....no need for any help form your Networking team to split ports etc.....

The ZCM Server Logs will show the ZCM Server Responding to Device Requests.....
However, it will never show what responses the device is getting across the network.

A Device will send out a "DHCP Inform Requests" to ask how to boot.
Everyone who hears that will respond.
Whoever gets the answer to the PC 1st will win.

So even though the ZCM Server may send bootinfo, no way to know that the PC did not get other offers it took.

With VMware Workstation, you can just turn on wireshark and boot an "Blank/Empty" VM.
It will send out PXE requests and you can look to find all the responses.
Even if you are not the best at reading them, Moises is an old hand.....Maybe I better say experienced...don't want him mad at me.....



anto28;2499505 wrote:
Yeah i thought about the rogue DHCP...

Thats why we even removed the voice VLAN in the area where we deploy images to be certain that nothing else would answer.

If we monitor the dhcpd.log and the novell-proxydhcp.log we see that there is activity in both while workstation are trying to boot UEFI PXE.

From what we see... the proxydhcp sends the boot filename... but then nothing else happens...

Yeah, i could try again with Moises to see if he has more ideas
0 Likes
Saget25
New Member.

Re: Configuring PXE for UEFI Zenworks 2017 U3a

CRAIGDWILSON;2499511 wrote:
Getting the LAN Trace will be Key....
VMware Workstation is the Easiest way to do that.
If you have that....no need for any help form your Networking team to split ports etc.....

The ZCM Server Logs will show the ZCM Server Responding to Device Requests.....
However, it will never show what responses the device is getting across the network.

A Device will send out a "DHCP Inform Requests" to ask how to boot.
Everyone who hears that will respond.
Whoever gets the answer to the PC 1st will win.

So even though the ZCM Server may send bootinfo, no way to know that the PC did not get other offers it took.

With VMware Workstation, you can just turn on wireshark and boot an "Blank/Empty" VM.
It will send out PXE requests and you can look to find all the responses.
Even if you are not the best at reading them, Moises is an old hand.....Maybe I better say experienced...don't want him mad at me.....


I ran a wireshark and the output is different when it does not work... We can see DHCP Decline entries

See a capture that didnt lead to a successfull uefi pxe boot :

0.103953	10.148.0.3	255.255.255.255	DHCP	362	DHCP Offer    - Transaction ID 0xf0425a29
0.103953 10.148.0.3 255.255.255.255 DHCP 362 DHCP Offer - Transaction ID 0xf0425a29
0.103954 10.148.0.3 255.255.255.255 DHCP 362 DHCP Offer - Transaction ID 0xf0425a29
0.104411 10.148.0.26 255.255.255.255 DHCP 322 DHCP Offer - Transaction ID 0xf0425a29
0.104411 10.148.0.3 255.255.255.255 DHCP 362 DHCP Offer - Transaction ID 0xf0425a29
0.104732 10.148.0.26 255.255.255.255 DHCP 322 DHCP Offer - Transaction ID 0xf0425a29
0.104733 10.148.0.26 255.255.255.255 DHCP 322 DHCP Offer - Transaction ID 0xf0425a29
0.105055 10.148.0.26 255.255.255.255 DHCP 322 DHCP Offer - Transaction ID 0xf0425a29
0.105055 10.148.0.26 255.255.255.255 DHCP 322 DHCP Offer - Transaction ID 0xf0425a29
0.105055 10.148.0.26 255.255.255.255 DHCP 322 DHCP Offer - Transaction ID 0xf0425a29
0.105056 10.148.0.26 255.255.255.255 DHCP 322 DHCP Offer - Transaction ID 0xf0425a29
0.105056 10.148.0.26 255.255.255.255 DHCP 322 DHCP Offer - Transaction ID 0xf0425a29
0.105770 10.148.0.26 255.255.255.255 DHCP 322 DHCP Offer - Transaction ID 0xf0425a29
0.105770 10.148.0.26 255.255.255.255 DHCP 322 DHCP Offer - Transaction ID 0xf0425a29
0.105771 10.148.0.26 255.255.255.255 DHCP 322 DHCP Offer - Transaction ID 0xf0425a29
0.105771 10.148.0.26 255.255.255.255 DHCP 322 DHCP Offer - Transaction ID 0xf0425a29
0.106323 10.148.0.26 255.255.255.255 DHCP 322 DHCP Offer - Transaction ID 0xf0425a29
0.106323 10.148.0.26 255.255.255.255 DHCP 322 DHCP Offer - Transaction ID 0xf0425a29
0.106643 10.148.0.26 255.255.255.255 DHCP 322 DHCP Offer - Transaction ID 0xf0425a29
0.106644 10.148.0.26 255.255.255.255 DHCP 322 DHCP Offer - Transaction ID 0xf0425a29
3.753801 0.0.0.0 255.255.255.255 DHCP 395 DHCP Request - Transaction ID 0xf0425a29
3.753814 0.0.0.0 255.255.255.255 DHCP 395 DHCP Request - Transaction ID 0xf0425a29
3.755212 10.148.0.26 255.255.255.255 DHCP 322 DHCP ACK - Transaction ID 0xf0425a29
3.755301 0.0.0.0 255.255.255.255 DHCP 329 DHCP Decline - Transaction ID 0xf0425a29
3.755308 0.0.0.0 255.255.255.255 DHCP 329 DHCP Decline - Transaction ID 0xf0425a29

3.755426 10.148.0.26 255.255.255.255 DHCP 322 DHCP ACK - Transaction ID 0xf0425a29
3.755563 10.148.0.26 255.255.255.255 DHCP 322 DHCP ACK - Transaction ID 0xf0425a29
3.755657 10.148.0.26 255.255.255.255 DHCP 322 DHCP ACK - Transaction ID 0xf0425a29


And this is what we get when we get to the pxe boot menu :

12	0.468293	10.148.0.26	255.255.255.255	DHCP	322	DHCP Offer    - Transaction ID 0xe30d3a45
13 0.468457 10.148.0.26 255.255.255.255 DHCP 322 DHCP Offer - Transaction ID 0xe30d3a45
14 0.468805 10.148.0.26 255.255.255.255 DHCP 322 DHCP Offer - Transaction ID 0xe30d3a45
15 0.468805 10.148.0.26 255.255.255.255 DHCP 322 DHCP Offer - Transaction ID 0xe30d3a45
16 0.469098 10.148.0.26 255.255.255.255 DHCP 322 DHCP Offer - Transaction ID 0xe30d3a45
17 0.469098 10.148.0.26 255.255.255.255 DHCP 322 DHCP Offer - Transaction ID 0xe30d3a45
18 0.469346 10.148.0.26 255.255.255.255 DHCP 322 DHCP Offer - Transaction ID 0xe30d3a45
19 0.469346 10.148.0.26 255.255.255.255 DHCP 322 DHCP Offer - Transaction ID 0xe30d3a45
20 0.469613 10.148.0.26 255.255.255.255 DHCP 322 DHCP Offer - Transaction ID 0xe30d3a45
21 0.469681 10.148.0.26 255.255.255.255 DHCP 322 DHCP Offer - Transaction ID 0xe30d3a45
22 0.469850 10.148.0.26 255.255.255.255 DHCP 322 DHCP Offer - Transaction ID 0xe30d3a45
23 0.470106 10.148.0.26 255.255.255.255 DHCP 322 DHCP Offer - Transaction ID 0xe30d3a45
24 0.470486 10.148.0.26 255.255.255.255 DHCP 322 DHCP Offer - Transaction ID 0xe30d3a45
25 0.470703 10.148.0.26 255.255.255.255 DHCP 322 DHCP Offer - Transaction ID 0xe30d3a45
26 0.470992 10.148.0.26 255.255.255.255 DHCP 322 DHCP Offer - Transaction ID 0xe30d3a45
27 0.471445 10.148.0.26 255.255.255.255 DHCP 322 DHCP Offer - Transaction ID 0xe30d3a45
37 1.467969 10.148.0.3 255.255.255.255 DHCP 362 DHCP Offer - Transaction ID 0xe30d3a45
38 1.468325 10.148.0.3 255.255.255.255 DHCP 362 DHCP Offer - Transaction ID 0xe30d3a45
39 1.468532 10.148.0.3 255.255.255.255 DHCP 362 DHCP Offer - Transaction ID 0xe30d3a45
40 1.468874 10.148.0.3 255.255.255.255 DHCP 362 DHCP Offer - Transaction ID 0xe30d3a45
72 3.677835 0.0.0.0 255.255.255.255 DHCP 401 DHCP Request - Transaction ID 0xe30d3a45
73 3.677849 0.0.0.0 255.255.255.255 DHCP 401 DHCP Request - Transaction ID 0xe30d3a45
74 3.678879 10.148.0.26 255.255.255.255 DHCP 322 DHCP ACK - Transaction ID 0xe30d3a45
75 3.678880 10.148.0.26 255.255.255.255 DHCP 322 DHCP ACK - Transaction ID 0xe30d3a45
76 3.679173 10.148.0.3 255.255.255.255 DHCP 362 DHCP ACK - Transaction ID 0xe30d3a45
77 3.679173 10.148.0.26 255.255.255.255 DHCP 322 DHCP ACK - Transaction ID 0xe30d3a45
78 3.679173 10.148.0.26 255.255.255.255 DHCP 322 DHCP ACK - Transaction ID 0xe30d3a45
81 3.679576 10.148.0.26 255.255.255.255 DHCP 322 DHCP ACK - Transaction ID 0xe30d3a45
82 3.679577 10.148.0.26 255.255.255.255 DHCP 322 DHCP ACK - Transaction ID 0xe30d3a45
83 3.679858 10.148.0.26 255.255.255.255 DHCP 322 DHCP ACK - Transaction ID 0xe30d3a45
84 3.679858 10.148.0.3 255.255.255.255 DHCP 362 DHCP ACK - Transaction ID 0xe30d3a45
85 3.679858 10.148.0.3 255.255.255.255 DHCP 362 DHCP ACK - Transaction ID 0xe30d3a45
86 3.680103 10.148.0.26 255.255.255.255 DHCP 322 DHCP ACK - Transaction ID 0xe30d3a45
87 3.680103 10.148.0.26 255.255.255.255 DHCP 322 DHCP ACK - Transaction ID 0xe30d3a45
88 3.680103 10.148.0.3 255.255.255.255 DHCP 362 DHCP ACK - Transaction ID 0xe30d3a45
89 3.680413 10.148.0.26 255.255.255.255 DHCP 322 DHCP ACK - Transaction ID 0xe30d3a45
90 3.680414 10.148.0.26 255.255.255.255 DHCP 322 DHCP ACK - Transaction ID 0xe30d3a45
91 3.680855 10.148.0.26 255.255.255.255 DHCP 322 DHCP ACK - Transaction ID 0xe30d3a45
92 3.680856 10.148.0.3 255.255.255.255 DHCP 362 DHCP ACK - Transaction ID 0xe30d3a45
93 3.681222 10.148.0.26 255.255.255.255 DHCP 322 DHCP ACK - Transaction ID 0xe30d3a45
94 3.681482 10.148.0.3 255.255.255.255 DHCP 362 DHCP ACK - Transaction ID 0xe30d3a45
95 3.681813 10.148.0.26 255.255.255.255 DHCP 322 DHCP ACK - Transaction ID 0xe30d3a45
96 3.682061 10.148.0.3 255.255.255.255 DHCP 362 DHCP ACK - Transaction ID 0xe30d3a45
98 3.682189 10.148.2.109 10.148.0.26 DHCP 389 proxyDHCP Request - Transaction ID 0x57a2bdd8
99 3.682196 10.148.2.109 10.148.0.26 DHCP 389 proxyDHCP Request - Transaction ID 0x57a2bdd8
100 3.682317 10.148.0.26 255.255.255.255 DHCP 322 DHCP ACK - Transaction ID 0xe30d3a45
101 3.682574 10.148.0.3 255.255.255.255 DHCP 362 DHCP ACK - Transaction ID 0xe30d3a45
102 3.682575 10.148.0.26 10.148.2.109 DHCP 322 proxyDHCP ACK - Transaction ID 0x57a2bdd8
103 3.682901 10.148.0.26 255.255.255.255 DHCP 322 DHCP ACK - Transaction ID 0xe30d3a45




We can also see that the DHCP that sent an offer first what the Novell(Microfocus) OES DHCP when it fails and when it works, the first DHCP Offer is from the Zenworks server...

Is there a way to address this problem ?

Obviously we still need our DHCP... and the proxyDHCP for the PXEboot

Any idea ?
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.