best-effort high 000000
...
Rewrite rule: dscp-ipv6-default, Code point type: dscp-ipv6, Index: 25
...
Rewrite rule: exp-default, Code point type: exp, Index: 26
...
Rewrite rule: ieee8021p-default, Code point type: ieee-802.1, Index: 27
...
Rewrite rule: ipprec-default, Code point type: inet-precedence, Index: 28
...
Default Drop Profile
Drop profile: <default-drop-profile>, Type: discrete, Index: 1
Fill level Drop probability
100 100
Default Schedulers
Scheduler map: <default>, Index: 2
Scheduler: <default-be>, Forwarding class: best-effort, Index: 17
Transmit rate: 95 percent, Rate Limit: none, Buffer size: 95 percent, Priority:
low
Drop profiles:
Loss priority Protocol Index Name
Low Any 1 <default-drop-profile>
High Any 1 <default-drop-profile>
...
Related
Documentation
Default Forwarding Classes•
• Default Behavior Aggregate Classification Overview
• Default Drop Profile
• Default Schedulers Overview
• Forwarding Classes and Fabric Priority Queues
CoS Applications Overview
You can configure CoS features to meet your application needs. Because the components
are generic, you can use a single CoS configuration syntax across multiple routing devices.
CoS mechanisms are useful for two broad classes of applications. These applications
can be referred to as in the box and across the network.
In-the-box applications use CoS mechanisms to provide special treatment for packets
passing through a single node on the network. You can monitor the incoming traffic on
each interface, using CoS to provide preferred service to some interfaces (that is, to some
customers) while limiting the service provided to other interfaces. You can also filter
outgoing traffic by the packet’s destination, thus providing preferred service to some
destinations.
Copyright © 2013, Juniper Networks, Inc.8
Class of Service Overview and Examples for EX9200 Switches