Ignite-UX Frequently Asked Questions

issues you may encounter please read the latest version of the
Ignite-UX release notes (and search for EVA).
You should note that these issues do NOT affect active/active EVA GL
or any EVA XL disk arrays. These disk arrays are fully supported
for use with Ignite-UX.
===============================================================================
1.12
Q: Why is install.log so difficult to read?
A: The installation messages that are logged into install.log are
obtained by Ignite-UX from multiple sources including the standard
output (stdout) and standard error (stderr of Software Distributor
and the contents of swagent.log. It is not possible to control how
these messages are logged into install.log, thus the file can be
confusing.
If you want to verify the installation of a product, HP recommends
that you examining the swagent.log file directly, rather than the
Ignite-UX install.log file.
===============================================================================
1.13
Q: Why is the message 'Cannot open /dev/vx/rdsk/rootdg/standvol' displayed
during an Itanium-based installation via golden image?
A: It is caused by the major number change between B.11.23 first release
and B.11.23 September 2004 for vxvm volumes. You will see this
message if the golden image was created on a system running B.11.23
first release, and then the golden image is installed using version
'C' of Ignite-UX.
You can move the kernel build a little earlier in the process to
avoid the message, though the message is not harmful.
post_load_cmd += "
unset SW_INITIAL_INSTALL
/usr/sbin/mk_kernel -f -o /stand/vmunix
"
===============================================================================
1.14
Q: Does HP support Ignite-UX through a firewall?
A: HP has not tested Ignite-UX through a firewall.
It should be possible to configure a firewall such that Ignite-UX
functions properly. For more information, see the section on
modifying a Bastille-hardened system for Ignite-UX in the security
chapter of the Ignite-UX Administration Guide available on
http://www.docs.hp.com.
HP does support Ignite-UX in conjunction with Bastille on HP-UX 11i
systems. The Ignite-UX Administration Guide describes how to
configure Bastille on both Ignite-UX servers and clients.
===============================================================================
1.15
Q: What do I do when I get file system full messages during installation
or recovery when '_hp_ignore_sw_impacts' is set to 1?
A: When installing or recovering a system, Ignite-UX takes a small
amount of space (a few MB) in each of the / and /usr file systems to
hold some commands that Ignite-UX will use. Some of these commands
are used during the installation or recovery of HP-UX, and some are
used after the first reboot.
If the / or /usr file systems are nearly full when creating a golden
image (and configuration) or recovery archive, or when installing an
SD depot where the impacts will leave file systems nearly full, and
you have set '_hp_ignore_sw_impacts' to 1 as follows:
init _hp_ignore_sw_impacts=1
It is possible that you may encounter a file system full problem
during recovery or installation. Normally, the configuration
variable that controls how much free space should be in a file system
increases the size of a file system so there is at least 10% free;
10% being the default value. This default value guarantees that