Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Managing system configuration

Saving the running configuration

You can save the configuration to file for your own use; for example copying to another device, by using the save <filename> command in configuration mode.

The running configuration is saved automatically when you enter commit or commit-confirm. Entering the save command without a filename has no effect.

You can also save a configuration file to a location path other than the standard configuration directory by specifying a different path. You can save the configuration to a location specivied as ftp, http, scp or tftp.


The save command writes only committed changes. If you try to save uncommitted changes, the system warns you that it is saving only the committed changes.

Loading a saved configuration

To load a previously saved configuration, use the load command in configuration mode. By default, the system reads the file from the /config configuration directory.

A loaded configuration then needs to be committed to become the active configuration.

Merging saved and running configurations

You can merge a saved configuration with the active (running) configuration by using the merge command.

The merger adds new configuration entries and applies any modifications to existing active entries to produce a new working configuration. This merged configuration must be committed before it becomes the active configuration.

Configuration can be loaded from a hard disk (including a Flash disk or USB device), a TFTP server, an FTP server, an SCP server, or an HTTP server. Note that you cannot load an empty configuration file; the configuration file must contain at least one configuration node.

Rolling back to a previous version

You can roll back system configuration to any archived version by using the rollback command.

To see a list of available configuration file revisions, use the show system commit command in operational mode.

Archiving configuration versions on commit

The system automatically archives the configuration whenever you commit a configuration change. Previous versions of the configuration are saved in the /config/archive directory, with a file name config.boot.<n>.gz.

By default, the system maintains 20 versions of configuration in the archive. You can change the number of versions maintained in the archive by using the system config-management commit-revisions command.

You can also direct the system to save configuration versions to a remote location whenever the configuration is committed by using the system config-management commit-archive archive command. FTP, SCP, and TFTP destinations are supported.

Comparing configuration versions

You can compare two versions of configuration by using the show system commit and compare commands.

  • Configuration Commands

    • compare

      • Difference between the working and active configuration.

    • compare n

      • Difference between the working configuration and revision n.

    • compare n m

      • Difference between revision n and revision m.

  • Operational Commands

    • show system commit

      • Summary of commits.

    • show system commit file n

      • Full configuration at revision n.

    • show system commit file n compare m

      • Difference between revision n and revision m.

    • show system commit diff n

      • What changed in a given commit (between revision n and revision n +1). This command is equivalent to the show system file n compare n +1 command.