Martin Bjorklund wrote:
Johan Rydberg <johan.rydberg@edgeware.tv> wrote:Martin Bjorklund skrev:Johan Rydberg <johan.rydberg@edgeware.tv> wrote:What is the difference between get and get-config(running) with the exception of <get/> returning device state information as well?That is the difference.Is this device state information read-only per defintion? Or is it possible edit it (via <edit-config/>) if the agent supports the writable running capability?<edit-config> modifies the configuration data only, not the state data. So from a <edit-config> perspective, the state data is read-only.
Also, if the non-volatile <startup> config is supported, then an explicit <copy-config> (from <running> to <startup>) is needed to update the NV storage contents. The agent will copy only the config data (like <get-config>) with this operation. It may not be clear in the RFC that <copy-config> works the same way as <get-config>. If there are read-only 'state' data objects mixed in with configuration data (in the agent), they are simply skipped when generating the XML output. The agent must know somehow (outside the standard) what to filter out.
/martin
Andy -- to unsubscribe send a message to netconf-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: <http://ops.ietf.org/lists/netconf/>