Defining CoS Schedulers (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 tail 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.
You can associate up to four user-defined scheduler maps with the interfaces.
This topic describes:
Configuring CoS Schedulers
To configure CoS schedulers:
- Create a scheduler (be-sched) and assign
it a priority:
[edit class-of-service schedulers]
user@switch# set be-sched priority low - Configure a scheduler map (be-map) that
associates the scheduler (be-sched) with the forwarding class
(best-effort):
[edit class-of-service scheduler-maps]
user@switch# set be-map forwarding-class best-effort scheduler be-sched - Assign the scheduler map (be-map) to one
or more Ethernet interfaces:
- To assign the scheduler map to one interface (ge-0/0/1):
[edit class-of-service interfaces]
user@switch# set ge-0/0/1 scheduler-map be-map - To assign the scheduler map to more than one interface
by using a wildcard (all Gigabit Ethernet interfaces):
[edit class-of-service interfaces]
user@switch# set ge-* scheduler-map be-map
- To assign the scheduler map to one interface (ge-0/0/1):
Assigning Scheduler Maps to Interfaces on a 40-port SFP+ Line Card
For interfaces on a 40-port SFP+ line card, you use the same procedure to configure CoS schedulers as you do for other interfaces. However, you must assign the same scheduler map to all the interfaces in a port group.
When you assign a scheduler map to one interface in a port group, you do not need to assign the scheduler map to the remaining interfaces. The switch automatically uses that scheduler map for the interfaces in the port group when you bring the interfaces up.
If you assign different scheduler maps to different interfaces in a port group, you do not receive an error when you commit the configuration. Instead, an error is logged to the system log. When you bring an interface in the port group up, the default scheduler map is used. If you assign a scheduler map to an interface that is down that is different from the scheduler map being used by the currently operating interfaces in a port group, the default scheduler map is used by all interfaces in a port group, even the currently operating ones, when you bring the interface up.
To change the scheduler map assigned to a port group:
- Delete the current scheduler map from the interfaces
(xe-0/0/1 and xe-0/0/2) it is currently assigned
to:
[edit class-of-service interfaces]
user@switch# delete xe-0/0/1 scheduler-map[edit class-of-service interfaces]
user@switch# delete xe-0/0/2 scheduler-map - Assign the new scheduler map (ef-map)
to at least one interface in the port group:
[edit class-of-service interfaces]
user@switch# set xe-0/0/1 scheduler-map ef-map
