- 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
-
Defining CoS Forwarding Classes (J-Web Procedure)
This topic applies only to the J-Web Application package.
You can define CoS forwarding classes on an EX Series switch using the J-Web interface. Assigning a forwarding class to a queue number affects the scheduling and marking of a packet as it transits a switch.
To define forwarding classes:
Field | Function | Your Action |
|---|---|---|
| Forwarding Class Summary | ||
Queue # | Specifies the internal queue numbers to which forwarding classes are assigned. By default, if a packet is not classified, it is assigned to the class associated with queue 0. You can have more than one forwarding class to a queue number. | To specify an internal queue number, select an integer from 0 through 11, appropriate for your platform as follows: Note: For EX2300 and EX2300-C switches, a maximum of eight egress queues are supported per port. To specify an internal queue number select an integer from 0 through 7. |
Forwarding Class Name | Specifies the forwarding class names assigned to specific internal queue numbers. By default, four forwarding classes are assigned to queue numbers 0 (best-effort), 1 (assured-forwarding), 5 (expedited-forwarding), and 7 (network-connect). | Type the name—for example, |
