Ignite-UX release notes HP-UX 11iv1, HP-UX 11iv2 and HP-UX 11iv3 Abstract This is the product release notes for Ignite-UX. The Ignite-UX product release notes are also shipped with the product, available at /opt/ignite/share/doc/release_note.
© Copyright 2009, 2012 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..........................................................................................
VxVM and VxFS Support.........................................................................................................35 LVM 2.0 Support....................................................................................................................35 Tape Device Support...............................................................................................................36 8 Native Language Support..........................................................................37 Localization.
1 Related information Documents The following documents are available on the HP Business Support Center (BSC) www.hp.com/ bizsupport/ and most are available on the HP-UX core documents page on the BSC www.hp.com/ go/hpux-core-docs. The Ignite-UX documents page on the BSC 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 • Links to documentation can be found on the Business Support Center http://www.hp.com/ go/ignite-ux-docs • 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.
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.14.274 (3/2012 - Web Release Only) The C.7.14.274 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.14.274 HP-UX release HP 9000 systems HP Integrity systems B.11.11 Yes No B.11.23 Yes Yes B.11.
• QXCR1001111979. Legacy DSFs for ciss-driver based HBAs are recovered properly with no stale DSFs left around. • QXCR1001129212. The bootable flags for the paths are appropriately set before the preferred path is selected. • QXCR1001130947. SAS disks are now recovered correctly even when multiple paths pointing to the same disk are present in a different order from that of the archive. • QXCR1001131156. The expected value of the final size of the LIF volume is now set to the maximum value possible.
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.259 contains the following new feature: Fix for the following Change Request: • QXCR1001120228. Following the replacement of Vx* 5.0 bits by Vx* 5.0.1 in the Operating Environment of September 2011 release of HP-UX 11i v3, Ignite-UX Install Environment has been completely updated with the Vx* 5.0.1 drivers and command binaries.
• QXCR1001102946. save_config can now handle any number of disks in a VxVM disk group. • QXCR1001108276. When make_*_recovery commands are run in preview mode and then resumed, the manifest file is created in the correct directory. • QXCR1001111254. list_expander doesn't walk through the autofs mount points anymore, thus preventing them from getting mounted every time. • QXCR1001111586. make_*_recovery will exit with an appropriate message in the presence of Cluster-wide Device Special File (cDSF).
After downloading from the Web, this version can be installed on any server running one of the above HP-UX releases. Ignite-UX version C.7.12.519 contains the following new features: The following manual page entries are either added or updated: • bootsys(1M) • ignite-ui(1M) • instl_adm(4M) • make_ipf_tape(1M) • make_medialif(1M) • make_net_recovery(1M) • make_sys_image(1M) Fixes for the following Change Requests: 14 • QXCR1000893208.
• QXCR1001039432. The -i option of make_sys_image, which was applicable only for B.11.00 and earlier releases, has been obsoleted. • QXCR1001044588. HP Integrity BL860c i2 Server Blade systems support network boot when incoming requests are relayed. • QXCR1001045036. Warning messages for B.11.31 clients will be displayed if the selected path is in either a standby or failed state. • QXCR1001045660. On B.11.
The following limitations are applicable for the current release: • Ignite-UX does not support Cluster Device Special files (cDSF) in Service Guard Cluster environment. Recovery support for such a configuration is not supported. If you require support for recovery archives in a Service Guard environment do not implement cDSF support. Version C.7.11.444 (9/2010 - Web Release Only) The C.7.11.
• ignite-version(1M) • ignite(1M) • instl_dbg(1M) • make_net_recovery(1M) and make_tape_recovery(1M) • print_manifest(1M) • auto_adm(4) • 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.
◦ QXCR1001006324. In order for print_manifest to always have access to the latest template file, /var/opt/ignite/local/manifest/template.def has been moved to /opt/ignite/manifest/template.def. Any current copy of /var/opt/ ignite/local/manifest/template.def will be saved to /opt/ignite/ manifest/template.def.saved in case it has been customized. ◦ QXCR1001006401. Ignite-UX will no longer display a warning message regarding a missing /etc/lvmrc file. ◦ QXCR1001029860.
This version can be installed on any server running one of the above releases of HP-UX when downloaded from the Web. Ignite-UX version C.7.10.472 contains the following new features: • Ignite-UX now supports boot, dump, swap and data volumes for LVM volume group version 2.2 for HP-UX 11iv3, as well as the earlier version 1.0. This new LVM volume group version supports higher limits on parameters such as "Max VG Size", "Max VGs"and "Max LVs" as compared to LVM volume group version 1.0.
◦ make_sys_image(1M) ◦ manage_index(1M) ◦ save_config(1M) ◦ instl_adm(4) ◦ ignite(5) Fixes for the following Change Requests: 20 • 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.
• QXCR1000972558. Ignite-UX will no longer remove /dev/deviceFileSystem during a system recovery. This was causing CDE to not come up after a recovery. • QXCR1000979395. Using the "-x print_manifest_args" option to make_net_recovery and make_tape_recovery will no longer interfere with the operation of other -x options. Notes related to known problems with this release: ◦ QXCR1000995198.
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.
Workarounds are as follows: ◦ make sure you enter all information at Ignite-UX time, or ◦ enter no information at Ignite-UX time (so set_parms will run), or ◦ make the remaining changes manually after the system comes up by using the following: /sbin/set_parms initial • Ignite-UX does not handle large size quantities. For example, close to, equal to, or greater than 2 TiB (2^31).
Table 12 Supported Network Interfaces (continued) Type Driver Amount of support Notes HPPB FDDI fddi full HSC/GSC FDDI fddi3 may work PCI FDDI fddi4 full EISA token token may work 2,3 HPPB token token2 may work 2 PCI token pcitr may work 2 Gigabit gelan full Gigabit igelan full 2 NOTE: 1. 2. 3. • • These interfaces are known to work correctly with DHCP.
• For NIO FDDI, the MTU size can now be specified by using the _hp_lanadmin_args variable. See instl_adm(4). • 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).
# /sbin/init.d/nfs.server start Repeat running the rpcinfo command above. You should now see NFS over TCP enabled. 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) for details.
they are packaged in a way so that make_config will omit the sd_software_list attribute which will result in those bundles being implicitly selected which avoids these problems. To change the default behavior of Ignite-UX to use a "-xpatch_match_target=true" type swinstall, the sd_command_line keyword can be used to define this. For example: sd_command_line += " -xpatch_match_target=true " This keyword can be either global or set inside a sw_source. See instl_adm(4) for more information.
• 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. • make_tape|net_recovery do not support the creation of the recovery archive for Volume Groups configured using Cluster-wide Device Specific Files (cDSF). If the input volume group, e.g.
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.
