Error: "The requested runtime information cannot be retrieve for all EnforcementPoints" when viewing statistics for or editing L2 VPNs
search cancel

Error: "The requested runtime information cannot be retrieve for all EnforcementPoints" when viewing statistics for or editing L2 VPNs

book

Article ID: 390586

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

  • When clicking the Edit button for an L2 VPN in the VMware Cloud Director (VCD) Portal, the current configuration information doesn't load, the Save button is greyed out, and you see an error similar to:

    [ ########-####-####-####-########8b9e ] Bad Request: Error occurred in the backing network provider: The requested runtime information cannot be retrieved for all EnforcementPoints because there is no support to get the specific runtime information for [/infra/sites/default/enforcement-points/alb-endpoint]. Please try the API with specific enforcement_point_path that supports such runtime information., error code 500276

  • When clicking the View Statistics button for an L2 VPN in the VCD Portal, no statistical information loads and you see errors similar to:

    [ ########-####-####-####-########8520 ] Bad Request: Error occurred in the backing network provider: The requested runtime information cannot be retrieved for all EnforcementPoints because there is no support to get the specific runtime information for [/infra/sites/default/enforcement-points/alb-endpoint]. Please try the API with specific enforcement_point_path that supports such runtime information., error code 500276

    [ ########-####-####-####-########bb62 ] Internal Server Error: Error occurred in the backing network provider: General error has occurred., error code 100

  • Attempting to view the L2 VPN Tunnel, its status, or its metrics via the VCD API, the response body contains the same errors as seen in the Portal.
  • Navigating to the L2 VPN via the NSX UI, the statistics view loads correctly.

Environment

  • VMware Cloud Director 10.6.0.1
  • VMware Cloud Director 10.6.1

Cause

This issue occurs when VMware Avi Load Balancer (ALB) has been registered to the NSX instance being used by VMware Cloud Director. When ALB is registered to NSX, a second Enforcement Point is created in NSX and the API call VCD sends to NSX to query information about the L2 VPN incorrectly does not filter out this additional Enforcement Point.

Resolution

This is a known issue impacting VMware Cloud Director 10.6.0.1/10.6.1.

This issue is resolved in VMware Cloud Director 10.6.1.1, available from the Broadcom Support Portal.

Workaround: None

Additional Information