NETCONF structure

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. For information about the operable data, see the NETCONF XML API reference for the device.

Operations

<get>,<get-config>,<edit-config>…

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

<rpc>,<rpc-reply>

The RPC layer provides a simple, transport-independent framing mechanism for encoding RPCs. The <rpc> and <rpc-reply> 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/HTTP/HTTPS/TLS

• In FIPS mode:Console/SSH/HTTPS/TLS

The transport protocol layer provides reliable, connection-oriented, serial data links.

In non-FIPS mode, the following login methods are available:

• You can log in through Telnet, SSH, or the console port to perform NETCONF operations at the CLI.

• You can log in through HTTP or HTTPS to perform NETCONF operations or perform NETCONF over SOAP operations.

In FIPS mode, all login methods are the same as in non-FIPS mode except that you cannot use HTTP or Telnet.