Ignite-UX Frequently Asked Questions

-c "HP-UX B.11.23 Default"
Note: The make_config command only works on bundles. If the
software is not contained within a bundle you must either create
bundles for it using the make_bundles command or manually create
configuration files for your software.
===============================================================================
5.6
Q: FDDI software is included in my archive, yet Ignite-UX requires that I
select it. Why?
A: Ignite-UX generates an error indicating that you must select the FDDI
software for installing if the following conditions exist:
- You are using an FDDI interface during the installation.
- There is a sw_sel defined in a configuration file that has the string
FDDI in the description.
Ignite-UX provides the error prior to starting the configuration
phase to avoid the client being unable to complete the installation
due to the lack of the FDDI drivers. Ignite-UX does not have any way
of detecting the inclusion of FDDI software in an archive so it
assumes that it is not.
If you have the FDDI software in the archive, you can avoid the error
by removing it from your depot then rerunning make_config to reflect
the removal in the associated configuration file.
Alternatively, you can select the FDDI software, which causes the
swinstall command to skip installing it since it is already on the
client.
===============================================================================
5.7
Q: How many clients can I install simultaneously or in parallel?
A: Although there are no set limits in Ignite-UX, you will find that
performance decreases as you reach the limits of your network and
server bandwidth.
Most users have found that installing about twenty (20) clients at a
time, from a single server, is the limit while maintaining reasonable
performance and avoiding network errors. This seems to be a
reasonable number for you to keep track of and test when the
installations complete. Also, you may find it useful to stagger the
installations so that they are not all doing the same operation at
the same time, thus do not all complete at the same time.
Using the NFS access method to access archives is suggested in order
to avoid a problem that occurs when installing many clients using the
ftp access method. When many ftp and tftp processes are running to a
server at once, the tftp commands start generating the following
error:
tftp: recvfile: recvfrom: Can't assign requested address
Note: You may need to make SD configuration changes to cope with
a large number of concurrently installing clients, please read the
section "Performance considerations for SD-UX based installs" in the
manual "Ignite-UX Custom Configuration Files" available at:
http://www.docs.hp.com/en/IUX/infolib.html
===============================================================================
5.8
Q: My installations are hanging; what is going on?
A: In certain circumstances installations may hang and could be due to a
problem with swagentd. If you are using an operating system archive,
the hang occurs after the following message appears in:
* Running "/opt/upgrade/bin/tlinstall -v" and correcting transition link
permissions.
If you are using swinstall only, the hang occurs after the following
message appears in install.log:
* Setting primary boot path to "<some hardware path>"