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

Why is the message Cannot open /dev/vx/rdsk/rootdg/standvol displayed
during an Itanium-based installation via golden image?
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.
post_load_cmd += "
ccunset SW_INITIAL_INSTALL
/usr/sbin/mk_kernel -f -o /stand/vmunix
"
Does HP support Ignite-UX through a firewall?
HP has not tested Ignite-UX through a firewall.
It must 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 Ignite-UX Administration Guide available on http://www.docs.hp.com.
HP supports Ignite-UX in conjunction with Bastille on HP-UX 11i systems. Ignite-UX Administration
Guide describes how to configure Bastille on both Ignite-UX servers and clients.
What do I do when I get file system full messages during installation or recovery
when _hp_ignore_sw_impacts is set to 1?
When installing or recovering a system, Ignite-UX uses a small amount of space (a few MB) in
each of the / and /usr file systems to hold some commands. While some of these commands are
used during the installation or recovery of HP-UX, others 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 might encounter a problem wherein the file system is full during recovery or
installation. Normally, the configuration variable that controls how much free space must be in a
file system increases the size of a file system so that there is at least 10% free space; 10% free
space being the default value. This default value guarantees that there is enough free space for
an installation or recovery.
Setting _hp_ignore_sw_impacts to 1 means that Ignite-UX will not resize the file systems
according to impacts to guarantee some free space. If you set _hp_ignore_sw_impacts to 1,
you must ensure that there is some free space available in / and /usr during installation or
recovery (at least 20 MB) to avoid file system full issues.
If you do not set _hp_ignore_sw_impacts to 1, you can ignore this information. This issue is
most likely to affect even if you create a recovery archive in which you have set
_hp_ignore_sw_impacts to 1 in the installation file system or config.local files and / or
/usr file system is nearly full.
What do I do when I get an error reading files greater than 2 GB in size?
The C.6.5.61 (December 2005) and newer versions of Ignite-UX contain the B.11.23 patch
PHKL_33110 which includes install kernels to resolve an issue where files on ISO9660 media
14 Known problems