_Distributing_configuration_objects

Before you use the BMC BladeLogic Server Automation console to manage a virtual environment, you must distribute the appropriate configuration objects to the target platform.

Running the Distribute Configuration Objects Job

Define the job

From within the BMC BladeLogic Server Automation console, navigate to the Jobs folder.
Select a job group under which you want to create your Distribute Configuration Objects Job.
Right-click the job group and select New > Administration Task > Distribute Configuration Objects. This starts the job wizard.
Provide a name for the Job and click Next.

Select the configuration object

On the Selected Configuration Objects panel, in the Available Configuration Objects section, expand the Global Configuration Objects list.
Select the configuration object appropriate for your virtualization platform and add it to the Selected Configuration Objects section.
Click Next.

Platform	Select
VMware vSphere	VMware vCenter Server version
Solaris	Global Zone version
IBM PowerVM	IBM Configuration version
Hyper-V	Microsoft SCVMM version
Red Hat Enterprise Virtualization	RHEL KVM version
Citrix XenServer	Citrix XenServer version

where version represents the version number of the Configuration Object, for example, v801,000 for version 8.1.

Set the targets

On the Targets panel, select the appropriate target server for your platform.
Click Finish, and execute the job.

Platform	Select
VMware vSphere	vCenter agent installed on the vCenter host
Solaris	Solaris agent installed on the Global Zone
IBM PowerVM	IBM Frame which is enrolled as an agentless managed object
Hyperv	Windows x64 agent on the SCVMM server
Red Hat Enterprise Virtualization	server running the Red Hat KVM hypervisor
Citrix XenServer	enrolled agentless managed object for the Citrix XenServer master server

Troubleshooting issues with virtualization configuration objects

Configuration objects on Red Hat Linux fail to load

Certain virtualization configuration objects running on a Red Hat Linux computer may encounter the following error: any action that you try to perform through the BMC BladeLogic Server Automation Console for the management of RedHat KVM or the Citrix XenServer server assets results in an error message, "Unable to start CO Server."
This problem arises when resource usage by the RedHat KVM or the Citrix XenServer configuration object exceeds the defined OS limitations for the allocation of shared memory segments or message queues.

Note

The configuration objects may load properly for the first few users that connect to the RSCD agent. After OS limitations have been reached, all additional user connections will experience the problem.

To prevent this issue from occurring, BMC BladeLogic Server Automation provides a shell script (blsysctl.sh ) that you can use to update the IPC configuration parameters in the Red Hat kernel so that the BMC BladeLogic Server Automation configuration object can run. This script updates the /etc/sysctl.conf file, which controls system parameters.
You must execute the script on any machine running a Red Hat Linux agent that has any of the following BMC BladeLogic Server Automation configuration objects installed:

RedHat KVM
Citrix XenServer

To run the blsysctl.sh script for modifying IPC parameters

Log on to the Red Hat Linux computer as root.
If you are not permitted to log on as root, use the su or sudo command to gain sufficient permissions.
Use the cd command to navigate to the installationDirectory/NSH/sbin directory.
Stop the RSCD agent using the agentctl stop command.
Run the blsysctl.sh script using the blsysctl.sh -options command, where options can be any of the parameters described in the following table.

Options available for the blsysctl.sh script

Option	Description
-d	Use this option to perform a dry run of the script, to verify the potential updates that the script will make to the /etc/sysctl.conf file and the IPC values in the kernel. Each listed update displays the key, the current system value, and the new value.
-w	Use this option to update the current IPC values in the kernel and in the /etc/sysctl.conf file. The script creates a backup file named /etc/sysctl.conf.beforeBMCScriptUpdate before updating the /etc/sysctl.conf file. Note: If you also use the -d option with the -w option, only a dry run is performed.
-l	Use this option with the -w option to create a sysctl.conf file in the current directory, instead of updating the /etc/sysctl.conf file. This option can be helpful for testing. The /etc/sysctl.conf file and the system are not updated.
-v	Use this option to run the script in verbose mode, which displays detailed messages. You can use this option with all other options except for -h.
-h	Use this option to display the usage message. As the script runs (with the -w option), the /etc/system.conf file is updated with new values for IPC parameters, within a new BMC BladeLogic section. Old values are commented out, as shown in the following figure, an example of an updated system.conf file. Example of updated system.conf file ### The line below is commented out by BMC blsysctl.sh script ### kernel.shmmax = 4294 # Controls the maximum number of shared memory segments, in pages ### The line below is commented out by BMC blsysctl.sh script ### kernel.shmall = 26842 #------------------------------------# ### BMC Bladelogic Section - Start #------------------------------------# kernel.sem=250 32000 32 1024 kernel.shmmni=4096 kernel.shmmax=32768 kernel.shmall=2097152 kernel.msgmni=1024 #------------------------------------# ### BMC Bladelogic Section - End #------------------------------------# Start the RSCD agent using the agentctl start command.