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

should look at the setting of both "patch_state" and state in the
swlist output.
For example:
# swlist -l patch -a state -a patch_state | grep PH
If the "patch_state" is applied (the patch has not been superseded)
and the state is installed, this may indicate an issue and you should
configure the patch with the swconfig command. If the "patch_state"
is superseded or committed, you do not have to worry about the state.
However, if you remove any patches and a previously superseded patch
changes to have a "patch_state" of applied, you must run swconfig
manually to configure the patch if its state attribute is installed.
Note: Do "NOT" manually modify the state attribute of an installed or
committed patch to be configured with the swmodify command.
=============================================================================
==
----------------------------------------
11. Network Recovery
----------------------------------------
11.1
Q: How can I learn more about network recovery?
A: In addition to the information in this FAQ, there are several other
sources of information on network recovery:
- The "System Recovery" chapter in the "Ignite-UX Administration
Guide" at:
http://docs.hp.com/en/IUX/infolib.html
- These manpages are applicable to network recovery are as follows:
* make_net_recovery(4)
* make_boot_tape(1M)
* pkg_rec_depot(1M)
* instl_adm(1M)
* instl_adm(4)
* ignite(5)
- The Ignite-UX Release Notes that detail new features, enhancements
and known problems with the product. It is located in Information
Library and in the /opt/ignite/share/doc/release_note directory.
- The recovery white papers "Successful Cloning using Ignite-UX" and
"Successful System Recovery using Ignite-UX" at:
http://docs.hp.com/en/IUX/infolib.html
=============================================================================
==
11.2