Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Maintaining Configuration Management History

 
  1. Select Maintain>Config Management>History in the J-Web user interface if you are using SRX5400, SRX5600, or SRX5800 platform.

    Or

    Select Administration>Devices>Config Management>History in the J-Web user interface.

    The History page appears. Table 272 explains the contents of this page.

  2. Click one:
    • Number — Displays a configuration .

    • Compare — Compares two configurations files that you select.

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

    • Download — Downloads a configuration file to your local system.

      • Select the options on your Web browser to save the configuration file to a target directory on your local system.

        The file is saved as an ASCII file.

    • Rollback — Rolls back the configuration to any of the previous versions stored on the device.

      • The main pane displays the results of the rollback operation.

        Note

        Click Rollback to load the device and download 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.

Enter the information specified in Table 272 to maintain the secure router.

Table 272: History Maintenance Options

FieldFunctionAction

Number

Indicates the version of the configuration file.

Date/Time

Indicates the date and time the configuration was committed.

User

Indicates the name of the user who committed the configuration.

Client

Indicates the method by which the configuration was committed.

The available options are:

  • cli—A user entered a Junos OS CLI command.

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

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

  • other—Another method was used to commit the configuration.

Comment

Indicates comments.

Log Message

Indicates the 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 specified version of the J-Web user interface.

  • 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

Indicates action to perform with the configuration file.

The available options are:

  • Download—Downloads a file.

  • Rollback—Rolls back a file.

Select an option.