attachments/lrayl/media/windows-live-writer/181a7612be85_b8ec/image_thumb.png

SCOM VMM Integration – How to correct the not monitored diagram and distributed application view

Over the past week, I got some time to work with Maarten Goet, President of OpsLogix (www.opslogix.com). Maarten is a SCOM MVP out of the Netherlands and we took a look at the issue with the VMM SCOM 2012 diagram view. We came up with a workaround so that the top level objects are displayed in the Diagram View as well as showing the Distributed Application for Virtual Machine Manager as monitored objects rather than showing as not monitored.

Basically, after you integrate VMM and OpsMgr 2012, you have to drill into the diagram for anything to display. From what I have seen on other posts, this “feature” is by design. the problem is; who wants to have to drill into a diagram to see the health of VMM in SCOM?

This is what the diagram looks like out of the box after the integration between SCOM and VMM in System Center 2012:

image

You have to drill into the diagram another couple levels before health status shows as monitored:

image

To be able to display health status on the items at the higher levels, you have to create Dependency Monitors. I have created a management pack that has most of the dependency monitors included and can be downloaded at the end of the blog. Here is what I did to create if you want to do it yourself.

On the diagram, select a one of the rollup items to get the name. To start with, I first selected the All Clouds group to get the name as displayed in the detail view:

image

In the Authoring Console, expand out Management Pack Objects, and right click on Monitors, select Create a Monitor > Dependency Rollup Monitor.

image

When the Create a Dependency Monitor wizard opens, the first thing I always do is create a new Management Pack for the Overrides. The MP I created is called Virtual Machine Manager Views Overrides which can be downloaded using the link below.

image

The first monitor I am creating is called “All Clouds Group Dependency Monitor”. For the Monitor Target, make sure All Targets is selected and search for the All Cloud Group class in the Management Pack for System Center 2012 Virtual Manager Discovery.

 

Select Next on the Dependency Monitor general page.

image

On the Monitor Dependency wizard page, drill down into the monitors and select the last "Object (Membership)" item. Drill down into the "Entity Health" item till you see "Availability", select this item. As you can see, there are two listings for Object (Membership). We are not sure why there are two listings here, just make sure you select the last one as shown in the picture. Select Next.

image

Leave the defaults on the Health Rollup Policy page. Select Next.

image

Leave the default for Configure Alerts, select Create.

image

After about a min, the All Clouds group will now display as monitored.

image

You have to repeat the steps outlined for all items displayed as not monitored. Items included in the MP created for Dependency Monitors are (Target Class Name in the Management Pack for System Center 2012 Virtual Manager Discovery):

  • Hosts Group
  • Library Server Group
  • Managed Services
  • VMM Managed Resources
  • Agent Watcher Group
  • Agent Watcher Group
  • Management Group

Not included (you will need to create these and save them in the MP if you want to include):

  • Network Resources
  • StoragePool Group
  • User Roles Group

When finished, the diagram and Distributed Application for VMM show as monitored:

image

image

If you want to import the unsealed MP I created, you can get it here:

http://www.systemcentercentral.com/wp-content/uploads/2013/02/Virtual.Machine.Manager.Views_.Overrides.MP_.zip

2 Comments

  1. Markus March 27, 2013
  2. redza August 18, 2015

Leave a Reply