Failed to add Velocloud Orchestrator due to "getEnterprise" API failure with "400 (Bad Request)"

12/18/2024 1:46 PM

1/7/2025 4:54 PM

When adding a Velocloud orchestrator, SolarWinds Platform fails to add it as a node.  In the Orchestator.BusinessLayer.log, the following error message may appear:

SolarWinds.Orion.Orchestrators.Common.API.RequestProcessor.RequestProcessorBase - An error occurred during 'https://XXXX/portal/rest/enterprise/getEnterprise' request. Exception: System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request).
   at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()
   at SolarWinds.Orion.Orchestrators.Common.Models.HttpResponseWrapper.EnsureSuccessStatusCode()
   at SolarWinds.Orion.Orchestrators.Common.API.RequestProcessor.RequestProcessorBase.<ProcessRequest>d__15.MoveNext(

Orion Platform

When adding the VeloCloud orchestrator as an MSP, the API call for getEnterprise will fail with a "400 (Bad Request)" response and will not add to the SolarWinds Platform.
 
The problem occurs because the MSP account requires each request to contain enterpriseId, which can be omitted when using a customer account.

enterpriseId

The Portal API enforces that an enterpriseId parameter is required on any request initiated by an Operator or Partner Administrator that accesses, or operates upon, a Customer-managed resource (e.g. Edges, Profiles, network services). enterpriseId is never required for API calls initiated by Customer Administrators (in such cases it is inferred based on the user's credential).

Reference Document: https://developer.broadcom.com/xapis/velocloud-orchestrator-api/latest/

As of January 2025, the SolarWinds Platform does not support the MSP account. If this feature is necessary, please file a support ticket and reference the following knowledge base article.

As a workaround, you can add each Velocloud tenant separately and assign it to a different additional polling engine (APE).