Configuring Netconf; Overview; Netconf Structure - HPE FlexFabric 5700 Series Network Management And Monitoring Configuration Manual

Hide thumbs Also See for FlexFabric 5700 Series:
Table of Contents

Advertisement

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 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
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
<get>,<get-config>,
operations include data retrieval operations, configuration
<edit-config>...
operations, lock operations, and session operations. For the device
supported operations, see
operations."
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/Telnet/
In non-FIPS mode, you can log in through Telnet, SSH, or the
SSH/HTTP/
console port to perform NETCONF operations at the CLI. You can
HTTPS/TLS
also log in 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
225

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents