Preparing agents for provisioning
To set up RSCD agents so that they can be installed as part of the BMC Server Automation provisioning process, you create an Agents directory. This directory holds the operating system-specific RSCD agent installers for unattended installations.
When you create a system package for provisioning, if you check the Install RSCD agent option, the provisioning process:
- Installs an RSCD agent on each server that is being provisioned.
- Registers the agent and adds the server to the list of managed servers under Available Servers in BMC Server Automation.
In this way you can seamlessly move from provisioning servers to managing servers with BMC Server Automation and Network Shell.
The topics in this section provide instructions for preparing RSCD agents for provisioning:
To create the Agents directory
Under the data store directory, create a directory called Agents.
Typically, for Windows, the path is C:\Program Files\BMC Software\BladeLogic\PXE\pxestore.
- In the Agents directory create directories for each operating system that you plan to provision. For example:
Copy the correct RSCD agent installation file into each of the respective directories that you just created.
ESXi 4.1 and ESXi 5.0 operating systems do not require an RSCD agent installation file. (These operating systems use agentless managed objects.)
Rename the agent installation files so that the file name is rscd with the same extension as the original name.
The installation programs for the RSCD agent must be named rscd.msi for Windows, and rscd.sh for Linux and UNIX platforms.
The following table shows examples of original and renamed file names.
Original Installation File Name
Renamed file in the data store
RSCD82-LIN32.sh (for ESX)
- (optional) For Linux and UNIX systems, if you want to override the agent installation defaults, you can create an nsh-install-defaults file. Store the response file in the data store in the same location as the agent installation program.
For information, see Creating an installation defaults file for Linux or UNIX agents.
- In the BMC Server Automation Console, on the System Package Types tab of the Provisioning Configurations window, identify the location of the agent installation program. For information about this tab, see System Package Types tab.
- When you create the system package in the BMC Server Automation Console, on the Post-Install Configuration tab, select the Install RSCD agent check box. (For Windows RSCD agents, you also specify the properties of the agent installation on this tab.) For information about this tab, see Post-install configuration - Windows and Windows R2.
The following example shows an Agents directory for Red Hat Linux x64 stocked with an installer file and unattended installation response file.
The following example shows an Agents directory for Windows x32 stocked with the .msi installer file.
To create an installation defaults file for Linux or UNIX agents
- Using any server, create a text file named nsh-install-defaults in the /tmp directory. The file must belong to root.
In the file, create an entry for each variable you want to set. Then for each variable you enter in the file, create another entry to export the variable. For example:
The following table describes how to set each possible variable:
Set this variable to choose an installation directory other than the default installation directory of /opt/bmc/bladelogic.
By default, running a silent installation installs all possible components in the installation. To override the default, set the
COMPONENT_CHECKEDvariable. In an RSCD agent only silent installation, the agent is the only possible component for installation. The
COMPONENT_CHECKEDvariable can have only this value:
1--RSCD agent When using the file with the Bulk RSCD Agent Installer, set the value to
Set this variable to
1to enable secure agent logging. When secure agent logging is enabled for an agent, agent logs are periodically rolled and digitally signed as they are rolled.
Set this variable to
1to enable keystroke (nexec ) logging on an agent. When keystroke logging is enabled on an agent, remote commands run against the agent using nexec are captured and logged in an encrypted manner in keystroke logs. These logs are also periodically rolled and digitally signed as they are rolled.
Set this variable to
1to install the BladeLogic Pseudo Random Number Generator Daemon (PRNGD). BMC Server Automation uses random data to encrypt communication securely. Most systems already have a random number generator device; you may not need this setting. However, if a server on which you are performing a silent installation does not include a hardware device for generating random numbers, the installation program installs the PRNGD.
Set this value to identify a client on which users are granted root privileges for this server. This option sets the
root=flag in the exports configuration file. By default, no clients are specified.
Set these values to configure a default user mapping in the users.local file. By default, no users are mapped. The values set with this variable create an entry in the users.local file that says:
NSH_USER_FROM rw,map=NSH_USER_TOFor example, by defining values for these variables, you could create an entry in users.local similar to the following example:
By default, a silent installation does not include the .nsh/etc/skel files. To install those files, set this variable to
Specifies a location where the installer should uncompress the sysinfo installation file before the file copy.
Specifies the type of startup script used for silent installation of the RSCD agent on AIX. You can specify these values:
1 --At system bootup, use the /etc/rc.tcpip file
2 -- Manually (I will do it myself)
3 --At system bootup, use the /etc/rc.d/init.d/rscd file
- Save /tmp/nsh-install-defaults.