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

Deleting Configuration Elements

To delete a configuration element (hierarchy level or configuration object) from the candidate configuration, a client application emits the basic tag elements described in Changing Individual Configuration Elements. It also emits the <default-operation> tag element with the value none to change the default mode to no-change.



<rpc>
    <edit-config>
        <target>
            <candidate/>
        </target>
        <default-operation>none</default-operation> 

  

   <!- - EITHER - ->
        <config>
            <configuration>
                <!- - tag elements representing the configuration elements to delete - ->
            </configuration>
        </config>
   <!- - OR - ->
        <url>
            <!- - location specifier for file containing elements to delete - ->
        </url>
  

    </edit-config>
</rpc>
]]>]]>

In no-change mode, existing configuration elements remain unchanged unless the corresponding element in the new configuration has the operation="delete" attribute in its opening tag. This mode prevents the NETCONF server from creating parent hierarchy levels for an element that is being deleted. We recommend that the only operation performed in no-change mode be deletion. When merging, replacing, or creating configuration elements, client applications use merge mode.

To represent each configuration element being deleted (either within the <config> tag element or in the file named by the <url> tag element), the application emits the tag elements representing its parent hierarchy levels, as described in Changing Individual Configuration Elements. The tag element in which the operation="delete" attribute is included depends on the element type, as described in the following sections:

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