- play_arrow Congestion Management, Tail Drop Profiles, Queue Shaping, and Explicit Congestion Notification (ECN)
- play_arrow Congestion Management
- play_arrow Tail Drop Profiles
- play_arrow Queue Shaping
- play_arrow Explicit Congestion Notification (ECN)
-
- play_arrow CoS on Overlay Networks
- play_arrow CoS on MPLS Networks
- Understanding Using CoS with MPLS Networks on EX Series Switches
- Example: Combining CoS with MPLS on EX Series Switches
- Configuring CoS on an MPLS Provider Edge Switch Using IP Over MPLS
- Configuring CoS on an MPLS Provider Edge Switch Using Circuit Cross-Connect
- Configuring CoS on Provider Switches of an MPLS Network
- play_arrow CoS on EVPN VXLANs
-
- play_arrow Configuration Statements and Operational Commands
Defining CoS Schedulers and Scheduler Maps (CLI Procedure)
You use schedulers to define the class-of-service (CoS) properties of output queues. These properties include the amount of interface bandwidth assigned to the queue, the size of the memory buffer allocated for storing packets, the priority of the queue, and the drop profiles associated with the queue.
You associate the schedulers with forwarding classes by means of scheduler maps. You can then associate each scheduler map with an interface, thereby configuring the queues and packet schedulers that operate according to this mapping.
On EX Series switches, you cannot configure a scheduler map on an individual
interface that is a member of a link aggregation group (LAG). Instead, you must
configure the scheduler map on the LAG itself (that is, on the aggregated Ethernet
(ae
) interface).
You can associate up to four user-defined scheduler maps with an interface.
This topic describes:
Configuring a Scheduler and a Scheduler Map
You can define the properties for an output queue by configuring a scheduler. You can then define a scheduler map to associate a forwarding class with a scheduler.
To configure a scheduler and a scheduler map:
Assigning a Scheduler Map to Interfaces
After defining a scheduler map, you can assign the scheduler map to one or more interfaces. You can also assign the scheduler map to multiple interfaces by using a wildcard representation of the interface or Virtual Chassis Ports (VCPs).
Following are sample syntaxes and examples for assigning a scheduler map to a single or to multiple interfaces:
To assign the scheduler map to one interface:
content_copy zoom_out_map[edit class-of-service interfaces] user@switch# set interface-name scheduler-map map-name
To assign the scheduler map to more than one interface, you can use a wildcard representation of the interface:
content_copy zoom_out_map[edit class-of-service interfaces] user@switch# set wild-card-representation-of-interface-name scheduler-map map-name
For example, following is the configuration to assign the
be-map
scheduler map to all Gigabit Ethernet interfaces (ge-*
):content_copy zoom_out_map[edit class-of-service interfaces] user@switch# set ge-* scheduler-map be-map
To assign the scheduler map to all VCPs:
content_copy zoom_out_map[edit class-of-service interfaces] user@switch# set wild-card-representation-of-vcp scheduler-map map-name
For example, following is the configuration to assign the
be-map
scheduler map to all VCPs:content_copy zoom_out_map[edit class-of-service interfaces] user@switch# set vcp-* scheduler-map be-map