Configuring Netconf; Overview; Netconf Structure - HP 5920 Configuration Manual

Configuring NETCONF

Overview

Network Configuration Protocol (NETCONF) is an XML-based network management protocol with good
filtering capabilities. It provides programmable mechanisms to manage and configure network devices.
Through NETCONF, you can configure device parameters, retrieve parameter values, and get statistics
information.
In NETCONF messages, each data item is contained in a fixed element. This enables different devices of
the same vendor to provide the same access method and the same result presentation method. For the
devices of different vendors, XML mapping in NETCONF messages can achieve the same effect. For a
network environment containing different devices regardless of vendors, you can develop a
NETCONF-based NMS system to configure and manage devices in a simple and effective way.

NETCONF structure

NETCONF has four layers: content layer, operations layer, RPC layer, and transport protocol layer.
Table 27 NETCONF layers and XML layers
NETCONF
layer
Content
Operations
RPC
Transport
Protocol
XML layer Description
The content layer contains a set of managed objects, which can be
Configuration data,
configuration data, status data, and statistics information. For more
status data, and
information about the operable data, see the NETCONF XML API
statistics information
reference for the switch.
The operations layer defines a set of base operations invoked as RPC
methods with XML-encoded parameters. NETCONF base operations
<get>,<get-config>,
include data retrieval operations, configuration operations, lock
<edit-config>...
operations, and session operations. For the device supported
operations, see
The RPC layer provides a simple, transport-independent framing
mechanism for encoding RPCs. The <rpc> and <rpc-reply> elements are
<rpc>,<rpc-reply>
used to enclose NETCONF requests and responses (data at the
operations layer and the content layer).
The transport protocol layer provides reliable, connection-oriented,
•
In non-FIPS
serial data links.
mode:
Console/Telnet/
In non-FIPS mode, you can log in through Telnet, SSH, or the console
SSH/HTTP/HTT
port to perform NETCONF operations at the CLI. You can also log in
PS/TLS
through HTTP or HTTPS to perform NETCONF operations in the perform
• NETCONF-over-SOAP operations.
In FIPS mode:
Console/SSH/H
In FIPS mode, all login methods are the same as in non-FIPS mode except
TTPS/TLS
that you cannot use HTTP or Telnet.
"Appendix A Supported NETCONF
240
operations."