Cannot invoke "com.vnera.model.core.Layer2Network.getModelKey()" because "l2l" is null for Cisco ACI environment

Products

• VCF Operations for Networks

Issue/Introduction

When performing data collection from an NSX-T data source in VCF Operations for Networks, you observe the following symptoms:

• Logical ports in NSX data collection fail to populate or show up in the interface.
• The VM-VM path topology fails to render correctly with "Unexpected Error: Cannot invoke "com.vnera.model.core.Layer2Network.getModelKey()" because "l2l" is null." 
  
• The collector logs (latest.log) contain the following error snippet:
  

  [YYYY-MM-DDTHH:MM:SSZ] ERROR common.utils.CommonUtils ,<datasource_name>_Config_OpMgr-1 logException:2680 Error in obtaining LogicalPortOperationalStatus for manager https://<datasource_name>:443
  java.util.ConcurrentModificationException: null
          at java.util.ArrayList.forEach(ArrayList.java:1513) _[_:_]
          at com.vnera.dataproviders.core.impl.vmware.nsxt.tasks.datafetchers.NSXTLogicalPortOperationalStatusFetcher.lambda_pushPayload_2(NSXTLogicalPortOperationalStatusFetcher.java:55) _[dataproviders-0.001-SNAPSHOT.jar:_]

  
  

NOTE:  VCF Operations for Networks was formerly named Aria Operations for Networks (AON), and prior to that was named vRealize Network Insight (vRNI).

Environment

• VCF Operations for Networks
• VMware NSX

Cause

The issue is caused by the enableNSXTPolicyAPI feature flag being set to false at the platform or collector level. This prevents the system from correctly utilizing the NSX-T Policy API to resolve Layer 2 network model keys during topology queries

Resolution

If you believe you have encountered this issue, please open a Broadcom Support case. For more information, refer Creating and managing Broadcom support cases.

Additional Information

Missing data from NSX - Logical Port Operational Status error in Logs for VCF Operations for Networks

VM_VM path Topology is not working in VCF Operations for Networks for Cisco ACI environment