Ignite-UX (IUX) Document for Frequently Asked Questions (FAQ) (762793-001, March 2014) (Edition: 3)

How can I install additional software from depots during a recovery?
In situations where a system needs additional software installed to support restoring a recovery
archive onto a different hardware platform, or perhaps a vPar or HP-VM, you can load additional
software from a depot during the recovery.
To do this, generate a config file using make_config for the depot containing the additional
software. Then add the path to that config file to each recovery clause required in the /var/
opt/ignite/clients/<client>/CINDEX file. The example below will create a config file
and add it to all entries in the client's CINDEX file.
# make_config -s <depot> -c
/var/opt/ignite/data/Rel_B.XX.YY/sw.cfg
# manage_index -a -f /var/opt/ignite/data/Rel_B.XX.YY/sw.cfg
\
-i /var/opt/ignite/clients/<client>/CINDEX
You might instead choose to save the config file for the client in the path /var/opt/ignite/
clients/0x<LLA>/recovery/config.local. In which case, each time a new recovery
archive is made, the config.local file will be automatically added to the new CINDEX entry.
(See FAQ item 11.8)
During a system recovery, the software bundles available in the depot will be available for selection
from the user interface.
Why am I getting this message, Warning: untrusted X11 forwarding setup
failed?
If you try to initiate a recovery session on a client from the Ignite-UX server GUI and you see the
following warning:
Warning: untrusted X11 forwarding setup failed: xauth key
data not generatedWarning: No xauth data; using fake
authentication data for X11 forwarding.
Check the setting of the ForwardX11Trusted variable in /opt/ssh/etc/ssh_config on the
server. If it is no, try setting it to yes.
Why does the -n option to make_net_recovery not clean up old client recovery
subdirectories?
The -n option to make_net_recovery can be used to limit the number of archives that are
retained on the Ignite-UX server, but in some cases it will not clean up the client recovery
subdirectories in /var/opt/ignite/clients/<client>/recovery where configuration
files are stored. This can happen for two reasons:
• Archives were manually removed without removing their corresponding configuration
directories. If you manually remove archives, you must also remove the corresponding directory
under /var/opt/ignite/clients/<client>/recovery and any associated entries
in /var/opt/ignite/clients/<client>/CINDEX.
• Unsuccessful make_net_recovery invocations may create a partial recovery directory
without a corresponding archive. Because no archive was created, the -n cleanup process
of make_net_recovery will not clean up the recovery directories. You need to manually
clean up these directories periodically to keep your filesystem clean.
50 Network recovery