The following behavior is supported with use of network IP interface QoS policies for LDP, segment routing (SR), and RSVP (with fast reroute (FRR) or penultimate hop popping (PHP)) MPLS LSPs:
The mpls-lsp-exp-profile-map policy allows you to specify the profile mapping and FC mapping independently. The FC to use is always taken from the network policy using the EXP-to-FC mapping configured in the network policy. The EXP-to-profile mapping defined in the mpls-lsp-exp-profile-map policy associated with the network QoS policy is used. Each IP interface can define a unique network policy for use, and each network policy uses a different MPLS LSP EXP-to-FC mapping. If adequate network classification resources are available, this mapping allows the use of more than 32 distinct network policies.
MPLS transport tunnels that are set up using LDP and segment routing use a global mpls-lsp-exp-profile-map policy. Although the system assigns a default mpls-lsp-exp-profile-map policy, the user can change the default and specify the global policy to use.
Use the mpls-lsp-exp-profile-map policy to assign profile values based on the MPLS EXP bits for MPLS packets received over different IP interfaces. This is particularly useful for RSVP LSPs with FRR 1:1 configurations.
For LDP LSPs or when using the FRR facility, Nokia recommends that a single mpls-lsp-exp-profile-map policy should be used for all IP interfaces. If PHP is enabled, the egress LER receives only VC-labeled packets and the global mpls-lsp-exp-profile-map policy is used for profile mapping. Therefore, when PHP is enabled, a single mpls-lsp-exp-profile-map policy should be used for all IP interfaces to get consistent profile treatment.
If traffic is received on a transport tunnel set up using RSVP LSP, LDP or SR with an identical EXP bit value, the system provides the same QoS treatment to the MPLS traffic. The FC and meter from the network QoS policy are used for all MPLS traffic received on an IP interface, regardless of whether it is LDP or RSVP LSP. The profile value assigned depends on the configuration. If the user needs similar profile mapping for MPLS traffic received across all transport tunnels, a single mpls-lsp-exp-profile-map must be used for all IP interfaces and for the global mpls-lsp-exp-profile-map.