Datastores and URLs

The SR OS supports the following datastores:

• <running>

• <startup>

• <url>

The <candidate> datastore is not supported.

All configuration changes (<edit-config>) done to the <running> datastore through NETCONF take immediate operational effect.

The <startup> datastore and <url> tags can only be used with <copy-config> and <delete-config> and are not supported with any other operations (including <edit-config>, <get-config>, <get>, <validate>, and others).

The :startup capability is advertised in the SR OS NETCONF server <hello> as follows:

<capability>urn:ietf:params:netconf:capability:startup:1.0</capability>

The <url> tags support the same options as CLI <file-url>: local URLs (CF) and remote URLs (FTP and TFTP).

The :url capability is advertised in the SR OS NETCONF server <hello> as follows:

<capability>urn:ietf:params:netconf:capability:url:1.0?scheme=ftp,tftp,file</
capability>

The following examples show the format of each URL scheme:

• <target><url>ftp://name:passwd@a.b.c.d/usr/myfiles/myfile.cfg</url></target>

• <target><url>tftp://name:passwd@a.b.c.d/usr/myfiles/myfile.cfg</url></target>

• <target><url>file:///cf3:/myfiles/myfile.cfg</url></target>

• <target><url>cf3:/myfiles/myfile.cfg</url></target>

The <startup> datastore is identified by using the bof primary-config, secondary-config, and tertiary-config paths configured by the operator. The <startup> datastore is an alias for a special URL used for system startup with some extra resiliency (primary, secondary, and tertiary).

The BOF is not considered to be part of any configuration datastore.

Debug configurations (such as debug mirrors, or configurations saved using the admin debug-save command) are not considered to be part of any configuration datastore.

Configuration changes made through NETCONF are subject to CLI rollback operations (revert, save, and so on) and are included in the configuration when an admin save operation is performed in the CLI.