Cisco Cisco Elastic Services Controller 2.3 Developer's Guide
1.5 NETCONF Capabilities
This table captures what are the NETCONF capabilities supported by ESC.
Name
Description
Supported
:candidate
The server supports the <candidate/> database. It will allow this special database to be
locked, edited, saved, and unlocked. The server will also support the <discard-
changes> and basic <commit> operations.
locked, edited, saved, and unlocked. The server will also support the <discard-
changes> and basic <commit> operations.
No
:confirmed-
commit
commit
For servers that support the :candidate capability, this additional capability will also
be advertised if the server supports the 'confirmed commit' feature. This special mode
requires a server to send two <commit> RPC method requests instead of one, to
save any changes to the <running/> database. If the second request does not arrive
within a specified time interval, the server will automatically revert the running
configuration to the previous version.
be advertised if the server supports the 'confirmed commit' feature. This special mode
requires a server to send two <commit> RPC method requests instead of one, to
save any changes to the <running/> database. If the second request does not arrive
within a specified time interval, the server will automatically revert the running
configuration to the previous version.
No
:interleave
The server will accept <rpc> requests (besides <close-session> while notification
delivery is active. The :notification capability must also be present if this capability is
advertised.
delivery is active. The :notification capability must also be present if this capability is
advertised.
No
:notification
The server supports the basic notification delivery mechanisms defined in RFC 5277,
e.g., the <create-subscription> operation will be accepted by the server. Unless the
:interleave capability is also supported, only the <close-session> operation must be
supported by the server while notification delivery is active.
e.g., the <create-subscription> operation will be accepted by the server. Unless the
:interleave capability is also supported, only the <close-session> operation must be
supported by the server while notification delivery is active.
Yes
:partial-lock
The server supports the <partial-lock> and <partial-unlock> operations, defined in
RFC 5717. This allows multiple independent clients to each write to a different part of
the <running> configuration at the same time.
RFC 5717. This allows multiple independent clients to each write to a different part of
the <running> configuration at the same time.
No
:rollback-on-
error
error
The server supports the 'rollback-on-error' value for the <error-option> parameter to
the <edit-config> operation. If any error occurs during the requested edit operation,
then the target database (usually the running configuration) will be left affected. This
provides an 'all-or-nothing' edit mode for a single <edit-config> request.
the <edit-config> operation. If any error occurs during the requested edit operation,
then the target database (usually the running configuration) will be left affected. This
provides an 'all-or-nothing' edit mode for a single <edit-config> request.
No
:startup
The server supports the <startup/> database. It will allow the running configuration to
be copied to this special database. It can also be locked, and unlocked, but a server is
not required to allow it to be edited.
be copied to this special database. It can also be locked, and unlocked, but a server is
not required to allow it to be edited.
No
:url
The server supports the <url> parameter value form to specify protocol operation
source and target parameters. The capability URI for this feature will indicate which
schemes (e.g., file, https, sftp) that the server supports within a particular URL value.
The 'file' scheme allows for editable local configuration databases. The other schemes
allow for remote storage of configuration databases.
source and target parameters. The capability URI for this feature will indicate which
schemes (e.g., file, https, sftp) that the server supports within a particular URL value.
The 'file' scheme allows for editable local configuration databases. The other schemes
allow for remote storage of configuration databases.
No
:validate
The server supports the <validate> operation. When this operation is requested on a
target database, the server will perform some amount of parameter validation and
target database, the server will perform some amount of parameter validation and
No