This monitor checks if replication is working between Configuration Manager primary site and secondary site.
Configuration Manager keeps continuously monitors the health of connectivity between parent and child sites and parent and child SQL Servers to make sure that replication is active across sites within a Configuration Manger hierarchy. These checks occur regularly to ensure that data is synchronized across the hierarchy among site servers for global data (e.g., application metadata and configuration items) and up the hierarchy for site data.
Any number of causes will cause a failure of replication between Configuration Manger parent and child sites:
• Database machine certificate is invalid.
• Database service broker certificate is invalid.
• SQL Port defined in configuration manager is not correct.
• SQL Service Broker port is incorrect.
• SQL Port is not open on the firewall.
• Cannot use the specified account to connect to SQL server.
• The disk space on SQL server is insufficient.
• SQL Server service is down.
• SQL Server service broker is down.
• SMSEXEC service is down.
• Network connectivity between Configuration Manager Sites is down.
System administrators for both SQL Server and Configuration Manager as well as the network administrator should discuss options available to remedy the replication issues among Configuration Manager sites. You may also check the hman.log in the [Configuration Manager Installation folder]\Logs for further information.
| Target | MECM.ReplicationToSecondarySite | ||
| Parent Monitor | MECM.Replication.AggregateRollup.Monitor | ||
| Category | Custom | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | MatchMonitorHealth | ||
| Alert Priority | Normal | ||
| Alert Auto Resolve | True | ||
| Monitor Type | MECM.LinkStatus.MT | ||
| Remotable | True | ||
| Accessibility | Public | ||
| Alert Message |
| ||
| RunAs | Default |
Home
<UnitMonitor ID="MECM.PrimaryToSecondaryGlobalReceive.LinkStatus.Monitor" Accessibility="Public" Enabled="true" Target="MECM.ReplicationToSecondarySite" ParentMonitorID="MECM.Replication.AggregateRollup.Monitor" Remotable="true" Priority="Normal" TypeID="MECM.LinkStatus.MT" ConfirmDelivery="true">
<Category>Custom</Category>
<AlertSettings AlertMessage="MECM.PrimaryToSecondaryGlobalReceive.LinkStatus.Monitor.AlertMessage">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Target/Host/Property[Type="MECM.Server"]/SiteCode$</AlertParameter1>
<AlertParameter2>$Target/Property[Type="MECM.Replication"]/TargetSiteCode$</AlertParameter2>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="UIGeneratedOpStateId7774bdb9848640fcaa9f8b8f62c3f5ba" MonitorTypeStateID="Good" HealthState="Success"/>
<OperationalState ID="UIGeneratedOpStateIdb00ecfe58eaa4e058cbcd67103e91279" MonitorTypeStateID="Warning" HealthState="Warning"/>
<OperationalState ID="UIGeneratedOpStateId011bd5cc96b2429fa07e757db984271f" MonitorTypeStateID="Error" HealthState="Error"/>
</OperationalStates>
<Configuration>
<ParentSite>$Target/Host/Property[Type="MECM.Server"]/SiteCode$</ParentSite>
<ChildSite>$Target/Property[Type="MECM.Replication"]/TargetSiteCode$</ChildSite>
<LinkType>Property[@Name='Site2ToSite1GlobalState']</LinkType>
<IntervalSeconds>360</IntervalSeconds>
<ProviderLocation>$Target/Host/Property[Type="MECM.SiteServer"]/ProviderLocation$</ProviderLocation>
<SiteCode>$Target/Host/Property[Type="MECM.Server"]/SiteCode$</SiteCode>
<IsSP1>$Target/Property[Type="MECM.Replication"]/IsSP1$</IsSP1>
<MatchCount>3</MatchCount>
</Configuration>
</UnitMonitor>