“Incomplete collection status” error while integrating Usage Meter with NSX Local Manager from Federation setup

Products

• VMware Usage Meter

Issue/Introduction

When integrating Usage Meter with an NSX Local Manager from Federation setup, the Usage Meter UI displays an “Incomplete collection status” error and reports a 404 response:

vDefend features collection DfwConfigDetector failed for server <number>:  
API endpoint 'policy/api/v1/infra/domains/default/security-policies/default-malicious-ip-block-rules' on server returned HTTP status 404.

Environment

VMware Usage Meter 9.0 and 9.0.1
NSX Local Manager (LM) configured in a Federation environment with Global Manager (GM)

Cause

This issue occurs only when the LM is config on-boarded to a GM. During onboarding, Global Manager takes over control of certain policy objects, including the default-malicious-ip-block-rules, and migrates them under the GM path:

Removed LM path:

/infra/domains/default/security-policies/default-malicious-ip-block-rules

New GM path:

/global-infra/domains/<SiteName>/security-policies/default-malicious-ip-block-rules

As a result, any Usage Meter collector queries to the old LM path return HTTP 404, triggering the “Incomplete collection” status.

 

Note: If the Local Manager is not config on-boarded to Global Manager, the object default-malicious-ip-block-rules continues to exist locally, and this issue will not be observed.

Resolution

Although Usage Meter 9.0 and 9.0.1 do not natively support federated Global Managers, you can work around this error by recreating the missing policy object on the LM:

1. Remove the affected LM from Usage Meter.
2. On the LM, navigate to DFW → Infrastructure and create a new empty DFW section named 'default-malicious-ip-block-rules' (no rules inside).
3. Re-add the LM to Usage Meter.
4. The LM registers successfully, and the “Incomplete collection” error is resolved.