Mirroring traffic to an interface, Configuring a qos policy, Applying a qos policy – H3C Technologies H3C MSR 50 User Manual
Page 191
Step Command
Remarks
By default, no match criterion is
configured in a traffic class.
457.
Configure match criteria.
if-match [ not ] match-criteria
For more information about the traffic classifier and if-match commands, see ACL and QoS Command
Reference.
Mirroring traffic to an interface
Step Command
Remarks
458.
Enter system view.
system-view
N/A
By default, no traffic behavior
exists.
459.
Create a behavior, and enter
behavior view.
For more information about the
traffic behavior command, see
ACL and QoS Command
Reference.
traffic behavior behavior-name
460.
Specify the destination
interface for traffic mirroring.
mirror-to interface interface-type
interface-number
By default, traffic mirroring is not
configured in a traffic behavior.
Configuring a QoS policy
Step Command
Remarks
461.
Enter system view.
system-view
N/A
462.
Create a policy and enter
policy view.
qos policy policy-name
By default, no policy exists.
463.
Associate a class with a traffic
behavior in the QoS policy.
classifier tcl-name behavior
behavior-name
By default, no traffic behavior is
associated with a class.
For more information about the qos policy and classifier behavior commands, see ACL and QoS
Command Reference.
Applying a QoS policy
For more information about applying a QoS policy, see ACL and QoS Configuration Guide.
By applying a QoS policy to a Layer 2 interface, you can mirror the traffic in a specific direction on the
interface. A policy can be applied to multiple interfaces, but in one direction (inbound or outbound) of
an interface, only one policy can be applied.
To apply a QoS policy to a Layer 2 interface:
Step Command
Remarks
464.
Enter system view.
system-view
N/A
178