D.7 Imaging Server

The imaging server is a software component of the Linux Management server. It enables imaging clients to connect with the network to receive imaging services, including:

Use the imaging server software to do the following:

D.7.1 Initiating the Imaging Processes

An imaging server daemon is initiated by running the script at the Linux terminal program command line, which in turn calls the executable and uses the configuration set in the corresponding .conf file. Because the scripts do not normally accept parameters, but only arguments (such as start), you can configure parameters in their corresponding .conf files.

The following Linux daemons run the imaging server processes:

novell-pbserv

The novell-pbserv daemon provides imaging services to devices.

This daemon is started automatically when installing ZENworks Linux Management, or when rebooting the server.

Understanding the novell-pbserv Components

To initiate the novell-pbserv daemon, enter the following command on the Linux command line in a terminal program:

/etc/init.d/novell-pbserv

Table D-5 lists the arguments for this command, the executable it starts, and the configuration file it uses:

Table D-5 Novell-pbserv Command Details

Script Arguments:

start, stop, restart, force-reload, status, showpid (for descriptions of these arguments, see Understanding Script Arguments)

Executable:

/opt/novell/zenworks/preboot/bin/novell-pbservd

Configuration File:

/etc/opt/novell/zenworks/preboot/novell-pbserv.conf

Configuring novell-pbserv

The novell-pbserv configuration file (novell-pbserv.conf), contains the following parameters:

Table D-6 Novell-pbserv Parameters

Parameter

Description

EnableLogging=YES

If YES, a log file is created for debug messages. This is the default.

If NO, no log file is created for debug messages.

The novell-pbserv.log file is created in the /var/opt/novell/log/zenworks/preboot directory.

IPAddress=

The IP address to be used by imaging for all communications. If nothing is entered, novell-pbserv attempts to detect an IP address.

Can be used in a clustering environment to specify the IP address of the virtual server.

Can also be used in a multiple-NIC environment to bind the imaging server to a specific IP address.

By default, this is commented out.

LIBRARY_NAME=

Full path of the library to be loaded by the ZENWorks Imaging Service. If the library name is not specified, then by default libzenimgweb.so is loaded from the /opt/novell/zenworks/preboot/lib directory.

By default, this is commented out.

novell-proxydhcp

The novell-proxydhcp daemon provides PXE devices with the information that they require to be able to connect to the ZENworks Preboot Services system.

This daemon is not started automatically when installing ZENworks Linux Management.

Understanding the novell-proxydhcp Components

To initiate the novell-proxydhcp daemon, enter the following command listed for Script Location on the Linux command line in a terminal program:

/etc/init.d/novell-proxydhcp

Table D-7 lists the arguments for this command, the executable it starts, and the configuration file it uses:

Table D-7 Novell-proxydhcp Command Details

Script Arguments:

start, stop, restart, force-reload, status, showpid, install (for descriptions of these arguments, see Understanding Script Arguments)

Executable:

/opt/novell/bin/novell-proxydhcpd

Configuration File:

/etc/opt/novell/novell-proxydhcp.conf

Configuring novell-proxydhcp

The novell-proxydhcp configuration file (novell-proxydhcp.conf), contains the following parameters:

Table D-8 Novell-proxydhcp Parameters

Parameter

Description

LocalDHCPFlag = 0

Indicates whether the DHCP server for this subnet resides on the same server as novell-proxydhcp.

0 (the default) means novell-proxydhcp is not running on the same server as the DHCP service. 1 means they are running on the same server.

The Proxy DHCP server needs to behave slightly differently if it is loaded on the same server as the DHCP service.

LocalInterface = 10.0.0.1

Indicates the IP address to be used by the Proxy DHCP server. This setting is intended only for use on servers with multiple LAN interfaces. The IP address must be valid on the server.

By default, this parameter is commented out.

NovellPolicyEngine = 10.0.0.1

