UTStarcom iSpirit 3026 Manual page 141

Switch(policy-map-class 3)# set dscp 40
Set port 2 is untrust port, choose Policy 2：
Switch(port 2)# qos service-policy 2
When QoS untrust port cannot be successfully configured, for ACL group 2 and group 3 have
the same ACL regulation.
●
Following command under PORT RANGE mode clear out QoS configuration of the
port：
no qos
●
Port 2 and 3 originally were configured as untrust port, choose P olic y 2 as its policy,
and now clear out the QoS configuration of the port：
Switch(port 2-3)# no qos
Switch(port 2-3)# show qos
Notes：
Each port can be only configured as one of the Trust COS, Trust IP_Precedence, Trust DSCP,
and untrust port, only one QoS policy can be chosen if it configured as untrust port.
One port can be configured with QoS untrust port at the same time with ACL filtration, but ACK
filtration must be configured firstly and then configure with QoS untrust port. ACL filtration will be
failed if QoS untrust port has been configured, so QoS configuration should be deleted firstly,
and then configure with ACL filtration. ACL regulation of "permit" action will be written into FFP if
one port has been configured as QoS untrust port, but ACL regulation of "deny " action cannot
be written into FFP, i.e. ACL regulation of "deny " action does not carry out with QoS for data
flow.
If there are two or mre classes with the same matched value in one QoS policy, the first matched
value carres out QoS, but instead of following matched value. The other COS class has the
same COS value of 5 to match if one COS class has a matched COS value as 5, the first
configured COS value of 5 will carry out QoS. It is suggested that users should not repeatedly
configure matched value.
7. Configure QoS Scheduling
iSpirit 3026 provides the same QoS scheduling for all ports output, iSpirit 3026 switch supports 3
kinds of scheduling ways: SPQ, RR, and WRR. For WRR, every PRI should be with one weight,
and default weight of queue 1 to 4 seperately is 1, 2, 3, and 4. You may configure the weight of