[
Contents]
[
Prev]
[
Next]
[
Index]
[
Report an Error]
Configuration Database and History Overview
When you commit a configuration, the Services Router saves the current operational
version and the previous 49 versions of committed configurations. To manage these configuration files
with the J-Web interface, select Configuration>History. The main pane displays Database Information and Configuration History
(see Figure 6).
Table 12 and Table 13 summarize the contents
of the display.
Figure 6: Configuration Database
and History Page
Table 12: 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 Services Router.
|
|
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 Services Router.
|
|
Edit Flags
|
Designates a private or exclusive edit.
|
|
Edit Path
|
Level of the configuration hierarchy that the user is editing.
|
Table 13: 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 command-line
interface 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 or RESET
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 Configuration>View
and Edit>Edit Configuration Text option. For more information,
see Editing and Committing the Configuration Text.
-
Imported upload [filename]—Configuration was uploaded with the Configuration>View and Edit>Upload Configuration File option.
For more information, see Uploading a Configuration File.
-
Modified via quick-configuration—Configuration was modified using the J-Web Quick Configuration
tool specified by quick-configuration. For more
information, see Using J-Web 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.
|
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 Services Router.
For more information about saved versions of configuration files,
see Editing and Committing a Configuration.
[
Contents]
[
Prev]
[
Next]
[
Index]
[
Report an Error]