Ignite-UX Release Notes (769572-001, March 2014)
Table Of Contents
- Ignite-UX Release Notes
- Contents
- HP secure development lifecycle
- 1 Related information
- 2 Announcements
- 3 Ignite-UX releases
- Version C.7.18.63 (March 2014 AR and Web release)
- Version C.7.17.391 (November 2013 - web release only)
- Version C.7.17.361 (October 2013 – This version is suspended and unsupported.)
- Version C.7.16.283 (March 2013)
- Version C.7.15.254 (September 2012)
- Version C.7.14.274 (March 2012 - web release only)
- Version C.7.14.264 (March 2012)
- Version C.7.13.259 (September 2011 - web release only)
- 4 General features
- 5 Known issues
- 6 Known problems and workarounds
- Required patches
- General issues
- Networking issues
- User interface issues
- Issues when installing from archives
- Common problems loading patches
- make_[tape|net]_recovery issues
- Log file issues
- Security issues
- Cluster File System(CFS) issue
- September 2004 or earlier Itanium based VxVM golden image load failure
- Memory File System(MemFS) issue
- Encrypted Volume and File System(EVFS) issue
- Disk space issues using VxVM & hard drive models ST318203[FL]C
- VxVM used for OS content with non-VxVM root volume install
- Support issue for B.11.11 installs
- 7 Compatibility and installation requirements
- 8 Native language support
- 9 Documentation feedback

Install PAX-ENH product on the system to continue with make_tape_recovery.
This problem is addressed in C.7.18.63 and later releases 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://h20565.www2.hp.com/portal/site/hpsc/public/psi/advisoriesResults/?
sp4ts.oid=407717)
• 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, 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.
Memory File System(MemFS) issue
Ignite-UX with the C.7.2 version does support recovery of Memory File System(MemFS) file systems.
It does not currently support MemFS during cold-install. The MemFS file system content will not be
preserved of course, but the file systems themselves will be.
Log file issues 29