HTTP status 400 when running API calls to NSX

Products

• VMware NSX

Issue/Introduction

• API calls made to the NSX Manager fail with HTTP status 400, this can be observed in /var/log/proxy/envoy_access_log.txt with entries similar to the below:

  "GET" "/api/v1/loadbalancer/pools?page_size=1000" "HTTP/1.1" 400
  "GET" "/api/v1/loadbalancer/services?page_size=1000" "HTTP/1.1" 400
  "GET" "/api/v1/loadbalancer/virtual-servers?page_size=1000" "HTTP/1.1" 400
  "GET" "/api/v1/logical-routers/########-####-####-####-############?page_size=1000" "HTTP/1.1" 400
  "GET" "/api/v1/logical-routers/########-####-####-####-############/routing/route-maps?page_size=1000" "HTTP/1.1" 400

• Entries similar to the below will be observed in /var/log/syslog:

  NSX 87536 SYSTEM [nsx@6876 audit="true" comp="nsx-manager" level="INFO" subcomp="manager"] UserName:'<user>' ModuleName:'internal-framework' Operation:'GET@/api/v1/loadbalancer/services' Operation status: 'failure' Error: Certificate was revoked: [LbRule, InternalGroup, StaticHopBfdPeer, IpSecVpnLocalEndpointConfig, InternalSwitchSecuritySwitchingProfile, LoadBalancerSslProfile, StaticRoute, LogicalSwitch, LogicalRouter, NatRule, IpfixDfwConfig, FirewallSection, IpSecVpnPeerEndpointConfig, L2VpnSessionConfig, Certificate, InternalTransportZoneProfile, LoadBalancerMonitor, DnsForwarder, InternalIpSecVpnDpdProfile, LoadBalancerPersistenceProfile, InternalIpv6NdraProfileConfig, BaseHostSwitchProfile, InternalCommunityList, InternalPrefixListConfig, TransportNodeProfile, LrPort, L2VpnServiceConfig, PolicyTransportZone, HostTransportNode, InternalIpv6DadProfileConfig].

• Entries similar to the below will be observed in /var/log/proton/nsxapi.log

  ERROR http-nio-127.0.0.1-7440-exec-2074 PersistedQueryProcessorImpl 87536 - [nsx@6876 comp="nsx-manager" errorCode="MP2060" level="ERROR" reqId="########-####-####-####-############" subcomp="manager" username="<user>"] Tablename missing from indexing keyset.

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

Environment

VMware NSX 4.x
VCF NSX 9.0

Resolution

This is a known issue impacting VMware NSX.

 

Workaround

• Should you encounter this issue restart the manager service on the impacted NSX Manager via the admin user in the NSX CLI:

  restart service manager