<capability>http://cisco.com/ns/nvo/devs?
module=nvo-devs&revision=2015-09-11</
capability>
<capability>http://cisco.com/ns/yang/Cisco-IOS-
XE-aaa?module=Cisco-IOS-XE-
aaa&revision=2017-09-05</capability>
<capability>http://cisco.com/ns/yang/Cisco-IOS-
XE-acl?module=Cisco-IOS-XE-
acl&revision=2017-08-01</capability>
<capability>http://cisco.com/ns/yang/Cisco-IOS-
XE-acl-
oper?module=Cisco-IOS-XE-acl-
oper&revision=2017-02-07</
capability>
...
</capabilities>
<session-id>5546</session-id></hello>]]>]]>All the YANG models supported by the device are
included in the HELLO message, and so is a session ID.
This version of Cisco IOS XE supports both NETCONF
1.0 and 1.1 as well as the writable-running capability
(which makes it possible to write directly to the running
configuration of the device), the rollback-on-error 1.0
capability, and the notification 1.0 capability. These
capabilities translate into YANG models defined by the
IETF, as you can see in their XPath definition:
urn:ietf:params:netconf:The delimiter string ]]>]]> at the end of the response
signifies the end of the message. Next, the client needs to
respond to the hello message with a list of capabilities
that it supports. The simplest response that a client can
send is the following:
Click here to view code image
<?xml version="1.0" encoding="UTF-8"?>
<hello
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<capabilities>