HP-UX Reference (11i v1 00/12) - 1M System Administration Commands N-Z (vol 4)
__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man1m/naaagt.1m
________________________________________________________________
___ ___
r
rbootd(1M) rbootd(1M)
NAME
rbootd - remote boot server for RMP clients
SYNOPSIS
/usr/sbin/rbootd [-a][-l loglevel ][-L logfile ][-t minutes][landevs ]
DESCRIPTION
rbootd services initial boot-up requests from RMP clients over a local area network. Early s700 worksta-
tions 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 refor-
mulating 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
booted.
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 files.
Options
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 logging levels:
0 Log only rbootd startup and termination messages.
1 Log all errors. This is the default logging level.
2 Log rejected boot requests from machines not found in /etc/bootptab
or /etc/opt/dtcmgr/map802
.
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
New Functionality
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 clients.
It is necessary to have the bootpd daemon running on the same machine as the rbootd daemon.
• Auto-Discovery:
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 inter-
faces (not X.25, token-ring, etc) and they must be up and running at the time rbootd
is started. See
HP-UX Release 11i: December 2000 − 1 − Section 1M−−685
___
___