In the system configuration file, you can direct the WAN boot installation programs to the following files.
sysidcfg file
rules.ok file
Custom JumpStart profile
WAN boot follows the pointers in the system configuration file to install and configure the client.
The system configuration file is a plain text file, and must be formatted in the following pattern.
setting=value
To use a system configuration file to direct the WAN installation programs to the sysidcfg, rules.ok, and profile files, follow these steps.
Assume the same user role as the web server user on the WAN boot server.
Create a text file. Name the file descriptively, for example, sys-conf.s9–sparc.
Add the following entries to the system configuration file.
This setting points to the flash directory on the install server that contains the sysidcfg file. Make sure that this URL matches the path to the sysidcfg file that you created in Creating the sysidcfg File.
For WAN installations that use HTTPS, set the value to a valid HTTPS URL.
This setting points to the Solaris Flash directory on the install server that contains the rules.okfile, profile file, and begin and finish scripts. Make sure that this URL matches the path to the custom JumpStart files that you created in Creating the Profile and Creating the rules File.
For WAN installations that use HTTPS, set the value to a valid HTTPS URL.
Save the file to a directory that is accessible to the WAN boot server.
For administration purposes, you might want to save the file to the appropriate client directory in the /etc/netboot directory on the WAN boot server.
Change the permissions on the system configuration file to 600.
# chmod 600 /path/system-conf-file |
Specifies the path to the directory that contains the system configuration file.
Specifies the name of the system configuration file.
In the following example, the WAN boot programs check for the sysidcfg and custom JumpStart files on the web server https://www.example.com on port 1234. The web server uses secure HTTP to encrypt data and files during the installation.
The sysidcfg and custom JumpStart files are located in the flash subdirectory of the document root directory htdocs.
SsysidCF=https://www.example.com:1234/htdocs/flash SjumpsCF=https://www.example.com:1234/htdocs/flash
In the following example, the WAN boot programs check for the sysidcfg and custom JumpStart files on the web server http://www.example.com. The web server uses HTTP, so the data and files are not protected during the installation.
The sysidcfg and custom JumpStart files are located in the flash subdirectory of the document root directory htdocs.
SsysidCF=http://www.example.com/htdocs/flash SjumpsCF=http://www.example.com/htdocs/flash