Worksheet for installing BMC Server Automation on Linux and UNIX

Installation parameter

Value

Names of the server or servers where you will install any BMC Server Automation components, including all managed servers.

Root password for each server. Installation must be performed by root.

Installation directory The default is: /opt/bmc/bladelogic

Components to select for installation
1-RSCD agent
2-Application Server
P-PXE Server
T-TFTP Server
Client utilities:
3-Network Shell
A-Select all

Certificate password (must be at least 6 characters) For information, see Certificate-password.

Whether to enable Provisioning on the Application Server. Select yes to enable a port that the Application Server uses to communicate with bare metal machines being provisioned.

Maximum heap size to use for the Java Virtual Machine (JVM) for the Application Server Launcher. (In a multiple-Application Server environment, the Application Server Launcher configures and controls all Application Servers on the host.) Specify a size between 512 - 2048 megabytes.

(PXE server installation) Whether to configure a DHCP server to run on this server.

If the DHCP server is located on another server, the installation program automatically configures this server to function as a DHCP proxy. You must configure the DHCP server differently, depending on whether it is installed on the same computer as the PXE Server. For more information on configuring the DHCP server, see Configuring-the-DHCP-server. BMC recommends that you install the PXE server and the DHCP server on different host computers.

Whether to install the default .nsh resource files into /etc/skel.

These files make it easy to set up Network Shell as a log-in shell.

Whether to use secure (digitally signed) logs for the RSCD agent. Secure agent logs have message authentication codes and sequence numbers assigned to the current log and digitally signed rolled logs. Enter y to use secure logs; enter n to use plain text logs.

Whether to use keystroke logs for nexec commands. Keystroke logs capture log information for remote commands run on the agent using nexec.

Whether to install the BMC Server Automation Pseudo Random Number Generator Daemon (PRNGD). For information, see BMC-Server-Automation-PRNGD.

Whether to set up an initial host with root equivalency. For information, see Root-equivalency.

Whether to set up mapping for a particular client user. If you choose y, you must specify:

• Client user you want to map, such as BLAdmins:BLAdmin or root.
• Local user on the server to which you want to map.

For information, see Client-mapping.

Select a mechanism for starting RSCD agent in the future. Choices:

• At system bootup
• Manually

(The system boot-up start method depends on the operating system platform.)

RSCD log directory Default is /opt/bmc/bladelogic/NSH/log

Directory for temp files The default is /tmp

Whether to configure Application Server with Post-Installation wizard. Running the Post-Install Configuration wizard requires an X Windows display. If you choose yes, you must define a display variable. For example: hostname 0.0. For information about configuration parameters, see Configuring-the-Application-Server.

If you are using VMware

VMware vCenter server name

Name of an administrator of VMware vCenter

Password corresponding to the user name

Web URL of the SDK of the vCenter server

If you are using Oracle Solaris Zones

Solaris server name

Name of a user that can log on to the Global Zone running on the Oracle Solaris server

Password corresponding to the user name

If you are using IBM Frames

Name of the Primary HMC Server which manages the Frame

Name of a user that has administrative access to the Frame

Password corresponding to the user name

If you are using Microsoft Hyper-V

Name of the Microsoft System Center Virtual Machine Manager (SCVMM) server

User name used for authenticating the web service running on the SCVMM server

Password corresponding to the user name