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, 2013 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 1 Related information.....................................................................................5 Documents...............................................................................................................................5 Websites.................................................................................................................................6 2 Announcements..........................................................................................
7 Compatibility and Installation Requirements.................................................38 Software Requirements............................................................................................................38 Hardware Support Matrix........................................................................................................38 VxVM and VxFS Support.........................................................................................................38 LVM 2.0 Support.........
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 on the HPSC http:// www.hp.com/go/hpsc. The Ignite-UX documents page on the HPSC iswww.hp.com/go/ignite-ux-docs and the HP-UX Software Deployment documents page is www.hp.com/go/sw-deployment-docs.
Websites • 6 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 to 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 the following location: http://www.hp.com/go/ignite-ux.
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.
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.16.283 (3/2013) The C.7.16.283 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.16.283 HP-UX release HP 9000 systems HP Integrity systems B.11.11 Yes No B.11.23 Yes Yes B.11.
Table 5 HP-UX Release/Architecture Combinations Supported on Ignite-UX Version C.7.15.274 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.15.
See “Version C.7.14.264 (3/2012)” (page 12) for information about the changes in this version of Ignite-UX. Version C.7.14.264 (3/2012) The C.7.14.264 release of Ignite-UX supports the following HP-UX release/architecture combinations: Table 7 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.
• QXCR1001141025. The make_*_recovery command is changed to call list_expander with the -m option, which allows archiving of files of size greater than 8GB. • QXCR1001144550. Available free space in a file system is calculated using a 64-bit variant of statvfs64 system call. This is for servers with greater than 2TB file systems to work as expected. • QXCR1001144624. The 'ignite client list' command correctly displays macaddress information for all the client NICs. • QXCR1001153339.
Table 9 HP-UX Release/Architecture Combinations Supported on Ignite-UX Version C.7.13.240 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.13.240 contains the following new features: The B.11.31 install kernels have been updated. The VxVM-Tools bundle was updated to the 5.0.
• QXCR1001121908. itool now accepts legacy hardware path even if it is longer than the width of its text box in the 'More Info' window. • QXCR1001124612. The autoboot status of a client is now gathered along with primary hardware path information with a single invocation of the setboot command. This will aid in not overwhelming the Onboard Administrator when multiple installs are going on simultaneously with virtual partitions on Superdome 2. • QXCR1001154804.
Fixes for the following Change Requests: 16 • QXCR1000893208. Ignite-UX is now capable of installing recovery images where APA was being used for HP-UX B.11.31. Please refer "Verifying Recovery Image Results" under Section 15 in the Ignite- UX Admin Guide for information regarding limitations of APA support. • QXCR1000926125. list_expander will now include symbolic links even if there are NFS mounts under it. This had affected the make_*_recovery commands. • QXCR1000965183.
• * QXCR1001055810. Ignite-UX has been updated to correctly display the maximum volume group size in itool window. • QXCR1001057724. When running make_net_recovery with the -r option to resume a preview, it will now remove all the configuration directories associated with an old recovery archive. • QXCR1001058334. Recovery image installs of 11.31 clients with either compartments enabled or configured as Secure Resource Partitions (SRP) are now supported. • QXCR1001059542.
Ignite-UX version C.7.11.444 contains the following new features: • The B.11.31 IINSTALL install kernel has been updated. The 10GigEthr-01 bundle was updated to the B.11.31.1007 revision in order to deal with issues using the AD386A PCIe 10 Gigabit Ethernet card. Fix for the following Change Request: ◦ QXCR1001027982. VxVM listener binaries, delivered as part of Ignite-UX, were updated to support up to a 31-character plus a null character hostname.
• • instl_adm(4) ignite(5) Fixes for the following Change Requests: ◦ QXCR1000776474. make_net_recovery(1M) was modified to add a WARNING regarding support of Auto Port Aggregation (APA). ◦ QXCR1000931459. Extraneous messages regarding missing OE content will no longer be seen when creating depots from 11.31 media content via server_setup from ignite. ◦ QXCR1000942141.
type 1 - default HP "month" "day" tape volume name; and type 2 - the user specified 6-character name that does not start with HP. Notes related to known problems with this release: ◦ A new known issue regarding Integrity i2 system firmware that has no impact on Ignite-UX operation has been added to this document: 4.5 EFI Firmware Networking Utilities and Integrity i2 Servers. Version C.7.10.474 (5/2010 - Web Release Only) The C.7.10.
NOTE: 11i v3. Ignite-UX does not support either LVM volume group versions 2.0 or 2.1 for HP-UX • An updated version of the copy_boot_tape command is shipped in this version of Ignite-UX. The new version of copy_boot_tape can be used replicate a PA-RISC boot tape to another PA-RISC boot tape, as well as an IPF boot tape to another IPF boot tape. Refer to copy_boot_tape(1M) for new options to support PA-RISC as well as IPF boot tapes.
Fixes for the following Change Requests: 22 • QXCR1000853553. Optical drives are no longer flagged as bad disks when empty. • QXCR1000879894. An issue where free physical extents exist on fully allocated 11.31 LVM systems after cold install has been resolved. • QXCR1000881477. Ignite-UX will now hide all paths to disks specified in _hp_hide_other_disks setting or via _hp_hide_boot_disk. • QXCR1000898153. In order to avoid problems with swapinfo reporting incorrect data on B.11.
Notes related to known problems with this release: • QXCR1000995198. Recovering systems that have the new HP StorageWorks MSA2000sa storage adapter hardware will likely have a WARNING message produced. The sequence will appear like this in the install.log: ◦ Swapping 140 SAS disk(s) to match selected configuration. ◦ Boot device is: 0/3/0/0/0/0.0x0.0x4000000100034002 WARNING: Could not make needed swaps to get system to match config selected.
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. See the chapter on creating your own installation media in the Ignite-UX Administration Guide for more information. • Ignite-UX provides tools to enable consistent, reliable recovery in the event of a catastrophic failure of the system disk or root volume group. See make_net_recovery(1M) and the chapter on recovery in the Ignite-UX Administration Guide for more information.
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 This is caused by an Ignite-UX issue and is tracked in QXCR1001268768. ◦ 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.
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 15 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. See instl_adm(4)(4) for details. 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. See instl_adm(4) for more information. 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 should 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.
• 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.
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. Encrypted Volume and File System (EVFS) Issue Ignite-UX does not currently support Encrypted Volume and File System (EVFS).
The archive will not be loaded successfully. You cannot load an archive when installing HP-UX B.11.11 from a Software Distributor depot until after PHSS_22898 or successor has been installed. If you encounter this problem you must use the load_order keyword to move the archive loads to somewhere after PHSS_22898 has been loaded. See instl_adm(4) for more information about the load_order keyword.
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.
install environment) to volume group version 2.2 using the LVM's volume group migration tool (vgversion(1M) command) prior to the archive creation. 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.
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 to the Web may also contain more current information than the version included in the product. For the most current information, go to: http://www.hp.com/go/ignite-ux.
