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

"Insert" key is inactive when entering data in the TUI by pressing
it.
=============================================================================
==
5.11
Q: What HP applications are tested for use with Ignite-UX?
A: HP applications that have been tested with Ignite-UX have an OD1
option on the HP Corporate Product List (CPL), which indicates the
factory integrate option. This option directs HP factories to
install the software on the client before it leaves the factory.
HP manufacturing installs the software from a depot using the
Ignite-UX process.
All HP applications identified with an OD1 ordering
option may be installed from a from a depot.
No applications are tested for proper installation or operation when
included in a golden image that is installed with Ignite-UX.
They might work fine in this mode, but it is up you to verify proper
installation and operation. Running "swconfig -x reconfigure=true
\*" after installation might cause some software to properly configure
itself after installing from a golden image archive.
=============================================================================
==
----------------------------------------
6. Network Installation
----------------------------------------
6.1
Q: When the client searches for bootable devices, the Ignite-UX server
does appear on the list. When I try to boot, I get the error: IPL
error: bad LIF magic. Why?
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.