Ensure that the logging monitor command is not availabel in the running configuration. Note The following sample POST request uses the logging monitor alerts command. Device:~# curl -i -k -X "POST" "https://10.85.116.30:443/restconf/data/Cisco-IOS-XE-native:native/logging/monitor" \ > -H 'Content-Type: application/yang-data+json' \ > -H 'Accept: application/yang-data+json' \ > -u 'admin:admin' \ > -d > "severity": "alerts" > }' HTTP/1.1 201 Created Server: nginx Date: Mon, 23 Apr 2018 14:53:51 GMT Content-Type: text/html Content-Length: 0 Location: https://10.85.116.30/restconf/data/Cisco-IOS-XE-native:native/logging/monitor/severity Connection: keep-alive Last-Modified:
Mon, 23 Apr 2018 14:53:51 GMT Cache-Control: private, no-cache, must-revalidate, proxy-revalidate Etag: 1524-495231-97239 Pragma: no-cache Device:~# PUT: (Create or Replace) Request: If the specified command is not present on the device, the POST request creates it ; however, if it is already present in the running configuration, the command will be replaced by this request. The following sample PUT request uses the logging monitor warnings command. Device:~# curl -i -k -X "PUT" "https://10.85.116.30:443/restconf/data/Cisco-IOS-XE-native:native/logging/monitor/severity" \ > -H 'Content-Type: application/yang-data+json' \ > -H 'Accept:
application/yang-data+json' \ > -u 'admin:admin' \ > -d > "severity": "warnings" > }' HTTP/1.1 204 No Content Server: nginx Date: Mon, 23 Apr 2018 14:58:36 GMT Content-Type: text/html Content-Length: 0 Connection: keep-alive Last-Modified: Mon, 23 Apr 2018 14:57:46 GMT Cache-Control: private, no-cache, must-revalidate, proxy-revalidate Etag: 1524-495466-326956 Pragma: no-cache Device:~# RESTCONF Protocol Example: Configuring the RESTCONF Protocol RESTCONF Protocol 28