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

282 Multi-Service IronWare Administration Guide
53-1003028-02
Basic NETCONF operations
8
After sending the hello message, the server starts the hello timer (default is 600 seconds) and
waits for the hello message from the client. If no hello message is received by the server before the
hello timer expires, the server aborts the NETCONF session by closing the underlying SSH session.
The NETCONF server must include the element, which contains the unique session
value for the NETCONF session, in the element. 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 the element without receiving the element aborts the
NETCONF session by closing the underlying SSH session.
The NETCONF client may send arbitrary data before sending a valid hello message. The server
discards the data until a valid
element is received from the client.
The following is an example for a element from the NETCONF server.
urn:ietf:params:netconf:base:1.0
urn:ietf:params:netconf:capability:writable-running:1.0
4
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 the NetIron platforms:
• Base capability: The base capability is 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: The writable-running capability indicates that the device supports
edit-config
and
copy-config
operations where the configuration is the target.
The URI is
urn:ietf:params:netconf:capability:writable-running:1.0
.