Delete Configuration Elements Using NETCONF

To delete a hierarchy level and all of its children (or a container object that has children but no identifier), a client application includes the operation="delete" attribute or the operation="remove" attribute in the empty tag that represents the level.

<configuration>
    <!-- opening tags for each parent level -->
        <level-to-delete operation="(delete | remove)"/>  
    <!-- closing tags for each parent level -->
</configuration>

We recommend that the application set the default mode to no-change by including the <default-operation> tag element with the value none, as described in Set the Edit Configuration Mode in a NETCONF Session. For more information about hierarchy levels and container objects, see Map Configuration Statements to Junos XML Tag Elements.

The following example shows how to remove the [edit protocols ospf] hierarchy level of the candidate configuration:

To delete a configuration object that has an identifier, a client application includes the operation="delete" attribute or the operation="remove" attribute in the container tag element for the object. Inside the container tag element, it includes the identifier tag element only, not any tag elements that represent other characteristics. In the following, the identifier tag element is called <name>:

<configuration>
    <!-- opening tags for each parent of the object -->
        <object operation="(delete | remove)">  
            <name>identifier</name> 
        </object> 
    <!-- closing tags for each parent of the object -->
</configuration>

We recommend that the application set the default mode to no-change by including the <default-operation> tag element with the value none, as described in Set the Edit Configuration Mode in a NETCONF Session. For more information about identifiers, see Map Configuration Statements to Junos XML Tag Elements.

The following example shows how to remove the user object barbara from the [edit system login user] hierarchy level in the candidate configuration:

To delete either a fixed-form option or an option that takes just one value from a configuration object, a client application includes the operation="delete" attribute or the operation="remove" attribute in the tag element for the option. In the following example, the identifier tag element for the object is called <name>. (For information about deleting an option that can take multiple values, see Deleting Values from a Multi-value Option of a Configuration Object.)

<configuration>
    <!-- opening tags for each parent of the object -->
        <object> 
            <name>identifier</name>  <!-- if object has an identifier -->
            <option1 operation="(delete | remove)">  
            <option2 operation="(delete | remove)">  
            <!-- tag elements for other options to delete -->
        </object> 
    <!-- closing tags for each parent of the object -->
</configuration>

We recommend that the application set the default mode to no-change by including the <default-operation> tag element with the value none, as described in Set the Edit Configuration Mode in a NETCONF Session. For more information about options, see Map Configuration Statements to Junos XML Tag Elements.

The following example shows how to remove the fixed-form option disable at the [edit forwarding-options sampling] hierarchy level:

As described in Map Configuration Statements to Junos XML Tag Elements, some Junos OS configuration objects are leaf statements that have multiple values. In the formatted ASCII CLI representation, the values are enclosed in square brackets following the name of the object:

object [value1 value2 value3 ...];

The Junos XML representation does not use a parent tag for the object, but instead uses a separate instance of the object tag element for each value. In the following example, the identifier tag element is called <name>:

<parent-object>
    <name>identifier</name>
    <object>value1</object>
    <object>value2</object>
    <object>value3</object>
</parent-object>

To remove one or more values for such an object, a client application includes the operation="delete" attribute or the operation="remove" attribute in the opening tag for each value. It does not include tag elements that represent values to be retained. In the following example, the identifier tag element is called <name>:

<configuration>
    <!-- opening tags for each parent of the parent object -->
        <parent-object> 
            <name>identifier</name> 
            <object operation="(delete | remove)">value1</object> 
            <object operation="(delete | remove)">value2</object> 
        </parent-object> 
    <!-- closing tags for each parent of the parent object -->
</configuration>

We recommend that the application set the default mode to no-change by including the <default-operation> tag element with the value none, as described in Set the Edit Configuration Mode in a NETCONF Session. For more information about leaf statements with multiple values, see Map Configuration Statements to Junos XML Tag Elements.

The following example shows how to remove two of the permissions granted to the user-accounts login class: