Configuring PRO integration between OpsMgr 2012 and VMM 2012

While Dynamic Optimization and Power Optimization replace the Performance and Resource Optimization (PRO) functionality in OpsMgr for basic workload thresholds (CPU, memory, disk, network), OpsMgr PRO still very much plays a role in delivering  dynamic workload management for your virtualization infrastructure by extending PRO functionality to OEM hardware, appliances and third party applications through PRO-enabled packs from the partner community .  Since configuring PRO integration has long been a sore spot, I thought I would outline how to make the magic happen VMM and OpsMgr 2012, where the process is very similar to the process in the past, but with a few steps and dependencies you need to be aware of.

High-Level Steps

  • Install the Consoles
  • Grant permissions to OpsMgr and VMM user accounts
  • Import the required management packs
  • Configure System Center Settings in VMM 2012 Console
  • Validating Your Results

IMPORTANT: Since we configuring OpsMgr integration with VMM, it is assumed you have deployed an OpsMgr agent to the VMM 2012 Server, all Hyper-V hosts and VM guests.

Install the Consoles

Before you configure the connect, you need to install the System Center consoles to facilitate SDK access

  • Install the Operations Manager 2012 console on the VMM 2012 Server
  • Install the VMM 2012 Admin console on one of the management servers in the resource pool handling the workflows previously managed on the RMS.

Grant permissions to OpsMgr and VMM user accounts

You will need an account with administrator permissions in Operations Manager 2012 and an account with administrator rights in Virtual Machine Manager 2012.

Import the required management packs

Next, import the Virtual Machine Manager 2012 and PRO management packs, which are present on your VMM 2012 Server in the ‘%ProgramFiles%\Microsoft System Center 2012\Virtual Machine Manager\Management Packs’ directory.

IMPORTANT:

  • The Operations Manager Connector setup job in VMM will fail if you  do not import these
  • The IIS 2003 management pack is required (its in the references of one of the VMM packs)

image

Configure System Center Settings in VMM 2012 Console

In the VMM 2012 Admin Console, select Settings, then System Center Settings to launch the wizard to configure

In the Connection to Operations Manager window, enter the FQDN of the OpsMgr 2012 management server in the resource pool handling the workloads formerly isolated to the RMS . You’ll need to specify an account with administrative permissions in OpsMgr. I did this using a Run As Account, which can be created in VMM much as it is in OpsMgr. For instructions on creating Run As credentials, see http://technet.microsoft.com/en-us/library/gg675082.aspx

image

In the Connection to VMM window, enter the account with VMM administrator credentials.

image

Review your settings in the Summary window, then hit Create. This launches a job titled New Operations Manager connector.

image

Validating Your Results

You will need to validate your results first in VMM, then in OpsMgr. Once the job completes in VMM, verify a successful result, as shown below

image

image

Wait a few minutes, then in the Operations Manager 2012 console, verify the VMM Server appears in the PRO Object State with a health state of something other than ‘Not Monitored’. If you don’t see this object in a monitored state, check for OpsMgr or VMM Event Log events with indications of communication or permission failures.

image

You should also see monitoring info for your cloud assets from the fabric up, including Clouds, Services, Hosts, Host Clusters, etc. in the Virtual Machine Manager –> Agent Folder

image

 

In my next post, we’ll talk about provisioning and permissions for cloud resources in VMM 2012.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.