Task |
Description |
For Instructions |
---|---|---|
Create a sysidcfg file. |
Create a unique sysidcfg file for every system that requires different configuration information. Note that sample files are available to use. | |
Create a profile for networked systems. |
When setting up a hands off installation for systems on the network, you need to create a directory on a server that is called a JumpStart directory. This directory can be created on the installation server. The JumpStart directory contains system configuration information that is required to complete a hands off installation of the Solaris software. |
How to Create a JumpStart Directory on a Server |
Create a rules file. |
Create the rules file for each group of systems on which you want to install the Solaris OS. Each rule distinguishes a group of systems that are based on one or more system attributes. Each rule also links each group to a profile. A profile is a text file that defines how the Solaris software is to be installed on each system in the group | |
Use the add_install_client command to set up each system you want to install from the network. Each system you want to install needs to find the installation server, the boot server if required, and configuration information about the network. Note that the procedure for adding systems to be installed from the network is the same for both CD and DVD media. |
How to Add Systems to Be Installed From the Network With add_install_client |
The tasks in the preceding table must be completed before installing the Solaris OS on the client systems. Preconfiguration can help you avoid being prompted by the system for this information when installing the Solaris OS. Information that is provided is specific to creating a sysidcfg file for a Solaris OS installation on IBM BladeCenter servers. For complete syntax rules and information about creating a sysidcfg file in other Solaris OS installation situations, refer to the full set of Solaris OS installation documentation at http://docs.sun.com.