Ignite-UX functions as a client-server application. Much of
the server configuration 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 configuration.
Installing Ignite-UX will take care of most server configuration
tasks. This can also be done outside Ignite-UX by using either the setup_server command as a simple interface or by using the Ignite-UX screen,
as explained in this chapter.
Installation tasks
The tasks required to set up an Ignite-UX server are:
“A:
Obtain Ignite-UX Software ”
“B:
Install Ignite-UX Software ”
“C:
Update PATH”
“D:
Set Up or Update the Software Source”
“E:
Add Optional Applications ”
“F:
Installing Minimal Ignite-UX Filesets”
“G:
Start Ignite-UX for the First Time”
“H:
Set an Initial Ignite-UX Server Configuration”
“I:
Starting Ignite-UX”
“J:
Configuring Server and Session Options”
Before proceeding to install an Ignite-UX server, review the
server's hardware, software and networking requirements
explained next.
Ignite-UX
Hardware Requirements |
 |
|
| |
|
 | IMPORTANT: NFS Diskless functionality is not supported on
HP-UX 11.0 and later versions. Do not update your server to HP-UX
11.0 or later versions if you intend to operate that server as a
NFS Diskless server. |
|
| |
|
Server requirements
You will need the following to install an Ignite-UX server:
Computer — A
Series 700/800 system running HP-UX 10.0, 10.10, 10.20, 11.0 or
11i. See Ignite-UX version requirements in“Ignite-UX release versions”.
Memory — Ignite-UX
requires 64MB minimum on each server and client. Your HP support
engineer can assist in determining the proper amount of RAM.
Source Device — Make
sure that your system has an appropriate source (CD-ROM, DVD, DDS
drive or LAN card). Ensure that tape drive heads are clean.
Disk Drive — A server
needs at least one hard-disk drive with at least the following capacities
(swinstall performs an analysis of disk space needed prior to loading
the software):
Generally, 2 GB or more for a usable
system, 2.2 GB if on HP-UX 11.0 and 4GB if on HP-UX 11i.
Ignite-UX will be loaded under the directory /opt/ignite. The data files Ignite-UX creates will be placed under /var/opt/ignite. Ignite-UX installation will require approximately 105MB
of disk space. You will probably need additional space available
under /var/opt/ignite for archive and software depot storage.
tftp — Ignite-UX
will transfer some of its files using tftp. The minimum directories
needed by tftp are set up in the /etc/inetd.conf file. Others may need to be added if you place configuration
scripts in non-standard locations.
An additional X11 display server (workstation,
X-terminal, PC running an X server, etc). This can be the same system
as above.
A separate graphics display may be
required if a Series 800 Ignite-UX server is being used. Or:
The display can be redirected to another X-windows
system by setting the DISPLAY environment variable. For example, in the Korn
Shell or Posix Shell, enter:
export DISPLAY=system_name:0.0
Product media or link to the web to load Ignite-UX
and any software depots you plan to distribute to target systems.
Client and server must be on the same subnet if
you plan to do the initial boot of the client over the network.
A boot-helper system can be used to get between
subnets and the bootsys command also works between subnets. See Appendix B “Using
a Boot-Helper System”.
|
| |
|
 | NOTE: You can boot over the network only from an Ethernet
interface. |
|
| |
|
Printable version
