Novell ZENWORKS LINUX MANAGEMENT 7.3 IR2, Administration Manual

Page: 340 / 684

340 Novell ZENworks 7.3 Linux Management Administration Guide
no
vd
ocx
(e
n)
7 Ja
nua
ry 201
0
Phase 1: Beginning the Process
Depending on whether novell-proxydhcp is configured on the same server as the standard DHCP
server or on a different server, the imaging process begins differently. The following sections
illustrate how the process begins for each configuration, then the phases illustrated in
“Phases 2
through 8: Continuing the Process” on page 342 are the same for them.
Š “Standard DHCP and Novell Proxy DHCP Configured on Separate Servers” on page 340
Š
“Standard DHCP and Novell Proxy DHCP Configured on the Same Server: Part A” on
page 340
Š
“Standard DHCP and Novell Proxy DHCP Configured on the Same Server: Part B” on
page 341
Standard DHCP and Novell Proxy DHCP Configured on Separate Servers
For this example, the DHCP server and the Preboot Services imaging server are two separate servers
on the network.
Figure 28-1
DHCP Configuration on Separate Servers
Processes:
1. When the device boots, the PXE BIOS issues a DHCP request with PXE extensions. The
request is broadcast on port 67.
2. The DHCP server responds with IP configuration information on port 68, and the Proxy DHCP
server responds on port 68 with the name of the bootstrap program (
nvlnbp.sys
) and the IP
address of the TFTP daemon where it can be found.
3. Continue with “Phases 2 through 8: Continuing the Process” on page 342 .
Standard DHCP and Novell Proxy DHCP Configured on the Same Server: Part A
For this example, the DHCP server and the Preboot Services imaging server are configured on the
same server on the network. See
“Standard DHCP and Novell Proxy DHCP Configured on the Same
Server: Part B” on page 341 for the second part of this example.
2
Imaging
Server
PXE Device
novell-proxydhcp
novell-tftp
novell-pbserv
PXE
BIOS
Data
Model
nvlnbp.sys
2
1
DHCP
Request
Network
DHCP
novell-zmgprebootpolicy
port
67
port
68
port
68
IP Configuration