Cluster Monitor
Previous
Next
Cluster Monitor |
Previous
Next
|
|
A Cluster Monitor is a cluster-aware component that provides extensive and configurable monitoring of Windows Server clusters via the Cluster API. A Cluster Monitor can be used to monitor any or all of the seven sets of Cluster APIs in real-time. Cluster Monitor Settings•Cluster Events - Cluster Monitor uses this set of APIs to collect cluster events, information on cluster objects (including the quorum), and overall cluster state information. This includes cluster-related events that do not get logged to the event logs. •Group Events - These APIs monitor cluster failover groups (also known as Resource Groups) by tracking and reporting group status and membership changes. •Quorum Events - Cluster Monitor uses this set of APIs to monitor the cluster database. The cluster database, which contains data on all physical and logical elements in a cluster, is stored in the Registry. Check the Quorum Events and Registry Events checkboxes to monitor the cluster through these APIs. •Resource Events - These APIs monitor clusters at the Resource level, including the initiation of operations on the resource (stopping, starting, etc.). •Network Events - Cluster Monitor uses these APIs to monitor the network interface(s) and report status changes, including those interfaces monitored by the Cluster Service. The Cluster Service monitors all networks available for use by the Cluster Service as the "heartbeat" network. •Registry Events - These APIs monitor cluster registry activity. •Node Events - Cluster Monitor uses these APIs to monitor and track node status, cluster membership and resource ownership. A Cluster Monitor can be assigned to Cluster Agents for physical nodes only. It cannot be assigned to an IP Agent, a Workstation Agent, a Server Agent or a Cluster Resource (i.e., a virtual server or cluster resource group). When using a Cluster Monitor, the Agent type (e.g., Service Agent or Virtual Agent) must be the same for both physical nodes. For example, if you are using a Service Agent on one node, you must use a Service Agent on the other node. If you are monitoring cluster nodes, but you are not using a Cluster Monitor to monitor Cluster APIs, you may use Agents of either type for each node. Note Actions•Warning 5540 - The Cluster Monitor has detected a warning condition. •Error 5541 - The Cluster Monitor has detected an error condition. •Informational 5539 - The Cluster Monitor has detected an informational condition. Monitory CategoryDisplays the Monitoring Categories to which the Monitor item is assigned. Click to select or deselect Monitoring Categories. Click New to create or Properties to Edit Monitoring Categories. AgentsDisplays the Agents to which the Monitor item is assigned. Click to select or deselect individual agents. Click New to deploy an agent or Properties to View/Edit an existing agent. ScheduleDisplays the Scheduled Interval and Scheduled Hours settings which control the frequency for the Monitor Item. Scheduled Interval tabSpecify the interval at which the monitoring, polling or action is to occur. Depending on the Monitor Item type, Items can be scheduled in interval increments of Seconds, Minutes, Hours and Days. The Scheduled Interval is relative to the top of the hour or top of the minute. For example, if a Scheduled Interval is configured for 10 minutes, the Monitor Item will execute at hh:10:00, hh:20:00, hh:30:00, hh:40:00, hh:50:00, h1:00:00, etc. If a Scheduled Interval is configured for 15 seconds, the Monitor Item will execute at hh:00:15, hh:00:30, hh:00:45, hh:01:00, hh:01:15, etc. Scheduled Hours tabSelect the days and/or hours this item is active. By default, the schedule is set to ON for all hours and all days. Mouse clicks toggle squares between ON and OFF. Clicking on an individual square will toggle the active schedule for that hour. Clicking on an hour at the top of the grid, or on a day of the week at the left of the grid will toggle the corresponding column or row. Keyboard equivalents are the arrow keys and the space bar.
|