iSM: Low Metric Assigned to iDRAC USB NIC Conflicts with IPv4 Resolution or Cluster Heartbeat
Summary:
Domain Name System (DNS) resolving the local hostname may return the internal IP address of the USB Network Interface Card (NIC) passthrough device enabled by iDRAC Service Module
(iSM). This can cause issues with internal network devices configured with 169.254.x.x nonroutable addresses. The metric of the USB NIC device should be manually set to a high number so that internal network devices take precedence.
...
Please select a product to check article relevancy
This article applies to This article does not apply toThis article is not tied to any specific product.Not all product versions are identified in this article.
Some third-party products and services rely on resolving the host’s local DNS name to the fastest network interface in the host. Windows determines this order by automatically assigning metric values based on the interface’s rated speed when determining the route table.
If the OS Passthrough feature of iDRAC is enabled, the USB NIC presented may be assigned an equal or lower (faster) value than other NICs. This can result in nslookup resolving the host with the USB NIC’s internal 169.254.x.x address.
To see what Windows chooses for the InterfaceMetric values for all interfaces including the USB NIC, use PowerShell:
Get-NetIPInterface | sort InterfaceMetric
Cause
iDRAC Service Module attempts to assign metrics to the USB NIC network device that only communicates internally with iDRAC. It may take precedence over internal devices with a lower metric.
Resolution
This does not cause issues with various internal Windows services but has been found to cause issues with certain third-party services such as web proxy servers that expect a routable address. Conflicts have also been seen with NICs also assigned 169.254.x.x addresses with higher (slower) metrics used for clustering heartbeats.
Engineering recommends overriding the automatic USB NIC metric with a higher value such as 999. This can be done with the Windows user interface by opening the USB NIC interface’s IPv4 properties then clicking Advanced > IP Settings and clear Automatic metric before entering 999. Alternately, this can be done using PowerShell with the command:
iDRAC Service Module (iSM) must enable this USB NIC interface and it still works correctly with the higher (slower) metric with no performance concerns.