Ignite-UX Frequently Asked Questions

modify the /var/opt/ignite/clients/0x<LLA>/CINDEX file for the client
you are recovering.
The CINDEX file contains one or more configuration clauses that refer
to the recovery images you have previously created with
make_net_recovery. Add a new configuration file entry to the clause
from which you intend to recover. If you want to add the HP standard
file system choices, add the file:
# /opt/ignite/data/Rel_<release>/config
where <release> is the operating system release on the client you
intend to recover. For example, /opt/ignite/data/Rel_B.11.23/config
would be added for a client with the HP-UX 11.23 operating system.
This new configuration file entry should be the first entry in the
clause you are modifying.
When you launch the Ignite-UX during recovery, select the file system
type you wish to use on the "Basic" tab.
===============================================================================
11.10
Q: I replaced the client machine and the LAN address is now different.
How can I restore the new machine from the old client network
recovery archive?
A: Ignite-UX uses a separate directory for each client under
/var/opt/ignite/clients. Each subdirectory is named based on the
client's LAN address (MAC address, LLA, etc.).
If you replace the client hardware or the LAN card that the old LAN
address was based on, then it can no longer access the same directory
on the Ignite-UX server.
The simplest solution is to obtain the new LAN address, which you can
do from the boot-ROM console using a command like LanAddress (the
actual command may vary depending on the hardware architecture).
Once you have the new address then manually rename the directory
under /var/opt/ignite/clients. You may remove the symbolic link to
the host name because it is recreated automatically. The LAN address
must be all in uppercase and begin with 0x.
If you have already booted the client from the server, which caused
it to create a new directory, you can remove that directory before
renaming the old directory. Be careful not to remove the original
directory or you will lose the recovery information.
For example:
# cd /var/opt/ignite/clients
# mv 0x00108300041F 0x00108300042A
# rm old_hostname
===============================================================================
11.11
Q: Dealing with hot swappable disks during recovery.
A: See question 4.3 (Dealing with hot swappable disks during recovery.).
===============================================================================
11.12
Q: Why does archive_impact fail during make_net_recovery?
A: The PHCO_21185 patch issued for ksh(1M) causes corrupt parameter
processing. The corruption occurs when archive_impact is run as a
part of a make_net_recovery command.
Software patch PHCO_21185 has been superseded by PHCO_22020. Remove
patch PHCO_21185 and install PHCO_22020 to correct this failure.
===============================================================================
11.13
Q: How can I restore VxVM DCO log volume groups?
A: The make_net_recovery/make_tape_recovery tools will create a recovery
archive for a client while preserving the configurations for all VxVM
(VERITAS Volume Manager) volumes except data change object (DCO) log
volumes. After recovering from the archive, the DCO log volume
configurations will be lost and must be reconfigured using VxVM
commands. There are basically two methods of reconfiguring lost DCO
log volumes; choose the method that is appropriate for your