Software Distributor debugging can be enabled on a per-session basis without modifying the Ignite-UX server configuration files. From the initial Ignite-UX menu on the client, select Advanced Options then Edit config file. This invokes vi and you can add, for example:

env_vars += "SDU_DEBUG_RPC=1"

sd_command_line += "-x logdetail=true -x loglevel=2"

Additionally, these configuration statements can be added to the Ignite-UX server configuration file /var/opt/ignite/config.local if debug output is wanted for multiple clients or for multiple installation sessions and avoids adding them interactively each time.

Booting errors on PA-RISC systems

Error:IPL error: bad LIF magic

Possible problems are:

•The tftp service does not have 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, correct the inetd.conf file and run inetd -c. Kill any tftpd processes that may be running. Installing Ignite-UX must set up inetd.conf. The tftp service can also be configured using SMH or SAM.

•Using a bootptab entry for the client that is referencing a nonexistent boot file (bf).

•A corrupted /opt/ignite/boot/boot_lif file.

Booting error on Itanium-based systems when using /etc/bootptab

Error:PXE-E16: Valid PXE offer not received.

Exit status code: Invalid Parameter

When using /etc/bootptab to define Ignite-UX boot services, a number of problems can be introduced resulting in this error. The following checklist can be used to isolate the problem:

1.Check inetd:

—Check /etc/inetd.conf to make certain bootps and tftp entries have been uncommented. Make certain the tftp line contains /opt/ignite and /var/opt/ ignite paths.

—Signal inetd to reread the configuration files (inetd -c) after the files are edited. If the inetd process is not running, start it using:

/sbin/init.d/inetd start

—Check /var/adm/syslog/syslog.log to make certain inetd was restarted and no bad messages are found. Specifically check for messages from bootpd and tftpd.

—Check for entries in /var/adm/inetd.sec that may cause inetd to deny service to certain clients.

2.Check bootpd:

—Check the /etc/bootptab entry. Make certain the MAC address matches the client MAC address. Use dhcptools -vto validate the format of the /etc/bootptab file.

—Check for entries in /etc/dhcpdeny to ensure that bootpd is not set 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.

If packets were not received, use a tool such as tcpdump to check for network packets. Verify that bootp packets are being seen by the system. If you do not have tcpdump on your system, you can download it for either HP-UX 11i v1 or HP-UX 11i v2 from the HP Internet Express Website at

230 Troubleshooting