Separating the WAN fabric this way makes it more
scalable, faster to converge, and cheaper to deploy and
maintain. On top of a transport-independent underlay
that supports all types of WAN circuits (MPLS, DSL,
broadband, 4G, and so on), an overlay network is being
built that runs OMP (Overlay Management Protocol).
Much like BGP, OMP propagates throughout the
network all the routing information needed for all the
components of the fabric to be able to forward data
according to the routing policies configured in vManage.
Cisco vManage provides a REST API interface that
exposes the functionality of the Cisco SD-WAN software
and hardware features. The API resources that are
available through the REST interface are grouped in the
following collections:
Administration: For management of users, groups, and local
vManage instance
Certificate Management: For management of SSL certificates and
security keys
Configuration: For creation of feature and device configuration
templates and creation and configuration of vManage clusters
Device Inventory: For collecting device inventory information,
including system status
Monitoring: For getting access to status, statistics, and related
operational information about all the devices in the network every 10
minutes from all devices
Real-Time Monitoring: For gathering real-time monitoring
statistics and traffic information approximately once per second
Troubleshooting Tools: For API calls used in troubleshooting, such
as to determine the effects of applying a traffic policy, updating
software, or retrieving software version informationCisco vManage exposes a self-documenting web interface
for the REST API, based on the OpenAPI specification.
This web interface is enabled by default and can be
accessed at
https://vManage_IP_or_hostname:port/apidocs.
vManage_IP_or_hostname is the IP address or
hostname of the Cisco vManage server, and the port is
8443 by default. The rest of this chapter uses the always-