Creating the Virtual Infrastructure Discovery Job

Create and run a Virtual Infrastructure Discovery Job to automatically discover and register the virtual machines in your environment. This topic contains the following sections:

Before you begin

Note the following about the Virtual Infrastructure Discovery Job:

  • The Virtual Infrastructure Discovery Job is supported for VMware, IBM, and Solaris platforms only.
  • The initial running of the job across the virtual infrastructure takes longer than subsequent executions of the job. For additional information, contact BMC Software Customer Support.

To create a Virtual Infrastructure Discovery Job

  1. Open the Jobs folder and navigate to a Job folder.
    Right-click the Job folder and select New > Virtual Infrastructure Discovery Job from the pop-up menu. The Virtual Sprawl Discovery Job wizard opens.

    Warning

    For VMware platforms, if an ESX host is in the disconnected state and has not been removed from VMware vCenter, the options in the Virtual Infrastructure Discovery Job are not supported against the vCenter server which manages the disconnected ESX host.

  2. Define the Virtual Infrastructure Discovery Job, as described in the following sections:
  3. Click Finish after completing the last step of the wizard, or click OK to save your revisions to an existing job.

To schedule a Virtual Infrastructure Discovery Job

In the Schedules panel, define any number of schedules for the Virtual Infrastructure Discovery Job in the list of schedules, and then click Next. You can use any of the following options:

  • Scheduling a job that executes immediately — To schedule a job that executes immediately, select Execute job now.

  • Scheduling a job — The Schedule tab lets you schedule a job so it can run one time, recur hourly, daily, weekly, or monthly, or recur at some arbitrary interval.
    While scheduling, you can set the time zone for the job. You can also set an execution priority level for the job.

    Note

    For a recurring schedule, TrueSight Server Automation automatically accounts for differences in time zones and changes in daylight savings time. For example, if you schedule a job that should run weekly at 06:00 Eastern Standard Time, the job always runs at 06:00 Eastern Time, no matter whether standard or daylight savings time is in effect.

    Ensure that all component machines in your TrueSight Server Automation system have their clocks synchronized. 

  • Defining job notifications — The Job Notifications tab lets you set up notifications that are generated when a scheduled job runs.

To set discovery to fully qualified domain names

For VMware Virtual Center and Solaris Global Zone servers, you can set the discovery to return the fully qualified domain names (FQDN).

  1. Through the Property Dictionary, expand the Built-in Property Classes node and the Job property class node.
  2. Select the Virtual Infrastructure Discovery Job class node.
  3. Through the Properties tab on the right, add a property named ENROLL_WITH_FQDN to the Virtual Infrastructure Discovery Job property class.
    Add this property as a simple, Boolean-type property.
  4. Set the ENROLL_WITH_FQDN property for your Virtual Infrastructure Discovery Job:
    1. In the Jobs folder in the console, navigate to your Virtual Infrastructure Discovery Job.
    2. Right-click the job, and select Set Property.
    3. Ensure that the ENROLL_WITH_FQDN property is present in the list, and select it.
    4. Set the Value of the property to True, and then click OK.

All virtual machines that are discovered from now on by this Virtual Infrastructure Discovery Job will be registered with their fully qualified domain names.

Note

Avoid running the same job with and without the ENROLL_WITH_FQDN setting. Doing so will result in duplicate server enrollment in the inventory — where VMs are registered once with the non-qualified name and then again with the fully qualified name (for example, my_virtual_guest and also my_virtual_guest.domain.com). 

For virtual guests registered with the FQDN, the BLCLI command Virtualization getVirtualGuestKeyByServerName fails if the virtual guest name differs from the initial part of the FQDN (for example, if the virtual guest is named virtual_guest_name in the virtual center and its FQDN is not_virtual_guest_name.domain.com).

In Solaris virtual environments, the FQDN of the zone is resolved by an IP DNS lookup. Therefore, for changes in FQDNs to take effect after they were successfully resolved, you must ensure that DNS caching is turned off.

Where to go from here

Modifying-the-Virtual-Infrastructure-Discovery-Job

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*