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 the RSCD agent on Linux and UNIX and Upgrading the RSCD agent on Windows.

   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 TrueSight 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 <version>-provision-files.zip file (which you obtained from within the main product package that you downloaded from the EPD site) 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:

   Platform	File
   SPARC	bl_8.1.0/provisioning/jumpstart/bmisolaris.tar
   x86 systems	bl_8.1.0/provisioning/jumpstart/bmisolaris-x86.tar

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:
   RSCD86-SOL10-SPARC.sh
   RSCD86-SOL10-X86.sh
   This file is included in the Optional Components zip package, which you download from the BMC Software Electronic Product Distribution (EPD) website.
   These files install an RSCD agent on each target server that is being provisioned.
6. Rename the Solaris agent installer file. For example:
   • Rename RSCD86-SOL10-SPARC.sh to rscd.sh.
   • Rename the RSCD86-SOL10-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

Automated Installer (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 the RSCD agent on Linux and UNIX and Upgrading the RSCD agent on Windows .

• 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 <version>-provision-files.zip file (which you obtained from within the main product package that you downloaded from the EPD site) 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:

   Platform	File
   SPARC	bl_8.1.0/provisioning/jumpstart/bmisolaris.tar
   x86 systems	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:
   RSCD86-SOL10-SPARC.sh
   RSCD86-SOL10-X86.sh
   This file is included in the Optional Components zip package, which you download from the BMC Software Electronic Product Distribution (EPD) website.
   These files install an RSCD agent on each target server that is being provisioned.

5. Rename the Solaris agent installer file. 
   For example:
   Rename RSCD86-SOL10-SPARC.sh to rscd.sh.
   Rename the RSCD86-SOL10-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:

BOOT_SERVER = jumpstart2
BOOT_SERVER_FULL_PATH = /js
CONFIG_SERVER = jumpstart2
CONFIG_SERVER_FULL_PATH = /js
INSTALL_SERVER = jumpstart2
INSTALL_SERVER_FULL_PATH = /js

_{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 the job being created. 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
   Disk partition - Solaris	The Disk Partition tab lets you define partitions for the provisioned servers. The information you provide here becomes part of the JumpStart profile file (for Oracle Solaris 10 or earlier) or part of the Automated Installer (AI) profile.xml file (for Oracle Solaris 11 or later). There are two ways to define a partition — by supplying a script or using the wizard: To supply a script, click Use script for disk partitioning. Then do one of the following: Type the script directly in the input box. Type the name of a local property that contains the 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. For information, see Inserting a script in a system package. To use the wizard, follow this procedure: Select the type of partition to define: Explicit Partition, Default Partition, or Existing Partition. Note The Existing Partition option is available only for Oracle Solaris 10 or earlier. Take one of the following actions. If you are adding a new partition, a wizard appears. If you are editing an existing partition, a tabbed window appears. Both provide the same options. To create a new partition, click Add . To modify an existing partition, select the partition in the Disk Partition list and click Update or Edit  . Under Slice Configuration, select one of the following slice options and then click Next. Any — place the file system on any disk. Disk Slice — place the file system on the slice you specify here, using one of the following formats: c<w>t<x>d<y>s<z> — For example: c0t0d0s0 c<w>d<y>s<z> — For example: c0d0s0 Root Disk — Place the system's root disk on the slice (integer) you specify here. Under Size Options, select one of the following size options and then click Next. Existing — Use the current size of the existing file system. Auto — Determine the size of the file system based on the software you are installing on this server. All — Have this slice use the entire disk for the file system. If you choose All, you cannot place any other file systems on this disk. Free — Use the remaining unused space on the disk for the file system. Specify Size — Set the size of the file system to the value (in MB) that you specify here. Explicit Partition — Partition the file system explicitly, using the format: start:size where start is an integer specifying the cylinder where the slice begins, and size is the number of cylinders for the slice. Under File System Settings (Optional), select one of the following optional settings: Swap — Make this slice the swap slice. Overlap — Define this slice as a representation of a disk region. Unnamed — Define this slice as a raw slice without a mount point name. Ignore — Tell JumpStart or AI not to use or recognize this slice. Mount Point — Use this mount point name for the file system, for example /var. Under Optional Parameters, select one of the following: Preserve — Preserve the file system on this slice. Mount Options — One or more mount options for the mount point name you specified in Mount Point. Click Finish. The partition appears in the Disk Partitions list.
   Basic configuration - Solaris	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 The unique name that should be assigned to the server. Enter a name or use click Select Property to insert a parameter that refers to a local property to supply the value for this field. OM Server Name (Optional) Specifies a different name for this server to display when it appears in the TrueSight Server Automation Console. Enter a name or use 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 in the TrueSight Server Automation Console, leave the OM Server Name field blank. If you do choose to use a different OM Server Name for this machine, make sure that this new name can be resolved to the IP address of the server. Root password The password used to access the root account. Enter a password. Then confirm your typing by entering the password again in the Confirm password field. Specify install type (Optional) Check this option and then use the drop-down menu to select Initial Install or Flash Install. Note that if you do not specify an install type here, you must do so on the Additional Profile Entries panel. Proceed to the Computer settings - Solaris 10 and earlier versions tab.
   Computer settings - Solaris	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. Important: TrueSight Server Automation does not support the TZ environment variable to set time zone. Functioning of TrueSight Server Automation might be impacted by this variable. 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 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 System Locale Select the character encoding scheme you want to use for your language. If the encoding scheme you need is not in the drop-down list, check Use a parameter. Use a parameter or specify an unlisted system locale Check this option if the character encoding scheme you need is not on the list for System Locale. The drop-down list changes to a field. Type in an encoding scheme or click Select Property to insert a parameter. (If you created a property for the unlisted encoding scheme(s), you can insert a parameter that references this property.) For information about system locales supported in the Solaris environment, see the Oracle documentation. Proceed to the Network - Solaris tab.
   Network - Solaris	The Network tab lets you provide networking information for a server, such as its IP configuration settings and name service. Field definitions Enable networking on the Primary interface Check this option if you want this machine's primary interface to connect to the network. Initialize the Primary interface using DHCP Specifies that the network connection should obtain an IP address automatically from a DHCP server. Use the following settings Specifies that the network connection should use a static IP address. If you choose this option, provide the following information: IP Address Netmask Default Route IP Address The static IP address that the network connection should use. Enter the IP address or click Select Property to insert a parameter that refers to a local property to supply the value for this field. Netmask The subnet mask number, which is used to identify which segment of the network the server is on. Enter the IP address or click Select Property to insert a parameter that refers to a local property to supply the value for this field. Default Route The address of the IP router that is used to forward traffic to destinations outside of the local network. Enter an address or click Select Property to insert a parameter that refers to a local property to supply the value for this field. If you want the installation program to detect the router by using the ICMP router discovery protocol, leave this field blank. Note If ICMP is disabled, you must provide an IP address for Default Router. Otherwise, JumpStart switches to interactive mode during an installation and starts prompting the user for values. Use IPv6 Check this option if the IP address conforms to the Internet Protocol version 6 (IPv6) network layer standard. Name service type The name service that this server should use. Enter a name or select NONE if this server should not use a name service. Name services and their associated fields are listed below. NISNIS+ Domain Name: Name of the group of systems using NIS. Name Server Host Name: Name of the NIS name server. Name Server IP Address: IP address of the NIS name server. DNS Domain Name: Domain name for the group of systems using DNS. Primary DNS Server: IP address of the primary DNS server. Secondary DNS Server: IP address of the secondary DNS server. Tertiary DNS Server: IP address of the tertiary DNS server. Additional Domains: Names of additional domains to search for name service information. You can specify up to six domain names to search. Use CSV format (separate domain names with commas). The total length of this field (including commas) cannot exceed 250 characters. LDAP Domain Name: Name of the group of systems using LDAP. Profile Name: Name of the LDAP profile server. Profile Server IP Address: IP address of the LDAP profile server. Proxy DN: Domain name of the LDAP proxy server. Proxy Password: Password to access the LDAP proxy server. This password must not include the following character string: ?? Proceed to the Package specifications - Solaris tab.
   Package specifications - Solaris	The Package Specifications tab lets you choose which Meta Cluster you want to use. A Meta Cluster contains packages that specify what operating system software components to install on the machine. Check the Meta Cluster that contains the operating system components you want to install. The Package Specifications tab gives you the option to check Use script for OS component selection and then either: Type in a script that specifies which operating system components you want to install. 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. For information, see Inserting a script in a system package. When finished, proceed to the Additional sysidcfg entries - Solaris tab.
   Additional sysidcfg entries - Solaris	The Additional sysidcfg tab lets you add or modify the keyword/value statements in the system identification configuration file (sysidcfg). The sysidcfg file is a set of keyword/value statements that describe how you want to configure a machine. Based on the information you provide in the basic system package panels, the TrueSight Server Automation system populates this file with some of your configuration choices. You can use the Preview panel to examine the existing contents of the sysidcfg file. To modify or add keyword/value statements, enter them in the text box. Sample keyword/value pair statements for this file include: security_policy=NONE timeserver=localhost terminal=vt100 nfs4_domain=dynamic Proceed to the Additional profile entries - Solaris tab.
   Additional profile entries - Solaris	The profile file uses keyword/value statements to specify the type of installation, which packages are to be installed, how disks should be partitioned and so on. Based on the information you provide in the basic system package panels, the TrueSight Server Automation system populates this file with some of your configuration choices. You can use the Preview panel to examine the existing contents of the profile file. Then, if you want to add or modify the keyword/value statements, you can do so, using the Additional Profile Entries panel. Sample keyword/value pair statements for this file include: install_type initial_install system_type standalone Proceed to the Add install client script - Solaris tab.
   Add install client script - Solaris	The Add Install Client Script tab lets you customize the add_install_client command. A default add_install_client command appears in this panel. If you want to customize the command, check Customize add_install_client script. Then do one of the following: Type your customized script directly in the input box. Type the name of a local property that contains the 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. For information, see Inserting a script in a system package. To return to the default add_install_client command, clear the Customize add_install_client script option. Proceed to the Rules file script - Solaris tab.
   Rules file script - Solaris	The Rules File Script tab lets you customize the contents of the rules file. This file becomes the Jumpstart rules file. Check Customize rules file and then do one of the following: Type your rules directly in the input box, using conventions and syntax for creating a rules file for Jumpstart. Type the name of a local property that contains the rules, enclosing the property name with double question marks. Click Select Property  to display available properties. Select the property that contains the rules. For information, see Inserting a script in a system package. The rules are included in the Jumpstart rules file. To return to the default rules file contents, clear the Customize add_install_client script option. Proceed to the Begin script - Solaris tab.
   Begin script - Solaris	The Begin Script tab lets you specify a script that JumpStart runs just after the target device boots from the network. At this point, no operating system or software is installed, but the script can perform operations such as special disk partitioning operations or change EEPROM settings. Do one of the following: Type the script directly in the input box. Type the name of a local property that contains the script, enclosing the property name with double question marks. Click Select Property to display available properties. Select the property that contains the script. For information, see Inserting a script in a system package. Click Browse to select the script. Proceed to the Finish script agent install - Solaris tab.
   Finish script agent install - Solaris	The Finish Script/Agent Install tab lets you specify processes to run after the operating system is installed on the server. Using this tab, you can: Choose whether to install a TrueSight Server Automation RSCD agent. An agent must be installed on every server that you want to manage using the TrueSight Server Automation Console or Network Shell. Choose whether 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 any additional scripts to run after the operating system is installed. Field definitions Install RSCD agent Check this option to install an agent on the server that you are provisioning. (For a Solaris WAN boot installation, this option is not available.) Push ACLs Check this option to push the ACLs defined for the server in the TrueSight Server Automation system to the RSCD agent that you are installing on the server. Selecting this option automatically translates the permissions you defined for the server in the TrueSight 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 TrueSight 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 click Browse to select it. To check Run post-install batch job, you must also check Install RSCD agent, because running a post-install job requires an agent 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 of the Jobs contained in the Batch Job. Application Server for BMI callback IP address The IP address of the Application Server to which you want to report the provisioning job completion status. This field lets you use different Application Servers for load balancing. Finish Script Specify the contents of the JumpStart finish script by doing one of the following: Type the script directly in the input box. Type the name of a local property that contains the 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. For information, see Inserting a script in a system package. The finish script runs one time immediately after an unattended installation of the operating system. Any commands you enter into the finish script are appended to commands that TrueSight Server Automation provisioning also inserts in this script, including a command to install the RSCD agent. The commands that you enter run before any post-install Batch Job that you specify. Proceed to the Reboot script - Solaris tab.
   Reboot script - Solaris	The Reboot Script tab lets you specify a script that connects to the target device and forces it to reboot from the network and send a BOOTP request to the JumpStart server. This starts the actual installation of the operating system. Sample reboot scripts are available from your TrueSight Server Automation representative. You must customize the scripts for your specific device hardware and networking environment, but the sample scripts can provide you with a useful head start. Do one of the following: Type the script directly in the input box. Type the name of a local property that contains the 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. For information, see Inserting a script in a system package. Proceed to the x86 parameters - Solaris tab.
   x86 parameters - Solaris	The x86 Parameters tab lets you define fdisk partitions and kernel parameters for provisioning x86 servers. The fdisk information you provide here becomes part of the JumpStart profile file. The x86 kernel parameters are passed to add_install_client. Section Description FDisk Partitions This section lets you create or modify fdisk partitions for provisioning x86 servers. For FDisk Partitions, do one of the following: To create a new partition, click Add . To modify an existing partition, select the partition in the FDisk Partitions list and click Open . To delete a partition, select the partition in the FDisk Partitions list and click Delete . If you are adding a new partition, a wizard appears. If you are editing an existing partition, a tabbed window appears. Both provide the same options. The Disk Name panel lets you specify where this fdisk partition is located. Select one of the following options and then click Next. Disk Slice — Place the partition on the slice you specify here, using one of the following formats: c<x>t<y>d<z> — For example: c0t0d0 c<x>d<z> — For example: c0d0 Root Disk — Place the partition on the system's root disk. All — Place the partition on all the disks. The Type panel lets you specify what type of fdisk partition this is. Select one of the following options and then click Next. Solaris — A Solaris fdisk partition (SUNIXOS fdisk type). Dos Primary — An alias for primary DOS fdisk partitions. Integer Partition — An integer fdisk partition. Specify a value between 1 and 255 inclusive. Hexadecimal Partition — A hexadecimal fdisk partition. Use format 0xHH where HH is a hexadecimal number between 01 and FF inclusive. Under Size, select one of the following settings: Specify size (in MB) — Make the size of this partition the number of megabytes specified here. All — Create this fdisk partition on the entire disk. All existing fdisk partitions are deleted. You can select All only if the fdisk type is solaris. Max Free — Create an fdisk partition in the largest contiguous free space on the specified disk. You can select Max Free only if type is solaris or dosprimary. Delete — Delete all fdisk partitions of the specified type on the specified disk. Click Finish. The partition appears in the FDisk Partitions list. Kernel Parameters This section lets you add new or modify existing kernel parameters for x86 servers being provisioned. For Kernel Parameters, do one of the following: To create a new kernel attribute/value pair, click Add . To modify an existing attribute/value pair, select the pair in the x86 Kernel Parameters list and click Open . Specify a kernel Attribute Name and associated Value. Then click OK. To delete an attribute/value pair, select the pair in the x86 Kernel Parameters list and click Delete. Proceed to the Local properties - Solaris tab.
   Preview - Solaris	The Preview tab lets you examine customizations you made to the sysidcfg file, profile file, and rules file, and add_install_client command options. The Preview panel displays the following files: sysidcfg file profile file rule entry to add to the rules file add_install_client command options This panel is display only.
   Local properties - Solaris	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. Optionally, proceed to the Preview - Solaris tab. Otherwise, save the package.

   Panel	Description
   Disk partition - Solaris	The Disk Partition tab lets you define partitions for the provisioned servers. The information you provide here becomes part of the JumpStart profile file (for Oracle Solaris 10 or earlier) or part of the Automated Installer (AI) profile.xml file (for Oracle Solaris 11 or later). There are two ways to define a partition — by supplying a script or using the wizard: To supply a script, click Use script for disk partitioning. Then do one of the following: Type the script directly in the input box. Type the name of a local property that contains the 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. For information, see Inserting a script in a system package. To use the wizard, follow this procedure: Select the type of partition to define: Explicit Partition, Default Partition, or Existing Partition. Note The Existing Partition option is available only for Oracle Solaris 10 or earlier. Take one of the following actions. If you are adding a new partition, a wizard appears. If you are editing an existing partition, a tabbed window appears. Both provide the same options. To create a new partition, click Add . To modify an existing partition, select the partition in the Disk Partition list and click Update or Edit  . Under Slice Configuration, select one of the following slice options and then click Next. Any — place the file system on any disk. Disk Slice — place the file system on the slice you specify here, using one of the following formats: c<w>t<x>d<y>s<z> — For example: c0t0d0s0 c<w>d<y>s<z> — For example: c0d0s0 Root Disk — Place the system's root disk on the slice (integer) you specify here. Under Size Options, select one of the following size options and then click Next. Existing — Use the current size of the existing file system. Auto — Determine the size of the file system based on the software you are installing on this server. All — Have this slice use the entire disk for the file system. If you choose All, you cannot place any other file systems on this disk. Free — Use the remaining unused space on the disk for the file system. Specify Size — Set the size of the file system to the value (in MB) that you specify here. Explicit Partition — Partition the file system explicitly, using the format: start:size where start is an integer specifying the cylinder where the slice begins, and size is the number of cylinders for the slice. Under File System Settings (Optional), select one of the following optional settings: Swap — Make this slice the swap slice. Overlap — Define this slice as a representation of a disk region. Unnamed — Define this slice as a raw slice without a mount point name. Ignore — Tell JumpStart or AI not to use or recognize this slice. Mount Point — Use this mount point name for the file system, for example /var. Under Optional Parameters, select one of the following: Preserve — Preserve the file system on this slice. Mount Options — One or more mount options for the mount point name you specified in Mount Point. Click Finish. The partition appears in the Disk Partitions list.
   Basic configuration - Solaris	The Basic Config tab lets you provide local information about a server, such as its name and the password needed to access the machine. Local Settings - Field definitions Computer name The unique name that should be assigned to the server. Enter a name or use click Select Property to insert a parameter that refers to a local property to supply the value for this field. OM Server Name (Optional) Specifies a different name for this server to display when it appears in the TrueSight Server Automation Console. Enter a name or use 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 in the TrueSight Server Automation Console, leave the OM Server Name field blank. If you do choose to use a different OM Server Name for this machine, make sure that this new name can be resolved to the IP address of the server. Root password The password used to access the root account. Enter a password. Then confirm your typing by entering the password again in the Confirm password field. Non Root User Settings - Field definitions Non root Username Specify a unique name for the non root user. Enter a name or click Select Property to insert a parameter that refers to a local property to supply the value for this field. Password for Non Root User The password used to access the non root account. Enter a password. Then confirm your entry by entering the password again in the Confirm password field. Confirm password Reenter the non root user password.
   Computer settings - Solaris	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. Important: TrueSight Server Automation does not support the TZ environment variable to set time zone. Functioning of TrueSight Server Automation might be impacted by this variable. 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 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 System Locale Select the character encoding scheme you want to use for your language. If the encoding scheme you need is not in the drop-down list, check Use a parameter. Use a parameter or specify an unlisted system locale Check this option if the character encoding scheme you need is not on the list for System Locale. The drop-down list changes to a field. Type in an encoding scheme or click Select Property to insert a parameter. (If you created a property for the unlisted encoding scheme(s), you can insert a parameter that references this property.) For information about system locales supported in the Solaris environment, see the Oracle documentation. Keyboard Select a language from the list. The Keyboard attached to the server will customize according to the language selected.
   Network - Solaris	The Network tab lets you provide networking information for a server, such as its IP configuration settings and name service. Field definitions Enable networking on the Primary interface Check this option if you want this machine's primary interface to connect to the network. Initialize the Primary interface using DHCP Specifies that the network connection should obtain an IP address automatically from a DHCP server. Use the following settings Specifies that the network connection should use a static IP address. If you choose this option, provide the following information: IP Address Netmask Default Route IP Address The static IP address that the network connection should use. Enter the IP address or click Select Property to insert a parameter that refers to a local property to supply the value for this field. Netmask The subnet mask number, which is used to identify which segment of the network the server is on. Enter the IP address or click Select Property to insert a parameter that refers to a local property to supply the value for this field. Default Route The address of the IP router that is used to forward traffic to destinations outside of the local network. Enter an address or click Select Property to insert a parameter that refers to a local property to supply the value for this field. If you want the installation program to detect the router by using the ICMP router discovery protocol, leave this field blank. Note If ICMP is disabled, you must provide an IP address for Default Router. Otherwise, JumpStart switches to interactive mode during an installation and starts prompting the user for values. Use IPv6 Check this option if the IP address conforms to the Internet Protocol version 6 (IPv6) network layer standard. Name service type The name service that this server should use. Enter a name or select NONE if this server should not use a name service. Name services and their associated fields are listed below. NISNIS+ Domain Name: Name of the group of systems using NIS. Name Server Host Name: Name of the NIS name server. Name Server IP Address: IP address of the NIS name server. DNS Domain Name: Domain name for the group of systems using DNS. Primary DNS Server: IP address of the primary DNS server. Secondary DNS Server: IP address of the secondary DNS server. Tertiary DNS Server: IP address of the tertiary DNS server. Additional Domains: Names of additional domains to search for name service information. You can specify up to six domain names to search. Use CSV format (separate domain names with commas). The total length of this field (including commas) cannot exceed 250 characters. LDAP Domain Name: Name of the group of systems using LDAP. Profile Name: Name of the LDAP profile server. Profile Server IP Address: IP address of the LDAP profile server. Proxy DN: Domain name of the LDAP proxy server. Proxy Password: Password to access the LDAP proxy server. This password must not include the following character string: ?? Proceed to the Package specifications - Solaris tab.
   Client Script Editor - Solaris	This tab allows you to customize the script which you would use to create a client. You can edit the commands in the script by selecting Customize Create Client Script option.
   AI Manifest Editor - Solaris	This tab shows the AI manifest file syntax. You can edit the XML file by selecting Customize the AI Manifest file option. Note This editor checks for XML syntax. It does not validate the content for correctness. Additional AI Manifest Entries The following fields are also available in the AI Manifest Editor tab: Field Description Script Contents Shows the script content. Add/Replace in the XML The text added or replaced in the XML file. Path The location of the XML file.
   Profile Editor - Solaris	This tab shows the Profile file syntax. You can edit the XML file by selecting Customize the Profile file option. Note This editor checks for XML syntax. It does not validate the content for correctness. Additional Profile Entries The following fields are also available in the Profile Editor tab: Field Description Script Contents Shows the script content. Add/Replace in the XML The text added or replaced in the XML file. Path The location of the XML file.
   Finish script agent install - Solaris	The Finish Script/Agent Install tab lets you specify processes to run after the operating system is installed on the server. Using this tab, you can: Choose whether to install a TrueSight Server Automation RSCD agent. An agent must be installed on every server that you want to manage using the TrueSight Server Automation Console or Network Shell. Choose whether 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 any additional scripts to run after the operating system is installed. Field definitions Install RSCD agent Check this option to install an agent on the server that you are provisioning. (For a Solaris WAN boot installation, this option is not available.) Push ACLs Check this option to push the ACLs defined for the server in the TrueSight Server Automation system to the RSCD agent that you are installing on the server. Selecting this option automatically translates the permissions you defined for the server in the TrueSight 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 TrueSight 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 click Browse to select it. To check Run post-install batch job, you must also check Install RSCD agent, because running a post-install job requires an agent 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 of the Jobs contained in the Batch Job. Application Server for BMI callback IP address The IP address of the Application Server to which you want to report the provisioning job completion status. This field lets you use different Application Servers for load balancing. Finish Script Specify the contents of the JumpStart finish script by doing one of the following: Type the script directly in the input box. Type the name of a local property that contains the 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. For information, see Inserting a script in a system package. The finish script runs one time immediately after an unattended installation of the operating system. Any commands you enter into the finish script are appended to commands that TrueSight Server Automation provisioning also inserts in this script, including a command to install the RSCD agent. The commands that you enter run before any post-install Batch Job that you specify. Proceed to the Reboot script - Solaris tab.
   Local properties - Solaris	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. Optionally, proceed to the Preview - Solaris tab. Otherwise, save the package.

   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