You can commit the current candidate configuration but require an explicit confirmation for the committed configuration to become permanent. This commit process is useful for verifying that a configuration change works correctly and does not prevent management access to the Services Router. If the change prevents access or causes other errors, an automatic rollback to the previous configuration restores access after the rollback confirmation timeout expires.
To commit the current candidate configuration, but require an explicit confirmation for the commit to become permanent, use the commit confirmed command:
-
commit confirmed <minutes>
Replace minutes with the number of minutes to allow for the timeout period. The default value is 10 minutes.
To make the new configuration permanent, enter the commit or commit check command within the timeout period specified in the commit confirmed command. If the commit is not confirmed within the timeout period, the Services Router automatically rolls back to the previous configuration.
If the configuration contains syntax errors, a message indicates the location of the error.