Ignite-UX Frequently Asked Questions

A: Typically, this has been caused by one of the following situations:
- Not having tftp access to /opt/ignite and /var/opt/ignite, the
/etc/inetd.conf file on the server should have an entry similar to:
tftp dgram udp wait root /usr/lbin/tftpd tftpd\
/opt/ignite\
/var/opt/ignite
If not, fix inetd.conf and run "inetd -c". Kill any tftpd
processes that may be running. Installing Ignite-UX should set
inetd.conf.
- Using a tftp entry for the client that is referencing a nonexistent
boot file (bf).
- A corrupted /opt/ignite/boot/boot_lif file.
- Some remnants of the old cold installation product are conflicting
with Ignite-UX. For example, an old instl_bootd is running.
===============================================================================
6.2
Q: I set "control_from_server=true" and "run_ui=false" in the INSTALLFS,
but I still get prompted for information on the client. What is
wrong?
A: Review the following possible answers dependent on the prompt that
you received:
- If the screen is showing the client name in an editable field and a
"Cancel" button at the bottom of the screen, then all is well and
there should be an icon waiting for you in the Ignite-UX server
GUI. The text screen allows you to change the icon name, or switch
to a client-side installation.
- If the screen is showing two or more LAN interfaces to select from,
there was not enough information in the configuration files to tell
it which LAN to use. Once you select a LAN, and then select
"HP-UX" and the installation continues.
- If the screen is prompting you for networking information, then
either DHCP did not respond or there is not an entry in
/etc/bootptab for the client. Enter the network information,
select "Install HP-UX" and continue the installation.
===============================================================================
6.3
Q: The bootsys command seems to work in reverse; if we typed:
# bootsys -w client
the client did not wait for the server, if we typed:
# bootsys client
the client waited for the server. Why?
A: This is probably because you ran through the GUI once on the
Ignite-UX server prior to running the bootsys command. The server
drops the instruction for the client to start installing and the next
time the client boots it uses this dropped instruction. The message
Ignite-UX generates attempts to tell you that the installation will
happen the next time "bootsys -w" is used, but does not indicate that
it happens automatically.
It is likely that the next time you executed a bootsys command, you
had not used the GUI without the client being booted from the
Ignite-UX server.
===============================================================================
6.4
Q: When executing "search lan install" on the client, the Ignite-UX
server does not appear in the list. Why?
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,