Ignite-UX Custom Configuration files

The re
sult is the estimated number of hours to install a system. Please note that these calculations
are only intended to illustrate that the time it takes to install a system is impacted by: 1) the size of
the data to be installed by SD, 2) the number of systems running concurrently, and 3) the speed of
the connection. The calculation is not intended to tell you exactly how long it takes to install an
actual system.
An understanding of the network topology between the Ignite server and the systems being installed
is important. If the Ignite server has a Gigabit Ethernet interface connected to a Gigabit Ethernet
switch port, but is connected to the installing systems via a 100BT link between switches, the Ignite
server will never achieve more than 100BT speeds in total to all of those clients.
Careful consideration should be given to your network topology as it can impact on network
throughput significantly.
Installation configurations using golden images
It is important to look at how to create the cfg clause used for a golden image installation in the
INDEX file.
Golden image configuration file explanation
Provided with Ignite-UX is a configuration file that you can use to define a golden image
installation. This file is /opt/ignite/data/examples/core11.cfg and the following is an
example of this file:
########################################################################
##
## Filename: core11.cfg (template for B.11.* systems)
##
## @(#) core11.cfg $Revision: 10.10 $
##
## Description:
## This is an sample configuration file that enables an OS archive
## to be installed via Ignite-UX.
##
## Before Ignite-UX can use an OS archive like that created by
## make_sys_image(1M), the following must be done:
##
The instructions for how to use this config file are actually located in it as comments (see below).
## - Make an OS archive of the desired system using
## /opt/ignite/data/scripts/make_sys_image
## (see make_sys_image(1M) for details).
##
## - Determine if you want to use ftp, NFS, or remsh to access
## the OS archive (stored on the Ignite-UX server).
##
## - Make a copy this sample configuration file.
##
## - Edit your copy of this configuration file and modify:
## - The IP addresses of the Ignite-UX server.
## - The paths to OS archives.
## - The sw_sel keyword descriptions.
195