To Provide cause and workaround for the VIF API not returning correct values and causing collection failure on the NSX-T Datasource

• NSX-T datasource throws error similar to "Data Source is not reachable from Collector VM"
• Security Group details are not attached to VMs in vRNI
• Collector logs are overly logging suppressed sdm message like below, causing the logs to rotate within 3min window:

2022-02-01T18:05:17.362Z INFO dataprovider.utils.CollectorUtils NSXT_nsxdeweiis.infoserve.endress.com_Config_OpMgr_Policy-0 pushPayLoadToCollector:311 Suppressing upstreamDataType=com.vnera.model.vmware.policymanager.VirtualNetworkInterface.config, hashKey=52d5c3ca-cd4e-4c06-b58a-2db6a5b2ec58, consumerIdentifier=1, dpIdentifier=dataProviderIdentifier: "NSXT_NSX_T_IP_or_FQDN"

customerId: 12885

suppressionKey=null

• NSX-T API outputs of

/policy/api/v1/infra/realized-state/enforcement-points/default/vifs

/api/v1/fabric/vifs

• Returns the same output

....

"result_count" : 1608,

"cursor" : "00406047232139751999022.-6804718935994577644TmV0d29yayBhZGFwdGVyIDE="

• NSX-T Environment has greater than 1000 VIFs

• The NSX-T API endpoint /policy/api/v1/infra/realized-state/enforcement-points/default/vifs?page_size=1000 returns 1000 entries and a cursor at the end in the response.
• Using the cursor value from the above response we fire another API as mentioned below: /policy/api/v1/infra/realized-state/enforcement-points/default/vifs?page_size=1000&cursor=<value-of-cursor>
• This returns the same cursor value
• NSX-T APIs which we use to fetch Virtual Network Interface return same cursor over and over, leading to fetch of the same set of entities, and in turn, leading to the task getting stuck.

This issue is resolved in NSX-T 3.2.2 and 4.0.

VMware TSEs can provide a patch for 3.2.0.1 and 3.2.1.1. Please open an NSX-T SR and reference this KB.

• NSX-T datasource will fail to collect.
• Security Groups will not be attached to NSX-T VMs