- play_arrow Overview
- play_arrow Overview
- J-Web User Interface for EX Series Switches Overview
- J-Web Interface—Application Package
- Understanding J-Web User Interface Sessions
- Dashboard for EX Series Switches
- Understanding J-Web Configuration Tools
- Understand Alarm Types and Severity Levels on EX Series Switches
- Using the Commit Options to Commit Configuration Changes (J-Web Procedure)
-
- play_arrow Monitoring
- play_arrow Monitoring Tasks
- Check Active Alarms with the J-Web Interface
- Monitor System Log Messages
- Monitoring Chassis Information
- Monitoring System Properties
- Monitoring System Process Information
- Monitoring Switch Control Traffic
- Monitoring Interface Status and Traffic
- Monitoring PoE
- Monitoring Hosts Using the J-Web Ping Host Tool
- Monitoring Network Traffic Using Traceroute
- Monitoring DHCP Services
- Monitoring OSPF Routing Information
- Monitoring RIP Routing Information
- Monitoring BGP Routing Information
- Monitoring Routing Information
- Monitoring Ethernet Switching on EX Series Switches (J-Web)
- Monitoring IGMP Snooping
- Monitoring Spanning Tree Protocols on Switches
- Monitoring CoS Classifiers
- Monitoring CoS Drop Profiles
- Monitoring CoS Value Aliases
- Monitoring CoS Forwarding Classes
- Monitoring Interfaces That Have CoS Components
- Monitoring CoS Rewrite Rules
- Monitoring CoS Scheduler Maps
- Monitoring the Virtual Chassis Status and Statistics on EX Series Virtual Chassis
- Monitoring 802.1X Authentication
- Monitoring Port Security
-
- play_arrow Troubleshooting
- play_arrow Troubleshooting Task
- play_arrow FAQ
-
Managing Configuration Files Through the Configuration History (J-Web Procedure)
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.
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:
|
Comment | Comment. |
Log Message | Method used to edit the configuration:
|
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.
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. |
See Also
Comparing Configuration Files with the J-Web Interface
To compare any two of the past 50 committed configuration files:
