Brocade Network OS NETCONF Operations Guide v4.1.1 - Manual (Page 43)

Network OS NETCONF Operations Guide 11
53-1003231-02
Retrieving configuration data
2
• Actions capability—Allows operations to be performed on the datastore using the custom
action mechanism for features that are supported by this mechanism in the YANG code. Refer
to
“Using the custom action mechanism” on page 17 for details. The URI for the actions
capability is http://tail-f.com/ns/netconf/actions/1.0.
• tailf-aaa capability—Supports proprietary authentication, authorization, and accounting (AAA).
The URI for the tailf-aaa capability is
http://tail-f.com/ns/aaa/1.1?revision=2010-06-17&module=tailf-aaa.
• Brocade proprietary capabilities—A set of capabilities that support Brocade Network OS
features. Each capability references a namespace containing instance data. Each namespace
corresponds to a file containing the YANG module that models the data. For example the
brocade-cee-map capability at URI
urn:brocade.com:mgmt:brocade-cee-map?revision=2011-04-18&module=brocade-cee-map
provides support for the features modeled in the brocade-cee-map module.
For an overview of each YANG module and structural details, refer to the Network OS YANG
Reference Manual. For element definitions, refer to the YANG file itself.
NOTE
The Candidate Configuration capability and Confirmed Commit capability are not supported.
Client capabilities
The client must support the base capability. In addition, Brocade recommends that the client
specify the identification capability with URI http://tail-f.com/ns/netconf/identification/1.0 while
establishing a session with the server. This capability provides client information to the server,
including the vendor, product name, and version of the client application in addition to user
information. Server administrators can subsequently gather information about who is accessing
the server using the show netconf client-capabilities command or the
custom RPC. Refer to
Appendix A, “Managing NETCONF,” for
details.
The following example shows a element from the NETCONF client.
urn:ietf:params:netconf:base:1.0
http://tail-f.com/ns/netconf/identification/1.0?
vendor=brocade&product=bna&version=3.0&
client-identity=adminUser
Retrieving configuration data
You can retrieve configuration data using either the or RPC. RFC 4741,
NETCONF Configuration Protocol specifies that the RPC returns only configuration
data while the RPC returns configuration data and operational state data. In the Brocade
implementation, the RPC does not return operational state data; Brocade instead provides a
set of custom RPCs and actions for returning operational state data. In the Brocade
implementation, the and operations are essentially the same. This document
will typically refer to the operation, though can be used equally.