Alcatel-Lucent 7210 SAS M OS Quality Of Service Manual page 146

Network QoS Policy Commands
Note: For LDP LSP traffic, the system always uses the global mpls-lsp-exp-profile-map policy.
For RSVP LSP traffic, system uses the mpls-lsp-exp-profile-map policy associated with the
network policy. It is highly recommended to use a single mpls-lsp-exp-profile-map policy for all
the network policies when FRR facility is in use for consistent QoS treatment.
The no form of the command assigns the default policy.
policy-id — The policy-id uniquely identifies the policy on the 7210 SAS.
Parameters
Values
ldp_local_fc_enable
Syntax ldp-local-fc-enable
no ldp-local-fc-enable
Context config>qos
This command determines the system QoS behavior for network IP interfaces for MPLS traffic.
Description
The no form of the command allows for backward compatibility with prior releases. With the no
form, the system continues to operate with release 3.0 (or before) network QoS behavior. The
following restrictions apply when operating with no form of the command:
•
•
•
Page 154
1 — 65535
For LDP LSP traffic, the system uses a single policy (default network policy 1) to assign
the FC & profile to the packet. User cannot modify the EXP bits to FC mapping defined in
the default policy. Using MPLS EXP bits received in the packet to match the EXP bits
configured in the network policy, the policer to use is known. Thus, the system in effect
supports only a single system-defined classification policy for all IP interfaces for LDP
LSPs though policers with different rates can be used. It does not allow for the flexibility
to use different classification policy on different IP interfaces for LDP LSP traffic.
When using only LDP LSPs, user needs to be aware that the LSP EXP bits to FC
classification specified in the global policy is used by the system and not the classification
map specified in the network qos policy. Only the meter/policer is used from the network
qos policy. It does not cause any issues when only LDP is in use, though the way the
policies have been defined currently, its usage is not intuitive to user and can potentially
result in confusion.
There are only 32 unique hardware resources available to map the MPLS EXP bits to
profile values. Hence, in release 3.0, only 32 unique network policies could be associated
with IP interfaces, though the platform supports more number of IP interfaces. In other
words, in release 3.0, multiple IP interfaces needed to share network policies. Though it is
sufficient and meets most of the network deployment scenarios, some of the IP interfaces
need to share a single network policy. IP interfaces that share the policy will use the same
EXP bits to FC mapping.
7210 SAS M OS Quality of Service Guide