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

Deactivating or Reactivating an Existing Element

To deactivate an existing element, or reactivate a previously deactivated one, a client application includes the basic tag elements or configuration statements for its parent levels, as described in Creating, Modifying, or Deleting Configuration Elements.

If using JUNOS XML tag elements to represent a configuration object that has an identifier, the application includes the inactive="inactive" or active="active" attribute in the object’s opening container tag and also emits the identifier tag element and value. In the following, the identifier tag element is called <name>. To represent a hierarchy level or container object that has children but not an identifier, the application uses an empty tag:

<configuration>
<!- - opening tag for each parent of the element - ->
  !- - For an object with an identifier - ->
<object (inactive="inactive” | active="active")>
<name>identifier</name>
</object>

<!- - For a hierarchy level or object without an identifier - ->
<level-or-container (inactive="inactive” | active="active")/>
<!- - closing tag for each parent of the element - ->
</configuration>

If using formatted ASCII text to represent the element, the application precedes the element with the inactive: or active: operator. The name of a hierarchy level or container object is followed by a semicolon (even though in the existing configuration it is followed by curly braces that enclose its child statements):

<configuration-text>
/* statements for parent levels */

/* For an object with an identifier */
(inactive | active):
object identifier;

/* For a hierarchy level or object without an identifier */
(inactive | active):
object-or-level;

/* closing braces for parent levels */
</configuration-text>

The following example shows how to deactivate the isis hierarchy level at the [edit protocols] hierarchy level in the candidate configuration.

Image t1145.gif
[Contents] [Prev] [Next] [Index] [Report an Error]