Implementing the OEM Plug-in for VMware vSphere (Beta) Part 3 – Discovery and Promoting Targets

by bluemedora_editor on July 26, 2012

This post is the third in a detailed series of articles that provide a visual (screenshot based) guide for implementing the new Oracle Enterprise Manager Plug-in for VMware vSphere environments — currently available as a Beta Evaluation from Blue Medora.  Part 1 covered importing the plugin in an EM12c Software Library.  Part 2 covered deploying the plugin to Management Servers (OMS) and Management Agents (OMA).  The information posted here is intended to supplement, not replace, the online User Guide available on the Blue Medora product page. This specific post will cover the process of Manually Adding the VMware vSphere targetDiscovering vSphere-related targets, Configuring connections to the those targets, and Promoting those targets.  For simplicity sakes, the demo environment these screen captures are captured from is an “All-on-One” EM12c OEL5 64-bit Server that contains both the OMS and OMA.   The example vSphere environment used in the examples is vSphere 5.0 based with 1 vSphere “Virtual Center”, 2 DataCenters, 3 ESX Hosts, 250+ VMs, 20+ Storage Repositories, and a number of Clusters and Resource Groups. Note: This post assume you have already executed all the steps covered in Part 1 and Part 2 of this Blog series.

Manually Adding the VMware vSphere target

1. From the EM12c Web UI, navigate to Setup -> Add Target -> Add Targets Manually.[vc_single_image image=”2017″ alignment=”center” border_color=”grey” img_link_large=”” img_link_target=”_self” img_size=”full”]2. Select Add Non-Host Targets by Specifying Target Monitoring Properties. From the Target Type drop-down menu, select VMware vSphere.  Specify the desired OMA and click Add Manually.

3. Specify monitoring properties for the VMware vSphere target type.  Click OK.

  • Target Name: name of the VMware vSphere target type instance. (Note: this value will be used later for discovery of additional target types)
  • vSphere Username: name of the user with necessary privelages to connect to the VMware vSphere api.
  • vSphere Password: password for the user enter for vSphere Username.
  • vSphere Hostname: hostname of the VMware vSphere server that is hosting the Webservices SDK
  • Use SSL: Whether the connection should use SSL.
  • vSphere Port: Port on the vSphere host that the Webservices SDK is listening. Default is port 443.

 

Discovering VMware vSphere-related targets

1. From the EM12c Web UI, navigate to Setup -> Add Target -> Configure AutoDiscovery.

2. The Configure Auto Discovery screen will appear.  In most cases, you will want to click Multiple-Type Target Discovery on Single Host.

3. The Target Discovery (Agent Based) dialog box appears next.  Highlight the Agent that you Deployed the VMware plugin into to Part 2 of this Blog series and click Configure.

4. The Configure Target Discovery screen appear.  Highlight the the Agent that you Deployed the VMware plugin into, check the Enabled boxand then click Edit Parameters. 

5. The Edit Parameters dialog box appears.  Enter the name of the VMware vSphere target type instances that you manually added previously.  The discovery process will find all related targets (datacenters, clusters, and hosts).

  • Note: You may monitor up to 5 VMware environments from a single OMA as long as the corresponding VMware vSphere target type has been manually added previously.

6. You will be returned to the  Target Discovery (Agent Based) dialog box.  Highlight the Agent that you Deployed the VMware plugin into to Part 2 of this Blog series and click Run Discovery Now.

7. The Run Discovery Now dialog box will appear asking you to confirm that you want run discovery on the Host you highlighted in Step 3.  Click Yes to continue.

8. The Confirmation Screen will appear.  It should indicate that Discovery ran successfully.  Click Close to continue

9. The Target Discovery (Agent Based) dialog box appears next. Click the Discovered Targets value for the Host you’ve been configuring the plugin on.

10. The Auto Discovery Results screen will  appear.  If Discovery has been configured and executed successfully, you should see a list of VMware vSphere targets in the list of Non-Host Targets.

Promoting vSphere Targets After Successful Discovery

1. There are a variety of VMware vSphere related targets are Discovered by the plugin including VMware vSphere (the entire managed entity), Datacenter, ESX Hosts,and Clusters.  We recommend you Highlight each Target separately or Highlight multiple “like” Targets an clickPromote.   Return to this screen and repeat this process until all the vSphere Targets you want visibility in EM for have been promoted.

1. Note: The vSphere Virtual Machine target type is not Discovered in the current Beta release of the plugin.  It will be available as part of the final release.

2. Also Note:  Data on each VM in the environment will still be available within the VMware vSphere, VMware vSphere Host, and VMware vSphere Datacenter target types.

3. In the example above, I highlighted the “Dev_Vmware Dev” & “Dev_Vmware Production” VMware vSphere Datacenter targets.  Below you will find the configuration details that were discovered for this target type.  Confirm the values and click Promote.

4. Once you have promoted all your vSphere target types, Installation, Discovery, and Promotion is complete.  After an initial start-up time of approximately 10-15 minutes, you will be able to navigate to the VMware  targets and view the data.  From the EM12c Web UI, navigate toTargets -> All Targets.  You should see the vSphere targets you promoted in previous steps.

5. To confirm that everything that the entire Deployment, Install, Discovery, and Promotion process has been successful, click any of the vSphere Targets and verify data is returning.  In this example, I selected the VMware vSphere top level target.

Get started

Try BindPlane for free. No credit card required.

Sign up
True Visibility
BindPlane for VMware vRealize Operations

True Visibility allows cloud management teams to use VMware vRealize’s powerful machine learning and capacity planning engine across their entire hybrid cloud environment.

Azure Monitor...everything
BindPlane for Microsoft Azure Monitor

Make Azure Monitor your first-pane-of-glass across your entire multi-cloud, multi-database or hybrid platform environment.

Thank you for contacting us. Your information was received. We'll be in touch shortly.