Home
  •  

Hyper-V 2016 Node's Replication broker configuration monitor

Microsoft.Windows.HyperV.2016.VMReplicationHealth33418.Monitor (UnitMonitor)

Hyper-V Replication broker configuration monitor.

Knowledge Base article:

Summary

The Hyper-V Replica Broker is not available on the cluster. If the Hyper-V Replica Broker is not available, the replication between the primary and replica VM could be affected.

Causes

This error could be observed if the cluster service stops unexpectedly, or if the Hyper-V Replica Broker is unable to come up on the destination node after a cluster migration.

Resolutions

Restart the cluster service and check if the Hyper-V Replica Broker’s SPN registration is successful for Kerberos based authentication, or if the required set of certificates are present in the cluster if certificate based authentication is being used.

Element properties:

TargetMicrosoft.Windows.HyperV.2016.ServerRole
Parent MonitorSystem.Health.AvailabilityState
CategoryStateCollection
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeMicrosoft.Windows.HyperV.2016.VMReplicationHealthMonitorType
RemotableTrue
AccessibilityPublic
Alert Message
Hyper-V Replication broker is not configured in this cluster.
The Hyper-V Replica Broker is either not configured, or not available for this cluster.
RunAsDefault

Source Code:

<UnitMonitor ID="Microsoft.Windows.HyperV.2016.VMReplicationHealth33418.Monitor" Accessibility="Public" Enabled="onEssentialMonitoring" Target="HVDisc!Microsoft.Windows.HyperV.2016.ServerRole" ParentMonitorID="Health!System.Health.AvailabilityState" Remotable="true" Priority="Normal" TypeID="Microsoft.Windows.HyperV.2016.VMReplicationHealthMonitorType" ConfirmDelivery="false">

  <Category>StateCollection</Category>

  <AlertSettings AlertMessage="Microsoft.Windows.HyperV.2016.VMReplicationHealth33418.ErrorAlert">

    <AlertOnState>Error</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>Error</AlertSeverity>

  </AlertSettings>

  <OperationalStates>

    <OperationalState ID="Healthy" MonitorTypeStateID="VMReplicationHealthy" HealthState="Success"/>

    <OperationalState ID="Unhealthy" MonitorTypeStateID="VMReplicationCritical" HealthState="Error"/>

  </OperationalStates>

  <Configuration>

    <IntervalSeconds>1800</IntervalSeconds>

    <TimeoutSeconds>30</TimeoutSeconds>

    <VMId>localhost</VMId>

    <ErrorProperty>ReplicationHealthIssuesList</ErrorProperty>

    <ErrorCode>33418</ErrorCode>

  </Configuration>

</UnitMonitor>