H3C Technologies H3C MSR 5600 - Manual (Page 142)

129
Configuring NETCONF
NOTE:
FIPS is not available for Russia.
Overview
Network Configuration Protocol (NETCONF) is an XML-based network management protocol. It provides
programmable mechanisms to manage and configure network devices. Through NETCONF, you can
configure device parameters, retrieve parameter values, and get statistics information.
NETCONF messages are XML-based with good filtering capabilities. Each data item is contained in a
fixed element, which 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 can help
implement the same effect. For a network environment containing different devices of the same vendor or
different vendors, you can develop an NMS system using XML mapping, and use NETCONF operations
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 9 NETCONF layers and XML layers
NETCONF
layer
H3C XML layer Description
Content
Configuration data,
status data, and
statistics information
The content layer contains a set of managed objects, which can be
configuration data, status data, and statistics information. The data must
comply with the XSD standard.
Operations
,,
…
The operations layer defines a set of base operations invoked as RPC
methods with XML-encoded parameters. NETCONF base operations
include data retrieval operations, configuration operations, lock
operations, and session operations. For the device supported
operations, see " Appendix A Supported NETCONF operations ."
RPC ,
The RPC layer provides a simple, transport-independent framing
mechanism for encoding RPCs. The and elements are
used to enclose NETCONF requests and responses (data at the
operations layer and the content layer).
Transport
Protocol
• In non-FIPS
mode:
Console/Telnet/
SSH/TLS
• In FIPS mode:
Console/Telnet/
SSH
The transport protocol layer provides reliable, connection-oriented,
serial data links.
In non-FIPS mode, you can log in through Telnet, SSH, or console port to
perform NETCONF operations at the CLI, or encapsulate NETCONF
messages into SOAP messages and transmit them over HTTP.
In FIPS mode, all login methods are the same as in non-FIPS mode except
that NETCONF over SOAP over HTTP is not available..