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
for Ignite-UX use, open a call with the IT Resource Center. Support for other use is available
through informal means such as the open source community or online forums.
• These tools do not function on B.11.11 32-bit systems.
Important support changes and plans
• Ignite-UX dropped support for B.11.00 with the C.7.3, September 2007, release.
• Ignite-UX added support for B.11.31 with the C.7.0, February 2007, release.
• Ignite-UX dropped support for B.11.22 with the C.6.5, December 2005, release.
• Changes to support better programmatic control of Ignite-UX servers will be made in future
Ignite-UX releases. This programmatic control is important for Central Management Server(CMS)
integration and may be useful for other automation solutions. An expected change is
modification of install.log messages so that successful installs and recoveries normally do not
include Ignite-UX WARNING messages. For example, WARNING messages for disks which
already contain file systems and insufficient dump space are likely to be reclassified. A new
message classification may be introduced for messages deemed more important than NOTE
but less serious than WARNING.
• In the next release, the -i option of make_sys_image will become obsolete. This option was
applicable only for the B.11.00 and earlier releases.
• The –a option for make_tape_recovery will be a required option on systems with legacy
I/O disabled in a future release of Ignite-UX. System and backup administrators who use
automated scripts based on Ignite-UX to initiate tape backup will be expected to update their
backup process.
• The –b and -c option for make_media_install will be a required option on systems with
legacy I/O disabled in a future release of Ignite-UX. System and backup administrators who
use automated scripts based on Ignite-UX will be expected to update their backup process.
Ignite-UX change request information change
Starting with the C.7.4.157 version of Ignite-UX, release notes and other information will refer to
product Change Requests(CRs) using a new identifier format. The new CR information repository
does include information to correlate migrated CR identifiers (such as JAGag12345) if needed.
10 Announcements