Ignite-UX release notes HP-UX 11iv1, HP-UX 11iv2 and HP-UX 11iv3 (5900-2307, April 2012)

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). In some cases, storagerelated software may significantly further limit
maximum sizes (failures for sizes greater than 1 TiB have been observed). This means that
Ignite- UX can not install or recover content to or from disks, volumes, file systems or other
storage units of larger sizes. In most cases these large disks will be hidden from Ignite-UX
interfaces and will not be available for install. In some cases large disks may be listed but use
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.
• Due to application dependencies, HP-UX software deployment tools, such as Ignite-UX, expect
legacy Device Special Files to be present and the legacy naming model to be enabled.
Therefore Ignite-UX supports only partial migration as detailed in the white paper "HP-UX 11i
v3 Persistent DSF Migration Guide" found at: http://www.docs.hp.com/en/
oshpux11iv3.html#Storage%20Area%20Management Ignite-UX does not support full migration
which involves disabling the legacy naming model.
• 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.23 with the PAX-Enh product installed because currently there is
no version of the pax command for B.11.11 that understands the pax format.
• The size of individual swap/dump and swap volumes created by Ignite-UX during a cold
install or recovery is limited to 128 GB. Larger amounts of swap/dump or swap volumes can
be utilized in disk or volume groups created during a cold install or recovery by defining
multiple swap/dump or swap volumes.
Networking Issues
• Ignite-UX Hewlett-Packard network interface support matrix.
The only interfaces supported for performing a network boot from a server are the built-in
ethernet (10-Base-T, 100-Base-T, and Gigabit) on all newer systems. The T, V, H, G, I, E class
and 9000/8*7S systems do not support network boot. Other network interfaces that are
supported (see the table below) can only be used when the system is booted using the
"bootsys" command or booted from an Ignite-UX tape or CD. See the bootsys(1M) and
make_boot_tape(1M) manpages.
Table 12 Supported Network Interfaces
NotesAmount of supportDriverType
1fulllan210-base-T
1fulllan310-base-T
1fullbtlan100-base-T
none100VG
full, 32-bit onlyfddi0EISA FDDI
Networking Issues 27