Wiping out any changes in candidate config

[ShannonRowe]

From Device Management, if I "Revert to last saved config" does this simply revert back to the previously committed or saved config? ie it just wipes out any unsaved changes to the candidate config?

Is there any impact in doing this?

I simply want to wipe out the current candidate config.

Cheers,

Shannon

[bat]

Hi ShannonRowe

If you just want to remove the changes done in candidate config select the option "Revert to running config" it will discard all the uncommitted changes

Thanks

[ShannonRowe]

Hi,

Thanks for your super fast answer. can you confirm there is no impact to traffic flowing through the devices while doing this?

Cheers,

Shannon

[bat · Accepted solution]

ShannonRowe

You are welcome .

It will not have any impact on the traffic.

Thanks

[pulukas]

you have the option to save configurations at any time during the candidate process.  The revert to last saved is used to go back to a fallback point that is in between the current running configuration and your current candidate configuration.

None of these operations, revert to running or revert to save affect traffic at all.

[andreip]

From CLI, configuration mode, one can load last committed configuration (i. e. running configuration) with load config version - Tab will display version number and date/time when the configuration was committed.

[Jimmer93]

Hi, 

Just as an addition to the reverting last saved configurations. If we are just doing this to remove the changes in the candidate configuration, will this impact network performance?

Kind regards

James Leishman