Ignite-UX functions through a client-server system. Much of
the server setup process will be performed for you in the Ignite-UX
installation process, but there are also some separate steps you
must take after installation. Tools are supplied to help you complete
the server setup. The following steps outline setting up or updating
the server:
Obtain access to a suitable system running HP-UX 10.x.
For information on upgrading from a 9.x
system to 10.x, please see the manual
Upgrading from HP-UX 9.x to
10.x.
If required, update with Extension Media from CD-ROM
(see Chapter 2 “Updating an Existing
Operating System and Software ”)
Install the Ignite-UX tools and data from the HP-UX
Applications
tape or CD-ROM, using the swinstall
utility.
If you are updating a 10.x system,
this may require running swgettools
first to update swinstall.
(See Chapter 2 “Updating an Existing
Operating System and Software ”)
The 11.0 bundle name is:
Versions that are on the DART Applications media will be labeled
B5724AA_APZ (Series 700) or B5725AA_APZ
(Series 800).
The release-specific bundles within these each contain
the filesets needed for installing a particular release to your
clients.It is recommended that you load one or more of these release-specific
bundles. They are designated as follows:
Ignite-UX-10-01
Ignite-UX-10-10
Ignite-UX-10-20
. . . |
You may load one or more of the Ignite-UX-10-XX
bundles onto your server depending on which releases of HP-UX you
plan on installing onto clients. That is, you can choose to load
a release-specific bundle, such as Ignite-UX-10-20,
or an entire bundle, such as B5724AA_APZ.
Installing Ignite-UX Software
Each software bundle contains the Ignite-UX tools plus the
data files required for support of the particular HP-UX release
indicated by the bundle name.
The Ignite-UX product replaces the capability previously supplied
by the NetInstall bundle that came with HP-UX releases 10.01, 10.10
and 10.20. (A system cannot be configured as a server for both NetInstall
and Ignite-UX.) Loading any of the Ignite-UX software bundles will
give an error until you remove the NetInstall bundle or touch the
file /tmp/okay_to_remove_net_install.
Once the application CD-ROM containing Ignite-UX has been
mounted, you may use the swinstall
command to load the desired Ignite-UX bundles. For example, the
command below would load the support needed for installing HP-UX
10.20 onto clients:
# swinstall -s /cdrom Ignite-UX-10-20 |
After the Ignite-UX bundle(s) has
been loaded, unmount and remove the media, and mount the media/drive,
if necessary, to load the CORE
software.
Set Up or Update CORE
Software.
Ignite-UX allows many options for installing software on the
target system. The most basic option is to install all software
from SD depots located on the server. Following is the procedure
for setting up the CORE
software on the server.
Setting up the software for the OS installation can be done
with the help of the add_release
tool. This tool can also be used interactively to add new releases
to the server and to remove old ones.
If you plan to use both SD sources and non-SD sources (tar,cpio,
or pax), it will
be necessary to consider each individually.
For SD OS software:
Run the add_release
tool to load the software release(s) you wish to install on the
target systems. The add_release
tool will add a new software release to an Ignite-UX server by creating
SD depots for that software. See the add_release(1M)
man page for more details.
To run add_release
to test what it would do, without actually modifying anything, you
can specify the -p
option (preview mode), as follows. For example:
# /opt/ignite/bin/add_release -s /dev/dsk/c0t2d0 -p |
To use a depot other than /dev/dsk/c0t2d0
to read the software, you can specify the depot with the -s
option.
For example, the following would apply if you already have
an OS depot, or you have made modifications to it. Then you can
use the make_config
and manage_index
commands to generate a configuration file. For example:
# make_config -s server:/depot_700 \
-c /var/opt/ignite/data/Rel_B.10.20/core_700
# manage_index -a -f /var/opt/ignite/data/Rel_B.10.20/core_700 |
See the ignite(5) man page for further
examples.
For non-SD OS software:
If the source is not an SD depot (i.e., it is an
archive image), then the add_releasecommand is not applicable.
You will need to create a unique config file that represents
the non-SD operating system software. A sample of a config file
that does a core archive can be found at the following location:
/opt/ignite/data/examples/core.cfg |
After copying this file and making edits to it as instructed
in the comments contained in the file, you can use the manage_index
tool to insert a reference to this configuration in the following
location:
Add additional applications (optional)
If you have other software that you would like to pull during
your install and want to have the software made available for selection
in the Ignite-UX UI, run the make_config
and manage_index
tools on those depots. If the contents are not 700/800 specific,
then the -a[78]00
option should not be used.
 |
| |
|
 | NOTE: Do
