Use this Knowledge Script to determine whether a Microsoft Windows cluster node, network, resource, group, or network interface is down. This script can also determine whether the ownership of a cluster group has changed.
Microsoft cluster node, network, resource, group, and network interface object
The default interval for this script is Every 10 minutes.
Set the following parameters as needed:
Description |
How to Set It |
---|---|
Data Collection |
|
Collect data? |
Select Yes to collect data for graphs and charts. The default is Yes. |
Monitoring |
|
Auto-start cluster resource? |
Select Yes to automatically start a cluster resource that is down. The default is Yes. |
Auto-start cluster group? |
Select Yes to automatically start a cluster group that is down. The default is Yes. |
List of resource to be excluded |
To exclude resources from monitoring:
|
Event Notification |
|
Raise event if changes occur in a network, resource, or group? |
Select Yes to raise separate events, one for each component, for changes that occur in Cluster Server components: network, resource, or group. The default is Yes. |
Raise a single event? |
Select Yes to raise one event that summarizes all changes that have occurred in all Cluster Server components: network, resource and group. The default is Yes. |
Event severity level when cluster-related API failure occurs |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which a cluster-related API failure occurs. The default is 15. |
Event severity level when a node is down |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which a node is down. The default is 8. |
Network |
|
Event severity level when network is down |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the network is down. The default is 8. |
Event severity level when network is partitioned |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the network is partitioned. The default is 9. |
Event severity level when cluster network interface is down |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the cluster network interface is down. The default is 8. |
Cluster Resources |
|
Event severity level when cluster resource is off-line and auto-start fails |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which a cluster resource is offline and auto-start fails. The default is 5. |
Event severity level when cluster resource is off-line and auto-start is set to 'No' |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which a cluster resource is offline and you deselected the Auto-start cluster resource? parameter. The default is 18. |
Event severity level when cluster resource is off-line and auto-start is successful |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which a cluster resource is offline and auto-start succeeds. The default is 25. |
Cluster Group |
|
Event severity level when cluster group owner changes |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which cluster group ownership has changed. The default is 5. |
Event severity level when cluster group is off-line and auto-start fails |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which a cluster group is offline and auto-start fails. The default is 5 (red event indicator). |
Event severity level when cluster group is off-line and auto-start is set to 'No' |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which a cluster group is offline and you deselected the Auto-start cluster group? parameter. The default is 18 (yellow event indicator). |
Event severity level when cluster group is off-line and auto-start is successful |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which a cluster group is offline and auto-start succeeds. The default is 2 (blue event indicator). |