Appendix A: Monitoring Pack Contents

  • Article

Applies To: System Center 2012 - Operations Manager

The Hyper-V Monitoring Pack for Windows Server 2012 discovers the object types described in the following tables. Not all of the objects are automatically discovered. Use overrides to discover those objects that are not discovered automatically.

Discoveries

Discovery Target Description Interval

Server running Hyper-V 2012

Windows2012DiscoveryMP!Microsoft. Windows.Server.6.2.Computer

Enables the ability to discover servers running Hyper-V Server 2012.

The discovery runs once a day by default, but can be reconfigured by using the IntervalSeconds parameter.

24 hours

Hyper-V 2012 Virtual Machine

Microsoft.Windows.HyperV.2012. ServerRole

Enables the ability to discover Hyper-V Server 2012 virtual machines.

The discovery runs every two hours by default, but can be reconfigured by using the IntervalSeconds parameter.

12 hours

Hyper-V 2012 Virtual Network

Management Server

Enables the ability to discover Virtual Internal Networks and Virtual External Networks.

The discovery runs once a day by default, but can be reconfigured by using the IntervalSeconds parameter.

24 hours

Monitors

Monitor Target Description Interval

Virtual Machine Management Service

Hyper-V Host

Summary

This monitor tracks the health state of the Virtual Machine Management service on the server that is running Hyper-V. When the service is running, the state of the monitor is Healthy. When the service is not running, the state of the monitor is Critical.

Cause

A critical state occurs when the Virtual Machine Management service is not running. An alert is raised when this monitor goes into an unhealthy state.

Resolution

This monitor runs an automatic recovery when it goes into an unhealthy state. The recovery attempts to restart the Virtual Machine Management service. If it is able to restart the service, the monitor returns to a healthy state and the alert is auto-resolved. If the recovery is not able to restart the service, the monitor remains in a critical state and the alert remains unresolved.

Not applicable

Hyper-V 2012 RemoteFX Capable GPU

Hyper-V Host

Summary

This monitor verifies that GPUs are RemoteFX-capable.

Cause

The GPU in the server may not be a DX11-capable GPU.

Resolution

Visit www.microsoft.com to learn more about RemoteFX-capable GPUs.

24 hours

Server GPU Configuration

Hyper-V Host

Summary

Server GPU configuration

Cause

There are two or more GPUs in this server that are not of the same make and model. This is an unsupported configuration.

Resolution

Ensure that all GPUs in the server are of the same make and model.

24 hours

Hyper-V 2012 RemoteFX Virtual Machine Display Resolution

Hyper-V Host

Summary

This monitor tracks configuration errors in display resolution for virtual machines running Windows 7 SP1.

Cause

This monitor will cause the following states:

  • Healthy: The display resolution is configured correctly.

  • Error: The display resolution is configured incorrectly.

Resolution

Virtual machines running Windows 7 SP1 are configured either with a display resolution greater than 1920 x 1200 or with more than four monitors. These configurations are not supported by this guest operating system. Choose a lower resolution or fewer monitors for this virtual machine.

Not applicable

Reset is 15 minutes

Virtual Hard Disk Free Disk Space

Hyper-V Host

Summary

This monitor tracks the amount of free disk space on the logical disk that contains the dynamically expanding or differencing virtual hard disk.

The monitor changes state based on the Warning and Error State Disk Space parameter values that can be reconfigured. The default values are 2GB for warning and 200MB for error state. Hyper-V will pause virtual machines when available free disk space is less than 200MB.

Cause

This monitor will cause the following states:

  • Healthy: Logical disk has more than 2GB of free disk space (Warning State Disk Space default) or the virtual hard disk is fixed.

  • Warning: Logical disk has less than 2GB of free disk space (Warning State Disk Space default) but more than 200MB (Error State Disk Space default).

  • Critical: Logical disk has less than 200MB of free disk space (Error State Disk Space default).

Resolution

Free more than 2GB of space (Warning State Disk Space default) on the logical disk that contains the virtual hard disk.

1 hour

Hyper-V 2012 Replica Network Listener

Hyper-V Host

Summary

The HTTP or HTTPS network listener that is required to receive replication traffic is not available on this server.

The monitor changes to Error State when it detects that the Replica service is unhealthy, which is likely due to an HTTP(S) listener not being available.

Causes

  • If you have configured Hyper-V to receive replication using Kerberos-based authentication (HTTP listener), the SPN registration might have failed or there could be a conflict in the network port on which the listener has been configured to receive replication traffic.

  • If you have configured Hyper-V to receive replication using certificate-based authentication (HTTPS listener), then verify that the provided certificate is valid and meets the prerequisites.

Resolutions

  • For Kerberos or for certificate-based authentication, retry by providing a different port number.

  • For Kerberos authentication, verify that Active Directory can be reached from the host.

  • For certificate-based authentication, verify the following:

    • The provided certificate is valid.

    • The Enhanced Key Usage (EKU) of the certificate allows for both server and client authentication.

    • The certificate terminates at a valid root certificate.

    • The subject common name of the certificate contains or is equal to the DNS name of the server.

