Solaris 10 Installation Guide for IBM BladeCenter Servers

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 installation server or a boot server. The profile server can be also be a separate server. The profile server can provide custom JumpStart files for different platforms.


Note –

After you create a profile server, you must enable all systems access to the server. For detailed instructions, see How to Enable All Systems to Access the Profile Server.


ProcedureHow to Create a JumpStart Directory on a Server

The JumpStart directory contains all of the essential custom JumpStart files, for example, the rules file, the rules.ok file, and profiles. You must save the JumpStart directory in the root (/) directory of the profile server.

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.

  1. On the server on which you want to create the JumpStart directory, log in as superuser.

  2. Create the JumpStart directory anywhere on the server.


    # mkdir -m 755 jumpstart-dir-path
    

    where 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
    
  3. 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
    
  4. Share the JumpStart directory by typing shareall. Press Enter.

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

    • If no, go to Step 8.

    • If yes, depending on the type of software media you are using, do one of the following:

      • At least the Solaris 10 1/06 Operating System DVD or the Solaris 10 1/06 Software – 1 CD

        Insert the CD into the server's CD-ROM drive.

        Solaris Volume Manager automatically mounts the CD.

      • Image of at least the Solaris 10 1/06 Operating System DVD or the Solaris 10 1/06 Software – 1 CD

        Change directory to the location of the Solaris Operating System DVD or the Solaris Software – 1 image.

        For example, type:


        # cd /export/install
        
  6. Copy the sample custom JumpStart files into the JumpStart directory on the profile server.


    # cp -r media-path/Solaris_Solaris_10.1/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 sample custom JumpStart files.

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


    cp -r /cdrom/cdrom0/s0/Solaris_Solariss_10.1/Misc/jumpstart_sample/* /jumpstart
    
  7. Update the sample 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 access to the profile server.

    For detailed instructions, see How to Enable All Systems to Access the Profile Server.