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

SD depot machine: sdsource
SD depot: /var/application_depot
For release: 11.23
You would execute the following:
# cd /var/opt/ignite/data/Rel_B.11.23
# make_config -s sdsource:/var/application_depot -c
app_name.cfg
# manage_index -a -f
/var/opt/ignite/data/Rel_B.11.23/app_name.cfg \
-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.
FDDI software is included in my archive, yet Ignite-UX requires that I select it. Why?
Ignite-UX generates an error indicating that you must select the FDDI software for installing if the
following conditions exist:
• You are using the 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 method
to detect the inclusion of FDDI software in an archive.
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.
How many clients can I install simultaneously or in parallel?
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 20 clients at a time from a single server is the limit
while maintaining reasonable performance and avoiding network errors. This is a reasonable
number for you to track and test when the installations complete. Also, you might find it useful to
stagger the installations so that they all are not performing the same operation at the same time,
thus all of them do not complete at the same time.
Using the NFS access method to access archives is suggested 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: It is required to make SD configuration changes to cope with a large number of concurrently
installing clients, see 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
Frequently asked questions 27