Unknown Configuration Error - Failed to get VIF : Not found

Products

• VMware NSX

Issue/Introduction

• VMkernel logs on the ESXi hosts reports the error Failed to get VIF : Not found
• The same error is reported as Configuration error on the VMware Aria Operations for Logs(Log insight)
• The issue is seen on multiple ESXi host across different vSphere clusters
• There is no functionality impact on the NSX-T environment
• VMkernel.log on the ESXi reports error similar to the below

2024-04-12T01:25:33.771Z esxi.hostname.com vmkernel: cpu30:2098532)LATAggregationHelper:423:[nsx@6876 comp="nsx-esx" subcomp="latency" errorCode="ESX3"]PortID 67108893: Failed to get VIF : Not found

source: esxi.hostname.com event_type: v4_f15750da facility: local6 priority: info hostname: esxi.hostname.com appname: vmkernel vmw_esxi_vmk_world: 2098532 vmw_nsxt_comp: nsx-esx vmw_nsxt_subcomp: latency vmw_nsxt_error_code: ESX3

• Running command nsxdp-cli vswitch instance list on the ESXi host confirms the PortID reported in the error log is for the vdr-vdrPort

Environment

VMware NSX-T Data Center
VMware NSX

Cause

The log line is being printed from latency component on function LATAggregationHelper. VDR port doesn't support end-to-end latency and also the VDR port does not have any VIF's connected. 

 

Resolution

Our engineering team is aware of the issue, and it is resolved in NSX 4.2.1

Note: This error can be safely ignored and there is no functionality impact on the NSX-T.