The IP address of the server where a Novell Preboot policy engine is running. Most often, this is a ZENworks imaging daemon. If no value is specified, the Proxy DHCP assumes that the daemon is running on the same server.

By default, this parameter is commented out.

NBPx86 = nvlnbp.sys

The name of the boot file this service will suggest for all x86 computers, such as nvlnbp.sys.

MenuTimeout = 2

The number of seconds the F8 menu is displayed before automatically choosing the first option, which is always this server and its default NBP. The default is 2 seconds.

ProxyLogLevel = 2

The value assigned here determines which events are entered in novell-proxydhcp.log. Specifying a high level in an active system can quickly fill the log. Valid values are: 0, 1, 2, 3, and 4. The default is 2.

Each message from the Proxy DHCP server is assigned a priority level. If ProxyLogLevel is set to a value equal to or greater than a message’s priority level, that message is entered in novell-proxydhcp.log. All other messages are ignored.

Priority meaning:

0: Critical information. Service start, stop, and critical events are logged.

1: Warning information. Additionally, warning information is logged.

2: Transaction information. All completed client transactions are logged.

3: Request information. All client requests and Proxy DHCP requests received are logged, including ignored requests. If a request is ignored, the reason for ignoring it is also logged.

4: Debugging information. All DHCP packets received and accepted are decoded and logged.

ProxyLogFile = /var/opt/novell/log/novell-proxydhcp.log

The file where all log file entries are placed. It is located at /var/opt/novell/log/novell-proxydhcp.log.

By default, this parameter is commented out.

ProxyLogFileSize = 15

The size of the ProxyLogFile file is controlled by the value of ProxyLogFileSize, where 15 is the default (in MB).

When the log file exceeds the ProxyLogFileSize value, it is deleted and restarted.

Parameters that are not commented out, but contain no values, are given a default value.

The novell-proxydhcp daemon is compliant with the following RFCs:

  •    RFC 2131 - Dynamic Host Configuration Protocol
  •    RFC 2132 - DHCP Options and BOOTP Vendor Extensions

The novell-proxydhcp daemon is compliant with the Preboot eXecution Environment (PXE) Specification v2.1 industry specification, published by Intel.

novell-tftp

The novell-tftp daemon provides TFTP services to imaging clients.

This daemon is started automatically when installing ZENworks Linux Management, or when rebooting the server.

Understanding the novell-tftp Components

To initiate the novell-tftp daemon, enter the following command (listed under Script Location) on the Linux command line in a terminal program:

/etc/init.d/novell-tftp

Table D-9 lists the arguments for this command, the executable it starts, and the configuration file it uses:

Table D-9 Novell-tftp Command Details

Script Arguments:

start, stop, restart, force-reload, status, showpid (for descriptions of these arguments, see Understanding Script Arguments)

Executable:

/opt/novell/bin/novell-tftpd

Configuration File:

/etc/opt/novell/novell-tftp.conf

Configuring novell-tftp

The novell-tftp configuration file (novell-tftp.conf), contains the following parameters for the Novell TFTP server:

Table D-10 Novell-tftp Parameters

Parameter

Description

TFTPInterface = 10.0.0.1

The IP address that is used for all TFTP communications. If a value is not given here, the service tries to detect one.

This value is most useful for multihomed servers.

By default, this parameter is commented out.

TransferBlockSize = 1428

This value determines the size of the data block used by the TFTP server to transmit and receive data to and from a client. Valid values are between 512 and 4428.

For ethernet networks, this value should be 1428.

For token ring networks, this value can be 4428, but only if you are sure there are no ethernet segments; otherwise, use 1428.

Older TFTP clients might be restricted to 512 bytes, the original transfer block size before the adoption of RFC 2348. The Novell TFTP server is compatible with these clients.

By default, this parameter is commented out.

TimeoutInterval = 1

This is the amount of time (in seconds) that the TFTP server waits for a client to acknowledge before resending a packet. However, because the TFTP server uses an adaptive algorithm to calculate the actual timeout interval, this value is only used as an initial value. It may increase or decrease, depending on the performance of the network.

