Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation

Associating Schedulers with Fabric Priorities

On Juniper Networks M320 Multiservice Edge Routers and T Series Core Routers only, you can associate a scheduler with a class of traffic that has a specific priority while transiting the fabric. Traffic transiting the fabric can have two priority values: low or high. To associate a scheduler with a fabric priority, include the priority and scheduler statements at the [edit class-of-service fabric scheduler-map] hierarchy level:

[edit class-of-service fabric scheduler-map]priority (high | low) scheduler scheduler-name;

Note: For a scheduler that you associate with a fabric priority, include only the drop-profile-map statement at the [edit class-of-service schedulers scheduler-name] hierarchy level. You cannot include the buffer-size, transmit-rate, and priority statements at that hierarchy level.

Example: Associating a Scheduler with a Fabric Priority

Associate a scheduler with a class of traffic that has a specific priority while transiting the fabric:

[edit class-of-service]
schedulers {fab-be-scheduler {drop-profile-map loss-priority low protocol any drop-profile fab-profile-1;drop-profile-map loss-priority high protocol any drop-profile fab-profile-2;}fab-ef-scheduler {drop-profile-map loss-priority low protocol any drop-profile fab-profile-3;drop-profile-map loss-priority high protocol any drop-profile fab-profile-4;}}
drop-profiles {fab-profile-1 {fill-level 100 drop-probability 100;fill-level 85 drop-probability 50;}fab-profile-2 {fill-level 100 drop-probability 100;fill-level 95 drop-probability 50;}fab-profile-3 {fill-level 75 drop-probability 100;fill-level 95 drop-probability 50;}fab-profile-4 {fill-level 100 drop-probability 100;fill-level 80 drop-probability 50;}}
fabric {scheduler-map {priority low scheduler fab-be-scheduler;priority high scheduler fab-ef-scheduler;}}

Published: 2013-08-28