09-01-2021 05:52 AM
Hi Community,
I am in desperate need of direction/assistance. In trying to achieve my aim, I keep going around in circles, not getting any closer.
I have a Catalyst 3850 with several VLAN Trunk Ports with multiple VLANs on each.
I need to apply shaping to the egress of each VLAN for two traffic classes: Voice and a single Data class
I wish to apply a guaranteed non buffered queue for the Voice and
A Shape Average queue for the data class
Each time I try a config I get the following error notification:
% Queuing actions supported only with dscp/cos/qos-group/precedence based classification!!!
I assume I am omitting a step but am lost.
Are there any step by step tutorials available that would cover setting up such a Config?
I am desperate for assistance.
Thanks
Craig
09-01-2021 08:27 AM
I don't really "know" a 3850's QoS features, especially regarding shaping. I "know" the earlier 3750 had both an inexact port "shaping" feature, and supported egress queue "shaping", but it also supported only 4 egress queues, one of which could be configured PQ.
I believe [?] the 3850 supports 8 egress queues, of which 1 (maybe 2?) can be PQ. Don't know what, "shaping" it supports. (Its QoS features should be documented in the configuration manual and guide for your IOS version.)
What you might be able to do, is direct all your VLAN VoIP traffic to a single egress PQ and direct VLAN data traffic to up to 7 other queues, which support "shaping" per queue. (They should support relative dequeuing priorities.)
If you identify the IOS being used, version and feature set, I could look over the documentation and, possibly, assist you further.
09-01-2021 01:38 PM
09-01-2021 02:42 PM
From a quick read of the user guide, the 3850 supports 8 egress queues, two of which can be configured as PQs, shaping on egress queues (but on physical ports).
What might work, assuming you don't need more than 8 classes, is to logically (using QoS groups) classify all traffic, VoIP to be directed to your physical (trunk) port's PQ, and up to 7 VLANs into physical (trunk) port queues, each shaped as desired.
09-01-2021 03:21 PM
09-01-2021 04:47 PM
8 per physical port.
09-13-2021 04:34 PM
Hi Joseph,
Thanks for your assistance thus far.
It would seem only 7 Queues are allowed per physical interface.
Also, the Catalyst 3850 will only allow the use of the same QoS-Group labels on multiple interfaces e.g.:
If I put the following policy on Int GE1/0/2
policy-map GE1/0/2_Shaping-Out
class Voice
priority level 1 10000
class QoS-Group_1
shape average 45000000
class QoS-Group_2
shape average 45000000
class QoS-Group_3
shape average 45000000
class QoS-Group_4
shape average 90000000
class QoS-Group_5
shape average 45000000
class QoS-Group_6
shape average 90000000
The only policy the switch will accept on a second interface GE1/0/4 is the following, where the same QoS-Goup classes/labels only are accepted, Input Marking policies are identical with the exception of different vlan IDs.
policy-map GE1/0/2_QoS-Groups
class vlan1008
set qos-group 1
class vlan1009
set qos-group 2
class vlan1010
set qos-group 3
class vlan1012
set qos-group 4
class vlan1013
set qos-group 5
class vlan1014
set qos-group 6
policy-map GE1/0/4_QoS-Groups
class vlan1006
set qos-group 1
class vlan1007
set qos-group 2
class vlan1020
set qos-group 3
class vlan1021
set qos-group 4
class vlan1022
set qos-group 4
class vlan1026
set qos-group 5
class vlan1017
set qos-group 6
policy-map GE1/0/4_Shaping-Out
class Voice
priority level 1 10000
class QoS-Group_1
shape average 90000000
class QoS-Group_2
shape average 45000000
class QoS-Group_3
shape average 90000000
class QoS-Group_4
shape average 90000000
class QoS-Group_5
shape average 90000000
class QoS-Group_6
shape average 90000000
Am I doing it correct?
Cheers
09-13-2021 05:29 PM
09-16-2021 08:00 AM
Sorry for the slow response - been working hard the last several days.
What do your class-maps look like and what's the actual ingress interfaces, both physical and logical for this traffic.
09-16-2021 03:29 PM
09-17-2021 08:08 AM
Sorry, still not clear to me. Clarify flow of traffic, i.e. which interfaces are used and in what direction for what kind of traffic.
What has me most confused is ingress and egress policies on same interfaces.
"class-map match-any Voice
match dscp 5"
DSCP 5? Not IPPrec 5 and/or DSCP EF?
09-19-2021 04:28 AM
09-19-2021 06:42 AM
So if g1/0/1 is the egress to the Internet, isn't that the interface you should be shaping on?
If g1/0/2 and g1/0/4 are ingress from access switches, then that would be the place to match and classify on, as you're doing with you ingress policy. (BTW, I've always had trouble getting QoS group to work, correctly, but what you're doing, is, I believe, correct for these ingress classification policies.)
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide