Ignite-UX Frequently Asked Questions

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 may cause inetd to deny
service to certain clients.
___ Check /var/adm/syslog/syslog.log to make certain inetd was restarted,
and that no bad messages were found. 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 insure 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
===============================================================================
6.8
Q: Does Ignite-UX Support Auto-Port Aggregation (APA)?
A. Yes, from March 2011 release onwards Ignite-UX supports recovery of a system with Auto-Port
Aggregation (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).
2. Cloning systems using recovery archives that contain definitions for aggregate LAN interfaces
3. Cold installing from a golden image containing definitions for aggregate LAN interfaces
4. When network booting a system any network information gained by DHCP must provide the hostname
of the system,
not doing so will lead to errors during the recovery if a system has aggregrate LAN interfaces
defined on HP-UX 11i v1 or v2.
5. Changing the hostname during a recovery on a system that has aggregate lan interfaces
defined on HP-UX 11i v1 or v2. Doing so will lead to errors during a recovery.
For more details on APA, please refer admin guide chapter-15 under section "Verifying Recovery
Image Results".
===============================================================================
6.9
Q: Does Ignite-UX Support IPv6?
A: No. Ignite-UX does not currently support installation over IPv6.
===============================================================================
----------------------------------------
7. Media Installation
----------------------------------------