How Health Rolls Up

In System Center 2012 – Virtual Machine Manager (VMM), the health of the VMM service and database, all VMM agents (on virtual machine hosts and library servers), virtual machines on managed hosts, and VMM Self-Service portals roll up to the health of a VMM management group. Each VMM management server is represented by a management group. This figure shows how the health states roll up in this management pack.

Engine health is determined by two factors. In addition to the monitors that roll up the health of the VMM database, the Virtual Machine Manager service, and the Virtual Machine Manager agent on the VMM management server, any failed discovery (monitored by a unit monitor) causes a Failed state for the VMM engine.

The health of managed hosts is rolled up through host groups. This figure shows how host group health rolls up.

The health of virtual machine hosts, child host groups, and child host clusters rolls up to the health of the host group. The exception is the health of VMware ESX hosts. Although Operations Manager monitors the health of ESX hosts and the virtual machines on the hosts, the health of an ESX host does not roll up to the host group.

If the VMM management server is running on a virtual machine that is managed by the same instance of VMM, the health of host groups is reported as Not Available. However, the health of hosts and virtual machines within host groups is monitored.

The illustrations in this topic show the relationships among monitored objects. The objects do not represent specific rollup monitors in the VMM Management Pack. For details about specific monitors, use Health Explorer in the Operations console to view the health monitors in the management pack.