 | Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |
When a configuration element (hierarchy level or configuration object) is deactivated, it remains in the candidate configuration or private copy, but when the configuration is later committed, the element does not affect the functioning of the routing platform. A client application can deactivate an element immediately as it creates it, or can deactivate an existing element. It can also reactivate an existing deactivated element so that when the configuration is committed, the element again has an effect on routing platform functioning.
See the following sections:
| Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |