Policy Management and MPLS Topology-Driven LSPs

Most policy management for MPLS is handled automatically by MPLS. However, in the case of both statically configured and signaled mapping between EXP bits and per-hop behavior (PHB), you must manually configure certain policy features for topology-driven LSPs only. See JUNOSe Routing Protocols Configuration Guide, Vol. 2, Chapter 2, Configuring MPLS for more information about and application of this feature.

NOTE: You apply policies to MPLS layer 2 interfaces by using the mpls policy command. See Applying Policy Lists to Interfaces and Profiles.

Statically Configured Mapping

You can specify a policy to be attached to all topology-driven LSPs in a VR. The policy is automatically attached when the LSP is created if the destination matches the access list.

mpls ldp lsp-policy

• Use to specify a policy that is automatically attached to all topology-driven LSPs in a VR when the LSP is created, if the destination matches the access list.
• Use the input keyword to have the policy applied to the incoming LSP (for which a label was advertised) to match on the EXP bits of incoming packets.
• Use the output keyword to have the policy applied to the outgoing LSP (for which a label was received) to set the EXP bits of outgoing packets.
• Example

host1(config)#mpls ldp lsp-policy input ingold access-list xyzcorp

• Use the no version to halt the attachment of the policy to subsequently created topology-driven LSPs.

Signaled Mapping

For signaled mapping between EXP bits and PHB, policies apply the EXP bits matching and setting on a per-LSP basis rather than a per-VR basis. For a topology-driven LSP, you must manually create the policies and specify the association between policies and LSPs.

mpls classifier-list

• Use to create or modify an MPLS classifier control list to match on traffic class/color combination or EXP bits.
• Example

host1(config)#mpls classifier-list be-green traffic-class best-effort color yellow

• Use the no version to remove the classifier control list from the LSP.

mpls ldp lsp-policy

• Use to specify a policy that is automatically attached to the topology-driven LSP when the LSP is created, if the destination matches on the access list.
• Use the input version to have the policy applied to the incoming LSP (for which a label was advertised) to match on the EXP bits of incoming packets.
• Use the output keyword to have the policy applied to the outgoing LSP (for which a label was received) to set the EXP bits of outgoing packets.
• Example

host1(config)#mpls ldp lsp-policy input ingold access-list xyzcorp

• Use the no version to halt the attachment of the policy to subsequently created topology-driven LSPs.