Traffic filtering configuration example, Network requirements, Configuration procedure – H3C Technologies H3C WX3000E Series Wireless Switches User Manual
Page 50

43
To do…
Use the command…
Remarks
Create a policy and enter policy view
qos policy policy-name
—
Associate the class with the traffic
behavior in the QoS policy
classifier tcl-name behavior
behavior-name
—
Return to system view
quit
—
Apply the QoS
policy
To an interface
Applying the QoS policy to an
interface
—
To online users
Applying the QoS policy to online
users
—
To a VLAN
Applying the QoS policy to a VLAN
—
Globally
Applying the QoS policy globally
—
Display the traffic filtering configuration
display traffic behavior user-defined
[ behavior-name ] [ | { begin |
exclude | include }
regular-expression ]
Optional
Available in any view
NOTE:
With filter deny configured for a traffic behavior, the other actions (except class-based accounting) in the
traffic behavior do not take effect. Whether traffic filtering can work with class-based accounting depends
on your device model.
Traffic filtering configuration example
Traffic filtering configuration example
Network requirements
As shown in
, Host is connected to GigabitEthernet 1/0/1 of Device.
Configure traffic filtering to filter the packets with source port not being 21 and received on
GigabitEthernet 1/0/1.
Figure 14 Network diagram for traffic filtering configuration
Configuration procedure
# Create advanced ACL 3000, and configure a rule to match packets whose source port number is 21.
<DeviceA> system-view
[DeviceA] acl number 3000
[DeviceA-acl-adv-3000] rule 0 permit tcp source-port eq 21
[DeviceA-acl-adv-3000] quit
# Create a class named classifier_1, and use ACL 3000 as the match criterion in the class.
[DeviceA] traffic classifier classifier_1