This monitor tracks the health of the Veeam Collector agentless network connection to a VMware 'target' - either VMware vCenter (the default), or a stand-alone vSphere host. This connection is the collection method for all VMware performance and event data.
This monitor will respond automatically to errors with the connection of the Veeam Collector to this VMware target. Any outage should be treated as critical, as failure of this connection will mean data cannot be gathered for VMware systems.
Causes can include:
Network-related issues, such as firewall or DNS configuration or network availability.
Performance issues related to an unresponsive vCenter Server.
Security issues such as expired password or incorrect role permissions for the Collector connection account to the VMware target.
Check the error description given in the alert for details on the specific error in this case.
Review the status of all connections to VMware systems in the Veeam Collector Health dashboard. All open alerts for the Veeam back-end collection systems can be seen in the 'All Collector Alerts' pane.
Check network configuration and availability, and status of the Collector server and the target VMware server. Check usernames, passwords and port numbers for this connection as configured in Veeam Virtualization Extensions Service.
For configurations where Collector(s) communicate directly with a vCenter Server, note the following:
Each Veeam Collector will raise an independent alert via this monitor, as each Collector maintains an individual datacomm connection to vCenter. However, the datacomm connection is also maintained by the Veeam Virtualization Extensions Service which manages all Collectors. If the Veeam Virtualization Extensions Service detects that the vCenter is offline or otherwise unavailable for more than 25 minutes (5 poll intervals, by default), then another monitor 'Veeam VMware: Connection lost to VMware vCenter server' will fire. As a Recovery Action on that monitor, all Collectors will be reconfigured to collect data directly from ESX(i) hosts, bypassing the failed vCenter.
When the Collectors are reconfigured, this alert will be closed (as the Collector will no longer attempt to connect to the vCenter).
When the vCenter comes back online, the Veeam Virtualization Extensions Service will automatically failback configuration for all Collectors so that they can communicate directly with the vCenter again.
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 analyze the relationships of this object to other components.
See the Help Center and full set of User Guides for the Veeam MP for VMware for more information including reference lists of all Rules and Monitors and details on vCenter failover functionality.
See the VMware Online Documentation for more information on VMware vSphere, in particular:
| Target | Veeam.Virt.Extensions.VMware.VIAPILink | ||
| Parent Monitor | System.Health.AvailabilityState | ||
| Category | AvailabilityHealth | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | MatchMonitorHealth | ||
| Alert Priority | High | ||
| Alert Auto Resolve | True | ||
| Monitor Type | Microsoft.Windows.2SingleEventLog2StateMonitorType | ||
| Remotable | True | ||
| Accessibility | Public | ||
| Alert Message |
| ||
| RunAs | Default |
Home
<UnitMonitor ID="Veeam.Virt.Extensions.VMware.vCenterEvents.VCConnectionStatus" Accessibility="Public" Enabled="onEssentialMonitoring" Target="VeeamVEVMwareLib!Veeam.Virt.Extensions.VMware.VIAPILink" ParentMonitorID="SystemHealth!System.Health.AvailabilityState" Remotable="true" Priority="Normal" TypeID="Windows!Microsoft.Windows.2SingleEventLog2StateMonitorType" ConfirmDelivery="true">
<Category>AvailabilityHealth</Category>
<AlertSettings AlertMessage="Veeam.Virt.Extensions.VMware.vCenterEvents.VCConnectionStatus_AlertMessageResourceID">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>High</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/Params/Param[11]$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="FirstEventRaised" MonitorTypeStateID="FirstEventRaised" HealthState="Error"/>
<OperationalState ID="SecondEventRaised" MonitorTypeStateID="SecondEventRaised" HealthState="Success"/>
</OperationalStates>
<Configuration>
<FirstComputerName>.</FirstComputerName>
<FirstLogName>Veeam Collector</FirstLogName>
<FirstExpression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">Params/Param[1]</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">VP210</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">Params/Param[5]</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">$Target/Property[Type="VeeamVEVMwareLib!Veeam.Virt.Extensions.VMware.VIAPILink"]/targetServer$</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</FirstExpression>
<SecondComputerName>.</SecondComputerName>
<SecondLogName>Veeam Collector</SecondLogName>
<SecondExpression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">Params/Param[1]</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">VP211</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">Params/Param[5]</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">$Target/Property[Type="VeeamVEVMwareLib!Veeam.Virt.Extensions.VMware.VIAPILink"]/targetServer$</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</SecondExpression>
</Configuration>
</UnitMonitor>