Ignite-UX Release Notes HP-UX 11iv1, HP-UX 11iv2, and HP-UX 11iv3 Abstract This document describes the new features with the current release of the product, known problems fixed in the current release, installation requirements, and known issues.
© Copyright 2009, 2014 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents HP secure development lifecycle......................................................................5 1 Related information.....................................................................................6 Documents...............................................................................................................................6 Websites.................................................................................................................................
VxVM and VxFS support.........................................................................................................32 LVM 2.0 support.....................................................................................................................32 Tape device support................................................................................................................33 8 Native language support...........................................................................
HP secure development lifecycle Starting with HP-UX 11i v3 March 2013 update release, HP secure development lifecycle provides the ability to authenticate HP-UX software. Software delivered through this release has been digitally signed using HP's private key. You can now verify the authenticity of the software before installing the products, delivered through this release. To verify the software signatures in signed depot, the following products must be installed on your system: • B.11.31.
1 Related information Documents The following documents are available on the HP Support Center(HPSC) http://www.hp.com/go/ hpsc and most are available on the HP-UX core documents page in http://www.hp.com/go/ hpux-core-docs. The Ignite-UX documents page on the HPSC is www.hp.com/go/ignite-ux-docs and the HP-UX Software Deployment documents page is www.hp.com/go/sw-deployment-docs.
Websites • The Ignite-UX product Website, http://www.hp.com/go/ignite-ux, contains: ◦ Product announcements ◦ Access to downloads of the latest version of Ignite-UX • Ignite-UX software depot webpage http://www.hp.com/go/ignite-ux-download • HP_UX_Docs Twitter account http://www.twitter.com/HP_UX_Docs • HP-UX 11i Knowledge-on-Demand: Best practices from our lab to yours http:// h71028.www7.hp.com/enterprise/us/en/os/hpux11i-kod-overview.
2 Announcements Ignite-UX is a product supplied with HP-UX to perform initial configuration and software installation of HP-UX systems. The English version of this document posted on the web may contain more current information than the version included in the product. For the most current information, go to: http://www.hp.
Supported versions of Ignite-UX It is important to periodically review the support status of the Ignite-UX versions you are using to avoid use beyond End of Support(EOS). These release notes include information about previous Ignite-UX versions. Some of this information may include details about Ignite-UX versions no longer supported. The current support status of Ignite-UX versions is available at http://www.hp.com/go/ignite-ux.
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.
3 Ignite-UX releases This section describes supported Ignite-UX releases. Major changes and defect fixes for each release are described here. Version C.7.18.63 (March 2014 AR and Web release) The C.7.18.63 release of Ignite-UX supports the following HP-UX release/architecture combinations: Table 4 HP-UX release/architecture combinations supported on Ignite-UX version C.7.18.63 HP-UX release HP 9000 systems HP Integrity systems B.11.11 Yes No B.11.23 Yes Yes B.11.
QXCR1001326162—When "-" is not used with any of the options that make_*_recovery command supports, then the arguments provided after that particular option are ignored. Version C.7.17.391 (November 2013 - web release only) The C.7.17.391 release of Ignite-UX supports the following HP-UX release/architecture combinations: Table 5 HP-UX release/architecture combinations supported on Ignite-UX version C.7.17.391 HP-UX release HP 9000 systems HP Integrity systems B.11.11 Yes No B.11.23 Yes Yes B.11.
Version C.7.17.361 (October 2013 – This version is suspended and unsupported.) IMPORTANT: The C.7.17.361 release of Ignite-UX is suspended and is unsupported to use due to packaging issues. For additional details, see HP customer advisory c04008140. Contact HP Response center if you face any issue with Ignite-UX version C.7.17.361. The C.7.17.
Table 7 HP-UX release/architecture combinations supported on Ignite-UX version C.7.16.283 HP-UX release HP 9000 systems HP Integrity systems B.11.11 Yes No B.11.23 Yes Yes B.11.31 Yes Yes After downloading from the web, you can install this version on any server running on any one of the HP-UX releases listed in the table. Ignite-UX version C.7.16.283 includes the following new features: • Support for cluster DSF.
The following manual page entries are either added or updated: • make_net_recovery(1M) • make_tape_recovery (1M) • make_sys_image (1M) Fixes for the following Change Requests: • QXCR1000943194—Ignite-UX now supports the archive and recovery of files/directories Access Control Lists(ACL) with pax format. • QXCR1001116529—Ignite-UX now supports the recovery of a system with legacy I/O disabled.
Table 10 HP-UX release/architecture combinations supported on Ignite-UX version C.7.14.264 HP-UX release HP 9000 systems HP Integrity systems B.11.11 Yes No B.11.23 Yes Yes B.11.31 Yes Yes After downloading from the web, this version can be installed on any server running on any one of the above HP-UX releases. Ignite-UX version C.7.14.
• QXCR1001144624—The 'ignite client list' command correctly displays macaddress information for all the client NICs. • QXCR1001153339—Ignite-UX uses the new -B option of the setboot command to avoid unnecessary generation of IPMI calls. • QXCR1001154910—The print_manifest command is changed to display disk sizes greater than 4TB. • QXCR1001155333—Ignite-UX provides support to automatically detect the pax block size.
4 General features Benefits: Ignite-UX is intended to address the needs of customers performing system installations and recoveries, often on a large scale. It provides the means for creating standard system configurations for reuse. It provides the ability to capture an installed system into an image, and use that image to quickly install standard systems. Ignite-UX also permits post-installation customizations, and is capable of both interactive and unattended operating modes.
• Ignite-UX provides a mechanism to construct your own customized bootable installation media. For more information, see Ignite-UX Administration Guide. • Ignite-UX provides tools to enable consistent, reliable recovery in the event of a catastrophic failure of the system disk or root volume group. For more information, see make_net_recovery(1M) and the Ignite-UX Administration Guide.
5 Known issues Open critical/serious customer-found defects Known customer-found critical/serious defects are listed in known problems associated with each release. When these defects are resolved they will be listed in the change content for the release where they are fixed.
device before installing the Active/Passive Switch(APSW) plug-in can cause some commands to take a long time. Disconnect any Active/Passive devices connected to your system before installing or recovering HP-UX 11i v3. After install or recovery it is important that the APSW plug-in be installed before connecting an Active/Passive device to the system.
6 Known problems and workarounds This section describes known problems with the Ignite-UX product as well as workarounds to these problems. More detail is often available in the FAQ available from: http://www.hp.com/go/ ignite-ux. Required patches Patch PHCO_31903, s700_800 B.11.11 libc cumulative patch, is required for the correct execution of list_expander on B.11.11 systems, and patch PHKL_31500 is required on B.11.23 systems that are running B.11.23 September 2004 or later.
ERROR: Could not execute net_cfg_prep NOTE: System rebooting... Shutdown at 10:36 (in 0 minutes) System shutdown time has arrived ◦ While installing an rx5670 via the network, when the installation settings are finalized and installation started, the following error message is displayed on the client console: * Loading configuration utility... * Beginning installation from source: 16.113.12.86 ======= 06/21/13 09:05:29 EDT Starting system configuration... * Configure_Disks: Begin * Will install B.11.
may result in errors or failure. Recovery archives should not be created which contain data residing on large storage units listed above. NOTE: Ignite-UX is not intended to be used instead of backup tools to save or restore large quantities of application data. • When a golden image is created for a B.11.23 or B.11.31 client using the pax format of the pax command, it is not possible to run archive_impacts on it from the server if the server is not running at least B.11.
Table 14 Supported network interfaces (continued) Type Driver Amount of support Notes HPPB token token2 may work 2 PCI token pcitr may work 2 Gigabit gelan full Gigabit igelan full NOTE: 1. These interfaces are known to work correctly with DHCP. 2. The drivers for these interfaces are included in the INSTALL kernel, but have not been tested due to lack of appropriate hardware in the test lab. They are "not known not to work" at this point in time. 3.
• Three special variables: _hp_nfs_mount_opts, _hp_nfs_mount_retries and _hp_tftp_cmds can be used where special networks (like WAN) require tuning of the NFS and tftp services to increase performance or reliability. See instl_adm(4). • It is highly recommended that NFS over TCP be enabled on Ignite-UX servers. Problems have been seen when only NFS over UDP is enabled (which is the default).
If your configurations use NFS to access archives on systems other than the Ignite-UX server, then those systems should have NFS over TCP enabled as well. User interface issues • The user interface does not currently allow you to directly specify kernel parameters. The target's kernel can be manipulated via the "mod_kernel" configuration file keyword. For details, see instl_adm(4). There is also a way to make kernel modifications user selectable in the UI by treating them as software.
This keyword can be either global or set inside a sw_source. For more information, see instl_adm(4). If you wish to implicitly select patch bundles, then the sd_software_list keyword for the patch bundle sw_sel must not be present. • Patches must be loaded after the software they are patching. To ensure that this is the case, use the load_order attribute in the sw_source for the patch depot. The default load_order is zero (0) for core software and five (5) for applications.
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.
Encrypted Volume and File System(EVFS) issue Ignite-UX does not currently support Encrypted Volume and File System(EVFS). This means that EVFS volumes can not be configured during cold-install and will not be preserved when using make_net_recovery or make_tape_recovery. Consult EVFS product documentation for information on configuring and backing up EVFS volumes. Support for EVFS is planned for a future release.
Furthermore, even if the above messages are not displayed, it may be possible that the following message appears when the process reboots after the kernel build: /usr/lib/dld.sl: Unresolved symbol: id__Q2_3std7codecvtXTcTcT9mbstate_t_ (data) from /configure3 /sbin/bcheckrc: In this case, PHSS_22898 or successor must be included in the installation, but the load order is not important. There is no workaround. Support issue for B.11.
7 Compatibility and installation requirements Software requirements Ignite-UX C.* can be installed on any HP-UX system running B.11.11, B.11.23, or B.11.31 when downloaded from the web. If installed from Application Media, it can only be installed on the same release of HP-UX that the Application Media is targeted at (i.e. Ignite-UX from the B.11.23 Application Media can only be installed on B.11.23). Hardware support matrix For current information on both supported and unsupported hardware for B.11.
Tape device support Starting with version C.6.8 recovery and custom boot tapes created with Ignite-UX may be used for direct tape boot with Hewlett-Packard Itanium-based systems. In order to use direct boot from tape, you will need an Itanium-based system or firmware upgrade which supports direct tape boot. Direct tape boot may not be supported with some I/O interfaces. Some Itanium-based systems may never have firmware support for direct tape boot. Support for the two-step media recovery process continues.
8 Native language support Localization The Ignite-UX product has Japanese EUC and Japanese SJIS localized manpages and online help. The Japanese localized release notes are only provided on the web so that translated information may be kept consistent with released product information. The English version of this document posted on the web may also contain more current information than the version included in the product. For the most current information, see http://www.hp.com/go/ignite-ux.
9 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
