Monitors configuration of Run As Account for vCenter Failover functionality
This rule is watching for issues on Health Service caused by an empty Run As profile for the vCenter failover functionality.
Note: It is recommended to disable this monitor if you are not planning to use the vCenter Connection Failover feature or if you have the Enterprise license edition (Enterprise edition does not support vCenter connection failover).
The rule fires an alarm when Health Service cannot correctly initialize workflows that are necessary for performing vCenter connection failover because the corresponding Run As profile is not configured.
In this case, you should also see a 'Secure Reference Override Failure' alert for all workflows responsible for vCenter connection failover:
Veeam.Virt.Extensions.VMware.EMTarget.ConnectionProblem.Recovery.Success
Veeam.Virt.Extensions.VMware.EMTarget.ConnectionProblem.Recovery.Error
Specify a correct account for the 'Veeam VMware Direct ESX(i) Connection Account' Run As profile. Once the account is distributed, the Health Service should initialize all necessary workflows, and vCenter connection failover functionality will be activated.
Use the Alerts View to see all current open issues for this object. Use the Events View to review any error and warning events for this object. Open a Performance View to see the performance metrics for this object and all contained objects. Open a Diagram View to analyse the relationships of this object to other components.
To learn how to configure the Run As account, refer to the Veeam MP for VMware Installation Guide.
| Target | Veeam.Virt.Extensions.VMware.EMServer | ||
| Parent Monitor | System.Health.ConfigurationState | ||
| Category | ConfigurationHealth | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | Warning | ||
| Alert Priority | High | ||
| Alert Auto Resolve | True | ||
| Monitor Type | Veeam.Virt.Extensions.VMware.MonitorType.RunAsProfileConfiguration | ||
| Remotable | True | ||
| Accessibility | Public | ||
| Alert Message |
| ||
| RunAs | Default |
Home
<UnitMonitor ID="Veeam.Virt.Extensions.VMware.EMServer.Monitor.ESXConnectionRunAsProfile" Accessibility="Public" Enabled="onEssentialMonitoring" Target="VeeamVEBaseDisc!Veeam.Virt.Extensions.VMware.EMServer" ParentMonitorID="SystemHealth!System.Health.ConfigurationState" Remotable="true" Priority="Normal" TypeID="Veeam.Virt.Extensions.VMware.MonitorType.RunAsProfileConfiguration" ConfirmDelivery="true">
<Category>ConfigurationHealth</Category>
<AlertSettings AlertMessage="Veeam.Virt.Extensions.VMware.EMServer.Monitor.ESXConnectionRunAsProfile_AlertMessageResourceID">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>High</AlertPriority>
<AlertSeverity>Warning</AlertSeverity>
<AlertParameters/>
</AlertSettings>
<OperationalStates>
<OperationalState ID="ProfileNotConfigured" MonitorTypeStateID="ProfileNotConfigured" HealthState="Warning"/>
<OperationalState ID="ProfileConfigured" MonitorTypeStateID="ProfileConfigured" HealthState="Success"/>
</OperationalStates>
<Configuration>
<UserName>$RunAs[Name="VeeamVEBaseDisc!Veeam.Virt.Extensions.VMware.ESXMonitoringAccount"]/UserName$</UserName>
<Password>$RunAs[Name="VeeamVEBaseDisc!Veeam.Virt.Extensions.VMware.ESXMonitoringAccount"]/Password$</Password>
</Configuration>
</UnitMonitor>