Configuring Mpls Priority Marking - HP MSR4080 Configuration Manual

Step
2. Enter interface view.
3. Configure an MPLS CAR
policy for the interface.
The action argument for MPLS can be:
remark-mpls-exp-continue new-exp: Sets the EXP value to new-exp and continues to process the
•
packet using the next CAR policy. The new-exp is in the range of 0 to 7.
remark-mpls-exp-pass new-exp: Sets the EXP value to new-exp and permits the packet to pass
•
through. The new-exp is in the range of 0 to 7.

Configuring MPLS priority marking

In an MPLS network, you can adjust the priority of an MPLS traffic flow by marking its EXP value. For more
information about priority marking, see "Configuring priority marking."
To configure the MPLS priority marking action for an MPLS traffic class:
Step
1. Enter system view.
2. Create a traffic class and
enter traffic class view.
3. Configure match criteria for
the traffic class.
4. Return to system view.
5. Create a traffic behavior and
enter traffic behavior view.
6. Configure an EXP marking
action in the traffic behavior.
7. Return to system view.
8. Create a QoS policy and
enter QoS policy view.
9. Associate the traffic class with
the traffic behavior in the QoS
policy.
10. Return to system view.
Command
interface interface-type
interface-number
qos car { inbound | outbound }
{ any | acl [ ipv6 ] acl-number } cir
committed-information-rate [ cbs
committed-burst-size [ ebs
excess-burst-size ] ] [ pir
peak-information-rate ] [ green
action | red action | yellow
action ] *
Command
system-view
traffic classifier classifier-name
[ operator { and | or } ]
if-match [ not ] mpls-exp
exp-value&<1-8>
quit
traffic behavior behavior-name
remark mpls-exp exp-value
quit
qos policy policy-name
classifier classifier-name behavior
behavior-name
quit
98
Remarks
N/A
By default, no CAR policy is
configured for an interface.
Remarks
N/A
By default, no traffic class is
created.
By default, no match criteria are
configured.
The match criteria apply only to
MPLS packets.
N/A
By default, no traffic behavior is
created.
By default, no EXP marking action
is configured.
N/A
By default, no QoS policy is
created.
By default, no traffic behavior is
associated with a traffic class.
N/A