1 hour

Hyper-V 2012 Replica Out of Sync

Virtual Machine

Summary

The primary virtual machine and Replica virtual machine are out of sync by more than an hour. In the event of an unplanned failover, more than an hour’s worth of data could be lost.

Causes

  • Lack of network connectivity between the primary and Replica servers.

  • Network bandwidth is insufficient to send the accumulated changes from the primary server to the Replica server.

  • Storage subsystem on either the primary or Replica site is not properly provisioned from a space and IOPS perspective.

  • Replication on the primary or Replica virtual machine is paused.

Resolutions

  • Verify that the Replica server is reachable from the primary server.

  • Verify that the network and storage is properly provisioned to handle the load.

  • Check the Replication Health of the replicating virtual machine, which may provide additional information.

  • Check to see if the virtual machine’s replication needs to be resumed manually.

½ hour

Hyper-V 2012 Replication - Reverse Replication Not Initiated

Virtual Machine

Summary

Failover has been initiated on the Replica virtual machine but it is currently not protected. Re-protect the virtual machine by reverse-replicating it back to the primary server or by replicating it to any other server.

Cause

Reverse replication has not been initiated.

Resolution

Initiate reverse replication of the virtual machine.

½ hour

Hyper-V 2012 Replication Critical Suspended State

Virtual Machine

Summary

The replicating virtual machine is in a critical state because the replication is abnormal.

Causes

  • Network bandwidth is insufficient to send the accumulated changes from the primary server to the Replica server.

  • Storage subsystem on either the primary or Replica site is not properly provisioned from a space and IOPS perspective.

  • Replication on the primary or Replica virtual machine is paused.

Resolutions

  • Verify that the Replica server is reachable from the primary server.

  • Verify that the network and storage is properly provisioned to handle the load.

  • Check the Replication Health of the replicating virtual machine, which may provide additional information.

  • Check to see if the virtual machine’s replication needs to be resumed manually.

½ hour

Hyper-V 2012 Replication Resync Required State

Virtual Machine

Summary

The replicating virtual machine is in a resync-required state.

Cause

If the replicating virtual machine is experiencing more activity than what the network or storage can handle, then the virtual machine could enter a resync-required state.

Resolution

Check the resync settings of the virtual machine to confirm whether the resync is expected to happen manually or automatically. Resume replication of the virtual machine, which will resync the primary and Replica virtual machines.

½ hour

Hyper-V 2012 Replication Not Started

Virtual Machine

Summary

After setting up a replication relationship, initial replication for the virtual machine should be completed.

Cause

Initial replication has not been completed after setting up a replication relationship.

Resolution

Complete the initial replication (IR) by doing one of the following:

  • Online IR: Send the initial copy over the network.

  • Out-of-band IR: Send the initial copy off the network (for example, to an external device).

  • Reuse copy on Replica site: Restore an earlier copy of the primary virtual machine on the Replica site.

12 hours

Hyper-V 2012  Replica Broker Configuration

Hyper-V Host

Summary

The Hyper-V Replica Broker is not available on the cluster. If the Hyper-V Replica Broker is not available, the replication between the primary and Replica virtual machines could be affected.

Causes

  • The cluster service stopped unexpectedly.

  • The Hyper-V Replica Broker is unable to come up on the destination node after a cluster migration.

Resolution

Restart the cluster service, and then do the following:

  • If you are using Kerberos-based authentication, verify that the Hyper-V Replica Broker’s SPN registration is successful.

  • If you are using certificate-based authentication, verify that the required certificates are present in the cluster.

6 hours

Hyper-V 2012 Replica Windows Firewall Rule

Hyper-V Host

Summary

For replication to work successfully, an entry should be available in the firewall that allows traffic on the configured port.

Cause

The Windows Firewall rule that allows replication traffic to the Replica site has not been enabled.

Resolution

If you are using Windows Firewall, do the following:

  • If you are using Kerberos-based authentication, enable the Hyper-V Replica HTTPS Listener (TCP-In).

  • If you are using certificate-based authentication, enable the Hyper-V Replica HTTP Listener (TCP-In).

Hyper-V 2012 Replication Count Percent

Virtual Machine

Summary

The replicating virtual machine has missed more than the configured percentage of replication cycles.

Cause

The network and storage subsystems are unable to handle the Replica traffic.

Resolution

Increase the network bandwidth between the primary and Replica sites, or ensure that there is sufficient IOPS headroom in the primary and storage subsystems to handle the Replica traffic.

1 hour

Note

If you are using connectors, you can disable the monitor and enable its corresponding rule to enable alerts without changing health status.

Rules

Rule Target Description Interval

Virtual Network Sent Throughput

Hyper-V Virtual Network

Collects sent bytes per second over the Hyper-V virtual network.

1 hour

Virtual Network Received Throughput

Hyper-V Virtual Network

Collects received bytes per second over the Hyper-V virtual network.

1 hour

Note

Disable the rule and enable its corresponding monitor to enable alerts, state changes, and health rollup.