Important

   

Starting version 8.9.03, BMC Server Automation is renamed to TrueSight Server Automation. This space contains information about BMC Server Automation 8.9.02 and previous versions. For TrueSight Server Automation 8.9.03 and later releases, see TrueSight Server Automation 8.9.

Adding and configuring a vCenter AMO

To add a vCenter server as an agentless managed object (AMO) that communicates with some other agent-based Windows proxy server, perform the following tasks:

Before you begin

Ensure that your environment meets the requirements described in Reviewing minimum requirements for VMware environments.

To add a vCenter server as an AMO

  1. Either select an existing 64-bit Windows or Linux managed server with the RSCD installed or add a new system with the RSCD installed to be the proxy to the vCenter server.  Ensure that the RSCD agent installed on the proxy server is the same version as the Server Automation Application Server.

    Note

    If you choose to use the AMO Proxy method to communicate with the vCenter server, you cannot install the RSCD on the vCenter server and register it with BSA as a managed server.

  2. Right-click the server group in the Servers folder, and select Virtualization > Add VMware Virtual Center.
  3. On the Add a new agentless managed object - Properties page, add the name or IP address of the VMware vCenter master server.
    Optionally, add a brief description.
  4. Under Properties, locate the AGENTLESS_MANAGED_OBJECT_PROXY_HOST property, and edit its property value by browsing to the name of the Windows system configured as the proxy host.
  5. Click OK and then click Finish.
    The agentless managed object for the VMware vCenter server is added to the folder that you specified.

To configure the vCenter server AMO in BMC Server Automation

  1. From within the BMC Server Automation Console, select Configuration > Property Dictionary View.
  2. Browse the Built-in Property Classes > Connection class.
  3. On the Instances  tab, find the new Connection instance that was created automatically for the AMO.
    The name of the instance is Connection_<agentlessManagedObjectName> (where <agentlessManagedObjectName> is the name of the Citrix XenServer object). For example, Connection_10.129.49.11 is the name of the enrolled Citrix XenServer.

    Note

    Your user role must have the appropriate RBAC permissions to create or update the Connection instance. Otherwise, the association between the instances will not be created and the server will not be enrolled.
    After creation of the Connection instance, a connection PSI is automatically created for the server in virtualization and the value of VIRTUAL_ENTITY_CONNECTION is set to the CONNECTION PSI that is created.
  4. Set the following properties for the new Connection instance:

    PropertyValue
    CONNECTION_URL

    Enter the web URL of the SDK of the vCenter server (for example, https://<vCenterServerName>/sdk).

    Note
    : This name should match the VMware vCenter server name registered in BMC Server Automation.

    CONNECTION_USEREnter the name of an administrator of VMware vCenter, or another user with required privileges.

    If you need to provide a domain name with the username, enter it here as <domainName\userName>
    CONNECTION_PASSWORDEnter the password of the user that is mentioned in the above property.
  5. Save the instance.
  6. Distribute the vCenter configuration object on the vCenter server:
    1. From the BMC Server Automation Console, navigate to the Jobs folder.
    2. Right-click a job group and select New > Administration Task > Distribute Configuration Objects.
    3. Provide a name for the Job and click Next.
    4. Expand the Global Configuration Objects list, select the VMware vCenter Server object, and add it to the Selected Configuration Objects section. Click Next.
    5. On the Targets panel, select the vCenter server.
    6. Click Finish, and execute the job. For details, see Distributing configuration objects.

  7. Go to the Windows server that you configured as the proxy for the vCenter AMO, and locate the AssetImplConfig.xml configuration file in the <RSCD_Dir>\daal\Implementation\BMC_VMware_VirtualInfrastructureManager_win64\win64 directory (where <RSCD_DIR> is typically C:\install\BladeLogic\RSCD\). In this configuration file, set the assetImpl_proxyCapable option to a value of true.

Note

After you upgrade to the latest version of BMC Server Automation, you must perform the following steps:

  1. Upgrade the RSCD agent on either the Windows vCenter server or the AMO proxy.
  2. Add the new VMware configuration object to the vCenter server object in BMC Server Automation.

Where to go from here

Now that you have set up the VMware vSphere environment, you are ready to perform various vSphere management tasks, as discussed in Managing a VMware vSphere environment.

Was this page helpful? Yes No Submitting... Thank you

Comments