Step
13.
Create a policy and
enter policy view.
14.
Associate the class with
the traffic behavior in the
QoS policy.
15.
Return to system view.
16.
Apply the QoS policy.
Display the priority
17.
marking configuration.
The following table shows the support for priority marking actions in the inbound and outbound
directions.
Table 4 Support for priority marking actions in the inbound and outbound directions
Action
802.1p priority marking
Drop precedence marking
DSCP marking
IP precedence marking
Local precedence marking
Local QoS ID marking
Local precedence re-marking configuration
example
Network requirements
As shown in
The network is described as follows:
Host A and Host B are connected to GigabitEthernet 1/0/1 of Device.
•
The data server, mail server, and file server are connected to GigabitEthernet 1/0/2 of Device.
•
Configure priority marking on Device to satisfy the following requirements:
Traffic source
Host A, B
Host A, B
Host A, B
Command
qos policy policy-name
classifier tcl-name behavior behavior-name
quit
•
Applying the QoS policy to an interface
•
Applying the QoS policy to online users
•
Applying the QoS policy to a VLAN
•
Applying the QoS policy globally
display traffic behavior user-defined
[ behavior-name ] [ | { begin | exclude |
include } regular-expression ]
Figure
19, the company's enterprise network interconnects hosts with servers through Device.
Destination
Data server
Mail server
File server
inbound
Yes
Yes
Yes
Yes
Yes
Yes
55
Remarks
N/A
N/A
N/A
Choose one application
destination as needed.
Optional.
Available in any view
outbound
Yes
No
Yes
Yes
No
Yes
Processing priority
High
Medium
Low