This is a dependency rollup monitor which determines the state of the NLB cluster based on the state of the nodes in the cluster. By default, if at least one node in the cluster is healthy, the overall status of the cluster will be healthy.
Use health explorer to determine the root cause of why the NLB cluster is in an error or warning state.
Target | Microsoft.Windows.NetworkLoadBalancing.Cluster | ||
Parent Monitor | System.Health.AvailabilityState | ||
Algorithm | BestOf | ||
Source Monitor | System.Health.AvailabilityState | ||
Relationship | Microsoft.Windows.NetworkLoadBalancing.ClusterContainsServerRole | ||
Category | AvailabilityHealth | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | Error | ||
Alert Priority | Normal | ||
Alert Auto Resolve | True | ||
Remotable | True | ||
Accessibility | Public | ||
Alert Message |
|
<DependencyMonitor ID="Microsoft.Windows.NetworkLoadBalancing.ClusterDependsOnServerRoles" Accessibility="Public" Enabled="true" Target="Microsoft.Windows.NetworkLoadBalancing.Cluster" ParentMonitorID="Health!System.Health.AvailabilityState" Remotable="true" Priority="Normal" RelationshipType="Microsoft.Windows.NetworkLoadBalancing.ClusterContainsServerRole" MemberMonitor="Health!System.Health.AvailabilityState">
<Category>AvailabilityHealth</Category>
<AlertSettings AlertMessage="Microsoft.Windows.NetworkLoadBalancing.ClusterDependsOnServerRoles_AlertMessageResourceID">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>Error</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Target/Property[Type="Microsoft.Windows.NetworkLoadBalancing.Cluster"]/IPAddress$</AlertParameter1>
<AlertParameter2>$Target/Property[Type="Microsoft.Windows.NetworkLoadBalancing.Cluster"]/DnsName$</AlertParameter2>
</AlertParameters>
</AlertSettings>
<Algorithm>BestOf</Algorithm>
<MemberUnAvailable>Error</MemberUnAvailable>
</DependencyMonitor>