Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Managing Configuration Files Overview

Configuration files in Junos Space Network Management Platform are created when device configuration data from managed devices are backed up to the Junos Space Platform database for the first time. A separate configuration file is created in the database for each managed device. Each time the configuration of a device changes, a new version of the configuration file is created on the device, which can then be backed up to the Junos Space Platform database or to a remote server at a fixed time, or at a set recurrence interval periodically.

Centralized configuration file management enables you to maintain multiple versions of your device configuration files in Junos Space Platform. This helps you recover device configuration files in case of a system failure and maintain consistent configuration across multiple devices.


Version management for configuration files in Junos Space Platform is independent of configuration file versioning on devices. Each commit command on a device creates a new version of the configuration file on the device, but no more than 49 versions can be stored on a device. However, Junos Space Platform allows you to store more than 49 versions of a configuration file on the Junos Space server.

The configuration files workspace helps you manage the following configuration files:

  • Running configuration—The configuration file currently in effect on the device. The running configuration file is labeled Version 0.

  • Candidate configuration—The new, not yet committed, configuration file that will become the running configuration.

  • Backup configuration—The configuration file for recovery or rollback purposes. When you execute a commit command, a backup configuration file is created and the oldest backup file (Version 49) is deleted from the device. The most recent backup configuration file is labeled Version 1.

The following is a potential workflow for an individual file or device in this workspace:

  1. Back up the device configuration file and thus bring the device’s running configuration under Junos Space Platform management.

  2. Edit a copy of the backup configuration file to create a candidate configuration file.

  3. Verify edits by comparing the initial backup version of the configuration file with the edited version.

  4. Restore the candidate configuration file to the device.

  5. Export the initial backup version to a zip file.

Over a period of time, the number of device configuration files that are backed up in Junos Space Platform database increases. Accumulation of configuration files in the database could increase the overhead to the database and adversely affect the overall performance of the server. You can purge the device configuration files that are older than the latest 2 versions of the configuration files that are backed up.

To purge the older device configuration files, use the /var/www/cgi-bin/ script.

On the Junos Space Platform UI, you can view stored configuration files on the Configuration Files > Config Files Management page. For information about the roles that you need to be assigned to perform various tasks related to configuration files, see Predefined Roles Overview.

On the Config Files Management page, you can perform the following actions: