Cisco Cisco Evolved Programmable Network Manager 1.2 Developer's Guide
Northbound RESTCONF/YANG Interface
Cisco EPN Manager RESTConf NBI Guide
14
14
The client issues HTTP GET requests to retrieve objects using the URLs and query
parameters described in this document.
parameters described in this document.
Containment Associations
The operations on supported RESTCONF/YANG interfaces return a single object or multiple
objects, depending how many objects match the URL and whether the object supports
containment associates. For example, when the client retrieves a managed element object,
the associated chassis, equipment, models, and physical connectors are returned as well.
Such requests can return large amounts of data in response to a single GET request.
objects, depending how many objects match the URL and whether the object supports
containment associates. For example, when the client retrieves a managed element object,
the associated chassis, equipment, models, and physical connectors are returned as well.
Such requests can return large amounts of data in response to a single GET request.
OSS Integration Usage Scenarios
2.4
In a typical scenario, OSS clients integrating with Cisco EPN Manager may use the
RESTCONF/YANG Interfaces supported by Cisco EPN Manager to retrieve the device
inventory and then export the inventory to other systems or use it to generate reports.
RESTCONF/YANG Interfaces supported by Cisco EPN Manager to retrieve the device
inventory and then export the inventory to other systems or use it to generate reports.
Retrieving Inventory
The RESTCONF/YANG interface supports standard HTTP 1.1 GET requests. The information
is returned in the format specified by the Accept header of the request. The client may
retrieve the physical information about devices through the Physical Inventory API. Logical
resource and service information are available through the other APIs.
is returned in the format specified by the Accept header of the request. The client may
retrieve the physical information about devices through the Physical Inventory API. Logical
resource and service information are available through the other APIs.