Setting up Solaris provisioning

Step 1: Set up the environment

Perform one of the following set up procedures, depending on the option you are using (JumpStart or Automated installer):

To set up a Solaris JumpStart environment

JumpStart is supported in Solaris 10 and earlier versions. Before you begin setting up the JumpStart  environment:

• 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-a-DHCP-server-on-Windows and Configuring-a-DHCP-server-on-Linux

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

_{Back to top}

To set up the Automated Installer environment

AI is supported in Solaris 11 and later versions. Before you begin setting up the environment:

• You must have a working AI environment configured for and stocked with all the operating system installation files that you want to use to provision target computers.
• Each AI server must be running version 8.3 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 .
• For AI environments that use DHCP, you must configure the DHCP server. See Configuring-a-DHCP-server-on-Windows and Configuring-a-DHCP-server-on-Linux  

To setup AI:

1. On the computer that you are using for your AI 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

2. 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: 
   
   

   SPARC	bl_8.1.0/provisioning/jumpstart/bmisolaris.tar
   x86	bl_8.1.0/provisioning/jumpstart/bmisolaris-x86.tar

3. Copy the bmisolaris.tar/bmisolaris-x86.tar file to the BladeLogic/rscd directory that you just created.
4. 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.
5. 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.  
6. Copy the renamed files to the newly created BMC BladeLogic/rscd directory.
7. 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 .
8. Confirm that the BladeLogic/rscd directory on the AI server contains the following files:
   
   bmisolaris.tar 
   bmisolaris-x86.tar 
   rscd.sh 
   rscd-sol-x86.sh 
   nsh-install-defaults
9. Create a local repository on the AI server with the folder name as solaris on any desired path. 
   For example: /repo/publisher/solaris. 
   Publish the repository with the name as solaris.

_{Back to top}

Step 2: Configure the data store properties

Perform one of the following set up procedures, depending on the option you are using (JumpStart or Automated installer):

To configure the data store - JumpStart properties

Configuring the data store sets required values for accessing the data sources for provisioning.

In particular, you define the location of the data store, which is where you store sets of installation files that are used for provisioning operating systems. Data store values are stored in the Data Store system object, which you can edit by using the Property Dictionary.

1. Select Configuration > Property Dictionary View.
2. In the Property Class Navigation panel at the left, open the Built-in Property Classes folder. Then open the DataStore sub-folder. Click Jumpstart DataStore.
3. In the right panel, click the Instances tab.
   A DataStore instance specifies the server that functions as a data store. You must create at least one instance of a data store. You can create more than one instance. For example:
   • One data store instance could contain files for provisioning Windows systems, and another instance could contain files for provisioning Linux systems.
   • For an enterprise WAN, you could create one data store instance to serve the London network segment, another to serve the New York network segment, and a third to serve the Tokyo network segment.
4. Create a data store instance. To configure a data store instance for JumpStart provisioning, set the following property values.

If all three JumpStart services (boot, config, install) are on the same partition of the same server, then set all three of the property pairs listed above to the same values. For example:

_{Back to top}

To configure the data store - AI properties

Configuring the data store sets required values for accessing the data sources for provisioning.

In particular, you define the location of the data store, which is where you store sets of installation files that are used for provisioning operating systems. Data store values are stored in the Data Store system object, which you can edit by using the Property Dictionary.

1. Select Configuration > Property Dictionary View.
2. In the Property Class Navigation panel at the left, open the Built-in Property Classes folder. Then open the DataStore sub-folder. Click AI DataStore.
3. In the right panel, click the Instances tab.
   A DataStore instance specifies the server that functions as a data store. You must create at least one instance of a data store. You can create more than one instance. For example:
   • One data store instance could contain files for provisioning Windows systems, and another instance could contain files for provisioning Linux systems.
   • For an enterprise WAN, you could create one data store instance to serve the London network segment, another to serve the New York network segment, and a third to serve the Tokyo network segment.
4. Create a data store instance. To configure a data store instance for AI provisioning, set the following property values.

Step 3: Configure a system package type for Solaris provisioning

1. In the menu bar, select Configuration > Provisioning Configurations.
2. To configure or change the information for a system package type, select the type in the list and click Edit. To add a new system package type, click Add.

