Ignite-UX Frequently Asked Questions

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
===============================================================================
6.5
Q: The bootsys command fails due to insufficient space in the /stand volume.
Why?
A: The bootsys commands needs to copy the two files:
# /opt/ignite/boot/Rel_<release>/*INSTALL
# /opt/ignite/boot/Rel_<release>/*INSTALLFS
where <release> is the operating system release, from the server into
the client's /stand directory. This error indicates that there is
not enough space in /stand on the client. To correct the error, you
may need to remove any backup kernels. Additionally, check for
kernels in the /stand/build directory (like vmunix_test).
===============================================================================
6.6
Q: Can I have the Ignite-UX server and client on different subnets?
A: 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, refer to 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, 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.