NSX Edge NAT Metrics not loading in Aria Operations For Networks User Interface

Products

• VCF Operations for Networks
• VMware NSX

Issue/Introduction

• From within AON User Interface, searching with query NSX-T Transport Node '<edge name>'  returns the Edge node data.
• When clicking the NAT Metrics tab, the following metrics are not displayed.
  
  
  • Top NAT Rules by Total Bytes
  • Top NAT Rules by Total Packets
  • Top NAT Rules by Session Count
    
    
• The NAT Rule Statistics are displayed. If not, please see the following KB 370358
• The collector logs does not show any API call being sent from Collector to NSX Manager to collect the NAT statistics in /var/log/arkin/collector/

#grep "/policy/api/v1/infra/tier.*nat.*statistic" var/log/arkin/collector/latest.log | wc -l
0

• The following API failure is seen within the collector logs.
  
  var/log/arkin/collector/latest.log
[Timestamp] ERROR dataprovider.utils.HttpUtils Config_OpMgr_Policy-0 checkStatusAndThrow:41 API /policy/api/v1/infra/tier-1s/[TIER Name]/nat/NAT64/nat-rules error response {
  "httpStatus" : "BAD_REQUEST",
  "error_code" : 500012, 
  "module_name" : "Policy",
  "error_message" : "The path=[/infra/tier-1s/[TIER Name]/nat/NAT64] is invalid"
}
  
  
  

Environment

VCF Operations for Networks 6.13

VCF Operations for Networks 6.14

VCF Operations for Networks 6.14.1

VMware NSX 

Cause

In 6.14.0 VCF Operations for Networks moved to Policy API and in some instances the enableNSXTPolicyAPI flag is set correctly on Platform and Collector nodes and needs to be reverted back to Management API.

Resolution

This is a known issue affecting Aria Operations For Networks/vRealize Network Insight.

If you believe you have encountered this issue, please open a support case with Broadcom Support and refer to this KB article.

For more information, see Creating and managing Broadcom support cases.