3. Complete the configuration window that appears.

   Click here to see descriptions of the fields in the configuration window.

   The System Package Types configurations window lets you add a system package type or change configuration information for the Solaris system package type.

   Field definitions

   WAN boot	Check this option to use the system package type with the WAN boot installation method to provision Solaris over a public network to Sparc target servers.
   Solaris 11	Select this option if you want to configure a Solaris 11 system package type.
   Solaris architecture	The type of machine you plan to provision with this system package type.
   WAN Boot Parameters (WAN Boot only)
   System package type	Name of the system package type.
   Archive location	Path to the Solaris Flash archive on the install server, relative to the install server document root directory.
   Miniroot location	Path to the miniroot file on the boot server, relative to the boot server document root directory.
   WAN Boot location	Path to the wanboot installation program on the boot server, relative to the boot server document root directory.
   OS Installation Configuration (options not applicable for WAN Boot)
   System package type	Name of the system package type.
   Service Name (Solaris 11 only)	Select the AI Server which could be an AI datastore. Select a service from the drop-down list for the selected AI server.
   Repository Path (Solaris 11 only)	Relative path to the repository.
   Installer location	Relative path to the Tools directory of the installer tree. The location you specify should be relative to the data store install server root. Example for Solaris 10 If the full path to the Tools directory is /jumpstart/solaris10/Solaris10 (meaning there exists a Tools directory under /jumpstart/solaris10/Solaris10) and the install server root is set up as /jumpstart, then enter solaris10/Solaris10. Example for Solaris 11 If the full path to the Tools directory is /ai/solaris11/Solaris11 (meaning there exists a Tools directory under /ai/solaris11/Solaris11) and the install server root is set up as /ai, then enter solaris11/Solaris11.
   RSCD Installer Configuration (option not applicable for WAN Boot)
   Installer Location	Path to the RSCD installer.

   Where to go from here

    System-package-panels-generic

4. When you finish adding or editing system package types, click OK on the System Package Types tab.

Step 4: Create a system package for Solaris provisioning

In the Depot, create one or more folders for your system packages.

1. In the Depot, right-click the folder where you want to add a new system package. From the pop-up menu, choose New > System package.

2. Provide information for the new system package, as described in the following sections: 

   Panel	Description
   System Package Creation - General	The General panel lets you provide information that identifies the system package, including the type of operating system. Field Definitions Name Enter an identifying name for the system package. This name appears in the Depot. Description (Optional) Enter descriptive text for the system package. Member of Verify the folder in the Depot under which this system package belongs. To change the displayed folder name, click Browse . System Package Type Select the type of operating system that you want this system package to install. The system package type controls which options and tabs are available when you open the system package to define the installation settings. Where to go from here System-Package-Creation-Properties
   System Package Creation - Properties	The Properties panel provides a list of properties automatically assigned to a Snapshot Job. In this list, you can modify the value of any properties that are defined as editable. For any property that has a check in the Editable column, select the property and click in the Value column. To set a property value back to its default value, click Reset to Default Value . The value of the property is reset to the value it inherits from a built-in property class. The Value Source column shows the property class from which the value is inherited. Depending on the type of property you are editing, you can take different actions to set a new value, such as entering an alphanumeric string, choosing from an enumerated list, or selecting a date. To insert a parameter into the value, enter the value, bracketed with double question mark delimiters (for example, ??MYPARAMETER??) or click Select Property . Where to go from here System-Package-Creation-Permissions
   System Package Creation - Permissions	The Permissions panel is an access control list (ACL) granting roles access to this system package. ACLs control access to all objects, including the sharing of objects between roles. Using the Permissions panel, you can add individual permissions to the system package. You can also set permissions by adding ACL templates. Task Procedure Adding an authorization An authorization grants permission to a role to perform a certain type of action on this object. To add an authorization to this object, click  in the Access Control List area. Then use the Add New Entry dialog box to specify the role and authorization you want to add. Adding an ACL template An ACL template is a group of predefined authorizations granted to roles. Using an ACL template, you can add a group of authorizations to this object. To add an ACL template to this job, click  in the Access Control List area. Then use the Select ACL Template dialog box to specify an ACL template that you want to add to this object. If you want the contents of the selected ACL templates to replace all entries in the access control list, check Replace ACL with selected templates. If you do not check this option, the contents of the selected ACL templates are appended to any existing entries in the access control list. Where to go from here System-package-panels-OS-specific

3. Click Finish. The system package opens in the content editor.

