Use the following commands to store and apply configuration changes:
save—Saves the candidate
configuration in the non-volatile storage on the appliance. The
saved configuration is retained until overwritten by subsequent save commands.
Note that this command does not make the configuration active.
commit—Applies the candidate
configuration to the appliance. A committed configuration becomes
the active configuration for the device.
set—Changes a value in the candidate
configuration.
load—Assigns the last saved
configuration or a specified configuration to be the candidate configuration.
When
exiting configuration mode without issuing the save or commit command,
the configuration changes could be lost if the appliance loses power.
Maintaining a candidate configuration and separating the save
and commit steps confers important advantages when compared with
traditional CLI architectures:
Distinguishing between the save and commit concepts allows
multiple changes to be made at the same time and reduces system
vulnerability.
Commands can easily be adapted for similar functions. For
example, when configuring two Ethernet interfaces, each with a different
IP address, you can edit the configuration for the first interface,
copy the command, modify only the interface and IP address, and
then apply the change to the second interface.
The command structure is always consistent.
Because the candidate configuration is always unique, all authorized
changes to the candidate configuration are consistent with each
other.