Creating a Profile Server for Networked Systems

When setting up custom JumpStart installations for systems on the network, you need to create a directory on a server that is called a JumpStart directory. The JumpStart directory contains all of the essential custom 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 custom JumpStart files for different platforms. For example, an x86 server can provide custom 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 To Allow All Systems Access to the Profile Server.

To Create a JumpStart Directory on a Server

Note - This procedure assumes that the system is running removable media services. If you have questions about removable media services that manage discs, refer to System Administration Guide: Devices and File Systems for detailed information.

1. Locate the server on which you want to create the JumpStart directory.
2. 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.

3. 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

4. Use either the sharemgr utility or the share command as follows:

   ---

   Note - Starting with the 5/07 Developer release, the sharemgr utility introduces the concept of share groups. See sharemgr Command in System Administration Guide: Network Services.

   ---

   • Using the share command, edit the /etc/dfs/dfstab file by adding the following entry.

     # 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

     Then, type shareall and press Enter.

   • Using the sharemgr utility, enter the following commands:

     # sharemgr add-share -s /jumpstart default

     # sharemgr set -P nfs -S sys -p ro="*" -s /jumpstart default

     # sharemgr set -P nfs -p anon=0 -s /jumpstart default

5. Determine if you want to copy examples of custom JumpStart files to your JumpStart directory.

   • If no, go to Step 8.

   • If yes, use the following decision table to determine what to do next.

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

6. Copy the example custom JumpStart files into the JumpStart directory on the profile server.

   # cp -r media_path/Solaris_11/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 custom JumpStart files

   For example, the following command copies the jumpstart_sample directory into the /jumpstart directory on the profile server:

   • For SPARC based systems:

     cp -r /media/cdrom/s0/Solaris_11/Misc/jumpstart_sample/* /jumpstart

   • For x86 based systems:

     cp -r /media/cdrom/Solaris_11/Misc/jumpstart_sample/* /jumpstart

7. Update the example JumpStart files so that the files work in your environment.
8. Ensure that root owns the JumpStart directory and that the permissions are set to 755.
9. Allow systems on the network to access the profile server.

   For detailed instructions, see 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 custom JumpStart installation. Use one of the following ways to ensure access.

To Allow All Systems Access to the Profile Server

Use the following procedure only if you store network installation information in the following places:

• In the /etc/bootparams file.

• In the naming service bootparams database. To update the bootparams database, add the entry that is shown in Step 3.

If you use the following procedure, the systems must be of the same type, such as all SPARC systems.

Do not use this procedure under the following conditions:

• If you save the JumpStart directory on a diskette.

• If you specify the location of the profile server when you boot the system. If you have systems of different architectures, you must specify the location of the profile server when you boot the system

If you have the above conditions, use the SPARC boot command or use the x86 GRUB menu.

Note - You also can store network installation information on a DHCP server.

• For SPARC based systems, you use the add_install_client command and the -d option to specify that the custom JumpStart program use the DHCP server. Or you use the boot command with the dhcp option to specify that the custom JumpStart program use the DHCP server. For instructions about using this option, see SPARC: Command Reference for the boot Command.

• For x86 based systems, you use dhcp in one of the following ways:

  • If you use an install server, use the add_install_client command and the -d option to specify that the custom JumpStart program use the DHCP server with PXE.

  • You can edit the GRUB entry on the GRUB menu and add the dhcp option. For instructions about editing the GRUB entry, see x86: Performing a Custom JumpStart Installation by Editing the GRUB Boot Command

1. On the installation or boot server, log in as superuser.
2. Use a text editor to open /etc/bootparams.
3. Add this entry.

   * 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 contains details about this error message.

   ---

   All systems can now access the profile server.