- 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 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
-
Configuring Redundant Trunk Groups on EX Series Switches (J-Web Procedure)
This topic applies only to the J-Web Application package.
A redundant trunk link provides a simple solution for network recovery when a trunk interface goes down. Traffic is routed to another trunk interface, keeping network convergence time to a minimum. You can configure redundant trunk groups (RTGs) with a primary link and a secondary link on trunk interfaces, or configure dynamic selection of the active interface. If the primary link fails, the secondary link automatically takes over without waiting for normal Spanning Tree Protocol (STP) convergence. An RTG can be created only if the following conditions are satisfied:
A minimum of two trunk interfaces that are not part of any RTG are available.
All the selected trunk interfaces to be added to the RTG have the same VLAN configuration.
The selected trunk interfaces are not part of a spanning-tree configuration.
To configure an RTG by using the J-Web interface:
Field | Function | Your Action |
|---|---|---|
Group Name | Specifies a unique name for the RTG. | Enter a name. |
Member Interface 1 | Specifies a logical interface containing multiple trunk interfaces. | Select a trunk interface from the list. |
Member Interface 2 | Specifies a trunk interface containing multiple VLANs. | Select a trunk interface from the list. |
Select Primary Interface | Enables you to specify one of the interfaces in the RTG as the primary link. The interface without this option is the secondary link in the RTG. |
|
Dynamically select my active interface | Specifies that the system dynamically select the active interface. | Select the option button. |
