vCenter has logged a network warning 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.redundancy.degraded | 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 |
Virtual machine {macAddress} on host {host.name} has a duplicate IP {duplicateIP}. | |
The Distributed Virtual Switch {dvs.name} configuration on the host differed from that of the vCenter Server. | |
VDL2 IP changed. | |
Mapping table entries of VDL2 network on DVS exhausted. This network might suffer a low performance. | |
VDL2 IP interface default route changed. | |
dhclient reported an error. | |
No working DHCP leases in persistent database. | |
VMkernel failed to set fenceId. | |
Maximum number of fence networks or ports have been reached. | |
dvSwitch fence property is not set. | |
Heap free size dropped. | |
Host has detected high round-trip vMotion network latency. High latency vMotion networks are supported only if both hosts have been configured for vMotion latency tolerance. | |
Maximum number of ports has been reached. Cannot apply for any more free ports. | |
Invalid VLANID. VLAN ID must be between 0 and 4095. | |
Virtual NIC with hardware address failed to connect to distributed virtual port. There are no more ports available on the host proxy switch. | |
A duplicate IP address was detected on a vmknic interface. | |
Taking down physical NIC because the link is unstable. | |
Uplink has recovered from a transient failure due to watchdog timeout. | |
Lacp warning: uplink on VDS is blocked. | |
Lacp warning: uplink on VDS got disconnected. | |
Lacp warning: uplink on VDS is moved out of link aggregation group. | |
The host advanced configuration option /Migrate/Vmknic is set to an invalid vmknic: {1}. | |
Failed to set MTU on an uplink. | |
vmknic {1} that is currently configured to be used with VSAN doesn't have an IP address yet. There are no other active network configuration and therefore the VSAN node doesn't have network connectivity. | |
VSAN network configuration doesn't have any redundancy. This might be a problem if further network configuration is removed. | |
VSAN network configuration redundancy has been reduced. This might be a problem if further network configuration is removed. | |
Configuration of host IP address is inconsistent on host {host.name}: address resolved to {ipAddress} and {ipAddress2}. | |
Cannot resolve IP address to short name on host {host.name}. | |
Host {host.name} could not reach isolation address: {isolationIp}. | |
Host {host.name} currently has no management network redundancy. | |
Host names {shortName} and {shortName2} both resolved to the same IP address. Check the host's network configuration and DNS entries. | |
Cannot resolve short name {shortName} to IP address on host {host.name}. | |
The ESX advanced config option /Migrate/Vmknic is set to an invalid vmknic: {1}. Note: Monitoring of this event is disabled by default. |
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 | Warning | ||
| 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 |
Home
<Rule ID="Veeam.Virt.Extensions.VMware.GroupEvents.Host.Network.Warning" 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">2</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.redundancy.degraded|esx.problem.net.dvport.redundancy.lost|vprob.net.redundancy.degraded|vprob.net.redundancy.lost|esx.problem.net.redundancy.degraded|esx.problem.net.redundancy.lost|esx.problem.net.vmnic.linkstate.down|vprob.net.migrate.bindtovmk</ExcludeEvents>
<ExcludeText>DummyEventText1|DummyEventText2</ExcludeText>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="Alert" TypeID="SystemHealth!System.Health.GenerateAlert">
<Priority>2</Priority>
<Severity>1</Severity>
<AlertOwner/>
<AlertMessageId>$MPElement[Name="Veeam.Virt.Extensions.VMware.GroupEvents.Host.Network.Warning.AlertMessage"]$</AlertMessageId>
<AlertParameters>
<AlertParameter1>[$Data/Params/Param[1]$] $Data/Params/Param[11]$</AlertParameter1>
</AlertParameters>
<Suppression>
<SuppressionValue/>
</Suppression>
</WriteAction>
</WriteActions>
</Rule>