Post-install configuration - Ubuntu Linux


The Post-install Configuration tab lets you specify the installation of a TrueSight Server Automation RSCD agent on the target server, specify a Batch Job that runs after the operating system is installed on the server, and enter commands that are included in the Kickstart file.

Field definitions

Field

Description

Install RSCD agent

Check this option to install an agent on the target servers. (An agent must be installed on every server that you want to manage using the TrueSight Server Automation Console or Network Shell.)

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 g_V95_BrowseIcon.gifto 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 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. To provide the DNS entry using a script in the Batch Job, the Batch Job must run even when the RSCD agent enrollment fails.

Application Server for BMI callback

For load balancing, you can use different Application Servers for reporting Provision Job completion status. Use these fields to identify the Application Server to which target servers in this job should report their Provision Job completion status.

  • IP address — Enter the IP address of the Application Server or click Select Property to specify a property that contains the value.
  • Port — Accept the default (9831) or enter a different port number.

Post-install Script

Commands to add to the post-install section of the Kickstart or AutoYast file, which runs once after a server reboots for the first time after an unattended installation of a Linux (including Red Hat and SUSE) operating system.

Enter commands in the box or click Select Property g_V95_ParameterizeIcon.GIFto insert a parameter.
Commands that you enter into the post-install 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.

The DOMAIN entry is a Local Property that is set in the System Package and is referencing the DNS suffix for the host.

  • For SUSE 11 Service Pack 2, enter the following in the Post-Install Script section to register the agent with the BSA Server:

echo "??HOST_NAME??.??DOMAIN??" > /etc/HOSTNAME

echo "??IP_ADDRESS?? ??HOST_NAME??.??DOMAIN?? ??HOST_NAME??" >> /etc/hosts

  • For RedHat Enterprise Linux 5 Update 9 (5.9), enter the following in the Post-Install Script section to register the agent with the BSA Server:
    echo "??IP_ADDRESS?? ??HOST_NAME??" >> /etc/hostsAnother workaround is to use the RHEL 6.0 package type when creating the Provisioning Manager Configuration for RHEL 5.9
  • New in 20.02For providing the read and write permission to access the RSCD agent from appserver1 and appserver2 hosts, enter the following command that modifies the Exports file:
    echo "appserver1,appserver2 rw" > /etc/rsc/exports
    For more information about configuring the Exports file, see Configuring-the-exports-file.

Proceed to the Local-properties-Ubuntu-Linux tab.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*