Popopinsel Absent Member.
Absent Member.
2503 views

PXE-E77: Bad or missing discovery server list

Hi,

some recent changes to our Novell DHCP server (separate from ZCM (Proxy DHCP) server) and to our Avaya router have lead to our devices not being able to PXE boot the ZCM Imaging Engine (11.2.3a). They get a valid IP from our DHCP pool and show the Novell DHCP server as DHCP IP and the Avaya router as GATEWAY IP. After that we get "PXE-E77: Bad or missing discovery server list". Isn't the ZCM server supposed to show up as the DHCP IP?

I didn't do those changes but I know that some DHCP Relays (pointing to the Novell DHCP server) were configured for recently created VLANs (for WLAN) and Option 43 was set on our DHCP pool on the Novell DHCP server for the WLAN access points.

Can anybody help me with this?
Labels (2)
0 Likes
6 Replies
Knowledge Partner
Knowledge Partner

Re: PXE-E77: Bad or missing discovery server list

Popopinsel,
> Can anybody help me with this?


Packet trace would help. Never seen that particular error, but it
indicates something is missing. In your scenario (separate DHCP and
PDHCP) both servers should answer to the WSes DHCP request and then the
WS takes contact on a different port.

Also yank up loglevel on PDHCP server and look at the logs.

--
Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Have an idea for a product enhancement? Please visit:
http://www.novell.com/rms

0 Likes
Knowledge Partner
Knowledge Partner

Re: PXE-E77: Bad or missing discovery server list

Also see:

"Troubleshooting the ZCM Imaging Environment Lecture"

http://www.novell.com/feeds/nih/wp-content/uploads/2012/05/ZEN03_lecture.pdf



--
Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Have an idea for a product enhancement? Please visit:
http://www.novell.com/rms

0 Likes
Popopinsel Absent Member.
Absent Member.

Re: PXE-E77: Bad or missing discovery server list

This is what novell-proxydhcp.log shows:

Received packet on 0.0.0.0:68
DHCP_OFFER sent to 255.255.255.255:68
Received packet on 0.0.0.0:68
0 Likes
Popopinsel Absent Member.
Absent Member.

Re: PXE-E77: Bad or missing discovery server list

OK, I raised the log level for PDHCP to 4 and this is the result:

Novell Proxy DHCP service 11.2.3
PXE Boot Services
Copyright Novell, Inc. 2003-2010 All rights Reserved
Started
Configuration file: C:\Program Files (x86)\Novell\ZENworks\conf\preboot\novell-proxydhcp.conf
Using interface: 139.64.221.227
Policy engine address: 139.64.221.227
Boot server menu timeout: 2
DHCP service on same server: NO
X86 NBP: nvlnbp.sys
Logging level: 4
fresult value 1
Received packet on 0.0.0.0:68
Opcode: 1 BOOTREQUEST
Hardware address type: 1
Hardware address len: 6
Hop count: 0
Transaction ID: 0x65a16b6d
Client elpased time: 0x4
Flags: 0x8000
Client self-assigned addr: 0.0.0.0
Client IP address: 0.0.0.0
Next server IP address: 0.0.0.0
Gateway IP address: 0.0.0.0
Client hardware address: d4 85 64 a1 6b 6d 00 00
00 00 00 00 00 00 00 00
Server host name:
Boot file name:
Option magic cookie: 0x63825363 valid
Options:
option 53 (len = 1): Message type DHCPDISCOVER
option 55 (len = 36): Parameter request list Request count 36:
1 Subnet mask
2 Time offset
3 Router
4 Time server
5 Name server
6 DNS server
11 Resource location server
12 Host name
13 Boot file size
15 Domain name
16 Swap server
17 Root path
18 Extensions path
22 Max datagram reassembly size
23 Default IP TTL
28 Broadcast address
40 NIS domain
41 NIS servers
42 Time protocol servers
43 Vendor specific information
50 Request IP
51 IP address lease time
54 Server ID
58 Renewal time value
59 rebinding time value
60 Vendor class ID
66 TFTP server name
67 Boot file name
128 Unknown
129 Unknown
130 Unknown
131 Unknown
132 Unknown
133 Unknown
134 Unknown
135 Unknown
option 57 (len = 2): Max message size 1260
option 97 (len = 17): PXE client UUID type 0
41 53 ca d5 a7 d2 de 11
bb da 64 a1 6b 6d d4 85
option 93 (len = 2): PXE client architecture type 0 IA x86 PC
option 94 (len = 3): PXE client UNDI version type 1, version 2.01
option 60 (len = 32): Vendor class ID
PXEClient:Arch:00000:UNDI:002001

DHCP_OFFER sent to 255.255.255.255:68
Opcode: 2 BOOTREPLY
Hardware address type: 1
Hardware address len: 6
Hop count: 0
Transaction ID: 0x65a16b6d
Client elpased time: 0x4
Flags: 0x8000
Client self-assigned addr: 0.0.0.0
Client IP address: 0.0.0.0
Next server IP address: 139.64.221.227
Gateway IP address: 0.0.0.0
Client hardware address: d4 85 64 a1 6b 6d 00 00
00 00 00 00 00 00 00 00
Server host name: Novell Proxy DHCP Server
Boot file name: nvlnbp.sys
Option magic cookie: 0x63825363 valid
Options:
option 53 (len = 1): Message type DHCPOFFER
option 54 (len = 4): Server ID 139.64.221.227
option 97 (len = 17): PXE client UUID type 0
41 53 ca d5 a7 d2 de 11
bb da 64 a1 6b 6d d4 85
option 60 (len = 9): Vendor class ID
PXEClient
option 220 (len = 4): Novell policy engine 139.64.221.227
option 43 (len = 123): Vendor specific information
PXE sub-option 6 (len = 1): Discovery control 0x3
Disable broadcast discovery
Disable multicast discovery
PXE sub-option 8 (len = 7): PXE boot servers
type: 42700
139.64.221.227
PXE sub-option 9 (len = 68): Boot menu
type: 42700 Novell Preboot Server -- 139.64.221.227
type: 0 Boot from local devices
PXE sub-option 10 (len = 38): Menu prompt timeout: 2
Press [F8] for a menu of boot servers

Received packet on 0.0.0.0:68
Tossing packet: Packet was not addressed to me
0 Likes
Knowledge Partner
Knowledge Partner

Re: PXE-E77: Bad or missing discovery server list

Popopinsel,
> OK, I raised the log level for PDHCP to 4 and this is the result:
> >


Yes. See the flowchart on p37. In your scenario, both DHCP and PDHCP
answer. Then the client should try to contact PDCHP on 4011. Does it?

--
Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Have an idea for a product enhancement? Please visit:
http://www.novell.com/rms

0 Likes
Knowledge Partner
Knowledge Partner

Re: PXE-E77: Bad or missing discovery server list

Popopinsel,
> > Received packet on 0.0.0.0:68
> > DHCP_OFFER sent to 255.255.255.255:68
> > Received packet on 0.0.0.0:68


OK. So packets are getting through. Then communicatin on port 4011
between WS and PDHCP should commence. Can you get a packet trace from
the WS?

--
Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)

Have an idea for a product enhancement? Please visit:
http://www.novell.com/rms

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.