HP-UX HB v13.00 Ch-06 - Ignite-UX

HP-UX Handbook – Rev 13.00 Page 20 (of 58)
Chapter 06 Ignite-UX
October 29, 2013
ux.html?jumpid=reg_R1002_USEN, chapter "Required Patches" in the latest
Release Notes at http://www.software.hp.com/products/IUX/docs.html.
 The most problematic when installing from network is permission and network
protocol errors. Before installing the client, you should check tftp, inet, NFS, etc.
The /var/adm/syslog/syslog.log can be very useful troubleshooting this issue.
Check the /etc/dfs/dfstab or /etc/exportfs and /etc/inetd.conf for correct
settings. Often the nfs export file states anon=-2 instead of -anon=2
 When changing config files, they should always be verified with:
# /opt/ignite/bin/instl_adm –T
 Also check the ignite server network settings with:
# /opt/ignite/bin/instl_adm –d
 When creating a Golden System Image, make sure that the source system does not
have the LLA (MAC address) of the network interface set explicitly. Otherwise, the
same LLA will be used by the cloned target system. The LLA is set in the section
HP_BASE100_STATION_ADDRESS in /etc/rc.config.d/hpbase100conf.
 If an installation via boot_sys fails or accidentally booted a client:
o Stop the boot process and boot into Single User Mode:
BOOT ADMIN> boot pri isl -> Interact with IPL? -> n
o Boot the hpux kernel:
ISL> hpux (;0)/stand/vmunix
o Correct the AUTO file
# /usr/sbin/mkboot –a "hpux" /dev/rdsk/c0t1d0
o If the old HP-UX system has already been overwritten via Ignite-UX, boot the
system over the network.
 If problems are encountered booting from a boot server, try the following (for PA-
RISC):
BOOT ADMIN> boot lan INSTALL -> Interact with IPL? -> y
 In this matter it can be seen which server wrongly answers the boot request.
Alternatively run:
# /usr/bin/tail /var/adm/syslog/syslog.log