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

A: 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
=============================================================================
==
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: