HP-UX 11i March 2002 Release Notes

HP-UX 11i Operating Environment Applications
Selectable Applications
Chapter 4
98
• HP Intrusion Detection System/9000 Administrator's Guide, version 2.0
(product no. J5083-90007)
Ignite-UX (IUX)
Ignite-UX (IUX) is an HP-UX administration toolset to help you do the following:
• install HP-UX on multiple systems in your network
• create custom install configurations
• recover HP-UX systems remotely
• monitor system-installation status
The complete Ignite-UX product, with support for HP-UX 11i, 11.0 and 10.20, is
available on the first CD of the 11i OE media kit.
For additional information about IUX, see “Ignite-UX Changed for 11i” on page 122.
updated for
March 2002
Ignite-UX has been updated to version B.3.6 to support changes to the Operating
Environments. Changes to B.3.6 include the following:
• An IUX feature has been enhanced so that newly installed core components and
patches will be swmodify’ed with the correct file data to avoid swverify problems
with those files.
• To avoid accidental tape rewinding, the print_manifest command will no longer
call diskinfo (or provide a tape capacity estimate) for tape devices.
updated for
December 2001
Ignite-UX version B.3.5 includes the following changes:
• Drivers such as X.25 (nioxb) now have their driver binding preserved during a
recovery. This prevents them from becoming “unclaimed” after a recovery.
• The hw_instance_num config file keyword includes a new optional driver parameter.
See the instl_adm (4) manpage for more information.
• The save_config command now sets the above driver parameter. A check was also
added that ensures that the hardware path is of the format expected by the parser for
HW_instance_num. This fixes the problem introduced by the sdm driver which has a
hardware path of “es” for the virtbus class.
• Ignite-UX servers that have multiple IP addresses assigned to a single network card
now work correctly—as far as doing network boots using instl_bootd is concerned.
However, this does not fix the issue documented in the FAQ item #1.9. The FAQ (a
text file) is installed with Ignite-UX in /opt/ignite/share/doc/FAQ.
• Ignite-UX now supports setting the block size for VxVS file systems. Previously this
was only allowed to default. The user interface now permits this to be set to valid
values and the save_config command saves it in order to restore it for a recovery. A
sanity check now tests for valid values (also covering block sizes for HFS file systems)
and applies this when laying out VxFS file systems.
• If an OS archive image contains volume group files (for example, the directory
/dev/vg00 and the files underneath that), and the major and minor numbers match
ones that have been created but have a different name (like if vg00 was renamed
bpr00), then the /dev/vg00 directory and its contents will be removed and the
action logged to install.log. This avoids problems with commands like swapinfo