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

- From the "Advanced Options" menu, select "Edit (vi) config file"
- From the vi editor, add one line such as:
hw_instance_num = 0 "ioa" "sba" 0
- This will override the hw_instance_num values from the other
config files on the tape.
- The system will not attempt to restore any prior device file
naming because of this.
=============================================================================
==
1.19
Q: Why do I see errors about io.info version 0.5 not being understood
and how do I work around it?
A: If an Ignite-UX version C.6.8 - C.6.10 was used to create a recovery
image and then an Ignite-UX version C.7.1 - C.7.6 was used to recover
that image, you might see errors like this:
ERROR: 0x40041e30: IOTree::parse_io_info_line: io.info version is
not
understood: 0.5
ERROR: Fatal error while parsing io.info file
ERROR: Cannot initialize I/O data: unable to parse
/var/opt/ignite/clients/0x00306E48CE61/io.info file.
The cause of these ERROR messages is that versions C.6.8 - C.6.10 of
Ignite-UX create a version 0.5 io.info file. When a recovery is
attempted with versions C.7.1 - C.7.6 of Ignite-UX, it is unable to
parse the old 0.5 version of the io.info file.
To work around this issue, you can do ONE of the following:
1) Run Actions -> Refresh Client from the ignite user interface.
2) Use "Boot Client" from the Actions menu to boot the client in
preparation for installing from the ignite user interface.
3) Use the client's console to boot from the Ignite-UX server.
4) Delete the io.info file in the client's directory.
=============================================================================
==
1.20
Q: When using the graphical interface, why do errors occur when opening
a terminal window to a client?
A: If errors occur when Ignite-UX attempts to bring up a terminal to a client
(for instance, to enter a password), it could be because hpterm does not
work with some name-services (like LDAP) and is unable to resolve a
hostname
specifed in the DISPLAY environment variable.
For HP-UX 11.23, the following patch introduced support of an environment
variable SAMTERM:
PHSS_31817 s700_800 11.23 ObAM Patch
The value of this variable will determine which type of terminal is
opened.
To make use of this variable, run Ignite as follows: