Config Management

Upload Configuration File

To upload a configuration file from your local system:

  1. Select Maintain>Config Management>Upload.

    The config management file is displayed.

  2. Specify the name of the file to upload using one of the following methods:
    • Type the absolute path and filename in the File to Upload box.
    • Click Browse to navigate to the file.
  3. Click Upload and Commit to upload and commit the configuration.

    The device checks the configuration for the correct syntax before committing it.

Using History

The J-Web interface provides configuration database and history information that allows you to manage configuration files. You can perform the following tasks:

Displaying Configuration History

When you commit a configuration, the device saves the current operational version and the previous 49 versions of committed configurations. To manage these configuration files with the J-Web interface, select Maintain>Config Management>History.

Table 194 summarizes the contents of the display.

The configuration history display allows you to perform the following operations:

Table 194: J-Web Configuration History Summary

Field

Description

Number

Version of the configuration file.

Date/Time

Date and time the configuration was committed.

User

Name of the user who committed the configuration.

Client

Method by which the configuration was committed:

  • cli—A user entered a JUNOS CLI command.
  • junoscript—A JUNOScript client performed the operation. Commit operations performed by users through the J-Web interface are identified in this way.
  • snmp—An SNMP set request started the operation.
  • button—The CONFIG button on the router was pressed to commit the rescue configuration (if set) or to clear all configurations except the factory configuration.
  • autoinstall—Autoinstallation was performed.
  • other—Another method was used to commit the configuration.

Comment

Comment.

Log Message

Method used to edit the configuration:

  • Imported via paste—Configuration was edited and loaded with the Configure>CLI Tools>CLI Editor option.
  • Imported upload [filename]—Configuration was uploaded with the Configuration>View and Edit>Upload Configuration File option.
  • Modified via quick-configuration—Configuration was modified with the J-Web Quick Configuration tool specified by quick-configuration.
  • Rolled back via user-interface—Configuration was rolled back to a previous version through the user interface specified by user-interface, which can be Web Interface or CLI.

Action

Action to perform with the configuration file. The action can be Download or Rollback.

For more information about saved versions of configuration files, see the Junos OS System Basics Configuration Guide.

Displaying Users Editing the Configuration

To display a list of users editing the device configuration, select Maintain>Config Management>History.

Table 195 summarizes the Database Information display.

Table 195: J-Web Configuration Database Information Summary

Field

Description

User Name

Name of user editing the configuration.

Start Time

Time of day the user logged in to the device.

Idle Time

Elapsed time since the user issued a configuration command from the CLI.

Terminal

Terminal on which the user is logged in.

PID

Process identifier assigned to the user by the device.

Edit Flags

Designates a private or exclusive edit.

Edit Path

Level of the configuration hierarchy that the user is editing.

Comparing Configuration Files

To compare any two of the past 50 committed configuration files:

  1. Select Configuration>History. A list of the current and previous 49 configurations is displayed as Configuration History in the main pane. Table 194 summarizes the Configuration History display.
  2. Click two of the check boxes to the left of the configuration versions you want to compare.
  3. Click Compare.

    The main pane displays the differences between the two configuration files at each hierarchy level as follows:

    • Lines that have changed are highlighted side by side in green.
    • Lines that exist only in the more recent configuration file are displayed in red on the left.
    • Lines that exist only in the least recent configuration file are displayed in blue on the right.

Downloading a Configuration File

To download a configuration file from the device to your local system:

  1. Select Configuration>History.

    A list of the current and previous 49 configurations is displayed as Configuration History in the main pane. Table 194 summarizes the Configuration History display.

  2. In the Action column, click Download for the version of the configuration you want to download.
  3. Select the options your Web browser provides that allow you to save the configuration file to a target directory on your local system.

    The file is saved as an ASCII file.

Loading a Previous Configuration File

To load (roll back) and commit a previous configuration file stored on the device:

  1. Select Configuration>History.

    A list of the current and previous 49 configurations is displayed as Configuration History in the main pane. Table 194 summarizes the Configuration History display.

  2. In the Action column, click Rollback for the version of the configuration you want to load.

    The main pane displays the results of the rollback operation.

    Note: When you click Rollback, the device loads and commits the selected configuration. This behavior is different from entering the rollback configuration mode command from the CLI, where the configuration is loaded, but not committed.

Using Rescue

If someone inadvertently commits a configuration that denies management access to a device, you can delete the invalid configuration and replace it with a rescue configuration. You must have previously set the rescue configuration through the J-Web interface or the CLI. The rescue configuration is a previously committed, valid configuration.

To view, set, or delete the rescue configuration, select Maintain>Config Management>Rescue. You can perform the following tasks: