Ignite-UX Release Notes (5900-3323, October 2013)

• make_tape_recovery does not support spanning multiple tapes when it is run remotely
from the Ignite-UX GUI on the server or locally on the client via cron. When a large archive
must span multiple tapes, the user must run make_tape_recovery interactively on the client.
• PAX-ENH product is needed to create pax format tape archives using make_tape_recovery,
even on 11iv3. Otherwise, an error like the following will result:
"pax: Cannot access /sbin/pax_enh : No such file or directory"
Install PAX-ENH product on the system to continue with make_tape_recovery.
This problem is expected to be addressed in a future release of Ignite-UX.
Log File Issues
The Ignite-UX log files found in /var/opt/ignite/logs on the Ignite-UX server do not
automatically get truncated. If you have a lot of server activity, these files may become very large.
They can be safely truncated as you see fit.
Security Issues
By default, an Ignite-UX server exports the directory /var/opt/ignite/clients to every
system. This is done so that any Ignite-UX client can use this server without any prior action being
performed on the server. If exporting this directory to all systems is a concern, you may choose to
export this directory only to your clients, by changing the /var/opt/ignite/clients -anon=2
in the /etc/exports file to be similar to the line below (but with client1, client2, etc., replaced
with your Ignite-UX client host names, or the host names that they use when performing the
installations if they are not the same):
/var/opt/ignite/clients -anon=2,access=client1:client:client3
You will need to execute "exportfs -a" after changing /etc/exports for the change to take
effect.
The following HP Security Bulletins pertain to Ignite-UX:
(see http://www.itrc.hp.com/service/cki/secBullArchive.do)
• HPSBUX01219
• HPSBUX02157
• HPSBUX02249
Cluster File System (CFS) Issue
Ignite-UX has not been verified to work with Cluster File System (CFS). To avoid potential problems,
do not include CFS volumes in Ignite-UX recovery images. The presence of CFS on a system can
cause issues for Ignite-UX. If you encounter any issues, please report them through your normal
support channel. HP will treat issues related to running Ignite-UX on systems with CFS as
enhancement requests, not defects, until after Ignite-UX has been tested with CFS and the
combination becomes fully supported.
September 2004 or earlier Itanium Based VxVM Golden Image Load
Failure
Due to a change in a device major number in VxVM, golden images created on Itanium-based
systems running VxVM and any HP-UX release prior to and including the September 2004 release,
cannot be installed without manual intervention with Ignite-UX releases C.6.2 through C.6.10. It
is recommended that you update any golden images that fit the described criteria to new releases
of 11i v2 (B.11.23). If this issue is encountered, reboot the system and allow Ignite-UX to complete
the installation. The system will come up into a usable state.
Log File Issues 35