Brocade Multi-Service IronWare Administration Guide (Supporting R05.6.00) - Manual (Page 299)

Multi-Service IronWare Administration Guide 281
53-1003028-02
Basic NETCONF operations
8
Recommendations for NETCONF
• Use an authentication method to secure the underlying SSH session and to prevent any
unauthorized access.
• Use a NETCONF client to generate the RPCs. If you have manually written the XML requests,
recycling the XML from a successful request is recommended.
• Refer to the Brocade MLX Series and Brocade NetIron Family YANG guide for XML and data
verification.
• Plan the configuration or state information that must be sent or retrieved to avoid sending and
receiving large RPC messages.
• Use of a scripting language or other custom interface is recommended.
Basic NETCONF operations
The NETCONF protocol provides a small set of low-level operations to manage device configurations
and retrieve device state information. The base protocol provides operations to retrieve, configure,
copy, and delete configuration data stores. Additional operations are provided based on the
capabilities advertised by the device.
The following base protocol operations are supported:
•
get
•
get-config
•
edit-config
•
close-session
NOTE
Other operations, including
copy-config
,
delete-config
,
lock
,
unlock
, and
kill-session
are
not supported.
Initial connection
Each NETCONF session begins with a handshake in which the NETCONF server and the client
specify the NETCONF capabilities they support. The following sections describe how to start a
NETCONF session.
Hello messages
After establishing a secure transport connection, both the NETCONF server and client send a
element simultaneously to announce their capabilities and session identifier.
Yes No
Yes Yes
TABLE 42 NETCONF operations and privilege levels
Operations NETCONF_PRIVILEGE_LEVEL_0 NETCONF_PRIVILEGE_LEVEL_5