NOTE: For a topology-driven LSP, you must configure and apply the classifier list and
policy list manually.
The packets are forwarded to the appropriate fabric queue according to the traffic
class/color combination. On a transit router, when the packet is forwarded out of the
tunnel, the router-generated output policy then sets the EXP bits back according to the
traffic class/color combination. Typically, the effect of the EXP bits to traffic class/color
combination to EXP bits is no change.
On an egress router, where the tunnel terminates, no router-generated output policy is
attached, and the packets pass out of the router subject to any manually configured IP
policy management applied to their traffic class/color combination.
Related Topics See the JunosE Policy Management Configuration Guide for more information about
defining policies.
•
• Configuring MPLS and Differentiated Services on page 303
• Configuring EXP Bits for Differentiated Services on page 304
• Example Differentiated Services Application and Configuration on page 305
• Classifying Traffic for Differentiated Services on page 307
• mark-exp
• mpls classifier-list
• mpls diff-serv phb-id traffic-class
• mpls match exp-bits
• mpls match traffic-class
• mpls policy-list
• mpls policy-statistics
• mpls traffic-class
• tunnel mpls diff-serv phb-id
Configuring Point-to-Multipoint LSPs
To set up a point-to-multipoint LSP, you configure the primary LSP from the ingress
router and the branch LSPs that carry traffic to the egress routers. The configuration of
the primary point-to-multipoint LSP is similar to a signaled LSP. In addition to the
conventional LSP configuration, you specify a path name on the primary LSP and this
same path name on each branch LSP. By default, the branch LSPs are dynamically
signaled by means of CSPF and require no configuration. You can alternatively configure
the branch LSPs as a static path.
317Copyright © 2010, Juniper Networks, Inc.
Chapter 4: Configuring MPLS
To Next Page
Loading...
Need help?
General
