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

•
Executing the command ldp-use-local-fc-enable, changes the mode of system behavior which
allows more flexibility to the user and removes some of the restrictions listed above. With ldp-use-
local-fc-enable set, the following is possible:
•
•
•
•
Note: User cannot execute the command 'no ldp-use-local-fc-enable' after executing the
command 'ldp-use-local-fc-enable'.
no ldp_fc_local_enable
Default
7210 SAS M OS Quality of Service Guide
If a user receives traffic on RSVP LSP and a LDP LSP with the same value in the EXP
bits and on the same IP interface, then potentially, the system can classify packets received
on a RSVP LSP to one FC and classify packets received on a LDP LSP to another
different FC. This is possible as LDP LSPs use the global network policy for classification
and RSVP LSPs used the network policy associated with the IP interface for classification.
If both of these policies specify the same EXP to FC mapping then there are no issues.
With release 3.0, it is good practice to setup the EXP bits to FC map, to be the same in the
default network policy and user-defined network policy when both LDP and RSVP
protocols are in use. This is required to ensure that all packets received on an IP interface
with a similar value of LSP EXP bit is classified to the same FC and a single policer is
used for all them. This ensures that all MPLS packets received with the same EXP bits
receive the same QoS treatment in the system.
LSPs setup using LDP uses a global mpls-lsp-exp-profile-map policy. By default, the
system assigns a default mpls-lsp-exp-profile-map policy. User has an option to change
the global policy to use. A new policy mpls-lsp-exp-profile-map policy allows the user to
assign different profile value for MPLS EXP bits for MPLS packets received over
different IP interface. This is helpful for use with primarily RSVP LSP with FRR 1:1. For
LDP LSPs or when using FRR facility it is recommended to use a single mpls-lsp-exp-
profile-map policy for all IP interfaces.
The new policies separate the profile mapping and FC mapping. The FC used is always
picked from the network policy. The new policy syntax allows for flexibility and is
intuitive.
Each IP interface can define a unique network policy for it use, each possibly using a
different mapping for MPLS LSP EXP bits to forwarding class (FC). It allows for use of
more than 32 distinct network policies, provided network classification resources are
available for use.
If user receives traffic on RSVP LSP and LDP LSP with the same value in the EXP bits,
the system provides the same QoS treatment. The system always uses the FC and the
meter from the network Qos policy for all MPLS traffic received on an IP interface
irrespective of whether its LDP or RSVP LSP.
Operational Commands
Page 155