Deactivate and Reactivate Statements and Identifiers in a Configuration

In a configuration, you can deactivate statements and identifiers so that they do not take effect when you issue the commit command. Any deactivated statements and identifiers are marked with the inactive: tag. They remain in the configuration, but are not activated when you issue a commit command.

To deactivate a statement or identifier, use the deactivate configuration mode command:

deactivate (statement | identifier) 

To reactivate a statement or identifier, use the activate configuration mode command:

activate (statement | identifier) 

In both commands, the statement or identifier you specify must be at the current hierarchy level.

In some portions of the configuration hierarchy, you can include a disable statement to disable functionality. One example is disabling an interface by including the disable statement at the [edit interface interface-name] hierarchy level. When you deactivate a statement, that specific object or property is completely ignored and is not applied at all when you issue a commit command. When you disable a functionality, it is activated when you issue a commit command but is treated as though it is down or administratively disabled.

Examples: Deactivate and Reactivate Statements and
Identifiers in a Configuration

Deactivate an interface in the configuration:

[edit interfaces]

user@host# show 

at-5/2/0 {

    traceoptions {

        traceflag all;

    }

    atm-options {

        vpi 0 maximum-vcs 256;

    }

    unit 0 {

...

[edit interfaces]

user@host# deactivate at-5/2/0

[edit interfaces]

user@host# show

inactive: at-5/2/0 {

    traceoptions {

        traceflag all;

    }

...

Reactivate the interface:

[edit interfaces]

user@host# activate at-5/2/0

[edit interfaces]

user@host# show

at-5/2/0 {

    traceoptions {

        traceflag all;

    }

...