4.5. Selective Activate

As discussed in Section 4.4, Activating Changes, the default action when configuration changes are activated is to deploy all unactivated changes. However, it is possible to activate changes selectively for a given standalone node or HA pair.

To do this, the activate command is followed by the name of the node or HA pair. For example, only the pending changes for the standalone node called my-node1 would be activated with the following command:

admin@InCenter:/> activate my-node1

In the same way, only the changes made on the HA pair called my-hapair might be activated:

admin@InCenter:/> activate my-hapair

An alternative method of activating only the pending changes for a particular standalone node or pair and enter an activate command with no parameters. For example, the following commands could be used to execute all the pending changes for the node called my-node1:

admin@InCenter:/> cc StandaloneNode my-node1 
admin@InCenter:/my-node1> activate

Note that changing the CLI context to a node within an HA pair and issuing an activate command is not permitted and will give an error message.