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

Changing the Configuration

The client application now emits tag elements to create a new login class called network-mgmt at the [edit system login class] hierarchy level in the candidate configuration. To confirm that it incorporated the changes, the NETCONF server returns an <ok/> tag in an <rpc-reply> tag element. (Understanding the meaning of these tag elements is not necessary for the purposes of this example, but for information about them, see Changing Configuration Information.)

Client Application	NETCONF Server
<rpc> <edit-config> <target> <candidate/> </target> <config> <configuration> <system> <login> <class> <name>network-mgmt</name> <permissions>configure</permissions> <permissions>snmp</permissions> <permissions>system</permissions> </class> </login> </system> </configuration> </config> </edit-config> </rpc> ]]>]]>
	<rpc-reply xmlns=”URN” xmlns:sdx=”URL” > <ok/> </rpc-reply> ]]>]]>

Client Application

NETCONF Server

<rpc>
  <edit-config>
    <target>
      <candidate/>
    </target>
    <config>
      <configuration>
        <system>
          <login>
            <class>
              <name>network-mgmt</name>
              <permissions>configure</permissions>
              <permissions>snmp</permissions>
              <permissions>system</permissions>
            </class>
          </login>
        </system>
      </configuration>
    </config>
  </edit-config>
</rpc>
]]>]]>

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

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