245
Parameters
policy-name: Specifies a QoS policy by its name, a case-sensitive string of 1 to 31 characters.
inbound: Applies the QoS policy to the incoming traffic of an interface, a control plane, or a
management interface control plane.
outbound: Applies the QoS policy to the outgoing traffic of an interface.
Usage guidelines
To successfully apply a QoS policy to an interface, make sure the total bandwidth assigned to AF and
EF queues in the QoS policy is smaller than the available bandwidth of the interface. If you modify
the available bandwidth of the interface to a value smaller the total bandwidth for AF and EF queues,
the applied QoS policy is removed. For a QoS policy to be applied in the inbound direction, the
referenced traffic behaviors cannot be configured with any of the commands queue af, queue ef,
queue wfq, and gts.
When you apply a QoS policy to an interface, follow these guidelines:
You can apply a QoS policy configured with various QoS actions (such as remark, car, gts,
queue af, queue ef, queue wfq, and wred) to common physical interfaces.
An inbound QoS policy cannot contain a GTS action or any of these queuing actions queue ef,
queue af, or queue wfq.
Examples
# Apply the QoS policy named USER1 to the outgoing traffic of GigabitEthernet 0/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 0/1
[Sysname-GigabitEthernet0/1] qos apply policy USER1 outbound
New feature: Configuring MPLS LDP FRR
Configuring MPLS LDP FRR
A link or router failure on a path can cause packet loss until LDP completes LSP establishment on the
new path. LDP FRR enables fast rerouting to minimize the failover time. LDP FRR bases on IP FRR
and is enabled automatically after IP FRR is enabled.