[Contents] [Prev] [Next] [Index] [Report an Error]

Providing Configuration Data as a Data Stream

To provide configuration data as a data stream, a client application emits <rpc>, <edit-config>, and <config> tag elements. To specify the configuration elements to change, the application emits the tag elements representing all levels of the configuration hierarchy from the root (represented by the <configuration> tag element) down to each element to change. The notation is the same as that used to request configuration information, as described in Requesting Information. For more detailed information about the mappings between configuration elements and XML tag elements, see Mapping Configuration Statements to SRC XML Tag Elements.


<rpc>
    <edit-config>
        <target>
            <candidate/>
        </target>
        <config>
            <configuration>
               <!- - tag elements representing the configuration changes - ->
            </configuration>
        </config>
        <!- - other child tag elements of the <edit-config> tag element - ->
    </edit-config>
</rpc>
]]>]]>

The following example shows how to provide new configuration data for the messages system log file in a data stream:

Client Application

NETCONF Server

<rpc>
  <edit-config>
    <target>
      <candidate/>
    </target>
    <config>
      <configuration>
        <system>
          <syslog>
            <file>
              <name>messages</name>
              <contents>
                <name>any</name>
                <warning/>
              </contents>
              <contents>
                <name>authorization</name>
                <info/>
              </contents>
            </file>
          </syslog>
        </system>
      </configuration>
    </config>
  </edit-config>
</rpc>
]]>]]>

 

 

<rpc-reply xmlns=”URN” xmlns:sdx=”URL” >
  <ok/>
</rpc-reply>
]]>]]>


[Contents] [Prev] [Next] [Index] [Report an Error]