Device:~ USER1$ ssh -s cisco1@172.16.167.175 -p 830 netconf cisco1@172.16.167.175's password: cisco1 version="1.0" encoding="UTF-8"?> xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> urn:ietf:params:netconf:base:1.0 urn:ietf:params:netconf:base:1.1 urn:ietf:params:netconf:capability:writable-running:1.0 urn:ietf:params:netconf:capability:xpath:1.0 urn:ietf:params:netconf:capability:validate:1.0 urn:ietf:params:netconf:capability:validate:1.1 urn:ietf:params:netconf:capability:rollback-on-error:1.0 . . . 2870 ]]>]]> Use ^C > to exit NETCONF is ready to use, when a successful reply is received in response to your hello message.
RESTCONF-Specific Prerequisites • Knowledge of RESTCONF and how to use it (when creating a subscription using RESTCONF). • RESTCONF must be configured on the device. • RESTCONF must send correctly-formed Uniform Resource Identifiers (URIs) that adhere to RESTCONF RFC 8040 . Enabling and Validating RESTCONF Validate RESTCONF using appropriate credentials and the following URI: Operation: GET Headers: " Accept: application/yang-data.collection+json, application/yang-data+json, application/yang-data.errors+json " Content-Type: application/yang-data+json Returned Output (omitted for breverity): { "ietf-restconf:data": { "ietf-yang-library:modules-state": { "module": [ "name":
"ATM-FORUM-TC-MIB", "revision": "", "schema": "https://10.85.116.28:443/restconf/tailf/modules/ATM-FORUM-TC-MIB", { "namespace": "urn:ietf:params:xml:ns:yang:smiv2:ATM-FORUM-TC-MIB" }, { "name": "ATM-MIB", "revision": "1998-10-19", "schema": "https://10.85.116.28:443/restconf/tailf/modules/ATM-MIB/1998-10-19", "namespace": "urn:ietf:params:xml:ns:yang:smiv2:ATM-MIB" }, { "name": "ATM-TC-MIB", Model-Driven Telemetry Prerequisites for Model-Driven Telemetry Model-Driven Telemetry 3