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. The History Database Information page displays Database Information and Configuration History (see Figure 19).

After you make changes to the configuration in this window, you must commit the changes immediately for them to take effect. To commit all changes to the active configuration, select Commit Options > Commit. See Using the Commit Options to Commit Configuration Changes (J-Web Procedure) for details about all commit options.

When you use an HTTPS connection in the Microsoft Internet Explorer browser to save a report from this page in the J-Web interface, the error message "Internet Explorer was not able to open the Internet site" is displayed. This problem occurs because the Cache-Control: no cache HTTP header is added on the server side and Internet Explorer does not allow you to download the encrypted file with the Cache-Control: no cache HTTP header set in the response from the server.

As a workaround, refer to Microsoft Knowledge Base article 323308, which is available at this URL: http://support.microsoft.com/kb/323308. Also, you can alternatively use HTTP in the Internet Explorer browser or use HTTPS in the Mozilla Firefox browser to save a file from this page.

Table 66 summarizes the contents of the display.

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

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

Figure 19: Configuration Database and History Page

Table 66: 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 Junos Script 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 > CLI Editor option. Imported upload [filename]—Configuration was uploaded with the Configure > CLI Tools > Point and Click CLI 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: Download or Rollback.

For more information about saved versions of configuration files, see the Junos OS Administration Library for Routing Devices.