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 BMC 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 BMC 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
|
The Target Disk tab lets you provide information about the disks in the target machine where you plan to install the operating system. The information you provide here is stored in the target_disk_data stanza(s) of the bosinst.data file. By default, bosinst.data has one target_disk_data stanza, but you can add additional stanzas by adding multiple entries on this panel. Each entry corresponds to a stanza. Multiple stanzas let you install the operating system on multiple disks, one stanza for each disk. There are two ways to provide information about the disks in the target machine: - To use a script to provide target disk information, click Use script for target disk selection. Then either type in your script in the large text box, or click Select Property . This icon indicates that you can insert a parameter that refers to a local property to supply the value for this field. For information about inserting a parameter, see Inserting a parameter in a system package field.
- To use the GUI fields, do one of the following:
- To create a new entry/stanza, click Add.
- To modify an existing entry/stanza, highlight the entry and click Edit.
Then fill in at least one of the following fields: PVID, Physical Location, San Disk ID, Connection, Location, Size (MB), HDISKNAME. Refer to the AIX documentation for information about the rules of precedence for these fields.
- Proceed to the Localization settings - AIX tab.
|
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
|
The Network Configuration tab lets you provide networking information for a server. Field definitions Use an existing network object. Leave unchecked to use find_net | To use an existing network object, check this option. The enter and the object's name in the Network object name field or click Browse to select an object. To use the NIM find_net keyword to find the target machine you want to provision, leave Use an existing network object check box unchecked, and leave the Network object name field blank. If you do these two things, NIM uses information you provide in other fields on this panel to find the target on the network. | Network Type | (For use with the find_net keyword.) Specify a network type. | Subnet Mask | (For use with the find_net keyword.) Enter a subnet mask number, which is used to identify which segment of the network the server is on. | Network Name | (Optional) The name to use for a network object you define, if NIM is not able to match the NIM device to an existing network. | Client Gateway | (Optional) The IP address or host name of the default gateway that the target machine uses to communicate with the NIM master. | Master Gateway | (Optional) The IP address or host name of the default gateway used by the NIM master to communicate with clients on other subnets. | Network Adapter Name | The logical device name of the network adapter in the target machine you plan to provision. | DNS IP Address | The IP address of the DNS server that the target machine uses. | Domain Name | The default domain to use when looking for machines via a host name, and the host name is not fully qualified. | Client IP Address | (Optional) The NIM client IP address to use to restart logical partitions (LPARs) created in a virtual guest job. You can specify either an explicit IP address or a property-based parameter (for example, ??CLIENT_IP_ADDRESS?? ). |
Proceed to the Agent install first boot script - AIX tab. |
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 BMC Server Automation RSCD agent. An agent must be installed on every server you want to manage using the BMC 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 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 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
|
NIM scripts are shell scripts that the NIM master runs on the client when the base operating system is finished being installed. You can use these scripts to customize the target machine's operating system before it reboots for the first time. 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 Edit .
In the script dialog, provide information for the following options and click OK. - 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.
- For Verbose Level, use the drop-down menu to specify the verbose level of the script's output. Specify a level from 1 to 5, 1 being the least verbose and 5 being the most verbose. You can also select 0, which means that the verbose level is unspecified.
- 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.
proceed to the Control flow tab. |
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
|
The Optional bos_inst Attributes tab lets you specify additional bos_inst attribute/value pairs, which are passed on to the nim -o bos_inst operation. The nim -o bos_inst operation lets you specify attributes to customize the operating system installation. The Optional Bos_inst Attributes tab has two sections: - Bosinst attributes — Lists the attributes specified by the system package type on which your system package is based.
- Other optional attributes — Lists the bos_inst attributes to add to the
nim -o bos_inst operation. Use this section to further customize the installation by adding or editing attributes. For example, to execute a custom script on the target machine after installation, add the script attribute with a value that is the name of the script.
To add or edit attribute/value pairs, do one of the following: - To define a new attribute/value pair, click .
- To modify an existing attribute/value pair, select the pair in the list and click .
In the edit dialog box, provide information for the following options and click OK. - For Bosinst attribute name, do one of the following:
- Type the name of the attribute.
- Type the name of a local property that contains an attribute 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 attribute name from the list.
- For Value, do one of the following:
- Type the value.
- Type the name of a local property that contains a value, enclosing the property name with double question marks.
- To display a drop-down menu of available properties, click Select Property. Select the property that contains the value from the list.
Proceed to the Pre-machine definition scripts tab. |
Pre-machine definition scripts
|
The Pre-Machine Definition Script tab lets you specify a script to run on the NIM master before the target's machine object is defined in NIM. You can leave this tab empty or specify a script. All machines to be provisioned must be defined as machine objects in the NIM environment. From the settings you define in the system package, the system package wizard creates the machine definition command that defines the machine object on the NIM master. (You can view this command on the Preview tab.) However, there might be settings you want to make on the machine before its machine object is defined in NIM. For such settings, you can specify a script on this tab. To specify a script, do one of the following: - Type the script in the text box.
- Type the name of a local property that contains a script, enclosing the property name with double question marks.
- To select an existing script, click . On the Edit dialog, click Import and select the script. The contents of the script appear in the text box. To add to the script, you can type commands or click Properties to reference scripts.
- Specify a property that references an existing script. Click Select Property to display a drop-down menu of available properties. Select the property that contains the attribute name from the list. For more information, see Inserting a script in a system package.
Proceed to the Pre-bos_inst script tab. |
Pre-bos_inst script
| |
Post bos_inst Script
| |
Preview - AIX
|
<[^>]+?>","")"/>
<[^>]+?>","")" class="contextID">
The Preview tab lets you examine the customizations you made to the bosinst.data file, the machine definition command, NIM resource definition, and the Bosinst command.
The tab displays the contents of the following files:
- bosinst.data file
- Machine definition command
- NIM resource definition
- Bosinst command
This panel is display only. |
Local properties - AIX
|
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 - AIX tab. |