[Prev][Next][Report an Error]

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 main pane displays Database Information and Configuration History (see Figure 54).

Table 250 summarizes the contents of the display.

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

Figure 54: Configuration Database and History Page

Configuration
Database and History Page

Table 250: 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. For more information, see Edit Configuration Text.
  • Imported upload [filename]—Configuration was uploaded with the Configuration>View and Edit>Upload Configuration File option. For more information, see Upload Configuration File.
  • Modified via quick-configuration—Configuration was modified with the J-Web Quick Configuration tool specified by quick-configuration. For more information, see Using 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. For more information, see Loading a Previous Configuration File.

Action

Action to perform with the configuration file. The action can be Download or Rollback. For more information, see Downloading a Configuration File and Loading a Previous Configuration File.

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


[Prev][Next][Report an Error]