A regional hospital is staging an SD-WAN upgrade and its asset team needs one automated list of every WAN edge known to SD-WAN Manager, including edges that are currently offline, showing each device's hostname, site ID, serial number and most recently reported software release for reconciliation. Which API family should the automation call to build that device record?
Select an answer to reveal the explanation.
Short Explanation
Use the device inventory API family to get one list of every edge SD-WAN Manager knows about, including offline devices, with hostnames, site IDs, serial numbers, and reported software releases. For an offline edge, that release is like its last check-in—not a guarantee of what it’s running now.
Full Explanation
SD-WAN Manager groups its REST endpoints into API families, and the device inventory family reads the controller's record of managed devices. The inventory can include hostname, site ID, serial number, reachability and a reported software version for an onboarded edge, including one that is offline. For an offline device, the version is its most recently reported value; the controller cannot verify that it is still the device's current running release. Monitoring feeds focus on operational state and may not provide a complete controller-side inventory of offline devices. Configuration data describes device settings and templates, rather than reliably providing the running software release. Polling each edge directly over NETCONF also omits offline devices. SD-WAN Manager is the current name for the product older material calls vManage, and endpoint paths can vary by release, so check the documentation for the deployed version.