vCenter has logged a network error event for this vSphere host. Additional Knowledge Base data is available using the links below. Click the relevant link for the [EventID] as seen in the alert description to search the Veeam MP Online Help Center for further troubleshooting assistance.
Additional events can be added to this rule using overrides; if the EventID is not in the list below, use the Help Center Search Page to locate the article for the event.
The rule is enabled by default. You can override the following parameters:
Name | Default Value | Description |
Include Events | Dummy.Event.Id.1 | Allows you to include one or several vCenter Server events for monitoring, in addition to events monitored by this rule. For the list of vCenter Server events, see Veeam MP Reference. To separate multiple event IDs, use commas. |
Exclude Events | esx.problem.net.dvport.connectivity.lost | Allows you to exclude one or several vCenter Server events from monitoring. The list of events that can be excluded is provided in the 'Causes' section. To separate multiple event IDs, use commas. |
Exclude Text | DummyEventText1 | Allows you to suppress alerts that this event rule can raise, based on a keyword or text string from the alert description. For example, when an alert is triggered, the name of the affected object is inserted into the alert description. If you specify the name of the object in the override for this rule, the rule will not raise alerts for this object. |
Note: If you have configured several overrides of the same type, select the Enforced check box for an override that should have priority over all other overrides.
The event IDs and details are:
vCenter Event | Description |
VSAN network is not configured on {host.name} in cluster {computeResource.name} in datacenter {datacenter.name}. | |
Unable to obtain a DHCP lease. | |
Guest-initiated IPv6 TCP Segmentation Offload (TSO) packets ignored. Manually disable TSO inside the guest operating system, or use a different virtual adapter. | |
Firewall configuration failed. | |
Adding port to Firewall failed. | |
Cannot connect to the specified gateway. Failed to set it. | |
VDL2 instance initialization failed. | |
VDL2 overlay instance is not created on DVS. | |
VDL2 IP interface on vmknic failed to join multicast group. | |
VDL2 network initialization failed. | |
VDL2 initialization failed. | |
VDL2 IP interface failed. | |
VDL2 IP interface does not exist. | |
Lacp error: No peer response on uplink for VDS. | |
Lacp error: Current teaming policy on VDS is incompatible, supported is IP hash only. | |
Current teaming policy on VDS {1} is incompatible, supported link failover detection is link status only. | |
Lacp error: Duplex mode across all uplink ports must be full, VDS uplink has different mode. | |
Lacp error: Speed across all uplink ports must be same, VDS uplink has different speed. | |
Lacp error: All uplinks on VDS must be active. | |
VSAN doesn't have any network configuration. This can severely impact several objects in the VSAN datastore. | |
Host {host.name} has the following extra networks not used by other hosts for HA communication:{ips}. Consider using HA advanced option das.allowNetwork to control network usage. | |
Cannot complete command 'hostname -s' on host {host.name} or returned incorrect name format. | |
Host {host.name} does not have the following networks used by other hosts for HA communication:{ips}. Consider using HA advanced option das.allowNetwork to control network usage. | |
Host {host.name} currently has no available networks for HA Communication. The following networks are currently used by HA: {ips}. | |
Host {host.name} has no port groups enabled for HA communication. Note: Monitoring of this event is disabled by default. | |
Primary agent {primaryAgent} was not specified as a short name to host {host.name}. | |
The MTU configured in the vSphere Distributed Switch does not match the physical switch connected to uplink port {healthResult.uplinkPortKey} in vSphere Distributed Switch {dvs.name} on host {host.name} in {datacenter.name} | |
Network configuration on the host {host.name} is rolled back as it disconnects the host from vCenter server. | |
Teaming configuration in the vSphere Distributed Switch {dvs.name} on host {host.name} does not match the physical switch configuration in {datacenter.name}. | |
Not all VLAN MTU settings on the external physical switch allow the vSphere Distributed Switch maximum MTU size packets to pass on the uplink port {healthResult.uplinkPortKey} in vSphere Distributed Switch {dvs.name} on host {host.name} in {datacenter.name}. | |
Not all the configured VLANs in the vSphere Distributed Switch were trunked by the physical switch connected to uplink port {healthResult.uplinkPortKey} in vSphere Distributed Switch {dvs.name} on host {host.name} in {datacenter.name}. | |
Guest-initiated IPv6 TCP Segmentation Offload (TSO) packets ignored. Manually disable TSO inside the guest operating system in virtual machine, or use a different virtual adapter. | |
Virtual NIC with hardware address failed to connect to distributed virtual port. No more ports available on the host proxy switch. |
Resolution is dependent on the nature of the event. Use the EventID KB links above to search for more information.
Note that this rule will suppress multiple events, even those with different IDs, in order to prevent unnecessary multiple alerts. However all underlying events will be collected. Check the Repeat Count on this alert to understand if multiple events have been suppressed.
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.
See the Help Center for more information including reference lists of all Rules and Monitors and full set of User Guides for the Veeam MP for VMware.
See the VMware Online Documentation for more information on VMware vSphere, in particular:
Target | Veeam.Virt.Extensions.VMware.VMHOST | ||
Category | EventCollection | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | Error | ||
Alert Priority | High | ||
Remotable | True | ||
Alert Message |
|
ID | Module Type | TypeId | RunAs |
---|---|---|---|
DS | DataSource | Veeam.Virt.Extensions.VMware.FilteredEventProvider | Default |
Alert | WriteAction | System.Health.GenerateAlert | Default |
<Rule ID="Veeam.Virt.Extensions.VMware.GroupEvents.Host.Network.Error" Enabled="onEssentialMonitoring" Target="VeeamVEVMwareLib!Veeam.Virt.Extensions.VMware.VMHOST" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>EventCollection</Category>
<DataSources>
<DataSource ID="DS" TypeID="VeeamVEVMwareLib!Veeam.Virt.Extensions.VMware.FilteredEventProvider">
<Expression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="Integer">EventLevel</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="Integer">1</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.VMHOST"]/id$</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</Expression>
<EventGroup>ESXHostNetwork</EventGroup>
<IncludeEvents>Dummy.Event.Id.1|Dummy.Event.Id.2</IncludeEvents>
<ExcludeEvents>esx.problem.net.dvport.connectivity.lost|esx.problem.net.connectivity.lost|vprob.net.connectivity.lost|SV132|SV138|HostNoHAEnabledPortGroupsEvent</ExcludeEvents>
<ExcludeText>DummyEventText1|DummyEventText2</ExcludeText>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="Alert" TypeID="SystemHealth!System.Health.GenerateAlert">
<Priority>2</Priority>
<Severity>2</Severity>
<AlertOwner/>
<AlertMessageId>$MPElement[Name="Veeam.Virt.Extensions.VMware.GroupEvents.Host.Network.Error.AlertMessage"]$</AlertMessageId>
<AlertParameters>
<AlertParameter1>[$Data/Params/Param[1]$] $Data/Params/Param[11]$</AlertParameter1>
</AlertParameters>
<Suppression>
<SuppressionValue/>
</Suppression>
</WriteAction>
</WriteActions>
</Rule>