1.Determine the MAC address of the client, either through the boot_admin commands at boot time or by using lanscan(1M) after the client is booted.
For more information, see boot(1M), efi(4), isl(1M), and pdc(1M).
2.Create the following directory, assuming the MAC address is 0x08000992E346: mkdir /var/opt/ignite/clients/0x08000992E346
3.Copy an example configuration file to be used as a starting point:
cp config /var/opt/ignite/clients/0x08000992E346/config
4.These files are accessed using NFS so you must ensure that the correct ownership and directory access permissions are assigned.
Set the client directory to 644 and change the ownership to ensure that bin can read and write to the directory:
chmod 644 /var/opt/ignite/clients/0x08000992E346 chown bin:bin /var/opt/ignite/clients/0x08000992E346 chown bin:bin /var/opt/ignite/clients/0x08000992E346/config
5.Edit your new configuration file to define your
6.Run bootsys on the
The client is booted and the operating system is installed without interaction using the
Scheduling installations
Client installations can also be automated using the cron daemon. To perform repeated installations for a client, you can use crontab entries. For more information, see cron(1M) and crontab(1).
For single installations, use the at command. For example, to perform an installation of a client at 8:00 PM using the at command, as root enter:
at 8:00pm
bootsys
Press
NOTE: This example requires remsh access from the
Setting installation parameters dynamically
This feature can make the configurations that you set up more general purpose and limit the need for multiple, custom configurations to handle minor system differences.
These decisions are specified in a
The following examples show how
Scheduling installations 177