Tuesday, 14 August 2012

Install VMware vCenter Operations Manager 5

Install and Configure VMware vCenter Operations Manager 5.0.2

Deployment Architecture Overview

VMware vCenter Operations Manager 5 is shipped as a VMware vSphere vApp, or virtual application—a preconfigured set of two virtual machines, complete with operating systems and application software, bundled in a ready-to-use configuration—to be deployed by VMware® vCenter into a vSphere environment. The vApp includes the following virtual machines working in unison:

  • The analytics virtual machine is responsible for collecting the data from your vCenter Server, VMware vCenter Configuration Manager (if available) and third-party data sources (metrics, topology and change events) and storing them in its scalable file system database (FSDB). The analytics engines for capacity and performance periodically process this raw data and store the results in their respective Postgres/FSDB databases.
  • The UI virtual machine provides the user interfaces by which users can access the results of the analytics presented as dashboards composed of badges and scores. The UI access paths for users include via a vSphere plug-in and, with the Enterprise edition, a customizable Web UI. Administrators access vCenter Operations Manager 5 through a Web UI dedicated to administrative functions.

Step 1: Deploying the vApp

Launch the vSphere Client and log in to your vCenter Server

Add an IP pool for vCenter Operations Manager 5 vApp.

The IP pool facilitates the future use of static IP addresses during the vApp deployment process. A DHCP deployment can work without an IP pool, but it generates warnings in the vSphere Client interface.
Enabling the IP pool is optional and not selected in this scenario. 
We are not configuring a real pool of IP addresses here; we need only the subnet and gateway associated with the static IP address to be used.
DNS and proxy settings (optional)
The IP pool must be configured at the datacenter level in vCenter.

To know more about creating a IP Pool, CLICK HERE 

Deploy the vCenter Operations Manager 5 vApp.

NOTE: Deploy only from vCenter Server. Do not deploy vCenter Operations Manager 5 from a VMware ESXi host

Select File >> Deploy OVF Template… from the menu.

Navigate to and select the following vCenter Operations Manager 5 vApp OVA file:

Review the vApp details and click Next

Accept the End User License Agreement and click Next

Provide a suitable name for the vApp and select where you want to deploy it

Select the Deployment Configuration as per your need
Choose the Small configuration for the first evaluation deployment. The configuration screen will
show the sizing limit guidelines. If the sizing guidelines for a Small deployment are insufficient, refer to the vCenter Operations Manager 5 Deployment and Configuration Guide for further details to ensure the availability of appropriate resources.

Choose the cluster (e.g., SEEPZ Cluster) for deployment

 Select the Resource Pool you want your vApp to be deployed in

Select the Datastore

Select a format to store the VMs Disks.
NOTE: In my case i chose Thin, but i would highly recommend to go for Thick Provisioned

Choose the VM Network for vApp connectivity. 
NOTE: The Destination Network was already created and assigned a IP Pool. To know more on how to create an IP Pool, CLICK HERE

Choose Fixed for the IP allocation.

  • Fixed is the preferred and recommended option. DHCP addressing for the vApp is also an option.
  • Transient is not recommended for evaluation environments.
  • Fixed requires the IP pool creations completed previously.

Set the Timezone and IP Addresses.

Choosing the incorrect Timezone can cause data troubles later. The vApp synchronizes time
with the ESX host time. Choose the Timezone corresponding to the vCenter Server system.
Assuming the selected Fixed setting, choose a UI VM IP Address in the associated IP pool
defined (e.g.,
Assuming the selected Fixed setting, choose an Analytics VM IP Address in the associated IP
pool defined (e.g.,

Verify the vApp settings.

If something is not correct, click Back and fix the setting.
Do not power on or off the individual machines.
Click Finish to start the deployment.

NOTE: This process can take up to 15 minutes, but it normally takes much less in a typical environment.

 Once deployed, you are now ready to Power On the vApp.

In PART 2 Of this tutorial we will now Power ON and configure the vApps. CLICK HERE to continue reading.

No comments :

Post a Comment

Note: only a member of this blog may post a comment.