[an error occurred while processing this directive][an error occurred while processing this directive]

Configuring CoS on MPLS Provider Edge Switch Using Circuit Cross-Connect (CLI Procedure)

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 provider edge (PE) switch that is using MPLS over circuit-cross connect (CCC).

Note: If you are using MPLS with CCC, you can use only one type of DSCP/IP precedence and only one type of IEEE 802.1p on the CCC interfaces.

This procedure creates a custom DSCP classifier and a custom EXP rewrite rule on the ingress PE. It also enables 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.

  1. Import the default DSCP classifier classes to the custom DSCP classifier that you are creating:

    [edit class-of-service]
    user@switch#set classifiers dscp dscp1 import default
  2. Add the expedited-forwarding class to this custom DSCP classifier, specifying a loss priority and code point:

    [edit class-of-service]
    user@switch#set classifiers dscp dscp1 forwarding-class expedited-forwarding loss-priority low code-points 000111
  3. Specify the values for the custom EXP rewrite rule, e1:

    [edit class-of-service]
    user@switch# set rewrite-rules exp e1 forwarding-class expedited-forwarding loss-priority low code-point 111
  4. Bind the DSCP classifier to the CCC interface:

    [edit ]
    user@switch# set class-of-service interfaces ge-0/0/1 unit 0 classifier dscp1
  5. Specify the number of bits per second permitted, on average, for the firewall policer, which will later be applied to the LSP:

    [edit firewall]
    set policer mypolicer if-exceeding bandwidth-limit 500m
  6. Specify the maximum size permitted for bursts of data that exceed the given bandwidth limit for this policer:

    [edit firewall policer]
    set mypolicer if-exceeding burst-size-limit 33553920
  7. Discard traffic that exceeds the rate limits for this policer:

    [edit firewall policer]
    set mypolicer then discard
  8. To reference the policer, configure a filter term that includes the policer action:

    [edit firewall]
    user@switch# set family any filter myfilter term t1 then policer mypolicer
  9. Apply the filter to the LSP:

    [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 (CLI Procedure).

Published: 2010-01-13

[an error occurred while processing this directive]