NSX UI does not display statistics for dFW rules hit count and N_VDS physical NIC statistics.
search cancel

NSX UI does not display statistics for dFW rules hit count and N_VDS physical NIC statistics.

book

Article ID: 317684

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

Symptoms:

  • NSX-T version 2.5.x, 3.0.x 
  • NSX-T Manager UI is unable to display N-VDS physical NIC statistics.
  • NSX-T Manager UI is unable to display dFW rules hit count statistics. 
  • API Call api/v1/transport-nodes/<TN-ID>/network/interfaces/<interfaceID>/stats returns an empty output. 
  • A remote console interface exists on the affected ESXi hosts as for example "vusb0"


In the NSX-T syslog.log and nsxapi.log you can see: 

2020-05-11T15:38:14.306Z WARN cvn-hv:HostNodeStatusVertical-0 GSROverwritePullResponseHandler - - [nsx@6876 comp="nsx-manager" level="WARN" subcomp="manager"] Failed to process overwrite stats: app=HostNodeStatusVertical, clientType=cvn-hv, clientToken=66b7c13c-8be0-###-####-########253, error=java.lang.Exception: target type must not be null.d


In the ESXi host logs nsx-syslog.log: 

2021-06-16T04:09:54Z nsx-exporter: NSX 2129105 - [nsx@6876 comp="nsx-esx" subcomp="agg-service" tid="2129548" level="INFO"] [EsxHostNodeStatusVertical][GetHostNodeInterfaceStatistics] Collecting all overwrite interface statistics
2021-06-16T04:09:54Z nsx-exporter: NSX 2129105 - [nsx@6876 comp="nsx-esx" subcomp="agg-service" tid="2129548" level="INFO"] [AddTargetError]: Adding target error [-5002] for [::node_interface:vusb0]
2021-06-16T04:09:54Z nsx-exporter: NSX 2129105 - [nsx@6876 comp="nsx-esx" subcomp="agg-service" tid="2129548" level="ERROR" errorCode="MPA12003"] [EsxHostNodeStatusVertical][SetInterfaceStatistics] Unable to set stats for intf: vusb0



Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment



Environment

VMware NSX-T

Cause

This issue occurs due to a software defect in NSX-T

Resolution

This issue is resolved in NSX-T 3.1.0 available at Support Documents and Downloads.