The alarm informs you about the packets that couldn't be transmitted because of errors. Do you constantly see this alarm for your Hyper-V host? How have you configured your networks for this server? Do you have many VMs using this NIC to transmit the data?
I always have this error on this server. I have a teeming of 4 network cards that make a virtual network. there are 4 vm on this server (3 tse and 1 file server)
no error on another server with the same configuration hardware and hyperv with 4 VM (1 exchange, sql 2, 1 dc)
Can you please navigate to this host and then click on a Network Tab and choose "Current Object" as a chart option and select a "Network Errors" chart view? What does this view show you? Do you see a NIC which might the reason for these outbound errors?
Do you possibly know what metrics does the HP utility use to calculate "Total Errors" parameter? The reason why I ask you about it is that with Veeam ONE we are relying on Windows performance metrics that can be found through Perf. monitor. Most likely HP is looking into something else for this metric.
Anyway it seems like these errors do no affect your VMs performance (based on your feedback), but I would still recommend to keep an eye on the outbound errors number. If this number will keep growing then you should take a closer look at your physical NICs/network configuration.
Actually there is nothing strange in this situation. Even though your hosts are from the same manufacturer, they have a different load on their network interfaces, which in turn might lead to situations like that.
As you can see in the previous screen shots, in the "Network and Sharing Center" ther is
Connexion au réseau local
Connexion au réseau local 2
Connexion au réseau local 3
Connexion au réseau local 4
Connexion au réseau local 5
Connexion au réseau local 6
Connexion au réseau local 8
Lan Blade
Team Iscsi
but I don't know what is "Connexion au réseau local*" with a star (*) at the end.
Oh, got it. One of the possible reasons for this extra character is a non-English Hyper-V server being used, looks like a localization UI glitch to me. Thanks for heads up!