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)
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 :
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 pack-
ets. 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 clients.
• 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
recommended.
If booting from remote
bootpd servers (across gateways), use NFS mounts to make the boot files avail-
able 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 minimized.
If booting from remote servers using the tftp method, there must also be temporary file space avail-
able 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.
WARNINGS
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 an option.
AUTHOR
rbootd was developed by HP.
Section 1M−−686 − 2 − HP-UX Release 11i: December 2000
___
___