Ignite-UX (IUX) Document for Frequently Asked Questions (FAQ) (762793-001, March 2014) (Edition: 3)

When executing search lan install on the client, the Ignite-UX server does not
appear in the list. Why?
Check the following on the Ignite-UX server that you are trying to boot from are:
• Messages from instl_bootd in /var/adm/syslog/syslog.log. If you need to add
more IP addresses to /etc/opt/ignite/instl_boottab, messages are written to
syslog.log similar to the following:
instl_bootd: Denying boot request for host: 080009F252B3 to
avoid IP address collision. Try booting again in 214 seconds,
or add more IP addresses to /etc/opt/ignite
• A message in syslog.log that indicates that you have no IP addresses in /etc/opt/
ignite/instl_boottab similar to the following:
instl_bootd: No available IP address found in:
/etc/opt/ignite/instl_boottab
The bootsys command fails due to insufficient space in the /stand volume. Why?
The bootsys command needs to copy the two files:
# /opt/ignite/boot/Rel_<release>/*INSTALL
# /opt/ignite/boot/Rel_<release>/*INSTALLFS
In the above files, <release> is the operating system release, from the server into the client's /stand
directory. This error indicates that there is no enough space in /stand on the client. To correct the
error, you might need to remove any backup kernels. Additionally, check for kernels in the /stand/
build directory (like vmunix_test).
Can I have the Ignite-UX server and client on different subnets?
Yes. It requires that you setup a boot-helper on the remote subnets, or limit yourself to using the
bootsys command.
Because the network boot firmware uses a broadcast BOOTP packet to find an Ignite-UX server to
boot from, these packets do not normally cross over subnets. This limits clients to booting from
Ignite-UX servers only on their local subnet.
When your Ignite-UX server is on a remote subnet, you have basically three options:
• Set up a boot helper system on the client's subnet that has the IUX.MinimumRuntime product
installed. This boot-helper system provides the client with the ability to boot the INSTALL kernel,
and then contact the server once it is booted. For more information, see Appendix B in the
Ignite-UX Administration Guide at 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, see 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.
My Itanium-based client fails to boot with a PXE-E16 error. Why?
The error message PXE-E16: Valid PXE offer not received indicates that the client did
not receive a valid message from either a BOOTP or DHCP server.
32 Network installation