Home
  •  

DHCP Server 2012 Failover Server Relationship Health Monitor

Microsoft.Windows.DHCPServer.2012.FailoverServerWatcher.UnitMonitor.State (UnitMonitor)

Knowledge Base article:

Summary

A failover relationship can be seen as a partnership link between two servers. Each server can enter into maximum 32 failover relationships and it is also possible for it to enter into multiple failover relations

If a partner server is down or communication was interrupted the state will change to error.

Causes

Check if partner server is running or if communication with local server is possible.

Resolutions

Check if you can communicate with Failover Partner Server using a Ping command.

Element properties:

TargetMicrosoft.Windows.DHCPServer.2012.FailoverServerWatcher
Parent MonitorSystem.Health.AvailabilityState
CategoryStateCollection
EnabledTrue
Alert GenerateTrue
Alert SeverityMatchMonitorHealth
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeMicrosoft.Windows.DHCPServer.2012.FailoverServerWatcher.MonitorType
RemotableTrue
AccessibilityPublic
Alert Message
DHCP Server 2012 Failover Server Relationship has reported a state Change
Failover Relationship named "{0}" in defined between Server: "{1}" and Partner Server: "{2}" for Scope ID: "{3}" changed its state to "{4}"
RunAsDefault

Source Code:

<UnitMonitor ID="Microsoft.Windows.DHCPServer.2012.FailoverServerWatcher.UnitMonitor.State" Accessibility="Public" Enabled="true" Target="Microsoft.Windows.DHCPServer.2012.FailoverServerWatcher" ParentMonitorID="Health!System.Health.AvailabilityState" Remotable="true" Priority="Normal" TypeID="Microsoft.Windows.DHCPServer.2012.FailoverServerWatcher.MonitorType" ConfirmDelivery="true">

  <Category>StateCollection</Category>

  <AlertSettings AlertMessage="Microsoft.Windows.DHCPServer.2012.FailoverServerWatcher.UnitMonitor.State.AlertMessage">

    <AlertOnState>Error</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>MatchMonitorHealth</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Target/Property[Type="Microsoft.Windows.DHCPServer.2012.FailoverServerWatcher"]/Name$</AlertParameter1>

      <AlertParameter2>$Target/Property[Type="Microsoft.Windows.DHCPServer.2012.FailoverServerWatcher"]/LocalServer$</AlertParameter2>

      <AlertParameter3>$Target/Property[Type="Microsoft.Windows.DHCPServer.2012.FailoverServerWatcher"]/PartnerServer$</AlertParameter3>

      <AlertParameter4>$Data/Context/Property[@Name='ScopeId']$</AlertParameter4>

      <AlertParameter5>$Data/Context/Property[@Name='State']$</AlertParameter5>

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

    <OperationalState ID="FailoverServerError" MonitorTypeStateID="Error" HealthState="Error"/>

    <OperationalState ID="FailoverServerOK" MonitorTypeStateID="Success" HealthState="Success"/>

  </OperationalStates>

  <Configuration>

    <ComputerName>$Target/Property[Type="Microsoft.Windows.DHCPServer.2012.FailoverServerWatcher"]/LocalServer$</ComputerName>

    <FailoverRelationshipName>$Target/Property[Type="Microsoft.Windows.DHCPServer.2012.FailoverServerWatcher"]/Name$</FailoverRelationshipName>

    <IntervalSeconds>900</IntervalSeconds>

    <SyncTime/>

    <TimeoutSeconds>300</TimeoutSeconds>

  </Configuration>

</UnitMonitor>