This value is only a default. It can be changed at the request of a client. See RFC 2349.

Valid values are 1 through 60.

By default, this parameter is commented out.

Linux -- TFTPDirectory = /srv/tftp

TFTPDirectory is the directory where the TFTP server can store and retrieve files. All paths submitted to the TFTP server by clients are assumed to be relative to this directory.

Because TFTP has no security, it is suggested that you not place files with sensitive information in this directory, and that you place a space quota on it.

The TFTP server does not load if this directory does not exist.

By default, this parameter is commented out.

TFTPAllowWrites = 0

This tells the TFTP server whether to allow users to place new files on the server. Setting this variable to 0 (the default) makes the TFTP server more secure by not allowing users to place new files on the server. The other option is 1, which allows users to place new files on the server.

AllowOverwrites = 0

This tells the TFTP server whether to allow users to overwrite existing files on the server. Setting this variable to 0 (the default) makes the TFTP server more secure by not allowing users to overwrite files on the server. The other option is 1, which allows users to overwrite files on the server.

TFTPAllowWrites must be set to 1 in order for the AllowOverwrites parameter to be recognized.

TFTPLogLevel = 2

The value assigned here determines which events are entered in novell-tftp.log. Specifying a high level in an active system can quickly fill the log. Valid values are: 0, 1, 2, 3, and 4. The default is 2.

Each message from the TFTP server is assigned a priority level. If TFTPLogLevel is set to a value equal to or greater than a message’s priority level, that message is entered in novell-tftp.log. All other messages are ignored.

Priority meaning:

0: Critical information. Service start, stop, and critical events are logged.

1: Warning information. Only failed client transactions are logged.

2: Transaction information. All completed client transactions are logged.

3: Request information. All client requests and TFTP options are logged.

4: Debugging information. All server events, including each packet received, are logged.

By default, this parameter is commented out.

TFTPLogFile = /var/opt/novell/log/novell-tftp.log

The file where all log file entries are placed.

By default, this parameter is commented out.

TFTPLogFileSize = 15

The size of the log file is controlled by the value of TFTPLogFileSize, where 15 is the default (in MB).

When the log file exceeds the TFTPLogFileSize value, it is deleted and restarted.

By default, this parameter is commented out.

Parameters that are not commented out, but contain no values, are given a default value.

The novell-tftp daemon is compliant with the following RFCs:

  •    RFC 1350 -- THE TFTP PROTOCOL (REVISION2)
  •    RFC 2347 - TFTP Option Extension
  •    RFC 2348 - TFTP Blocksize Option
  •    RFC 2349 - TFTP Timeout Interval and Transfer Size Options

novell-zmgprebootpolicy

The novell-zmgprebootpolicy daemon allows PXE devices to query the ZENworks Linux Management system for work to do and for Preboot Menu policies.

This daemon is started automatically when installing ZENworks Linux Management, or when rebooting the server.

Understanding the novell-zmgprebootpolicy Components

To initiate the novell-zmgprebootpolicy daemon, enter the following command (listed under Script Location) on the Linux command line in a terminal program:

/etc/init.d/novell-zmgprebootpolicy

Table D-11 lists the arguments for this command, the executable it starts, and the configuration file it uses:

Table D-11 Novell-zmgprebootpolicy Command Details

Script Arguments:

start, stop, restart, force-reload, status, showpid (for descriptions of these arguments, see Understanding Script Arguments)

Executable:

/opt/novell/zenworks/preboot/bin/novell-zmgprebootpolicyd

Configuration File:

/etc/opt/novell/zenworks/preboot/novell-zmgprebootpolicy.conf

Configuring novell-zmgprebootpolicy

The novell-zmgprebootpolicy configuration file (novell-zmgprebootpolicy.conf), contains the following parameters:

Table D-12 Novell-zmgprebootpolicy Parameters

Parameter

Description

LocalInterface = 10.0.0.1

The IP address that is used by the Policy server.

This setting is intended only for use on servers with multiple LAN interfaces. The address must be valid on the server.

By default, this parameter is commented out.

PolicyLogLevel = 1

The value assigned here determines which events are entered in novell-zenprebootpolicy.log. Specifying a high level in an active system can quickly fill the log. Valid values are: 0, 1, 2, 3, and 4. The default is 2.

Each message from the novell-zmgprebootpolicy server is assigned a priority level. If PolicyLogLevel is set to a value equal to or greater than a message’s priority level, that message is entered in novell-zenprebootpolicy.log. All other messages are ignored.

Priority meaning:

0: Critical information. Service start, stop, and critical events are logged.

1: Warning information. Only failed client transactions are logged.

2: Transaction information. All completed client transactions are logged.

3: Request information. All client requests are logged.

4: Debugging information. All server events, including each packet received, are logged.

By default, this parameter is commented out.

PolicyLogFile = /var/opt/novell/log/zenworks/preboot/novell-zenprebootpolicy.log

The file where all log file entries are placed.

By default, this parameter is commented out.

PolicyLogFileSize = 15

The size of the log file is controlled by the value of PolicyLogFileSize, where 15 is the default (in MB).

When the log file exceeds the PolicyLogFileSize value, it is deleted and restarted.

PrebootServer = 10.0.0.5

This field contains the address of the imaging server that should be used to resolve policies.

By default, this parameter is commented out.

EnableAMTSupport = Yes

This feature is not currently supported in Novell ZENworks Linux Management.

This field enables or disables support for Intel’s AMT technology.

By default, this support is disabled by commenting out the parameter.

Parameters that are not commented out, but contain no values, are given a default value.

Understanding Script Arguments

The following arguments are available for each of the Preboot Services daemons described above:

Table D-13 Script Arguments

Argument

Function

start

Starts the daemon.

Because novell-proxydhcp is optional, use this argument to start this daemon. However, this daemon does not automatically start when the server reboots. (See install below.)

start setjustimagedflag

For novell-zislnx only, it sets the Just Imaged flag so that a device can be imaged using its existing Image Safe Data.

stop

Stops the daemon.

restart

Stops and restarts the daemon if it is already running.

force-reload

Causes the daemon’s configuration file to be reloaded.

status

Displays the current status of the daemon.

For example, if you enter /etc/inid.d/novell-pbserv status, information similar to the following is returned:

Novell ZENworks Imaging Service running

showpid

Displays the daemon’s process ID.

For example, if you enter /etc/inid.d/novell-pbserv showpid, information similar to the following is returned:

Novell ZENworks Imaging Service running
10211

install

For novell-proxydhcp only, causes the daemon to be automatically loaded when the server boots.

D.7.2 Viewing Information About Imaging Requests

After the imaging server has started, you can view information about the status and results of the imaging requests that it has received from imaging clients. A statistical summary of these requests is shown on the server’s command line. The statistics shown on this screen are explained below. All statistics are reset to zero if you restart the imaging server.

To view the multicast imaging information, at the server’s command line enter:

/opt/novell/zenworks/preboot/bin/novell-zmgcast ‑status

The information in Table D-14 explains what is displayed:

Table D-14 Imaging Request Statistics

Statistic

Specifies

PXE Requests

The number of imaging requests of any kind that have been received by the Imaging Server since it was last started. This includes requests that failed, were denied, or were referred to other Imaging Servers. Information about each of these requests, such as the source, type, date/time, and results, is logged on the Imaging Server.

Images Sent

The number of images that the imaging server has sent to imaging clients since the imaging server was started. This includes only images that were retrieved from this imaging server.

Images Received

The number of new images that have been received and stored on the imaging server since it was started. This includes images that were received through client referrals.

D.7.3 Starting a Manual Multicast Session

At the bash prompt, you can start a manual multicast session, see any sessions in progress, and delete sessions. For more information, see Initiating a Multicast Session from Each Client.