Setting up AIX provisioning

Before you begin

• You must have a working NIM environment, configured for and stocked with all of the operating system installation files you want to use to provision target servers.
• The NIM master must be running version 7.4 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.

Step 1: Set up the NIM environment

1. On the NIM master, select or create a directory to use as a TrueSight Server Automation staging directory. This directory holds copies of the configuration files that TrueSight Server Automation generates. By convention, this directory is called /export.
    Make a note of this directory. You need it when you configure TrueSight Server Automation for NIM. (Specifically, you need to specify this staging directory in the STAGING_DIR_PATH property when you define your NIM data store instances.)
2. Directly beneath this staging directory, create a /BladeLogic/rscd subdirectory.
    For example, if your staging directory is called /export, your directory structure is:
   /export/BladeLogic/rscd
3. Obtain the AIX agent installer file. For example, RSCD86-AIX32.sh.
    This file is included in the Optional Components zip package, which you download from the BMC Software Electronic Product Distribution (EPD) website.
    This file installs an RSCD agent on each target server that is being provisioned.
4. Rename the RSCD86-AIX32.sh file to rscd.sh, and copy rscd.sh to the newly created BladeLogic/rscd directory.
5. 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.
6. Confirm that the BladeLogic/rscd directory on the NIM master contains the following files:
   • rscd.sh
   • nsh-install-defaults

_{Back to top}

Step 2: Configure the data store - NIM 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 NIM 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 NIM provisioning, set the following property values.

   Property Name	Description
   NIM_MASTER	The IP address of the NIM master. This value must be resolvable from the TrueSight Server Automation Application Server. The NIM master must have a running RSCD agent that is licensed. Success Tip Use the IP address instead of the host name of the NIM server in the NIM Datastore PSI to eliminate issues with the lpar_netboot command which is run as part of the Provisioning job.
   STAGING_DIR_PATH	An existing directory location on the NIM master. TrueSight Server Automation uses this directory to stage all generated NIM resources. The directory must be writable by users who create Provision Jobs, because Provision Job execution creates subfolders and files as necessary.

_{Back to top}

Step 3: Configure a system package type for AIX 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 AIX system package type.

   Field definitions

   System package type	Name of the system package type.
   SPOT name	Name of the NIM Shared Product Object Tree (SPOT) resource.
   Lpp_source name	Name of the NIM lpp_source resource.
   Mksysb name	Name of the NIM mksysb resource.
   Bosinst source	The NIM resource you want to use as the primary source for the operating system. Choose one of the following options: spot rte mksysb

   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 AIX 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
   System Package Creation - Properties
   System Package Creation - Permissions

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 - AIX	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 (Required) The unique name that should be assigned to the server. Enter a 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 (Optional) Specifies a different name for this server to display when it appears in the TrueSight Server Automation Console. Enter a 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 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. NIM Machine name The name by which this machine is known within the NIM environment. The provisioning process creates a machine object with this name in the NIM database. The name must be a legal NIM machine name (one that does not include periods). If you do not explicitly specify a name in this field, the Computer name is used as the NIM machine name. In that case, you must make sure that the Computer name is a legal NIM machine name. 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. Proceed to the Target disk - AIX tab.
   Target disk - AIX
   Localization settings - AIX	The Localization Settings tab lets you provide localization information. Field definitions BosInst Locale Select a locale from the list. If the locale you need is not on the list, check Use parameter or specify an unlisted timezone. Use a parameter or specify an unlisted locale for use during bosinst Check this option if the locale you need is not on the list for BosInst Locale. The drop-down list changes to a field. In the field, type the name of a time zone or click Select Property to insert a parameter that references a property you created for the unlisted locales. For information about the locales supported in the AIX environment, consult the AIX documentation. Cultural Convention Select a cultural convention from the list. If the convention you need is not on the list, check Use parameter or specify an unlisted locale for the cultural convention. Use a parameter or specify an unlisted locale for the cultural convention Check this option if the cultural convention you need is not on the list for Cultural Convention. The drop-down list changes to a field. In the field, type the name of a convention or click Select Property to insert a parameter that references a property you created for the unlisted cultural conventions. For information about the cultural conventions supported in the AIX environment, consult the AIX documentation. Messages Catalogs Select the name of the messages catalogs from the list. If the name of the messages catalogs is not on the list, check Use parameter or specify an unlisted locale for the messages catalogs. Use a parameter or specify an unlisted locale for the messages catalogs Check this option if the messages catalogs name is not on the list for Messages Catalogs. The drop-down list changes to a field. In the field, type the messages catalogs name or click Select Property to insert a parameter that references a property you created for the unlisted messages catalogs. For information about the messages catalogs supported in the AIX environment, consult the AIX documentation. 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 AIX environment, consult the AIX documentation. Proceed to the Network config - AIX tab.
   Network config - AIX
   Agent install first boot script - AIX	The Agent Install/First Boot Script tab lets you specify processes you would like to run after the operating system is installed on the server. You can use this tab to: Choose whether you want to install a TrueSight Server Automation RSCD agent. An agent must be installed on every server you want to manage using the TrueSight Server Automation Console or Network Shell. Choose whether you want 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 NIM first boot script you want 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. Before installing the RSCD agent, the provisioning process dynamically computes the size of these disk partitions on the target server and extends them if necessary: The /tmp partition The partition on which the agent is to be installed (for example, /opt)  For these extensions to be successful, you must ensure that each partition is mounted on a logical volume with enough space the partition to be extended. Use the following AIX operating system commands: To show information about the current size of the file system, percentage of utilization, and the name of its logical volume, enter: df To show information about the logical volume, including its volume group nam, enter: lslv logicalVolumeName  For information about required space for RSCD agent installation, see Minimum-hardware-requirements. Push ACLs Check this option to push the ACLs defined for the server in the TrueSight 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 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. 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. Firstboot Script Specify the contents of the NIM first boot script by doing one of the following: 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. Type a shell script directly in the input box. Note that you cannot use property-based parameters in this type of script. The following example script installs perl on the target server during the first boot: #!/usr/bin/ksh #Installing perl  echo “downloading the perl” wget http://www.oss4aix.org/download/RPMS/bash/bash-3.2-4.aix5.1.ppc.rpm echo “Installing perl on the target” rpm -i bash-3.2-4.aix5.1.ppc.rpm  The expected echo return code is: $? The script runs one time immediately after an unattended installation of the operating system. Proceed to the NIM-scripts tab.
   NIM scripts
   Control flow	The Control Flow tab lets you edit the first section of the bosinst.data file. This section is called the control_flow stanza. You can modify this section to change any of the default settings. To modify the default settings, do one of the following: Type your changes directly into the text box. 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. Proceed to the Optional-bos_inst-attributes tab.
   Optional bos_inst attributes
   Pre-machine definition scripts
   Pre-bos_inst script
   Post bos_inst Script
   Preview - AIX
   Local properties - AIX

   Success

   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