NETCONF in SR OS
Page 340 7450 ESS System Mangement Guide
• <source>=<running> and <target>=<startup>
∅ Equivalent of "admin save"
∅ An index file is also saved if "persist on" is configured in the bof
<running> cannot be a <target> for a <copy-config>.
Remote url to remote url copies are not supported. For example, if primary-image is a remote
url then a <startup> to remote-url copy will fail with an error.
The <copy-config> operation uses the CLI Content Layer format. The format of the source
and target is block CLI.
The <delete-config> operation is supported for the following targets:
•<url>
• <startup>
<delete-config> is not allowed on the <running> datastore.
<validate>
The validate:1.1 capability is supported:
• The validate:1.1 and 1.0 capabilities are advertised in the NETCONF server's <hello>:
∅ <capability>urn:ietf:params:netconf:capability:validate:1.0</capability>
∅ <capability>urn:ietf:params:netconf:capability:validate:1.1</capability>
• The <validate> request is supported for an XML content layer request but not for a
CLI content layer request. Detection of a <config-format-cli-block> or <oper-data-
format-cli-block> tag in a <validate> request will result in an "operation not
supported" error response.
• A <validate> request is supported for a selection of config (<source><config>), or for
the <running> datastore, which only returns 'OK'. <validate> is not supported for url
sources or the <startup> datastore.
Datastores and URLs
SR OS supports the <running> datastore, the <startup> datastore, and <url> tags (Note: <url>
is not a datastore in itself). The <candidate> datastore is not supported.
All configuration changes (<edit-config>) done to the <running> datastore via NETCONF
take immediate operational effect.
To Next Page
Loading...
