NSX-T An error occurred during host configuration. "Operation Failed. Diagnostics report: Unable to complete sysinfo operation." error when adding vmknic(s) to NVDS"
search cancel

NSX-T An error occurred during host configuration. "Operation Failed. Diagnostics report: Unable to complete sysinfo operation." error when adding vmknic(s) to NVDS"

book

Article ID: 318280

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

 

  • vmknic cannot be attached to NVDS
  • vmknics may be set to "disabled" state during migration of a vmknic to N-VDS segment
  • In NSX-T Data Center UI, you may see the error message on Host Transport Node:

Host configuration: MigrateTOLs(vDS UUID) failed: [error: vmknic vmkX is not found; vmknic vmkY is not found; ]; LogicalSwitch full-sync: LogicalSwitch full-sync realization query skipped.

  • NSX-T is linked to VMware vRealize Network Insight (vRNI), which has "Latency" feature enabled in NSX-T.
  • In vmkernel.log on the impacted ESXi host, you may observe the following warning (/scratch/log/vmkernel.log):

2022-01-19T15:18:44.380Z cpu19:2103207 opID=65911259)WARNING: NetDVS: 2413: failed to init client for data com.vmware.nsx.latency.param on port ########-####-####-####-########fa85
or
2021-11-30T18:17:55.455Z cpu8:2294665)WARNING: kcp: KCPSetPortProp:513: [nsx@6876 comp="nsx-esx" subcomp="kcp"]Failed to set port ######### property com.vmware.nsx.latency.param : Bad parameter
vmkernel.log:2021-11-30T18:17:55.455Z cpu8:2294665)WARNING: kcp: KCP_CPProcessUpdateMsg:2222: [nsx@6876 comp="nsx-esx" subcomp="kcp"]Failed to process port property list : Failure

 

Environment

VMware NSX-T Data Center 3.x
VMware NSX-T Data Center
VMware NSX
VMware NSX 4.2

Cause

VMware vRealize Network Insight latency feature is only supported with a vNIC and a pNIC; vmknic doesn't support latency feature.

Due to this, vmknic is disabled during migration to a switch with latency feature enabled.

Resolution

This issue is resolved in NSX-T Data Center 3.2.1, available at VMware vSphere downloads, VMware Converter, OEM custom images, patches and addons in the Broadcom Support Portal


Workaround:
There are two approaches to workaround this issue:

---- Approach 1 ----

  1. Disable VMware vRealize Network Insight latency in NSX-T. POST https://<NSX-Manager-IP>/api/v1/latency-profiles with "pnic_latency_enabled=false" in the body. 
    Ref. NSX-T Data Center REST API: POST /api/v1/latency-profiles
  2. Disable vRNI latency in vRNI.
    Ref. VMware vRealize Network Insight - Add VMware NSX-T Manager
  3. Add/migrate vmknic(s).
  4. Enable vRNI latency (revert steps 2 and 1).

---- Approach 2 ----
Attach vmknic to a distributed portgroup instead of logical switch.