Ignite postinstall help

[Doug Van tol]

Hello all,

I'm attempting to use Ignite to make 3 idententical systems, with the only
exception being the hostname and ip address. I tried having the post install
script update the /etc/rc.config.d/netconf file by querying the system name
from the user. The script creates a copy of the netconf file and then attempts
to copy it back over the original. I made sure I changed the permissions on
the file to allow write access. The new netconf file is generated, however, it
seems to get overwritten by the file contained in the archive. I have tried
changing the post load script in the netconf section to no avail. Any
suggestions would be greatly appreciated.

Thanks in advance,

Doug

[Carlos Riera]

Hi:

You have two posibilities:

1- Dont make anything. At instalation time select advanced install from first
menu.

On system tab you can configure hostname and ip address or select ask for them
after reboot.

2- Edit CONFIG file and set following parameters:

system_name="xxxxx"
ip_addr[]="xxx.x.xxx.xx"
netmask[]="255.255.255.0
route_gateway"xxx.x.xxx.xxx"
route_destination[0]="default"

Then make differents tapes for each server.
See instl_adm(4). instl_adm is a language so you can program to do just a tape.


I like first option because it is simple, but in real work I had used then
second.

[Doug Van tol]

Thanks Carlos,

I currently have the second method implemented. I am really looking for a way
to prompt the installer (customer) for the system name and then have the system
configure itself corrently based on the name. I was trying to implement this
method without the GUI interface. Now I'm not sure if that is possible.

Doug

[Carlos Riera]

Helo again:

I have instaled about 20 remote servers just telling to end users how to boot
from the DAT.

Previously i had send them a DAT and a CD.

CD was duplicated copies from Ignite cold instalation.

DAT was generated with the information for each server. DATs only contains Boot
system and a CONFIG file in it with, also generated by ignite make_medialif.


Before i Had copy with dd the LIF_VOLUME generate by iginte:

dd if=/dev/rmt/0m of=/tmp/LIF_DAT bs=2k

PARAMETER FILE ( server_xx):
_______________-


run_ui=false
control_from_server=false
disable_dhcp=true
server="xxx.xx.xx.xx"
# instl_adm defaults:
server="xxx.xx.xx.xx"
system_name="XXXXX"
ip_addr[]="xxx.x.xx.xx"
netmask[]="255.255.255.0"
route_gateway[0]="xxx.x.xx.xxx"
route_destination[0]="default"
sysadm_message = " You will install
System XXXX IP XXX.XX.XX.X
"

_______________
#Apply parameter file (Server_xx)
instl_adm -f Server_xx -F /tmp/LIF_DAT

dd if=/tmp/LIF_DAT of=/dev/rmt/0m bs=2k

Of course, some parameter from CONFIG were changed to set CD as software
source.

It take a some work but , you ( and Ignite) can do it.

Regards.

[Jim Butler_4]

We use ignite to create clients for 10.10, 10.20, 11.00. Workstations, and have
the same need you do.
here are the steps that we follow:
1. - Create the desired image "golden image" as hp calls it, by going to the
"model" workstation and running 'make_sys_image' [man page avail.] (You will
need to trust the root client to the server - mod the /.rhosts file on the
server)
2. Once it is created, put it on a partition that is exported [/etc/exports]
and nfs available.
3. On the ignite server - edit the file /var/opt/ignite/INDEX to point to a
config file.
4. Edit the config file - there are examples if you follow a set up config file
from the orginal INDEX.
A sample of a config file that can be used with a core
archive can be found at:
/opt/ignite/data/examples/core.cfg
5. Run Ignite from the server and set the workstation up. If the clients are
on a separate subnet, then you will need to set up
6. Just ignite the workstation. I think I have detailed instructions around,
but the man pages are pretty good. Each system takes 40 minutes to load a 4Mb
OS (roughly ex-B180)