Creating a Profile Server for Networked Systems

When setting up JumpStart installations for systems on the network, you need to create a JumpStart directory on a server. The JumpStart directory contains all of the essential JumpStart files, for example, the rules file, rules.ok file, and profiles. You must save the JumpStart directory in the root (/) directory of the profile server.

The server that contains a JumpStart directory is called a profile server. A profile server can be the same system as an install server or a boot server, or the server can be a completely different server. A profile server can provide JumpStart files for different platforms. For example, an x86 server can provide JumpStart files for both SPARC based systems and x86 based systems.

Note - After you create a profile server, you must allow systems to access the server. For detailed instructions, see Using a Wildcard Entry to Allow All Systems Access to the Profile Server.

How to Create a JumpStart Directory on a Server

Note - This procedure assumes that the system is running Solaris Volume Manager. If you are not using Solaris Volume Manager to manage discs, refer to System Administration Guide: Devices and File Systems for detailed information about managing removable media without Solaris Volume Manager.

Locate the server on which you want to create the JumpStart directory.
Become superuser or assume an equivalent role.
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
Create the JumpStart directory anywhere on the server.
```
# mkdir -m 755 jumpstart-dir-path
```
In the command, jumpstart-dir-path is the absolute path of the JumpStart directory.
For example, the following command creates a directory that is called jumpstart in the root (/) directory and sets the permissions to 755:
```
# mkdir -m 755 /jumpstart
```
Add the following entry to the /etc/dfs/dfstab file.
```
share -F nfs -o ro,anon=0 jumpstart-dir-path
```
For example, the following entry shares the /jumpstart directory:
```
share -F nfs -o ro,anon=0 /jumpstart
```
Type shareall and press Return.

(Optional) Copy examples of JumpStart files to your JumpStart directory.

Access the installation disc or image.

Example Locations	Instructions
The Oracle Solaris Operating System DVD or the Oracle Solaris Software - 1 CD for your platform	Insert the Oracle Solaris Operating System DVD or the Oracle Solaris Software - 1 CD into the server's CD-ROM drive. Solaris Volume Manager automatically mounts the CD or DVD.
An image of the Oracle Solaris Operating System DVD or the Oracle Solaris Software - 1 CD for your platform on a local disk	Change directory to the location of the Oracle Solaris Operating System DVD or the Oracle Solaris Software - 1 image. For example, type the following command: cd /export/install

Copy the example JumpStart files into the JumpStart directory on the profile server.
```
# cp -r media-path/Solaris_10/Misc/jumpstart_sample/* jumpstart-dir-path
```
media-path

The path to the CD, DVD, or image on the local disk

jumpstart-dir-path

The path on the profile server where you are placing the example JumpStart files

For example, the following command copies the jumpstart_sample directory into the /jumpstart directory on the profile server:
```
cp -r /cdrom/cdrom0/Solaris_10/Misc/jumpstart_sample/* /jumpstart
```
Update the example JumpStart files so that the files work in your environment.

Ensure that root owns the JumpStart directory and that the permissions are set to 755.
Allow systems on the network to access the profile server.
For detailed instructions, see Using a Wildcard Entry to Allow All Systems Access to the Profile Server.

Allowing All Systems Access to the Profile Server

When you create a profile server, you must ensure that systems can access the JumpStart directory on the profile server during a JumpStart installation. Use one of the methods described in the following table to ensure access.

Command or File	Providing Access	Instructions
`add_install_client` command	Each time that you add a system for network installation, use the `-c` option with the `add_install_client` command to specify the profile server. Note - If you are not using NFS, then you must use another means to provide access. For SPARC based systems, use the `boot` command For x86 based systems, edit the GRUB menu. GRUB is a feature of Oracle Solaris.	For DVD media, see Adding Systems to Be Installed From the Network With a DVD Image in Oracle Solaris 10 1/13 Installation Guide: Network-Based Installations For CD media, see Adding Systems to Be Installed From the Network With a CD Image in Oracle Solaris 10 1/13 Installation Guide: Network-Based Installations
Specify the location of the JumpStart directory when you boot the system	For SPARC based systems, use the `boot` command to boot the system. Specify the location of the JumpStart directory on the profile server when you boot the system. You must compress the JumpStart configuration files into one file. Then, save the compressed configuration file on an HTTP or HTTPS server.	Creating a Compressed Configuration File Step 3 in SPARC: To Perform an Installation or Upgrade With the JumpStart Program
	For x86 based systems, specify the location of the JumpStart directory on the profile server when you boot the system by editing the boot entry on the GRUB menu. You must compress the JumpStart configuration files into one file. Then, save the compressed configuration file on an HTTP or HTTPS server. When you edit the GRUB menu entry, specify the location of the compressed file.	Creating a Compressed Configuration File x86: How to Perform an Installation or Upgrade With the JumpStart Program and GRUB
`/etc/bootparams` file or naming service bootparam database	Add a wildcard.

Using a Wildcard Entry to Allow All Systems Access to the Profile Server

You can use a wildcard entry to allow all systems access to the profile server only if you store network installation information in the following places:

In the /etc/bootparams file
In the naming service bootparams database

The systems must be of the same type, such as all SPARC systems.

Add the following entry to the file or database:

* install_config=server:jumpstart-dir-path

*: A wildcard character that specifies that all systems have access
server: The host name of the profile server where the JumpStart directory is located
jumpstart-dir-path: The absolute path of the JumpStart directory

For example, the following entry enables all systems to access the /jumpstart directory on the profile server that is named sherlock:

* install_config=sherlock:/jumpstart

Caution - Use of this procedure might produce the following error message when an installation client is booted:

WARNING: getfile: RPC failed: error 5: (RPC Timed out).

Booting From the Network, Error Messages in Oracle Solaris 10 1/13 Installation Guide: Network-Based Installations contains details about this error message.

All systems can now access the profile server.

Skip Navigation Links
Exit Print View
	Oracle Solaris 10 1/13 Installation Guide: JumpStart Installations Oracle Solaris 10 1/13 Information Library