NETCONF Configuration Datastore

A configuration datastore is a collection of complete configuration parameters for a device. Table 4.4 describes NETCONF-defined configuration datastores.

TABLE 4.4 NETCONF-Defined Configuration Datastores

(1) Configuration Datastore

Description

(m)

Stores the effective configuration, status information, and statistics on the current device

Unless the NETCONF server supports the candidate capability, this configuration datastore is the only mandatory standard datastore To support modification of the configuration datastore, a device must have the writable-running capability

Stores the configuration data to be run by a device An administrator can perform operations on the configuration datastore. Any change to the datastore does not affect the current device

To support the configuration datastore, the current device must have the candidate capability

Stores the configuration data loaded for device startup, which is similar to the saved configuration file. To support the configuration datastore, the current device must have the Distinct Startup capability

XML Encoding

The NETCONF client and server communicate through the RPC mechanism. They must establish a secure and connection-oriented session for communication. The client sends an RPC request message to the server. After processing the request message, the server sends a response to the client. The RPC request from the client and the response from the server are encoded in XML format.

XML is a NETCONF encoding format, allowing complex hierarchical data to be expressed in a text format that can be read, saved, and manipulated with both traditional text tools and tools specific to XML.

XML-based network management uses XML’s powerful data presentation capabilities to describe managed data and management operations so that computers can easily parse management information. XML-based network management helps computers efficiently process network management data, improving network management capabilities.

The XML encoding format file header is ?>, where

  • xml identifies an XML file.
  • • version indicates the NETCONF version. "1.0" indicates that the XML1.0 standard version is used.
  • • encoding is the character set encoding format. Only UTF-8 encoding is supported.
  • • ?>: is the end of an instruction.

RPC Mode

NETCONF uses an RPC-based communication model. NETCONF uses XML-encoded and elements to provide the transport- protocol-independent framework of NETCONF request and response messages. Table 4.5 covers some commonly used RPC elements.

 
Source
< Prev   CONTENTS   Source   Next >