GET method (running configuration)
RESTCONF GET
------------------------
URL: https://10.85.116.59:443/restconf/data/Cisco-IOS-XE-native:native/logging/monitor/severity
Headers: {'Accept-Encoding': 'gzip, deflate', 'Accept': 'application/yang-data+json, application/yang-data.errors+json'}
Body:
RESTCONF RESPONSE
----------------------------
200
{
"Cisco-IOS-XE-native:severity": "critical"
}
RESTCONF GET
--------------------------------
URL: https://10.85.116.59:443/restconf/data/Cisco-IOS-XE-native:native/logging/monitor/severity
Headers: {'Accept-Encoding': 'gzip, deflate', 'Accept': 'application/yang-data+json, application/yang-data.errors+json'}
Body:
Response:
404 Client Error: Not Found
RESTCONF PUT
--------
URL: https://10.85.116.59:443/restconf/data/Cisco-IOS-XE-native:native/logging/monitor/severity
Headers: {'Content-type': 'application/yang-data+json', 'Accept': 'application/yang-data+json, application/yang-data.errors+json'}
Body:
{
"severity": "debugging"
}
RESTCONF RESPONSE
-----------------------------
204
RESTCONF PATCH
-----------------------
URL: https://10.85.116.59:443/restconf/data/Cisco-IOS-XE-native:native
Headers: {'Content-type': 'application/yang-data+json', 'Accept': 'application/yang-data+json, application/yang-data.errors+json'}
Body:
{
"native": {
"logging": {
"monitor": {
"severity": "alerts"
}
}
}
}
RESTCONF RESPONSE
-----------------------------
204
To create port-channel 1 interface and add multiple configurations to the interface.
If the POST method succeeds, a "201 Created" status-line is returned
and there is no response message-body. A "Location" header field
identifying the child resource that was created MUST be present in
the response in this case.
URL: https://10.85.116.59:443/restconf/data/Cisco-IOS-XE-native:native/interface/
Headers: {'Content-type': 'application/yang-data+json', 'Accept': 'application/yang-data+json, application/yang-data.errors+json'}
Body:
{
"Cisco-IOS-XE-native:Port-channel": [
{
"name": "1",
"description": "This is a port-channel interace",
"delay": 22222,
"load-interval": 30,
"mtu": 1501
}
]
}
RESTCONF RESPONSE
-----------------------------
201
Final router config:
csr_dmp_ova#show run interface Port-channel 1
Building configuration...
Current configuration: 183 bytes
!
interface Port-channel1
description This is a port-channel interace
mtu 1501
no ip address
load-interval 30
delay 22222
no negotiation auto
no mop enabled
no mop sysid
end
Delete Port-channel interface from running config
RESTCONF DELETE
------------------------
URL: https://10.85.116.59:443/restconf/data/Cisco-IOS-XE-native:native/interface/Port-channel=1
Headers: {'Content-type': 'application/yang-data+json', 'Accept': 'application/yang-data+json, application/yang-data.errors+json'}
Body:
{}
RESTCONF RESPONSE
-----------------------------
204
Provides header information with the methods supported by the server
RESTCONF OPTIONS
---------------------------
URL: https://10.85.116.59:443/restconf/data/Cisco-IOS-XE-native:native/interface/
Headers: {'Accept-Encoding': 'gzip, deflate', 'Accept': 'application/yang-data+json, application/yang-data.errors+json'}
Body:
RESTCONF RESPONSE
-----------------------------
200
>>> resp.headers
{'Server': 'nginx', 'Pragma': 'no-cache', 'Content-Type': 'text/html', 'Connection': 'close', 'Cache-Control': 'private, no-cache, must-revalidate, proxy-revalidate', 'Date': 'Mon, 10 Jul 2017 12:06:29 GMT', 'Allow': 'DELETE, GET, HEAD, PATCH, POST, PUT, OPTIONS', 'Accept-Patch': 'application/yang-data+xml, application/yang-data+json', 'Content-Length': '0'}
URL: https://10.85.116.59:443/restconf/data/Cisco-IOS-XE-native:native
Headers:
Body:
{
"logging": {
"alarm": "critical"
}
}
RESTCONF RESPONSE
409 Conflict status-line. The error-tag value object already exists is returned if used for other methods or resource types.
409 Client Error: Conflict
{"errors": {"error": [{"error-message": "object already exists: /ios:native/ios:logging", "error-path": "/Cisco-IOS-XE-native:native", "error-tag": "data-exists", "error-type": "application"}]}}
Note: Successful Response Messages
200 – Message body is present in the RESTCONF response
204 – Message body Is not present in RESTCONF response
201 – Message body Is not present in RESTCONF response. It is used with POST operation to show that the targeted resource is created.
Error Response Messages
409 - Client Error: Conflict