Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Announcement: Try the Ask AI chatbot for answers to your technical questions about Juniper products and solutions.

close
header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Configuring CoS on an MPLS Provider Edge Switch Using Circuit Cross-Connect

date_range 14-Dec-23

You can use class of service (CoS) within MPLS networks to prioritize certain types of traffic during periods of congestion. This topic describes configuring CoS components on a provider edge (PE) switch that is using MPLS over circuit-cross connect (CCC).

Note:

If you are using MPLS over CCC, you can use only one DSCP or IP precedence classifier and only one IEEE 802.1p classifier on the CCC interfaces.

This procedure is for creating a custom DSCP classifier and a custom EXP rewrite rule on the ingress PE. It also includes enabling a policer on the label-switched path (LSP) of the ingress PE to ensure that the amount of traffic forwarded through the LSP never exceeds the requested bandwidth allocation.

This topic includes:

Configuring CoS

To configure CoS on a provider edge switch:

  1. Import the default DSCP classifier classes to the custom DSCP classifier that you are creating:
    content_copy zoom_out_map
    [edit class-of-service]
    user@switch# set classifiers dscp classifier-nameimport default
  2. Add the expedited-forwarding class to this custom DSCP classifier, specifying a loss priority and code point:
    content_copy zoom_out_map
    [edit class-of-service]
    user@switch# set classifiers dscp classifier-name forwarding-class forwarding-class loss-priority loss-priority code-points code-point
  3. Specify the values for the custom EXP rewrite rule, e1:
    content_copy zoom_out_map
                                  [edit class-of-service]
    user@switch# set rewrite-rules exp e1 forwarding-class forwarding-class loss-priority loss-priority code-point code-point
  4. Bind the DSCP classifier to the CCC interface:
    content_copy zoom_out_map
    [edit ]
    user@switch# set class-of-service interfaces interface unit unit classifier classifier-name       

Configuring an LSP Policer

To configure an LSP policer:

  1. Specify the number of bits per second permitted, on average, for the policer, which will later be applied to the LSP:
    content_copy zoom_out_map
    [edit firewall]
    set policer mypolicer if-exceeding bandwidth-limit 500m
  2. Specify the maximum size permitted for bursts of data that exceed the given bandwidth limit for this policer:
    content_copy zoom_out_map
    [edit firewall policer]
    set mypolicer if-exceeding burst-size-limit 33553920
  3. Discard traffic that exceeds the rate limits for this policer:
    content_copy zoom_out_map
    [edit firewall policer]
    set mypolicer then discard
  4. To reference the policer, configure a filter term that includes the policer action:
    content_copy zoom_out_map
                                  [edit firewall]
    user@switch# set family any filter myfilter term t1 then policer mypolicer                         
  5. Apply the filter to the LSP:
    content_copy zoom_out_map
    [edit protocols mpls]
    set label-switched-path lsp_to_pe2_ge1 policing filter myfilter
Note:

You can also configure schedulers and shapers as needed. See Defining CoS Schedulers and Scheduler Maps (CLI Procedure).

footer-navigation