Managing Systems and Workgroups: A Guide for HP-UX System Administrators

Setting Up and Administering an HP-UX NFS Diskless Cluster
NFS Diskless Questions and Answers
Chapter 10 937
As the system administrator, you can create other shared roots with any
name you choose, although HP recommends certain name elements:
architecture, application vs. OS, release level. You can create these
directories “by hand”, and they are also created by swinstall when you
perform an alternate root install.
An alternate root install populates a shared root with sharing points (i.e.
products). See swinstall (1M) for details.
Question: My client won’t boot. What could be wrong?
Answer: If the client is not booting because the server simply does not respond to
the client, the problem may be:
• The client’s bootptab record may be incorrect or missing.
Check the /etc/bootptab file to make sure that the client’s
hardware address is specified correctly.
• The bootp daemon is incorrectly configured.
See “Boot Service Setup” in section 4 of the NFS Diskless Concepts
and Administration White Paper, supplied in
/usr/share/doc/NFSD_Concepts_Admin.ps on most 10.x systems.
• rbootd daemon not running.
If the client has RMP-protocol boot ROMs, check to see if rbootd is
running on the server. If it is not, start it and confirm that the
RBOOTD_START parameter in /etc/rc.config.d is set to 1.
NOTE You may need to restart rbootd after configuring a new LAN card.
• The /export/tftpboot/ client /stand/uxbootlf file is missing.
This is the file that is specified in the bf field in the client’s bootptab
record. If it is missing, bootpd will not respond to the client.
Fix: copy /usr/lib/uxbootlf to
/export/tftpboot/ client /stand/uxbootlf.
If the client is able to transfer its boot files, but fails at a later point, the
problem may be with file system exports from the server. Check the
client’s /etc/fstab (/export/private_roots/ client /etc/fstab on
the server) against the file system exports on the server.