Federated API calls made to non Federated NSX deployment fail with Operation status: 'failure'

Products

• VMware NSX

Issue/Introduction

• A non Federated NSX deployment is in place.
• Services are running API calls to the NSX Manager that result in failures. 
• Entries similar to the below will be observed on the NSX Manager in /var/log/syslog

  NSX 77523 SYSTEM [nsx@6876 audit="true" comp="nsx-manager" level="INFO" subcomp="manager"] UserName:<username>' ModuleName:'Policy' Operation:'GET@/api/v1/infra/global-managers' Operation status: 'failure' Error: The path=[/global-infra] is invalid

• A HTTP 400 response will be observed on the NSX Manager in /var/log/proton/localhost_access_log.txt

  "GET /nsxapi/api/v1/infra/global-managers HTTP/1.1" 400 157 6 5 -

• Security audits may flag this issue as a security concern if the Operation Failures are categorized as login attempts.

 

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

Environment

VMware NSX 4.x
VMware NSX-T Data Center 3.x

Cause

This is encountered when services poll a non Federated deployment with Federated API calls. 

Resolution

This is a condition that may occur in a VMware NSX environment when Federated API calls are executed against a non Federated NSX Manager.

 

Workaround

Review the configuration of the API client making the calls and disable Federated calls. 

Additional Information

VCF Operations for Networks continually reports bad request 400 for API call, GET /policy/api/v1/global-infra/global-managers