Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Creating Policy Lists for MPLS

    The following example creates an MPLS policy list.

    1. Create the policy list routeForMpls.
      host1(config)#mpls policy-list routeForMpls host1(config-policy-list)#
    2. Create the classification group.
      host1(config-policy-list)#classifier-group * precedence 200 host1(config-policy-list-classifier-group)#
    3. Add one rule that sets the EXP bits for all packets to 2, and a second rule that uses the rate-limit profile mplsRLP
      host1(config-policy-list-classifier-group)#mark-exp 2 host1(config-policy-list-classifier-group)#rate-limit-profile mplsRLP5
    4. Exit Policy List Configuration mode to save the configuration.
      host1(config-policy-list-classifier-group)#exit host1(config-policy-list)#exit host1(config)#
    5. Display the policy list.
      host1#show policy-list routeForMpls
      
                                        Policy Table
                                        ------ -----
      MPLS Policy routeForMpls
         Administrative state: enable
         Reference count:      0
         Classifier control list: *, precedence 200
            mark-exp 2 mask 7
            rate-limit-profile mplsRLP5

    Note: In JunosE releases numbered lower than 11.3.x, when you attached a QoS profile to an interface configured for MPLS on an ES2 10G LM, the egress traffic from the MPLS interface that was classified as non-best-effort traffic was forwarded using the best-effort queue. In higher-numbered releases, when an output policy is specified with a non-best-effort traffic class and applied on an MPLS interface, the correct traffic class is used to classify and forward outgoing packets from the interface. For example, when an output policy is applied on an MPLS interface configured with a non-best-effort class, the outgoing traffic from the interface is correctly categorized according to the defined traffic class and does not use the best-effort queue.

    Published: 2014-08-14