Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

close
keyboard_arrow_left
list Table of Contents
file_download PDF
keyboard_arrow_right

Defining CoS Schedulers and Scheduler Maps (CLI Procedure)

date_range 14-Dec-23

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.

Note:

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:

  1. Create a scheduler, and assign one or more output queue properties to it:
    content_copy zoom_out_map
    [edit class-of-service]
    user@switch# set schedulers scheduler-name output-queue-properties 
     

    For various properties that you can define for an output queue, see the schedulers hierarchy.

  2. Configure a scheduler map that associates the scheduler with the forwarding class:
    content_copy zoom_out_map
    [edit class-of-service]
    user@switch# set scheduler-maps map-name forwarding-class class-name scheduler scheduler-name

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
external-footer-nav
Ask AI
close

How can I help you today?

LLMs can make mistakes. Verify important information.
chat_add_on New topic
send progress_activity
This conversation will be monitored and recorded. Any information you provide will be subject to our Privacy Notice and may be used for quality assurance purposes. Do not include any personal or sensitive information. Ask AI can make mistakes. Verify generated output for accuracy.
Protected by hCaptcha arrow_drop_down arrow_drop_up
Juniper Networks, Inc. | Privacy Notice | Terms of Use