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

7 Network installation
Frequently asked questions
Following are the frequently asked questions in installing the network, which is a compilation of
all the available feedback from the users.
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?
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 must 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 installation product are conflicting with Ignite-UX. For example, an
old instl_bootd is running.
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?
Review the following possible answers depending 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 client icon is enabled on 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 regarding which LAN to use. The installation continues,
once you select the required LAN, and click HP-UX.
• 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.
The bootsys command seems to work in reverse; if we entered: # bootsys -w
client the client did not wait for the server, if we entered: # bootsys client
the client waited for the server. Why?
This is probably because you ran through the GUI once on the Ignite-UX server prior to running
the bootsys command. The server pushes the instruction to the client to start installing and the
next time the client boots it uses this pushed instruction. The message Ignite-UX generates, inform
you that the installation will happen the next time bootsys -w is used, but does not indicate that
it happens automatically.
It is possible 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.
Frequently asked questions 31