Installing and Administering Internet Services

Chapter 5 169
Configuring TFTP and BOOTP Servers
Booting RMP Clients
Booting RMP Clients
Remote Maintenance Protocol (RMP) is an HP-proprietary boot and file
transfer protocol used in early Series 700 workstations and in the
Datacommunications and Terminal Controllers (DTC/9000). The rbootd
daemon allows BOOTP servers to serve clients that use RMP. rbootd
must be run on a BOOTP server on the same subnet as the RMP client.
That is, both rbootd and bootpd must run on the same system.
The rbootd daemon translates RMP bootrequests into a BOOTP
bootrequest using the client’s hardware address. rbootd then forwards
the bootrequest to bootpd. bootpd can send a bootreply back to rbootd
if it finds the client’s boot information in its database. Or, it can relay the
bootrequest to other BOOTP servers if it has relay information for the
client in its database. rbootd translates the BOOTP bootreply back to
RMP and sends it to the client.
Figure 5-2 shows an example of an RMP bootrequest that is sent to
rbootd, which then forwards a BOOTP bootrequest for the client to
bootpd. bootpd finds the client’s boot information in its database and
sends a BOOTP bootreply back to rbootd. rbootd then sends an RMP
bootreply to the client.
Figure 5-2 BOOTP Server for RMP Client
As mentioned previously, the BOOTP bootrequest can be relayed to other
BOOTP servers. A BOOTP bootreply is sent back to the original bootpd
daemon, which then sends the bootreply back to the rbootd daemon on
RMP
Client
Boot Server
rbootd
bootpd
1
RMP bootrequest
RMP bootreply
BOOTP
bootrequest
BOOTP
bootreply
2
3
4