Bagikan melalui

  • Artikel

Monitoring Clusters by Using Operations Manager

 

Updated: May 13, 2016

Applies To: System Center 2012 R2 Operations Manager, System Center 2012 - Operations Manager, System Center 2012 SP1 - Operations Manager

The purpose of this topic is to explain how to use System Center 2012 – Operations Manager to monitor computers that are in clustered configurations. For information on monitoring clustering services, see the guide for the management pack you are using, such as Windows Server 2003 Cluster Management Pack Guide or Windows Server Failover Cluster Management Pack Guide.

To begin monitoring computers in a cluster, perform the following steps:

  1. Install an agent on all cluster nodes (computers).

  2. Enable agent proxy on all cluster nodes. For more information, see How to Configure a Proxy for Agentless Monitoring.

In the Administration workspace, cluster nodes will be displayed in Agent Managed, and the cluster will be displayed in Agentless Managed. The cluster will show as “not monitored” unless a management pack contains monitors that specifically target the cluster object. The agent on the active cluster node will perform all monitoring. If the node fails, the agent on the cluster node that clustering fails over to will begin monitoring, but the agent on the failover node will have no awareness of anything the agent on other node had monitored previously, such as alerts, state changes, and so forth. The agents are independent.

When you are monitoring virtual servers on a cluster, you must deploy agents to the cluster nodes, configure them to be managed as a proxy, and then monitor the virtual servers as you would monitor an agentless-managed computer.

The Windows Server Operating System Management Pack provides discovery and monitoring of cluster shared volumes.

Note

You might see alerts from Cluster discovery connect functionality monitor and Cluster state connect functionality monitor when the Action Account uses low privilege credentials. To resolve this problem, assign higher privilege credentials to the Windows Cluster Action Account. For instructions, see the procedure “To modify Run As account properties” in How to Create a Run As Account.