Refer to the exhibit. A network engineer must collect error statistics for interfaces on Cisco Catalyst SD-WAN vManage routers. The engineer creates a Python script to make Cisco Catalyst SD-WAN…

Question

Explanation

A Python script querying Cisco Catalyst SD-WAN vManage for real-time interface error statistics returns HTTP 400 (Bad Request). This indicates the client sent a malformed or invalid request - not an authentication or server failure.

Approach. An HTTP 400 Bad Request from the vManage REST API means the server understood the request but rejected it due to a client-side error - most commonly an incorrect HTTP method, a malformed request body, or missing required parameters. For vManage statistics endpoints (e.g., /dataservice/statistics/interface or /dataservice/device/interface/synced), queries typically require a POST request with a properly structured JSON body specifying fields such as query criteria, time range, and device identifiers - not a simple GET. The fix is to correct the API call: ensure the HTTP method is POST (not GET), include a valid JSON payload with required query parameters (startDate, endDate, fields, filter), and set the Content-Type header to 'application/json'. Validating the exact endpoint path against the vManage API documentation for the target software version is also essential, as endpoint paths can vary between releases.

Concept tested. Cisco Catalyst SD-WAN vManage REST API usage - specifically understanding that HTTP 400 indicates a malformed client request (wrong method, missing/invalid body, or incorrect parameters) rather than an authentication or server-side fault, and knowing that vManage statistics queries require POST with a structured JSON body rather than a simple parameterless GET.

Reference. Cisco Catalyst SD-WAN vManage REST API documentation - Statistics and Monitoring endpoints; Cisco DevNet SD-WAN API Learning Labs

No community discussion yet for this question.