Usage Meter 9.X reports "Incomplete collection" or "Collection error" status for NSX-T.

Products

• VMware Usage Meter

Issue/Introduction

• Status for NSX-T endpoint is reported as 'Incomplete collection' in Usage Meter UI
  
• Status 'Collection error' for NSX-T endpoint.
  
• Notifications tab on the UI report the following messages:
  
• In /var/log/vmware-um-platform/collection-nsx-t-main.log of Usage Meter appliance, you see errors similar to:
  

  ERROR --- [collector-main-thread] c.v.u.n.addon.NSXTAddOnCollector   : vDefend features collectoin GatewayConfigDetector failed for server 16: API endpoint policy/api/v1/search/querypipeline on server 16 returned HTTP status 400
  com.vmware.um.collector.UnexpectedResponseCode: API endpoint policy/api/v1/search/querypipeline on server 16 returned HTTP status 400
          at com.vmware.um.collector.http.RequestBuilder.getResponse(RequestBuilder.java:202)
          at com.vmware.um.collector.http.RequestBuilder.as(RequestBuilder.java:235)

• Running the NSX API  'https://<nsx-manager>/policy/api/v1/search/querypipeline' with following body returned large number of Gateway Firewall rules in 'UNINITIALIZED' state
  {
    "query_pipeline": [
        {
            "query": "resource_type:(GatewayPolicy) AND stateful:true AND is_default:false"
        }
    ]
}

Environment

VCF Usage Meter 9.x
NSX-T 4.x

Cause

A large number of uninitialized Gateway Firewall rules on NSX are causing this issue, as Usage Meter is unable to parse them.

Resolution

To resolve this issue, cleanup the policies that have no rules in NSX. Refer NSX gateway Firewall polices/sections with no rules.

For assistance in removing these references from NSX, please contact NSX Support and note these Article IDs (372642 and 406275).

Note: Delete and re-add the NSX product in Usage Meter if the issue persists.