Unsupported content

 

This version of the product is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

BMC Atrium Orchestrator VMotion events

BMC Atrium Orchestrator integrates, automates, and orchestrates processes across multiple applications and tools, as well as across multiple IT groups, such as support and operations.

The integration between BMC Discovery and BMC Atrium Orchestrator currently supports a single as well as multiple VMotion events. When a running virtual machine is moved either manually (VmMigratedEvent), or by distributed resource scheduler (DRS) (DrsVMMigratedEvent) using VMware VMotion, this is detected by BMC Atrium Orchestrator. When integrated with BMC Discovery, BMC Atrium Orchestrator triggers a rescan of the virtual machine that was moved, and the source and destination hosts.

The following section provides details on how to configure BMC Atrium Orchestrator:

Before you begin

To detect when a running virtual machine is moved from one physical host to another.

  1. BMC Discovery must be running.
  2. The physical hosts and the virtual host must already have been scanned by BMC Discovery.

If these requirements are not fulfilled, the VMotion event is not stored for BMC Discovery to catch up. However, this will occur as part of routine discovery.

Non-matching hostnames

BMC Atrium Orchestrator derives hostnames from the VMware API and BMC Discovery derives hostnames by using the discovery techniques. The derived hostnames could either be a Fully Qualified Domain Name (FQDN), or an actual host name. For successful integration between BMC Atrium Orchestrator and BMC Discovery, the derived hostnames must match (that is, in both the products, the derived hostname for a specific host must be either be an FQDN, or an actual hostname). If there is a hostname mismatch, Discovery rescan is not triggered for that particular host.

Configuration in BMC Atrium Orchestrator

BMC Atrium Orchestrator must have the Discovery-SA-Synchronization runbook installed.

Use the BMC Atrium Orchestrator Grid Manager to specify the correct BMC Discovery appliance, username, and password.

  1. From the Manage tab, click Modules.
  2. From the Modules in Repository panel, select the Discovery-SA-Synchronization module.
  3. Click Activate.
  4. From the Activated on Grid panel, click the Discovery-SA-Synchronization module.
    The Edit Module Configuration page is displayed.
  5. Select Virtualization-SA-Management.
  6. Expand the Configuration tree to expand the following:
    Configuration → VM → Discovery.
  7. Enter values for the following items appropriate to your system.

    HTTP_POST_URL

    1. Click on the HTTP_POST_URL link.
    2. For the Value (string) enter https://appliancename/ui/aoint where appliancename is the name of your BMC Discovery appliance. This URL must use https.
    3. To save the changes, click OK.

    password

    1. Click on the password link.
    2. For the Value (string) field, enter the password corresponding to the username specified below.
    3. To save the changes, click OK.

    username

    1. Click on the username field.
    2. For the Value (string) field, enter the username on the BMC Discovery system with permissions to launch scans, that is, a member of the Discovery group. For more information, see Group Permissions.
    3. To save the changes, click OK.

    Recommendation

    Create a dedicated user to simplify security, support, and auditing.

  8. To exit from BMC Atrium Orchestrator, click Logout.
Was this page helpful? Yes No Submitting... Thank you

Comments