Setting up the JumpStart environment for provisioning

This section describes how to set up an Oracle Solaris JumpStart environment for use in BMC Server Automation provisioning.

Before you begin

• You must have a working JumpStart environment configured for and stocked with all the operating system installation files that you want to use to provision target computers. Your JumpStart environment can use one, two, or three physical servers for the boot, config, and install JumpStart services.
• For JumpStart environments that use DHCP, you must configure the DHCP server. See Configuring-the-DHCP-server.

To set up JumpStart

1. Each JumpStart server must be running version 7.4.x or later of the RSCD agent. For information on installing or upgrading the agent, see Installing only the RSCD agent (Linux and UNIX) or Upgrading RSCD agents. 

   Note

   For successful provisioning, an RSCD agent must be running on each of your JumpStart infrastructure computers (the boot server, the config server, and the install server). Each agent must be licensed for use with both NSH and BMC Server Automation.

2. On the computer that you are using for your JumpStart configuration server, create the following subdirectory under the root directory of the configuration server:
   /BladeLogic/rscd
    For example, if you created a directory called /configserver to act as the root directory of the configuration server, your directory structure is:
   /configserver/BladeLogic/rscd.
3. Extract the provision-files.zip file into a temporary directory.
    This file expands into a large number of files and subdirectories. Depending on which architectures you plan to provision, navigate to one or both of the following files:
   The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
   This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.
4. Copy the bmisolaris.tar/bmisolaris-x86.tar file to the BladeLogic/rscd directory that you just created.
5. Obtain the Solaris agent installer files. For example:
   RSCD820-GA-SOL8-SPARC.sh
   RSCD820-GA-SOL8-X86.sh
    You can download these files from the BMC Support site.
   These files install an RSCD agent on each target server that is being provisioned.
6. Rename the Solaris agent installer file. For example:
   • Rename RSCD820-GA-SOL8-SPARC.sh to rscd.sh.
   • Rename the RSCD820-GA-SOL8-X86.SH file to rscd-sol-x86.sh.
7. Copy the renamed files to the newly created BMC BladeLogic/rscd directory.
8. Create a response file for the installation of the RSCD agent and store the response file in the newly created BladeLogic/rscd directory. The response file is called nsh-install-defaults.
    For information about creating an nsh-install-defaults file, see Creating an installation defaults file for Linux or UNIX agents.
9. Confirm that the BladeLogic/rscd directory on the configuration server contains the following files:
   bmisolaris.tar
   bmisolaris-x86.tar
   rscd.sh
   rscd-sol-x86.sh
   nsh-install-defaults
10. Copy the check file from the JumpStart installation server to the root directory for the JumpStart configuration server.
     When you set up the JumpStart installation server, the JumpStart setup process creates a file called check, and places it in a directory structure whose higher level subdirectories reflect the names of the relevant operating system.
    For example, the directory structure for a set of Solaris version 10 install files is install_root/solaris10/Solaris_10/Misc/jumpstart_sample.
    Regardless of the higher level directory names (for example, for Solaris 8, Solaris 9, and so on) the lower level Misc/jumpstart_sample subdirectory contains the file that you want to copy (check ).
    Copy this check file into the root directory for the JumpStart configuration server. In this example, you copy the check file into the /configserver directory.