Configuring Cos Schedulers; Assigning Scheduler Maps To Interfaces On A 40-Port Sfp+ Line Card - Juniper JUNOS OS 10.4 - FOR EX REV 1 Manual

Complete Software Guide for Junos

Configuring CoS Schedulers

Assigning Scheduler Maps to Interfaces on a 40-port SFP+ Line Card

3438
®
OS for EX Series Ethernet Switches, Release 10.4
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 on page 3438
Assigning Scheduler Maps to Interfaces on a 40-port SFP+ Line Card on page 3438
To configure CoS schedulers:
Create a scheduler ( be-sched
1.
[edit class-of-service schedulers]
user@switch# set be-sched priority low
Configure a scheduler map (
2.
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 (
3.
To assign the scheduler map to one interface (
[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
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
) and assign it a priority:
) that associates the scheduler (
be-map
):
) to one or more Ethernet interfaces:
be-map
ge-0/0/1
Copyright © 2010, Juniper Networks, Inc.
) with
be-sched
):