Server capabilities – Brocade Network OS NETCONF Operations Guide v4.1.1 User Manual
Page 42

10
Network OS NETCONF Operations Guide
53-1003231-02
Establishing a NETCONF session
2
The following example shows a
aaa
ocade-aaa
e=brocade-aaa-ext
ocade-cdp
e=brocade-cee-map
urn:brocade.com:mgmt:brocade-chassis?revision=2011-04-11&module=brocade-chassis
(output truncated)
Server capabilities
A NETCONF capability is a set of protocol extensions that supplements the base NETCONF
specification. A NETCONF capability is identified with a Uniform Resource Identifier (URI).
Capabilities augment the base operations of the NETCONF server, describing both the additional
operations and the contents allowed inside the operations. To support a capability, the NETCONF
server must support all the dependent capabilities.
The following capabilities are supported on Network OS switches:
•
Base capability—The set of operations and contents that any NETCONF implementation must
support. The URI for the base capability is urn:ietf:param:xml:ns:netconf:base:1.0. Both the
NETCONF client and server must support the base capability.
•
Writable-running capability—Indicates that the device supports
urn:ietf:params:netconf:capability:writable-running:1.0.
•
Startup capability—Supports separate datastores for the running and startup configuration.
Operations performed on the running-config datastore do not affect the startup configuration
until a
startup configuration. The URI for the startup capability is
urn:ietf:params:netconf:capability:startup:1.0.
•
Xpath capability—Supports XPath expressions in
in
xpath capability is urn:ietf:params:netconf:capability:xpath:1.0.
•
Validate capability—Allows validation to be performed on a configuration. The URI for the
validate capability is urn:ietf:params:netconf:capability:validate:1.0.