Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Managing Configuration Files Through the Configuration History (J-Web Procedure)

 
Note

This topic applies only to the J-Web Application package.

Use the Configuration History function to manage configuration files.

Displaying Configuration History

To manage configuration files with the J-Web interface, select Maintain > Config Management > History. The main pane displays History — Database Information page.

Table 1 summarizes the contents of the display.

The configuration history display allows you to:

  • View a configuration.

  • Compare two configurations.

  • Download a configuration file to your local system.

  • Roll back the configuration to any of the previous versions stored on the switch.

Table 1: 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 OS CLI command.

  • junoscript—A Junos XML protocol 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.

  • 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 > Edit Configuration Text option.

  • Imported upload [filename]—Configuration was uploaded with the Configure > CLI Tools > Point Click Editor option.

  • Modified via J–Web Configure — Configuration was modified with the J-Web Configure menu.

  • 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.

Displaying Users Editing the Configuration

To display a list of users editing the switching platform configuration, select Config Management > History. The list is displayed as Database Information in the main pane. Table 2 summarizes the Database Information display.

Table 2: 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 switch.

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 switching platform.

Edit Flags

Designates a private or exclusive edit.

Edit Path

Level of the configuration hierarchy that the user is editing.

Comparing Configuration Files with the J-Web Interface

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

  1. Select Config Management > History. A list of the current and the previous 49 configurations is displayed as Configuration History in the main pane.
  2. Select the check boxes to the left of the two 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 older configuration file are displayed in blue on the right.

Downloading a Configuration File with the J-Web Interface

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

  1. Select Config Management > History. A list of current and previous 49 configurations is displayed as Configuration History in the main pane.
  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 with the J-Web Interface

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

  1. Select Config Management > History. A list of current and previous 49 configurations is displayed as Configuration History in the main pane.
  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 switch loads and commits the selected configuration. This behavior is different from the switch's behavior that occurs after you enter the rollback configuration mode command from the CLI. In the latter case, the configuration is loaded but not committed.