rbootd - remote boot server for RMP clients
/usr/sbin/rbootd [-a] [-l loglevel] [-L logfile] [-t minutes] [landevs]
rbootd services initial boot-up requests from RMP clients over a local
area network. Early s700 workstations and all Datacommunications and
Terminal Controllers (DTC/9000) use this RMP protocol and can only
communicate with rbootd during boot-up. Later s700 workstations
(starting with the s712) use the industry standard BOOTP protocol and
communicate with bootpd(1M). Future s700 workstations will use the
BOOTP protocol. See the listings below.
rbootd now acts as a forwarding agent for s700 RMP clients, receiving
their RMP boot requests and reformulating them into BOOTP boot
requests that are sent to the local bootpd daemon. If bootpd replies
to this boot request, rbootd receives the BOOTP reply and produces an
RMP reply which is sent to the client. rbootd continues to act as the
intermediary in this transaction until the client is successfully
rbootd only responds to DTC clients if they are listed in the map802
file. The map802 file (a binary file) is created when a DTC is
configured by dtcconfig(1M) on the host machine.
In order to boot a s700 RMP client run rbootd and bootpd on the server
machine, on the same subnet as the client. If the local bootpd daemon
is acting as a relay agent, there must also be a remote NFS Diskless
server with the necessary boot files and NFS or tftp access to those
rbootd supports the following options:
-a Append to the rbootd log file. By default,
starting up rbootd truncates the log file.
-l loglevel Set the amount of information that will be logged
in the log file. rbootd supports the following
0 Log only rbootd startup and termination
1 Log all errors. This is the default
2 Log rejected boot requests from machines
not found in /etc/bootptab or
Hewlett-Packard Company - 1 - HP-UX Release 11i: November 2000
3 Log all boot requests.
-L logfile Specify an alternate file that rbootd should use to
log status and error messages.
-t minutes Grace period before removing inactive temporary
files. Meaningful only in the tftp-remote
configuration. Default is 10 minutes.
landevs Specify the only devices that rbootd should use to
listen for boot requests. The default is all LAN
devices. The device names must be of the form lan0
or lan1 etc, where the device name matches what is
reported by lanscan
Beginning with HP-UX 10.0 rbootd has the following behavior:
+ bootpd/bootptab Dependency :
rbootd now relies on bootpd(1M) to verify the identity of cluster
clients and locate the bootable images (from /etc/bootptab). RMP
clients are thus administered in exactly the same way as new BOOTP
clients. The old methods for administering RMP clients
(/etc/clusterconf, context-dependent files, /usr/boot/*) are
obsolete and no longer work.
See bootpd(1M) and sam(1M) for details on configuring cluster
It is necessary to have the bootpd daemon running on the same
machine as the rbootd daemon.
To aid the system administrator, rbootd now discovers working
ethernet interfaces at startup time and monitors them for boot
requests. Alternatively, the system administrator may put a list of
up to ten ethernet devices on the command line. Putting device
names on the command line means "monitor these devices ONLY". If
device names are included on the command line, they must be
ethernet interfaces (not X.25, token-ring, etc) and they must be up
and running at the time rbootd is started. See lanscan(1M) and
ifconfig(1M) to determine the state of system devices. Attempting
to have rbootd monitor non-ethernet devices will not succeed. The
device names must always be of the form lan0 or lan1 etc, where the
device name matches what is reported by lanscan.
+ Multiple LAN Coverage :
Hewlett-Packard Company - 2 - HP-UX Release 11i: November 2000
rbootd can monitor up to 10 lan devices (depending on hardware) and
can boot clients from all of them. Clients are still restricted to
booting from their own builtin lan devices.
+ Gateway Booting :
RMP clients can now be booted from servers that are not on the same
subnet as the client. The RMP boot requests and replies cannot
cross gateways, but the repackaged BOOTP requests and replies can.
The BOOTP requests and replies are relayed across gateways by
bootpd. This is known as the remote configuration.
rbootd uses the NFS or tftp mechanism to transfer the necessary
files from the remote server to the rbootd machine, and then
transfers the bootable images to the client in a succession of RMP
packets. Thus the remote server must make the necessary files
accessible by NFS or tftp.
In the remote-tftp case, the boot files are temporarily stored in
/var/rbootd/C0809*, and are removed after a period of inactivity,
controlled by the -t option. The default is 10 minutes.
+ S800 Servers :
S800 machines can now be used as cluster servers, booting s700
clients and DTCs. S800 machines are not supported as cluster
+ Network Install :
rbootd now forwards install requests to instl_bootd(1M). If there
is no appropriate response, rbootd will deny the request.
+ S300/400 Not Supported :
S300/400 machines are not supported as diskless clients.
+ Performance Recommendations :
Boot from a local server for the fastest boot times. Run the
rbootd daemon and the bootpd server daemon on the same machine, and
avoid transferring the boot files by NFS or tftp. This is strongly
If booting from remote bootpd servers (across gateways), use NFS
mounts to make the boot files available to the rbootd server. See
mount(1M) for more information. The system administrator can
configure local and remote diskless clients in any mix, but it is
strongly recommended that the number of remote diskless clients be
Hewlett-Packard Company - 3 - HP-UX Release 11i: November 2000
If booting from remote servers using the tftp method, there must
also be temporary file space available on the rbootd server
machine. Generally 6-8 MBytes per diskless client must be
available under /var, but this number could be larger when booting
customized kernels. These temporary files are removed
automatically after some period of inactivity, controlled by the -t
option. The default is 10 minutes.
+ RMP/BOOTP :
The RMP clients are the older s700 workstations and all DTCs:
workstations: 705, 710, 715/33, 715/50, 715/75, 720, 725/50,
725/75, 730, 735, 750, 755
The BOOTP clients are the s712, s715/64, s715/100, B-Class, C-
Class, D-Class and future workstations.
It is necessary to stop rbootd before running bootpquery because they
use the same reserved port (67/udp).
The rbootd daemon binds to port 1067 for cold-install clients through
instl_bootd. Because this is not a reserved port, sometimes rbootd
will be unable to start when another process is holding this port. Use
netstat -an to find the other process and kill it. Rebooting is also
rbootd was developed by HP.
/var/adm/rbootd.log Default rbootd log file.
/etc/boottab Bootstrap configuration file.
/etc/opt/dtcmgr/map802 DTC/9000 configuration file.
/var/rbootd/C0809* Temporary boot files.
bootpd(1M), instl_bootd(1M), tftpd(1M), mount(1M), sam(1M),
dcnodes(1), dtcconfig(1M), dtcnmd(1M), dtcnmp(1M).
Hewlett-Packard Company - 4 - HP-UX Release 11i: November 2000