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

Network OS NETCONF Operations Guide 9
53-1003231-02
Chapter
2
Basic NETCONF Operations
In this chapter
• Establishing a NETCONF session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
• Retrieving configuration data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
• Retrieving operational data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
• Editing the configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
• Managing the configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
• Disconnecting from a NETCONF session . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Establishing a NETCONF session
Up to 16 concurrent sessions can be established with a NETCONF server. A session times out if it is
idle for 30 minutes.
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 the message
exchange on starting a NETCONF session.
Hello messages exchange
After establishing a secure transport connection, both the NETCONF server and client send a
element simultaneously to announce their capabilities and session identifier.
The NETCONF server must include the element in the element. The
element contains the unique session value for the NETCONF session. If the client
receives the element without the , the client aborts the NETCONF session by
closing the underlying SSH session.
The NETCONF client must not include the element in the element. If the
server receives the element with the , the server aborts the NETCONF session
by closing the underlying SSH session.
The NETCONF client must include a valid xmlns attribute in the element. If the server
receives the element without a valid xmlns attribute, the server aborts the NETCONF
session by closing the underlying SSH session.
The NETCONF client must include a base capability. The server receiving the element
without a NETCONF base capability aborts the NETCONF session by closing the underlying SSH
session.
The server receiving an element without first receiving a element aborts the
NETCONF session by closing the underlying SSH session.