- play_arrow Configuration
- play_arrow Starting J-Web
- play_arrow J-Web Configuration Tools
- play_arrow System Basics Configuration
- Connecting and Configuring an EX Series Switch (J-Web Procedure)
- Configuring Date and Time for the EX Series Switch (J-Web Procedure)
- Configuring System Identity for an EX Series Switch (J-Web Procedure)
- Configuring Management Access for the EX Series Switch (J-Web Procedure)
- Generating SSL Certificates to Be Used for Secure Web Access (EX Series Switch)
- Rebooting or Halting the EX Series Switch (J-Web Procedure)
- play_arrow Class of Service Configuration
- Defining CoS Drop Profiles (J-Web Procedure)
- Defining CoS Classifiers (J-Web Procedure)
- Defining CoS Code-Point Aliases (J-Web Procedure)
- Assigning CoS Components to Interfaces (J-Web Procedure)
- Defining CoS Forwarding Classes (J-Web Procedure)
- Defining CoS Rewrite Rules (J-Web Procedure)
- Defining CoS Schedulers (J-Web Procedure)
- Defining CoS Scheduler Maps (J-Web Procedure)
- play_arrow Security and Management Configuration
- play_arrow Routing Policies and Packet Filtering Configuration
- play_arrow Ethernet Switching Configuration
- play_arrow Interfaces
- play_arrow Configuring Services
- play_arrow Configuring Layer 3 Protocols
- play_arrow Configuring Real-Time Performance Monitoring
- play_arrow Software Installation and Upgrades
- play_arrow Configuration, Files, Users, Licenses, and Product Registration
- Managing Configuration Files Through the Configuration History (J-Web Procedure)
- Setting or Deleting the Rescue Configuration (J-Web Procedure)
- Uploading a Configuration File (J-Web Procedure)
- Managing Log, Temporary, and Crash Files on the Switch (J-Web Procedure)
- Managing Users (J-Web Procedure)
- Managing Licenses for the EX Series Switch (J-Web Procedure)
- Registering the EX Series Switch with the J-Web Interface
- Generating Support Information Reports for EX Series Switches Using the J-Web Interface
- play_arrow Virtual Chassis Configuration
-
- 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 Administration
- play_arrow Software, Files, Licenses, Logs
- Uploading a Configuration File (J-Web Procedure)
- Managing Configuration Files Through the Configuration History (J-Web Procedure)
- Setting or Deleting the Rescue Configuration (J-Web Procedure)
- Updating J-Web Interface on EX Series Switches (J-Web Procedure)
- Upgrading Junos OS on EX Series Switches (J-Web Procedure)
- Managing Licenses for the EX Series Switch (J-Web Procedure)
- Rebooting or Halting the EX Series Switch (J-Web Procedure)
- Managing Log, Temporary, and Crash Files on the Switch (J-Web Procedure)
- Registering the EX Series Switch with the J-Web Interface
- Generating Support Information Reports for EX Series Switches Using the J-Web Interface
-
- play_arrow Troubleshooting
- play_arrow Troubleshooting Task
- play_arrow FAQ
-
Using the Commit Options to Commit Configuration Changes (J-Web Procedure)
You can use the single-commit feature to commit all outstanding configuration changes in the J-Web interface on EX Series switches simultaneously. This helps in reducing the time J-Web takes for committing configurations because when changes are committed at every step, rollback configurations pile up.
For example, suppose you want to delete a firewall filter and add a new one. With immediate commits, you would need to commit your changes twice for this action. Using single commit, you can decrease the number of commits to one, thus saving time for working on other configurations.
When you edit a configuration, you work on a copy of the current configuration, which is your candidate configuration. The changes you make to the candidate configuration are visible through the user interface immediately, allowing other users to edit those configurations, but they do not take effect on the switch until you commit the changes. When you commit the configuration, the candidate file is checked for proper syntax, activated, and marked as the current, operational software configuration file. If multiple users are editing the configuration when you commit the candidate configuration, changes made by all users take effect.
You can configure the commit options to either commit all configuration changes together or commit each configuration change immediately using the J-Web Commit Preference page.
There are some pages on which configuration changes must be committed immediately. For such pages, if you configure the commit options for a single commit, the system displays warning notifications that remind you to commit your changes immediately. An example of such a page is the Interface Page (Configure > Interface).
To configure the commit options on an EX Series switch using the J-Web interface:
Menu Item | Function | Your Action |
|---|---|---|
Commit | Commits the candidate configuration of the current user session, along with changes from other user sessions. |
|
Compare | Displays the XML log of pending uncommitted configurations on the device. |
|
Discard | Discards the candidate configuration of your current session, along with changes from other user sessions. |
|
Preference | Indicates your choice of committing all global configurations together or committing each configuration change immediately. |
|
Option | Function |
|---|---|
Validate and commit configuration changes | Sets the system to validate and force an immediate commit on every screen after every configuration change. |
Validate configuration changes | Loads all the configuration changes for an accumulated single commit. If there are errors in loading the configuration, the errors are logged. This is the default mode. Once you select this option, you need to select Commit Options > Commit to commit your changes. |
