Ignite-UX (IUX) Frequently Asked Questions (July 2013)

group data from the other disks on the system, thus eradicating the
duplicate disk group names.
Note that LVM has the same sort of problem, but it would be observed
when the duplicate group is imported back via vgimport. VxVM is
different in that the problem is detected at volume group creation
time. VxVM looks at all the disks on the system, and not just those
selected for use in the current installation.
=============================================================================
==
1.11
Q: Is SecurePath (previously known as AutoPath) supported by Ignite-UX
during installation or recovery?
A: It depends on what Securepath is controlling. Ignite-UX does not
support active/passive EVA GL (EVA3000/EVA5000) disk arrays because
of multiple known issues. For more information about potential
issues you may encounter please read the latest version of the
Ignite-UX release notes (and search for EVA).
You should note that these issues do NOT affect active/active EVA GL
or any EVA XL disk arrays. These disk arrays are fully supported
for use with Ignite-UX.
=============================================================================
==
1.12
Q: Why is install.log so difficult to read?
A: The installation messages that are logged into install.log are
obtained by Ignite-UX from multiple sources including the standard
output (stdout) and standard error (stderr of Software Distributor
and the contents of swagent.log. It is not possible to control how
these messages are logged into install.log, thus the file can be
confusing.
If you want to verify the installation of a product, HP recommends
that you examining the swagent.log file directly, rather than the
Ignite-UX install.log file.
=============================================================================
==
1.13
Q: Why is the message 'Cannot open /dev/vx/rdsk/rootdg/standvol' displayed
during an Itanium-based installation via golden image?
A: It is caused by the major number change between B.11.23 first release
and B.11.23 September 2004 for vxvm volumes. You will see this
message if the golden image was created on a system running B.11.23
first release, and then the golden image is installed using version
'C' of Ignite-UX.
You can move the kernel build a little earlier in the process to
avoid the message, though the message is not harmful.
post_load_cmd += "