Configuring Netconf; Overview; Netconf Structure - HPE FlexNetwork 5510 HI Series Network Management And Monitoring Configuration Manual

Configuring NETCONF

Overview

Network Configuration Protocol (NETCONF) is an XML-based network management protocol with
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 36 NETCONF layers and XML layers
NETCONF
layer
Content
Operations
RPC
Transport
Protocol
XML layer Description
Configuration data, The content layer contains a set of managed objects, which can be
status data, and configuration data, status data, and statistics information. For
statistics information about the operable data, see the NETCONF XML API
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
<rpc>,<rpc-reply>
are 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/Telne
In non-FIPS mode, you can log in through Telnet, SSH, or the console
t/SSH/HTTP/
port to perform NETCONF operations at the CLI. You can also log in
HTTPS/TLS
through HTTP or HTTPS to perform NETCONF operations or perform
•
NETCONF-over-SOAP operations.
In FIPS mode:
Console/SSH/
In FIPS mode, all login methods are the same as in non-FIPS mode
HTTPS/TLS
except that you cannot use HTTP or Telnet.
"Appendix A Supported NETCONF
244
operations."