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

Itanium-based clients differ from PA-RISC clients because the Ignite-UX instl_bootd boot protocol
server cannot 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.
Instead, a BOOTP/DHCP server such as HP-UX bootpd must be configured and /etc/bootptab
entries made for each client. If this Ignite-UX server has been configured and the client still does
not boot, the following is a checklist of items to verify:
Check inetd for the following:
• Check /etc/inetd.conf to make certain bootps and tftp entries have
been uncommented.
• Was inetd restarted or given an option to re-read the configuration files (inetd
-c), after they were edited? Is the inetd process running?
• Check for entries in /var/adm/inetd.sec that might cause inetd to deny
service to certain clients.
• Check /var/adm/syslog/syslog.log to make certain inetd was
restarted, and no error messages were displayed. Check for messages from
bootpd and tftpd.
Check bootpd for the following:
• Check the /etc/bootptab entry. Make certain the MAC address matches
the client MAC address. Use dhcptools -v to validate the format of the
/etc/bootptab file.
• Check for entries in /etc/dhcpdeny to ensure that bootpd is not set up to
deny service for particular clients.
• Check /var/adm/syslog/syslog.log for a message from bootpd that
indicates it was started when a bootpd packet was received.
Check tftpd for the following:
• Check the tftp line in /etc/inetd.conf to make certain /opt/ignite
and /var/opt/ignite directories are listed.
• Check the tftpd connection manually by using the tftp command; for
example:
prompt% tftp [server-name]
tftp> get /opt/ignite/boot/nbp.efi /tmp/nbp.efi Received n
bytes in s seconds
> quit
Does Ignite-UX Support APA (auto-port aggregation)?
Yes. From March 2011 release onwards Ignite-UX supports recovery of a system with APA
configured on HP-UX 11i v3 OS.
Ignite-UX does not support the following activities on systems with aggregate LAN interfaces:
1. Configuring or changing network information associated with aggregate links during a recovery
(nor can they be configured in during a cold install using either SD depots or golden images).
Cloning systems using recovery archives that contain definitions for aggregate LAN interfaces.
2. Cold installing from a golden image containing definitions for aggregate LAN interfaces.
Frequently asked questions 33