This monitor represents internal health state of synthetic transactions that monitor User Exchange UM Connectivity. If this monitor is unhealthy, then it means that Synthetic transactions are unable to monitor User Exchange UM Connectivity.
Cmdlet Executed: Test-CSExUMConnectivity
For more information on this cmdlet, open a Skype for Business Server 2015 Management Shell window and type:
Get-help Test-CSExUMConnectivity -detailed
To configure users for Synthetic Transactions to execute periodically please use the New-CSwatcherNodeConfiguration cmdlet.
The following are possible causes for this failure:
Watcher Node Configuration issues
Server/Component is down for maintenance.
Network/connectivity issues between Watcher node (where the ST executes) and the Front-end Pool.
SCOM maintenance
Configuration errors: Most common issues are: Test user password is invalid or expired, Test users have not been configured correctly for this Pool. Please refer Synthetic Transaction Internal Alerts View for more details. To fix this problem, check if test users are assigned correctly for the pool being monitored, using the New-CSwatcherNodeConfiguration cmdlet. Also ensure that these test users are correctly provisioned and enabled for services.
Server/Component is down for Maintenance: Please ensure that you put Synthetic Transactions in maintenance mode before performing server/pool maintenance. To do this, use the Start Pool maintenance task in the Pools view.
Network/Connectivity issues: Look at Alert Context tab for more details on the exact connectivity error such as DNS resolution errors or Connection Timeout. You can also get more details on Connectivity errors by looking at Port Check Alerts view.
SCOM maintenance: Ensure that SCOM agent on the Synthetic transaction watcher node is healthy and heartbeating correctly.
| Target | Microsoft.LS.2015.PoolWatcher.ExUMConnectivity | ||
| Parent Monitor | System.Health.ConfigurationState | ||
| Category | ConfigurationHealth | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | Error | ||
| Alert Priority | High | ||
| Alert Auto Resolve | True | ||
| Monitor Type | Microsoft.LS.2015.MonitorType.Health.ST.Config | ||
| Remotable | True | ||
| Accessibility | Public | ||
| Alert Message |
| ||
| RunAs | Default |
Home
<UnitMonitor ID="Microsoft.LS.2015.Monitoring.UnitMonitor.SyntheticTransaction.ExUMConnectivity.Internal" Accessibility="Public" Enabled="true" Target="Microsoft.LS.2015.PoolWatcher.ExUMConnectivity" ParentMonitorID="Health!System.Health.ConfigurationState" Remotable="true" Priority="Normal" TypeID="Microsoft.LS.2015.MonitorType.Health.ST.Config" ConfirmDelivery="false">
<Category>ConfigurationHealth</Category>
<AlertSettings AlertMessage="Alert_Exchange_Unified_Message_Connectivity_Synthetic_Transaction_Internal_Error_Occurred.">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>High</AlertPriority>
<AlertSeverity>Error</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Target/Host/Property[Type="Microsoft.LS.2015.PoolWatcher"]/TargetFqdn$</AlertParameter1>
<AlertParameter2>Test-CSExUMConnectivity</AlertParameter2>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="SuccessState" MonitorTypeStateID="Success" HealthState="Success"/>
<OperationalState ID="ErrorState" MonitorTypeStateID="Error" HealthState="Error"/>
</OperationalStates>
<Configuration>
<TargetFqdn>$Target/Host/Property[Type="Microsoft.LS.2015.PoolWatcher"]/TargetFqdn$</TargetFqdn>
<TestId>ExUMConnectivity</TestId>
<InstanceId/>
</Configuration>
</UnitMonitor>