Ignite-UX (IUX) Frequently Asked Questions (July 2013)

http://docs.hp.com/en/IUX/infolib.html
- Use the bootsys command from the Ignite-UX server to initiate the
installation of the client. The bootsys command copies the
*INSTALL and *INSTALLFS files to the client's local disks and
instructs it to boot from them. This option avoids the need to do
a network boot.
- Create a minimal bootable tape or CD to boot from, and then point
the client to the Ignite-UX server once it is booted. For more
information, refer to make_medialif(1M).
- On HP Integrity servers use direct boot profiles (if your system
supports them) and directly contact a remote Ignite server without
needing a boot helper.
=============================================================================
==
6.7
Q: My Itanium-based client fails to boot with a PXE-E16 error. Why?
A: A "PXE-E16: Valid PXE offer not received" error indicates that the
client did not receive a valid message from either a BOOTP or DHCP
server.
Itanium-based clients differ from PA-RISC clients because the
Ignite-UX instl_bootd boot protocol server can not be used. The
"Configure Booting IP Addresses" button on the "Server Configuration"
tab of the Ignite-UX GUI and the /etc/opt/ignite/instl_boottab file
do not apply to Itanium 2-based clients.
Instead, a BOOTP/DHCP server such as HP-UX bootpd must be configured
and /etc/bootptab entries made for each client. If this Ignite-UX
server has been configured and the client still does not boot, the
following is a checklist of items to verify:
Check inetd for the following:
___ Check /etc/inetd.conf to make certain bootps and tftp entries have
been uncommented.
___ Was inetd restarted or given an option to re-read the configuration
files (inetd -c), after they were edited? Is the inetd process
running?
___ Check for entries in /var/adm/inetd.sec that may cause inetd to deny
service to certain clients.
___ Check /var/adm/syslog/syslog.log to make certain inetd was
restarted,
and that no bad messages were found. Check for messages from bootpd
and tftpd.
Check bootpd for the following:
___ Check the /etc/bootptab entry. Make certain the MAC address matches