A Network Management Protocol operating between a Managing Server and Managed Devices in a Managed Network.
The protocol messages and the stored configurations are encoded in XML.
The management data uses YANG to specify the structure, syntax, and semantics.
NETCONF use a remote procedure call (RPC) paradigm and exchange messages over a secure connection-oriented sessions (like Transport Layer Security (TLS)).
Usage
- Retrieve, set, and modify configuration data at managed devices.
- Query operational data and statistics and managed devices.
- Subscribe to notification generated by managed devices.
Operations
Some common operations are:
<get-config>: Retrieve all or part of a given configuration. A device may have multiple configurations. There is always a running/ configuration that describes the device’s current (running) configuration.<get>: Retrieve all or part of both configuration state and operational state data.<edit-config>: Change all or part of a specified configuration at the managed device. If the running/configuration is specified, then the device’s current (running) configuration will be changed. If the managed device was able to satisfy the request, an <rpc-reply> is sent containing an <ok> element; otherwise, the device’s configuration state can be rolled-back to its previous state.<lock>, <unlock>: The <lock> (<unlock>) operation allows the managing server to lock (unlock) the entire configuration datastore of a managed device. Locks are intended to be short-lived and allow a client to make a change without fear of interaction with other NETCONF, SNMP, or CLIs commands from other sources.<create-subscription>, <notification>: This operation initiates an event notification subscription that will send asynchronous event <notification> for specified events of interest from the managed device to the managing server, until the subscription is terminated.