not attempt to use non-core-OS archives (i.e. layered applications)
that contain files that get loaded in/var/adm/sw/*
. Shipping files in this directory in this method may corrupt the
software distributor database. |
|
| |
|
For SD application software
For non-SD application software:
If the source is not an SD depot, the make_config
command is not applicable. You will need to create a unique config
file that references the non-SD software. A sample of a config file
that does a non-core archive can be found at the following location:
/opt/ignite/data/examples/noncore.cfg |
Copy this file first to /var/opt/ignite/data/Release/configx.
Then make the changes to the copy in that directory.
After copying and editing this file, you can use
manage_index
to insert a reference the copy of the configuration in the following
location:
Starting the Ignite-UX Server |
|
Run ignite
to complete the configuration and to start the server process. Type
the following:
This will start the Ignite-UX server.
Complete the Configuration:
After you have Ignite-UX up and running, you will see the
Welcome screen and then the Ignite-UX Server GUI. When you have
booted the clients you will see client icons on the Server GUI.
These can be manipulated as follows:
Click once on a client icon to select
it for further actions.
Click twice on the client to get a Client Status
screen.
Click the right mouse button
(Mouse Button Three) on the selected client icon to get an Actions
screen similar to the pulldown Actions menu.
Server Configuration: Server Options.
This allows the OS product configuration to be selected, along
with the default printer configuration, client timeout allowance,
and where the client interface will be booted from and displayed.
Server Configuration: Session Options.
This configures general interaction behavior for the client
sessions.
Details for these screens are on the following pages.
Configuring Server Options |
|
The fields in these tabs ("Server Options" and "Session Options")
serve to identify and set up your installation server, and to configure
the IP source address range to be used for initially booting the
install clients (target systems) and the DHCP address range to be
used for directing the client installation process. You will see
the following screen after selecting: Options --> Server Configuration.
The Server Options Tab
Select on Default Configurations,
highlight the one you want to use from the list. When doing a client
installation, this configuration will be installed on targets if
no other is specified. (The default setting can be overridden on
a per-client basis by Ignite-UX).
Click on the selection list to display the available
(configured) printers. Select the one you want to use.
If necessary, use the SAM → Printers and Plotters
area to configure a new printer onto the system.
This will be the printer for printing the manifest or installation
history. The printer address will be checked by Ignite-UX before
a job is sent.
Select the appropriate Client Timeout time, or "Off",
to set the time limit for the client to be connected without responding.
(This will set a limit on the time since the client install log
has been written in. Fifteen to thirty minutes may be required at
some points in the installation.) A warning note will be displayed
if this time is exceeded.
Setting Client Timeout to "off" disables this notification.
To use Add Booting IP Addresses..., see the following
section.
Adding Booting IP Addresses...
If you clicked on Add Booting IP Addresses..., in Figure 4-2 “Title not available (Configuring Server Options )”, you would get the following
screen.
Booting Clients
This screen allows you to enter appropriate values to use
for IP addresses for the initial boot of the target systems. The
number of such addresses determines the number of simultaneous installations
you can do.
First, ensure that these IP addresses are not assigned elsewhere.
These IP addresses are used to initially boot the target systems.
They are used until the system is assigned one of the DHCP-assigned
boot addresses. One address is required for each simultaneous boot.
Typically one to three are needed, depending on your usage.
This data can also be configured from a command line by using
the tool setup_server(1M) for this procedure.
Or you can directly edit the instl_boottab
file; this is necessary in order to modify the listing of existing
IP addresses.
See the instl_bootd(1M) man page for
further details.
DHCP Address Range
First ensure that these IP addresses are not assigned elsewhere.
These IP addresses are used during the OS download and application
loading. The addresses are in use for most of the Ignite-UX download
to a target machine. One address is required for each simultaneous
download. You should set more, if the addresses are assigned permanently.
You would click the "Temporary" box in case
you would like to manage a
small group of temporary IP
addresses, just for use in doing
installations, and then
reassign the clients new addresses when they are
deployed.
The provision of DHCP capability is for the purpose of installation
only and you may want to limit configurations so that they do not
interfere with prior DHCP server functions.
Also see Appendix A “Configuring for a DHCP Server ”
for examples of usage. See the setup_server(1M)
and instl_adm(4) man pages for more information
on setting up DHCP functions, addresses and class IDs.
Server Session Options Tab
The Session Options tab displays a number of check boxes to
configure client response behavior.
Confirm New Clients:
This check box, if set, results in the appearance of a dialog
screen each time a new client is booted from the Ignite-UX server.
Ask for customer information during client installation:
If you do not want to see the form for "Customer Name", "System
Serial #", and "Order Number" select the button to disable their
display.
Show Welcome Screen for the Install Server:
Select the button to enable or disable the automatic display
of the welcome screen for the install server.
This welcome screen is a useful default if many new operators
run the Ignite-UX server.
Halt the client after installation:
Select this button to cause the client system to halt (rather
than reboot) after installation.
Automatically move completed clients to history:
Select this button to automatically add completed clients
to the end of the history log, /var/opt/ignite/clients/history/history.log.
It will also move their config and manifest files to history for
future reference. The client icon will be removed from the Server
screen. The client must be complete
(fully installed) for this to take place.
If the client systems are prepared and booted, you
can skip to Chapter 5 “Installing from the Ignite-UX Server” for the procedures for using
the server with the client systems.
Preparing the Clients for Installation
Boot the Series 700 or Series 800 client system that supports
network boot by entering the appropriate command on the console
for that client.
Note that, if a client with a known IP address is already
running HP-UX, you can use the bootsys(1m)
command from the Ignite-UX server to install it with specific configuration,
without further interaction.
See the exact boot ROM commands for manual booting of your
system in “Booting Client Systems from the Network”.
If the client cannot find the server, check the following
items:
Client is on the same subnet as the
server.
Any instl_bootd errors in /var/adm/syslog/syslog.log.
Your /var/adm/inetd.sec
file to make sure that IP address 0.0.0.0
is not being disallowed.
If /etc/services
comes from NIS, make sure that the NIS server has instl_boot*
entries.
The daemon rbootd
is running.
The icons for all clients booted from the Ignite-UX server
should now appear on the Ignite-UX interface. If the server has
not been set up completely, or if the client could not obtain enough
networking parameters via DHCP, then the client may require interaction
on the client console.
You can now proceed with using the Ignite-UX interface (“Installing from the Server ”).
For More Information
See Appendix B “Using Configuration Files”for
the details of setting up configuration files for Ignite-UX.
For more details about server configuration and "golden disks",
see the "Ignite-UX Startup Guide for System Administrators" and
"Ignite-UX Cold Installations", both on your Ignite-UX server system
in /opt/ignite/share/docs/.
Printable version
