Avamar: AVE proactive health check fails to recognize Ethernet Settings on node deployed in Hyper-V or AWS

Summary: Avamar: Virtual Edition: The proactive health check fails to recognize Ethernet Settings on an Avamar node deployed in a Hyper-V or AWS environment

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.

Symptoms


The proactive health check script reports the "Ethernet Settings" as failed.
The proactive health check shows empty speed for the eth0. 
Example for the Hyper-V environment:

# --> Hardware Manufacturer           hyperv
 .
ERROR:  (0.0) eth0 speed is  instead of at least 1000Mb/s
ERROR:  (0.0) eth0 duplex is  instead of Full
ERROR:  (0.0) eth0 auto negotiation is  instead of on
RESOLUTION:  See KB466119 for troubleshooting NIC cards and speeds

# --> Ethernet Settings              *FAILED*


Example for the AWS environment:

# --> Hardware Manufacturer           other
 .
ERROR:  (0.0) eth0 speed is  instead of at least 1000Mb/s
ERROR:  (0.0) eth0 duplex is  instead of Full
ERROR:  (0.0) eth0 auto negotiation is  instead of on
RESOLUTION:  See KB466119 for troubleshooting NIC cards and speeds

# --> Ethernet Settings              *FAILED*

Cause

The failure is caused by the fact that the Hyper-V and AWS network drivers for Linux OS are very limited and do not provide information about speed and duplex to ethtool.
Example:

#: ethtool eth0
Settings for eth0:
        Link detected: yes

 

Resolution

Please check if the correct driver is being used by the VM

ethtool -i eth0

Sample output for Hyper-V:

driver: hv_netvsc
version:
firmware-version: N/A
bus-info:
supports-statistics: no
supports-test: no
supports-eeprom-access: no
supports-register-dump: no


Sample output for AWS:

driver: netfront
version:
firmware-version:
bus-info: vif-0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no


If the driver name reported by the ethtool command is hv_netvsc or netfront, the error message can be simply ignored, otherwise the correct driver should be selected at the VM level after stopping the Avamar services. The future versions of the proactive health check will have ethernet checks adjusted.
 

Additional Information

More information about the Hyper-V driver's limitation: http://mindworks.shoutwiki.com/wiki/Ethtool_Support_for_Microsoft_Hyper-VThis hyperlink is taking you to a website outside of Dell Technologies.

 

Affected Products

Avamar

Products

Avamar, Avamar Virtual Edition
Article Properties
Article Number: 000065446
Article Type: Solution
Last Modified: 06 Mar 2025
Version:  4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.