4. Define settings in the system package using the tabs at the bottom of the content editor. Each OS type has a different set of tabs.

   Panel	Description
   Basic configuration - HP-UX	The Basic Config tab lets you provide local information about a server, such as its name and the password needed to access the machine. Field Definitions Computer Name A unique name that should be assigned to the server. Type the name or click Select Property to insert a parameter that refers to a local property to supply the value for this field. OM Server Name You can choose a different name for this server to display when it appears in the BMC Server Automation Console. If you want this server to appear with a different name, enter that name in the OM Server Name text box. (Make sure that this new name can be resolved to the IP address of the server.) Type the name or click Select Property to insert a parameter that refers to a local property to supply the value for this field. If you want this server to display its Computer name when it appears within the BMC Server Automation Console, leave the OM Server Name text box blank. Root password Type the password used to access the root account. Confirm password Type the password again to confirm it. Proceed to the Disk-partition-HP-UX tab.
   Disk partition - HP-UX	The Disk Partition tab lets you define partitions for the servers being provisioned. You can use the default Ignite disk partitioning, or specify your own disk partitioning script: To use the default disk partitioning configuration associated with this system package type, click Use Default Disk Partition. To provide your own script for disk partitioning, click Use Custom Disk Partition. Then type the script into the box, or click Select Property to use a property to reference the script. Proceed to the Computer-settings-HP-UX tab.
   Computer settings - HP-UX	The Computer Settings tab lets you provide information about localization settings. Field definitions Timezone Select a time zone from the list. If the time zone you need is not on the list, check Use parameter or specify an unlisted timezone. Use parameter or specify an unlisted timezone Check this option if the time zone you need is not on the list for Timezone. The drop-down list changes to a field. In the Timezone field, type the name of a time zone or click Select Property to insert a parameter. (If you created a property for the unlisted time zones, you can insert a parameter that references this property.) Valid time zones for this field are contained in the directory: /usr/share/lib/zoneinfo This directory contains both file names and subdirectory names. If you see your time zone listed as a file in this directory, use the name of the file as the value for the Timezone field. If your time zone file is located in a subdirectory, specify the relative path to the time zone file from the /usr/share/lib/zoneinfo directory, for example: America/New_York Keyboard Select a keyboard map from the list. If the keyboard you need is not on the list, check Use parameter or specify an unlisted locale for the keyboard map. Use a parameter or specify an unlisted locale *for the keyboard map* Check this option if the keyboard you need is not on the list for Keyboard. The drop-down list changes to a field. In the field, type the name of a keyboard map or click Select Property to insert a parameter that references a property you created for the unlisted keyboard map. For information about the keyboards supported in the HP-UX environment, consult the HP-UX documentation. Proceed to the Network-settings-HP-UX tab.
   Network settings - HP-UX	The Network Settings tab lets you provide networking information for a server. Note HP-UX does not support IPv6 addresses. Field definitions Obtain an IP address automatically Specifies that the network connection should obtain an IP address automatically from a DHCP server. Use the following IP address Specifies that the network connection should use a static IP address that you specify. If you choose this option, provide the following information: IP address Subnet mask Default gateway IP address The static IP address that the network connection should use. Subnet mask The subnet mask number, which is used to identify which segment of the network the server is on. Default gateway The address of the IP router that is used to forward traffic to destinations outside of the local network. Obtain DNS server automatically Specifies that the DHCP server should provide the addresses for DNS servers. Use the following DNS server address Specifies that you want to manually configure a DNS server. Select this option and enter an IP address for DNS Server. DNS server The IP address of the DNS Server. Hardware Address The MAC address of the server. Use Network Configuration Script Check this option to use a network configuration script. Type script into the box or click Select Property to use a property to reference the script. Proceed to the Ignite-commands-and-scripts-HP-UX tab.
   Ignite commands and scripts - HP-UX	Ignite scripts are shell scripts that the Ignite master runs on the client when the base operating system installation is finished. The Ignite Commands/Scripts tab lets you define Ignite scripts to customize the target machine's operating system before it reboots for the first time. To define an Ignite script, do one of the following: To define a new script, click Add . To modify an existing script, select the script in the list and click Update or Edit . A script dialog box appears. In the script dialog box: For Script Name, do one of the following: Type the name of the script. Type the name of a local property that contains a script name, enclosing the property name with double question marks. Click Select Property to display a drop-down menu of available properties. Select the property that contains the script name from the list. For Script Contents, do one of the following: Type the contents of the script. Type the name of a local property that contains a script, enclosing the property name with double question marks. Click Select Property to display a drop-down menu of available properties. Select the property that contains the script from the list. Click OK. Proceed to the Optional-Ignite-parameters-HP-UX tab.
   Optional Ignite parameters - HP-UX	The Optional Parameters tab lets you add parameter entries to Ignite configuration scripts. On this tab, you can add entries to the following scripts: Client parameters script Installation control parameters script Kernel parameters script Variables script To add entries to a script, do one of the following: Type your changes directly into the text box under the heading for that script. Type the name of a local property that contains a setting, enclosing the property name with double question marks. Click Select Property to display a drop-down menu of available properties. Select the property that contains the setting from the list. Proceed to the Software-selection-HP-UX tab.
   Software selection - HP-UX	The Software selection tab lets you install the default software from the Ignite depot. To install the default software from the Ignite depot, leave this tab blank. Otherwise, you can specify a script that installs a custom set of software. You can either type the script into the box, or use a property to reference the script. Proceed to the Boot-script-HP-UX tab.
   Boot script - HP-UX	The Boot script tab provides instructions to automatically reboot the target during provisioning. To specify a Boot script, type the script into the box, or use a property to reference the script. Proceed to the Post-install-configuration-HP-UX tab.
   Post-install configuration - HP-UX	The Post-Install Configuration tab lets you specify processes you would like to run after the operating system is installed on the server. On this tab you can: Choose to install a BMC Server Automation RSCD agent. An agent must be installed on every server that you want to manage using the BMC Server Automation Console or Network Shell. Choose to run a Batch Job. A Batch Job can sequentially run a series of other jobs that install software and perform additional configuration on the server. Specify the first script to run after the operating system is installed. This script runs before any post-install Batch Job that you specify. Field definitions Install RSCD agent Check this option to install an agent on the server being provisioned. (An agent must be installed on every server you want to manage using the BMC Server Automation Console or Network Shell.) Push ACLs Check this option to push the ACLs defined for the server in the BMC Server Automation system to the RSCD agent you are installing on the server. Selecting this option automatically translates the permissions you have defined for the server in the BMC Server Automation system into a users configuration file on the RSCD agent. In this way, you control users' access to the server not only through the BMC Server Automation Console but also through Network Shell and the BLCLI. Run post-install batch job Check this option to run a post-install Batch Job that can install software and configure the server. Then for Path to post-install job, enter the path to the job or Browse to select it. In order to check Run post-install batch job, you must also check Install RSCD agent, because running a post-install job requires that there is an agent installed on the server. If you specify a Post-install Batch Job, make sure that the provisioning operator who runs the provisioning wizard logs is using a role that has Read and Execute authorizations on the Batch Job and has Read and Execute authorizations on all the Jobs contained in the Batch Job. Force Post-install Batch Job Select this option to ensure that the post-install Batch Job runs, even if RSCD agent enrollment fails. If you do not select this option, the post-provisioning Batch Job does not execute if RSCD agent enrollment fails. For example, if you use DNS, the RSCD agent enrollment cannot succeed until a DNS entry for the target server is provided. If you want to provide the DNS entry using a script in the Batch Job, you need the Batch Job to run even when the RSCD agent enrollment fails. Post-install Script Specify the first script you want to run after the operating system is installed. Enter the script in the box or click Select Property to use a property to reference the script. This script runs before any post-install Batch Job that you specify. Proceed to the Local-properties-HP-UX tab.
   Preview - HP-UX	The Preview tab lets you examine the customizations that you made to the complete configuration, software selection, other configuration, disk partition, and network configuration script files. The tab displays the contents of the following files: Complete configuration script Software selection script Other configuration script Disk partition script Network configuration script This panel is display only.
   Local properties - HP-UX	The Local Properties tab lets you add properties to an individual system package and modify its existing properties. Do one of the following: If you are adding a new property, click Add . If you are modifying an existing property, right-click the name of the property and click Edit from the drop-down menu. Then use the property dialog box to add or modify a local property. Proceed to the Preview-HP-UX tab.

   Tip

   When defining a system package, note the presence of the Select Property icon  next to various input fields. This icon indicates that you can insert a parameter that refers to a local property to supply the value for the field. For information on inserting a parameter, see Inserting a parameter in a system package field and Inserting a script in a system package. For an example of how using parameters can streamline provisioning, see Assigning-configuration-values-during-device-import.

5. When you finish defining the system package, select File > Save.

_{Back to top}

Where to go from here

Setting-up-provisioning-jobs-and-post-provisioning-jobs