Download complete user manual (PDF). - Brocade

1
NETCONF in client/server architecture
RPC and error handling
If the RPC request fails, an element is encoded inside the element and
sent to the client. The element indicates the first detected error. The server is not
required to detect or report multiple errors. If the server detects multiple errors then the order of
the error detection and reporting is at the discretion of the server.
SSH subsystem
The NETCONF client must use Secure Shell Version 2 (SSHv2) as the network transport to connect
to the NETCONF server. Only the SSHv2 protocol is supported as the NETCONF transport protocol.
To run NETCONF over SSHv2, the client establishes an SSH transport connection using the SSH
transport protocol to the NETCONF port. The default NETCONF port is 830. The underlying SSH
client and server exchange keys for message integrity and encryption.
The SSHv2 client invokes the ssh-userauth service to authenticate the user. All currently supported
SSH user authentication methods such as the public-key, password, and keyboard-interactive
authentications are supported for a NETCONF session also. If the SSH user authentication is
disabled, the user is allowed full access.
On successful user authentication, the client invokes the ssh-connection service, also known as
the SSH connection protocol. After the SSH session is established, the NETCONF client invokes
NETCONF as an SSH subsystem called netconf.
RFE References
For details about NETCONF and YANG as defined by the Internet Engineering Task Force (IETF),
refer to the following documents:
• RFC 4741, “NETCONF Configuration Protocol.”
• RFC 4742 “Using the NETCONF Configuration Protocol over Secure SHell (SSH).”
• RFC 6020, “YANG - A Data Modeling Language for the Network Configuration Protocol
(NETCONF)”
6 Network OS NETCONF Operations Guide
53-1002565-01