MLS QOS problems on 3750
When i enable mls qos on 3750 running EMI image the ingress ports should switch to non-trusted and therefore reclassify all DSCP/COS bits to 0.
This is not happening and the COS bits are reamining as set by the IP handsets and pc's.
This does not happen on 3550 or 6500's which i have just tested to verify.
What is the exact version of OS you are using ?
Similar Messages
-
I can't understand dropping algorithm used by WTD on Catalyst 3750.
Giving the following configuration:
Switch(config)# mls qos queue-set output 2 buffers 40 20 20 20
Switch(config)# mls qos queue-set output 2 threshold 2 40 60 100 200
1. What happens if buffer utilization for queue 2 is between drop-threshold1 and drop-threshold2? Are the packets dropped using a specific algorithm as in WRED?
2. What happens if buffer utilization for queue 2 is between drop-threshold2 and maximum threshold? Are the packets dropped using another algorithm?
3. Is it true that with buffer utilization above maximum threshold all packets are dropped?
Thanks
StefanoParesh,
thanks a lot for your suggestions!
Anyway I still have some doubt related to WTD thresholds. The sintax is the following:
mls qos queue-set output qset-id threshold queue-id drop-threshold1 drop-threshold2 reserved-threshold maximum-threshold
For drop-threshold1 and drop-threshold2 the range is 1 to 400 percent. For reserved-threshold the range is 1 to 100 percent.
By default, drop-threshold1 and drop-threshold2 for queues 1, 3, and 4 are set to 100
percent. Drop-threshold1 and drop-threshold2 for queue 2 are set to 50 percent. The reserved
thresholds for queues 1, 3, and 4 are set to 50 percent. The reserved
threshold for queue 2 is set to 100 percent. The maximum thresholds for
all queues are set to 400 percent.
With these default settings, queue 2 has drop-threshold1 and drop-threshold2 set to 50 percent and reserved threshold set to 100 percent.
The problem is that drop-thresolds are percentage values related to the ENTIRE buffer, reserved threshold is related to the specific queue's buffer.
So with default settings (1/4 of total buffer for each queue) reserved threshold seems to be HIGHER than drop-thresolds!!!
reserved threshold = 1/4 total buffer
drop thresholds = 50% over 400% total buffer = 1/8 total buffer
Maybe there's something missing...
Thanks
Stefano -
QOS problem (multicast) with 3750
Hi,
I need help to solve following problem.
I have setup qos in our 3750, see below.
Unicast traffic is handle correct, However with multicast streams the router set the dscp to 0
Has somebody any idea what is missing?
Too old sw? Cisco IOS Software, C3750 Software (C3750-ADVIPSERVICESK9-M), Version 12.2(35)SE,
Regards Niklas
ip multicast-routing distributed
ip multicast multipath
mls qos srr-queue input priority-queue 1 bandwidth 10
mls qos srr-queue input dscp-map queue 1 threshold 1 46
mls qos srr-queue input dscp-map queue 2 threshold 1 11 24 30 48
mls qos srr-queue output dscp-map queue 1 threshold 1 48
mls qos srr-queue output dscp-map queue 2 threshold 1 46
mls qos srr-queue output dscp-map queue 3 threshold 1 40
mls qos srr-queue output dscp-map queue 4 threshold 1 11 24 30
mls qos
interface GigabitEthernet1/0/22
switchport access vlan 41
switchport mode access
load-interval 30
srr-queue bandwidth share 25 25 25 20
priority-queue out
mls qos trust dscp
interface GigabitEthernet1/0/23
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 40
switchport mode trunk
load-interval 30
srr-queue bandwidth share 25 25 25 20
priority-queue out
mls qos trust dscpHi,
Here comes the printouts:
with mls qos enabled:
cisco-Mcast#sh mls qos interface gigabitEthernet 1/0/22 statistics
GigabitEthernet1/0/22
dscp: incoming
0 - 4 : 0 0 0 0 0
5 - 9 : 0 0 0 0 0
10 - 14 : 0 0 0 0 0
15 - 19 : 0 0 0 0 0
20 - 24 : 0 0 0 0 0
25 - 29 : 0 0 0 0 0
30 - 34 : 0 0 0 0 0
35 - 39 : 0 0 0 0 0
40 - 44 : 0 0 0 0 0
45 - 49 : 0 0 0 0 0
50 - 54 : 0 0 0 0 0
55 - 59 : 0 0 0 0 0
60 - 64 : 0 0 0 0
dscp: outgoing
0 - 4 : 8881981 0 0 0 0
5 - 9 : 0 0 0 0 0
10 - 14 : 0 0 0 0 0
15 - 19 : 0 0 0 0 0
20 - 24 : 0 0 0 0 0
25 - 29 : 0 0 0 0 0
30 - 34 : 0 0 0 0 0
35 - 39 : 0 0 0 0 0
40 - 44 : 0 0 0 0 0
45 - 49 : 0 0 0 307 0
50 - 54 : 0 0 0 0 0
55 - 59 : 0 0 0 0 0
60 - 64 : 0 0 0 0
cos: incoming
0 - 4 : 0 0 0 0 0
5 - 7 : 0 0 0
cos: outgoing
0 - 4 : 8881981 0 0 0 0
5 - 7 : 0 307 0
Policer: Inprofile: 0 OutofProfile: 0
cisco-Mcast#sh mls qos interface gigabitEthernet 1/0/23 statistics
GigabitEthernet1/0/23
dscp: incoming
0 - 4 : 8931330 0 0 0 0
5 - 9 : 0 0 0 0 0
10 - 14 : 0 0 0 0 0
15 - 19 : 0 0 0 0 0
20 - 24 : 0 0 0 0 0
25 - 29 : 0 0 0 0 0
30 - 34 : 0 0 0 0 0
35 - 39 : 0 0 0 0 0
40 - 44 : 0 0 0 0 0
45 - 49 : 0 0 0 202 0
50 - 54 : 0 0 0 0 0
55 - 59 : 0 0 0 0 0
60 - 64 : 0 0 0 0
dscp: outgoing
0 - 4 : 0 0 0 0 0
5 - 9 : 0 0 0 0 0
10 - 14 : 0 0 0 0 0
15 - 19 : 0 0 0 0 0
20 - 24 : 0 0 0 0 0
25 - 29 : 0 0 0 0 0
30 - 34 : 0 0 0 0 0
35 - 39 : 0 0 0 0 0
40 - 44 : 0 0 0 0 0
45 - 49 : 0 0 0 1206 0
50 - 54 : 0 0 0 0 0
55 - 59 : 0 0 0 0 0
60 - 64 : 0 0 0 0
cos: incoming
0 - 4 : 11357772 0 0 0 0
5 - 7 : 0 2 0
cos: outgoing
0 - 4 : 0 0 0 0 0
5 - 7 : 0 1206 2
Policer: Inprofile: 0 OutofProfile: 0
cisco-Mcast#
mls qos disabled:
cisco-Mcast#sh mls qos interface gigabitEthernet 1/0/22 statistics
GigabitEthernet1/0/22
dscp: incoming
0 - 4 : 0 0 0 0 0
5 - 9 : 0 0 0 0 0
10 - 14 : 0 0 0 0 0
15 - 19 : 0 0 0 0 0
20 - 24 : 0 0 0 0 0
25 - 29 : 0 0 0 0 0
30 - 34 : 0 0 0 0 0
35 - 39 : 0 0 0 0 0
40 - 44 : 0 0 0 0 0
45 - 49 : 0 0 0 0 0
50 - 54 : 0 0 0 0 0
55 - 59 : 0 0 0 0 0
60 - 64 : 0 0 0 0
dscp: outgoing
0 - 4 : 0 0 0 0 0
5 - 9 : 0 0 0 0 0
10 - 14 : 0 0 0 0 0
15 - 19 : 0 0 0 0 0
20 - 24 : 0 0 0 0 0
25 - 29 : 0 0 0 0 0
30 - 34 : 0 0 7371 0 0
35 - 39 : 0 0 0 0 0
40 - 44 : 0 0 0 0 0
45 - 49 : 0 0 0 0 0
50 - 54 : 0 0 0 0 0
55 - 59 : 0 0 0 0 0
60 - 64 : 0 0 0 0
cos: incoming
0 - 4 : 0 0 0 0 0
5 - 7 : 0 0 0
cos: outgoing
0 - 4 : 7371 0 0 0 0
5 - 7 : 0 0 0
Policer: Inprofile: 0 OutofProfile: 0
cisco-Mcast#sh mls qos interface gigabitEthernet 1/0/23 statistics
GigabitEthernet1/0/23
dscp: incoming
0 - 4 : 0 0 0 0 0
5 - 9 : 0 0 0 0 0
10 - 14 : 0 0 0 0 0
15 - 19 : 0 0 0 0 0
20 - 24 : 0 0 0 0 0
25 - 29 : 0 0 0 0 0
30 - 34 : 0 0 23281 0 0
35 - 39 : 0 0 0 0 0
40 - 44 : 0 0 0 0 0
45 - 49 : 0 0 0 0 0
50 - 54 : 0 0 0 0 0
55 - 59 : 0 0 0 0 0
60 - 64 : 0 0 0 0
dscp: outgoing
0 - 4 : 0 0 0 0 0
5 - 9 : 0 0 0 0 0
10 - 14 : 0 0 0 0 0
15 - 19 : 0 0 0 0 0
20 - 24 : 0 0 0 0 0
25 - 29 : 0 0 0 0 0
30 - 34 : 0 0 0 0 0
35 - 39 : 0 0 0 0 0
40 - 44 : 0 0 0 0 0
45 - 49 : 0 0 0 2 0
50 - 54 : 0 0 0 0 0
55 - 59 : 0 0 0 0 0
60 - 64 : 0 0 0 0
cos: incoming
0 - 4 : 29272 0 0 0 0
5 - 7 : 0 0 0
cos: outgoing
0 - 4 : 0 0 0 0 0
5 - 7 : 0 2 0
Policer: Inprofile: 0 OutofProfile: 0
cisco-Mcast#
BR Niklas -
3750 - Show mls qos interface statistics
Hi All,
Sorry if this is posted in the wrong place but can anyone shed any light on the meaning of the five columns given in the output for the following command on a 3750 ?
Show Mls Qos Interface <interface id> Statistics
Many Thanks
ShaunI think that this is my first post, so I hope it will be useful ;-)
It's indeed very strange, I faced the same problem before, so I tried to check older switches, and I was able to find what these values are, for example, if You check the link :
Understanding QoS Policing and Marking on the Catalyst 3550
http://www.cisco.com/en/US/products/hw/switches/ps646/products_tech_note09186a00800feff5.shtml
You will find that these five fields mean:
incoming no_change classified policed dropped (in pkts)
This is a description of the fields in the example:
Incoming—shows how many packets arrive from each direction
NO_change—shows how many packets were trusted (such as QoS level not changed)
Classified—shows how many packets have been assigned this internal DSCP after classification
Policed—shows how many packets were marked down by policing; DSCP shown before markdown.
Dropped—shows how many packets were dropped by policing -
Catalyst 3550 & 3560/3750 command 'show mls qos interface statistics'
On the Catalyst 3550 the command 'show mls qos interface statistics' will show ingress packet (or byte) counts with DSCP values. If you have policers configured then it also shows a count of packets that have been marked down to another DSCP value due to policing or any that have been dropped (obviously 'mls qos monitor dscp x' needs configuring). The same command on the 3560/3750 only shows the ingress & egress DSCP values, there is no column that shows packets (or bytes) that have been policed or dropped. Is there any command to display the same information with the 3560/3750?
Neither platform show counters when the command 'show policy-map interface x/x' is used so this won't work.
Thanks
AndyHi, I believe there is a command on the 3560 'sh mls qos interface policers' may be what you are looking for.
Here is what the command says it outputs:
To display QoS information at the interface level. This information includes:
The configuration of the egress queues and the CoS3-to-egress-queue map
Which interfaces have configured policers
Ingress and egress statistics, which includes the number of bytes that have been dropped -
QoS Questions for 3750 Switches
2x3750 switches are stacked and we are trying to simulate traffic congestion at the UTP ports by using Smartbit 6000C. The objective of the test is to see if the QoS setting works in reality even though we see from Wireshark that the packets are marked with DSCP for voice traffic.
Setup is as follows :
Smartbit<->Avaya IP Phone<->3750 switches<->6509 switch.
Please note that the configuration is set on the 3750 switch port as well as trusted on the Cat 6 switch port. However, when I set to continuous traffic with byte size of 64. Even though its a 100Mbps port, the Avaya IP Phone is already acting weird with hanged symptom. Just side note is that performing "show mls qos inter gi2/0/7 statistic" shows that data and voice traffic are marked on the different priority which seemed correct.
1) Is this the right way to test? If not, what should be the correct way?
2) The port that's connected to Smartbit is configured and it seemed that with the continuous traffic, even other IP Phones are hanged even though I have set Smartbit to hit on the IP address of the CAT6 Switch port. This is not normal right as this is supposed to be unicast traffic. Any idea what could be the reason?Hello Brandon,
I understand your concern and how you want to test, but with the VoIP services you need to understand that there are 2 points (telephones if you want) involved. Your local one, where you might have taken all the necessary steps to protect and prioritize your voice traffic, and the oposite end which also need to have the voice packets prioritized.
Now, from your description, I understand that the packets (voice and data) marked correctly (I believe on C3750), but that's not enough. You need to use CBWFQ together with LLQ to give priority to the Voice traffic over data in case of congestion. Do you have such configuration? Can you show us some excerpt from it?
Next, during the testing, you said that your phone hang-up...where you in a call?
To respond to your questions:
1. The start is ok, but we need more details. You are pushing traffic from Smarbit, this is your local end, but where is the traffic pushed to (remote end), who is receiving the traffic?
2. In theory, you shouldn't have any impact over voice if links are 100Mbit, only if you have such a power packet generator that could fill 100Mbit. What do you mean by "This is not normal right as this is supposed to be unicast traffic"? VoIP is also unicast traffic...
I can see that you are determined to solve this issue, and this is OK as it will help you back with gained knowledge, but I have to warn you that troubleshooting QoS / Voice related problems may be more tricky than you think, as it will involve a strong know-how in these areas.
We will help, but you have to come back with more precise details.
Good luck!
Calin -
Version 03.03.00.XO - MLS QOS not supported
Hi All,
Anyone face the same problem with the following IOS Version?
MLS QOS is not supported in global command.
Switch#sh ver
Cisco IOS Software, IOS-XE Software, Catalyst 4500 L3 Switch Software (cat4500es8-UNIVERSALK9-M), Version 03.03.00.XO RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2013 by Cisco Systems, Inc.
Compiled Wed 14-Aug-13 07:26 by prod_rel_team
Cisco IOS-XE software, Copyright (c) 2005-2013 by cisco Systems, Inc.
All rights reserved. Certain components of Cisco IOS-XE software are
licensed under the GNU General Public License ("GPL") Version 2.0. The
software code licensed under GPL Version 2.0 is free software that comes
with ABSOLUTELY NO WARRANTY. You can redistribute and/or modify such
GPL code under the terms of GPL Version 2.0. For more details, see the
documentation or "License Notice" file accompanying the IOS-XE software,
or the applicable URL provided on the flyer accompanying the IOS-XE
software.
ROM: 15.1(1r)SG2
Switch uptime is 6 minutes
System returned to ROM by power-on
Running default software
Jawa Revision 3, RadTrooper Revision 0x0.0x41, Conan Revision 0x1449
Last reload reason: power-on
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
[email protected].
License Information for 'WS-X45-SUP8-E'
License Level: entservices Type: Permanent
Next reboot license Level: entservices
cisco WS-C4506-E (P5040) processor (revision 2) with 4194304K bytes of physical memory.
Processor board ID FXS1812Q346
P5040 CPU at 2.2GHz, Supervisor 8-E
Last reset from PowerUp
1 Virtual Ethernet interface
20 Ten Gigabit Ethernet interfaces
511K bytes of non-volatile configuration memory.
Configuration register is 0x2101
SWITCH(config)#mls qos
^
% Invalid input detected at '^' marker.
SWITCH(config)#
SWITCH(config)#?
Configure commands:
aaa Authentication, Authorization and Accounting.
access-list Add an access list entry
access-session Access Sesion Global Configuration Commands
agent-server Modify DNS server properties
alias Create command alias
ancp Configure ANCP
archive Archive the configuration
arp Set a static ARP entry
async-bootp Modify system bootp parameters
audit Router Audit
authentication Auth Manager Global Configuration Commands
auto Configure Automation
banner Define a login banner
beep Configure BEEP (Blocks Extensible Exchange
Protocol)
bfd BFD configuration commands
bfd-template BFD template configuration
boot Modify system boot parameters
bridge Bridge Group.
buffers Adjust system buffer pool parameters
bulkstat Bulkstat Application
call-home Enter call-home configuration mode
cdp Global CDP configuration subcommands
cef Cisco Express Forwarding
cisp Set CISP parameters
class-map Configure CPL Class Map
clns Global CLNS configuration subcommands
clock Configure time-of-day clock
cluster Cluster configuration commands
cns CNS agents
comet-server Configure comet-server properties
config-register Define the configuration register
configuration Configuration access
control-plane Configure control plane services
crypto Encryption module
cts Cisco Trusted Security commands
default Set a command to its defaults
default-value Default character-bits values
define interface range macro definition
device-sensor IOS Sensor Commands
diagnostic Configure diagnostic information
dns-server Modify DNS server properties
dnsix-dmdp Provide DMDP service for DNSIX
dnsix-nat Provide DNSIX service for audit trails
do-exec To run exec commands in config mode
dot1x IEEE 802.1X Global Configuration Commands
downward-compatible-config Generate a configuration compatible with older
software
eap EAP Global Configuration Commands
emm Specify pre-loading of MDF
enable Modify enable password parameters
end Exit from configure mode
energywise EnergyWise Global Configuration Commands
epm EPM Global Configuration Commands
errdisable Error disable
ethernet Ethernet configuration
event Event related configuration commands
exception Exception handling
exit Exit from configure mode
fallback Fallback configuration commands
fhrp Configure First Hop Redundancy Protocols
file Adjust file system parameters
fips FIPS mode after next reload
flow Global Flow configuration subcommands
format Format the output
global-address-family Enter address-family base routing topology mode
help Description of the interactive help system
hostname Set system's network name
hw-module Apply command (e.g. shutdown) to specified
hardware target
hw-module Control of individual components in the system
hw-switch Control of individual components in the switch
id-manager ID Pool Manager
identity Identity Configuration Commands
infra-test Configure end2end properties
interface Select an interface to configure
ip Global IP configuration subcommands
ipc Configure IPC system
ipv6 Global IPv6 configuration commands
isis Global ISIS configuration subcommands
issu no description
key Key management
kron Kron interval Facility
l2 Layer 2
l2protocol-tunnel Tunnel Layer2 protocols
lacp LACP configuration
li-view LI View
license Configure License
line Configure a terminal line
link Enable Link State Tracking feature
lldp Global LLDP configuration subcommands
location Global location configuration commands
logging Modify message logging facilities
login Enable secure login checking
mab MAC Authentication Bypass Global Configuration
Commands
mac Global MAC configuration subcommands
macro Macro configuration
media-proxy Global media proxy configuration
mediatrace Mediatrace Application
memory Configure memory management
metadata Metadata Application
mka MACsec Key Agreement (MKA) configuration
module Module
monitor Monitoring different system events
mvr Enable/Disable MVR on the switch
netconf Configure NETCONF
Thank you.Hi,
QOS implementation has radically changed since the advent of
sup-7 & later
You no longer set mls qos as qos is on the engine by default.
Please see the following links
http://www.cisco.com/c/en/us/products/collateral/switches/catalyst-4500-series-switches/white_paper_c11-539588.html
"Ingress QoS: Default Actions
First and foremost, QoS does not need to be enabled on the Supervisor Engine, it is on by default in compliance with the MQC construct.
When a packet arrives at an interface, there are two options to take into consideration: is there a policy attached or not? If the packet arrives with or without a marking and there is not a policy attached to the interface, packets will flow through the switch untouched. There are no questions as to where the packet came from or if it has a valid marking. If the packet arrives with or without a marking, and a policy is attached to the interface, the packet will only then be subject to the policy classification."
And the config guide
http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst4500/15-1/XE_330SG/configuration/guide/config/qos_mrg.html#wp1461453
Hope this helps
Regards
Alex -
MLS QOS commands not accepted on 3800...what's the alternative?
ging from 3750 to 3800, MLS QOS commands not accepted on 3800...I'd heard that this command was deprecated, how do we translate our QoS statements onto the new platform?
To clarify, our 3750 mls qos statements are as follows:
mls qos map cos-dscp 0 8 16 26 32 46 48 56
mls qos srr-queue input bandwidth 90 10
mls qos srr-queue input threshold 1 8 16
mls qos srr-queue input threshold 2 34 66
mls qos srr-queue input buffers 67 33
mls qos srr-queue input cos-map queue 1 threshold 2 1
mls qos srr-queue input cos-map queue 1 threshold 3 0
mls qos srr-queue input cos-map queue 2 threshold 1 2
mls qos srr-queue input cos-map queue 2 threshold 2 4 6 7
mls qos srr-queue input cos-map queue 2 threshold 3 3 5
mls qos srr-queue input dscp-map queue 1 threshold 2 9 10 11 12 13 14 15
mls qos srr-queue input dscp-map queue 1 threshold 3 0 1 2 3 4 5 6 7
mls qos srr-queue input dscp-map queue 1 threshold 3 32
mls qos srr-queue input dscp-map queue 2 threshold 1 16 17 18 19 20 21 22 23
mls qos srr-queue input dscp-map queue 2 threshold 2 33 34 35 36 37 38 39 48
mls qos srr-queue input dscp-map queue 2 threshold 2 49 50 51 52 53 54 55 56
mls qos srr-queue input dscp-map queue 2 threshold 2 57 58 59 60 61 62 63
mls qos srr-queue input dscp-map queue 2 threshold 3 24 25 26 27 28 29 30 31
mls qos srr-queue input dscp-map queue 2 threshold 3 40 41 42 43 44 45 46 47
mls qos srr-queue output cos-map queue 1 threshold 3 5
mls qos srr-queue output cos-map queue 2 threshold 3 3 6 7
mls qos srr-queue output cos-map queue 3 threshold 3 2 4
mls qos srr-queue output cos-map queue 4 threshold 2 1
mls qos srr-queue output cos-map queue 4 threshold 3 0
mls qos srr-queue output dscp-map queue 1 threshold 3 40 41 42 43 44 45 46 47
mls qos srr-queue output dscp-map queue 2 threshold 3 24 25 26 27 28 29 30 31
mls qos srr-queue output dscp-map queue 2 threshold 3 48 49 50 51 52 53 54 55
mls qos srr-queue output dscp-map queue 2 threshold 3 56 57 58 59 60 61 62 63
mls qos srr-queue output dscp-map queue 3 threshold 3 16 17 18 19 20 21 22 23
mls qos srr-queue output dscp-map queue 3 threshold 3 32 33 34 35 36 37 38 39
mls qos srr-queue output dscp-map queue 4 threshold 1 8
mls qos srr-queue output dscp-map queue 4 threshold 2 9 10 11 12 13 14 15
mls qos srr-queue output dscp-map queue 4 threshold 3 0 1 2 3 4 5 6 7
mls qos queue-set output 1 threshold 1 138 138 92 138
mls qos queue-set output 1 threshold 2 138 138 92 400
mls qos queue-set output 1 threshold 3 36 77 100 318
mls qos queue-set output 1 threshold 4 20 50 67 400
mls qos queue-set output 2 threshold 1 149 149 100 149
mls qos queue-set output 2 threshold 2 118 118 100 235
mls qos queue-set output 2 threshold 3 41 68 100 272
mls qos queue-set output 2 threshold 4 42 72 100 242
mls qos queue-set output 1 buffers 10 10 26 54
mls qos queue-set output 2 buffers 16 6 17 61
mls qos
What would all this translate to on the 3800 platform? -
Good Morning, everyone. I am looking for some clarification with an existing 3750x Switch configuration.
I am reviewing the configuration of my network switches and found the following MLS QoS configuration on one of my switches and a partial of this same config on another switch. Can someone please explain what function, this line of code, is performing; and is it necessary?
mls qos map policed-dscp 0 14 24 30 38 to 8
mls qos map policed-dscp 10 to 12
mls qos map policed-dscp 12 to 14
mls qos map policed-dscp 26 to 28
mls qos map policed-dscp 28 to 30
mls qos map policed-dscp 32 to 34
mls qos map policed-dscp 34 to 36
mls qos map policed-dscp 36 to 38
mls qos map cos-dscp 0 8 16 24 34 46 48 56
mls qos srr-queue input bandwidth 70 30
mls qos srr-queue input threshold 1 80 90
mls qos srr-queue input threshold 2 80 90
mls qos srr-queue input priority-queue 2 bandwidth 30
mls qos srr-queue input dscp-map queue 1 threshold 2 16 24
mls qos srr-queue input dscp-map queue 1 threshold 3 48 56
mls qos srr-queue input dscp-map queue 2 threshold 1 36 38
mls qos srr-queue input dscp-map queue 2 threshold 2 32 34
mls qos srr-queue input dscp-map queue 2 threshold 3 40 46
mls qos srr-queue output cos-map queue 1 threshold 2 4
mls qos srr-queue output cos-map queue 1 threshold 3 5
mls qos srr-queue output cos-map queue 2 threshold 1 2
mls qos srr-queue output cos-map queue 2 threshold 2 3
mls qos srr-queue output cos-map queue 2 threshold 3 6 7
mls qos srr-queue output cos-map queue 3 threshold 3 0
mls qos srr-queue output cos-map queue 4 threshold 3 1
mls qos srr-queue output dscp-map queue 1 threshold 2 32 34
mls qos srr-queue output dscp-map queue 1 threshold 3 40 46
mls qos srr-queue output dscp-map queue 2 threshold 1 18 20 22 26 28 30
mls qos srr-queue output dscp-map queue 2 threshold 2 16 24
mls qos srr-queue output dscp-map queue 2 threshold 3 48 56
mls qos srr-queue output dscp-map queue 3 threshold 3 0
mls qos srr-queue output dscp-map queue 4 threshold 1 8
mls qos srr-queue output dscp-map queue 4 threshold 2 12 14
mls qos srr-queue output dscp-map queue 4 threshold 3 10
mls qos queue-set output 1 threshold 1 100 100 100 100
mls qos queue-set output 1 threshold 2 80 90 100 400
mls qos queue-set output 1 threshold 3 100 100 100 400
mls qos queue-set output 1 threshold 4 90 100 100 400
mls qos queue-set output 1 buffers 15 30 35 20
mls qos
If more information is required for a response, please let me know.
Thank you, E.Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
The function of each command is perhaps best explained by the Command Reference and Software Configuration Guide for your IOS version. If you have a question that's unanswered by those, please post another question. BTW, Cisco also publishes whitepapers that further explain some subjects. There are a couple on 3750 QoS.
Regarding whether a particular command is necessary would depend on what your QoS policy is attempting to accomplish. -
3560 mls qos interface statistics output
Hi
I've seen questions like this before, but never seen a satisfactory answer... I can't find any good documentation anywhere about this command.
If you run it, you get tabular output of some statistics - with no headers to the columns.
The closest thing I've found to it is in this document:
http://www.cisco.com/univercd/cc/td/doc/product/lan/c3550/12113ea1/3550cr/cli2.htm#wp2418191
It shows the fields as: Incoming, No_Change, Classified, Policed and dropped.
I have a switch with a modified cos-dscp map so that cos 5 is marked to dscp 46. This shows normal traffic as in the row titled 0-4 in the 'incoming' column, and cos 5 traffic appears in the 40-44 row and the 'dropped' column... which can't be right.
Anyone know what the columns mean?
AaronI figured this out after looking at it sideways and upside down. Here is part of the output from the command I ran on one of our 3750 switches (copy it and paste it into notepad so the rows stretch back out): 'sh mls qos int f0/35 statistics'
dscp: outgoing
0 - 4 : 63683 0 0 0 0
5 - 9 : 0 0 0 0 0
10 - 14 : 0 0 0 0 0
15 - 19 : 0 0 0 0 0
20 - 24 : 0 0 0 0 81
25 - 29 : 0 0 0 0 0
30 - 34 : 0 0 0 0 13366
35 - 39 : 0 0 0 0 0
40 - 44 : 0 0 0 0 0
45 - 49 : 0 10749 0 13653 0
50 - 54 : 0 0 0 0 0
55 - 59 : 0 0 0 0 0
On the left side X - X are the DSCP values for the five columns of that row. For example, 20 - 24 row has the number 81 in the fith column. That shows that 81 packets with the DSCP value of 24 went out of that port. In row 45 - 49, 10749 packets with DSCP of 46 and 13653 packets with DSCP value of 48 went out that port.
I finally was able to use this table to show that a video conferencing unit was truely generating voice packets with DSCP 46 (EF), video packets with DSCP 34, and call control packets with DSCP 24 (this is COS 3 that is mapped to DSCP 24 in the cos-dscp map entry.)
So to clarify, the five columns have nothing to do with Incoming, No_Change, Classified, Policed and dropped, they represent the number of packets that have the DSCP values as referred to by the far left table.
Hope this helps. -
I'm new to setting up QoS so I would like some input.
I'm setting up QoS on my 3750X:
Cisco IOS Software, C3750E Software (C3750E-UNIVERSALK9-M), Version 15.2(2)E, RELEASE SOFTWARE (fc3)
I enabled Auto QoS on the switch:
mls qos map policed-dscp 0 10 18 24 46 to 8
mls qos map cos-dscp 0 8 16 24 32 46 48 56
mls qos srr-queue input bandwidth 70 30
mls qos srr-queue input threshold 1 80 90
mls qos srr-queue input priority-queue 2 bandwidth 30
mls qos srr-queue input cos-map queue 1 threshold 2 3
mls qos srr-queue input cos-map queue 1 threshold 3 6 7
mls qos srr-queue input cos-map queue 2 threshold 1 4
mls qos srr-queue input dscp-map queue 1 threshold 2 24
mls qos srr-queue input dscp-map queue 1 threshold 3 48 49 50 51 52 53 54 55
mls qos srr-queue input dscp-map queue 1 threshold 3 56 57 58 59 60 61 62 63
mls qos srr-queue input dscp-map queue 2 threshold 3 32 33 40 41 42 43 44 45
mls qos srr-queue input dscp-map queue 2 threshold 3 46 47
mls qos srr-queue output cos-map queue 1 threshold 3 4 5
mls qos srr-queue output cos-map queue 2 threshold 1 2
mls qos srr-queue output cos-map queue 2 threshold 2 3
mls qos srr-queue output cos-map queue 2 threshold 3 6 7
mls qos srr-queue output cos-map queue 3 threshold 3 0
mls qos srr-queue output cos-map queue 4 threshold 3 1
mls qos srr-queue output dscp-map queue 1 threshold 3 32 33 40 41 42 43 44 45
mls qos srr-queue output dscp-map queue 1 threshold 3 46 47
mls qos srr-queue output dscp-map queue 2 threshold 1 16 17 18 19 20 21 22 23
mls qos srr-queue output dscp-map queue 2 threshold 1 26 27 28 29 30 31 34 35
mls qos srr-queue output dscp-map queue 2 threshold 1 36 37 38 39
mls qos srr-queue output dscp-map queue 2 threshold 2 24
mls qos srr-queue output dscp-map queue 2 threshold 3 48 49 50 51 52 53 54 55
mls qos srr-queue output dscp-map queue 2 threshold 3 56 57 58 59 60 61 62 63
mls qos srr-queue output dscp-map queue 3 threshold 3 0 1 2 3 4 5 6 7
mls qos srr-queue output dscp-map queue 4 threshold 1 8 9 11 13 15
mls qos srr-queue output dscp-map queue 4 threshold 2 10 12 14
mls qos queue-set output 1 threshold 1 100 100 50 200
mls qos queue-set output 1 threshold 2 125 125 100 400
mls qos queue-set output 1 threshold 3 100 100 100 3200
mls qos queue-set output 1 threshold 4 60 150 50 200
mls qos queue-set output 1 buffers 15 25 40 20
mls qos
auto qos srnd4
All ports are setup like this:
interface GigabitEthernet1/0/1
switchport mode access
srr-queue bandwidth share 1 30 35 5
priority-queue out
mls qos trust dscp
auto qos trust dscp
The problem is this:
I have an IPTV application that I tag with AF41 (DSCP 34):
policy-map QoS-Ceton-InfiniTV-Policy
class QoS-Ceton-InfiniTV-Data-Class
set dscp af41
But when I'm playing that application back on a client, packets are dropped when I'm also running Remote Desktop tagged with AF21 (DSCP 18).
Temporarily, I solved the problem by changing all ports to queue-set 2:
Queueset: 1
Queue : 1 2 3 4
buffers : 15 25 40 20
threshold1: 100 125 100 60
threshold2: 100 125 100 150
reserved : 50 100 100 50
maximum : 200 400 3200 200
Queueset: 2
Queue : 1 2 3 4
buffers : 25 25 25 25
threshold1: 100 200 100 100
threshold2: 100 200 100 100
reserved : 50 50 50 50
maximum : 400 400 400 400
What I don't get is Auto QoS is suppose to make this easy, isn't it?
How come AF41 packets are dropped for AF21 packets?
Thanks for any input.Even with queue-set 2, I still see drops, just not as many.
GigabitEthernet1/0/27 (All statistics are in packets)
dscp: incoming
0 - 4 : 7324189 0 0 0 0
5 - 9 : 0 0 0 0 0
10 - 14 : 0 0 0 0 0
15 - 19 : 0 0 0 236744 0
20 - 24 : 0 0 0 0 0
25 - 29 : 0 1127 0 0 0
30 - 34 : 0 0 0 0 0
35 - 39 : 0 0 0 0 0
40 - 44 : 0 0 0 0 0
45 - 49 : 0 0 0 0 0
50 - 54 : 0 0 0 0 0
55 - 59 : 0 0 0 0 0
60 - 64 : 0 0 0 0
dscp: outgoing
0 - 4 : 17433393 2 94 0 163
5 - 9 : 0 291 0 1 0
10 - 14 : 30613 0 0 0 0
15 - 19 : 0 3822 0 281615 0
20 - 24 : 0 0 0 0 103072
25 - 29 : 0 11 0 0 0
30 - 34 : 0 0 7605 0 15387535
35 - 39 : 0 0 0 0 0
40 - 44 : 0 0 0 0 0
45 - 49 : 0 0 0 16394 0
50 - 54 : 0 0 0 0 0
55 - 59 : 0 18872 0 0 0
60 - 64 : 0 0 0 0
cos: incoming
0 - 4 : 7564272 0 0 0 0
5 - 7 : 0 0 0
cos: outgoing
0 - 4 : 17467998 30614 285437 103083 15395140
5 - 7 : 7914 16394 209955
output queues enqueued:
queue: threshold1 threshold2 threshold3
queue 0: 0 0 7605
queue 1: 15673244 245425 264513
queue 2: 0 0 17441610
queue 3: 1 30602 0
output queues dropped:
queue: threshold1 threshold2 threshold3
queue 0: 0 0 0
queue 1: 0 0 0
queue 2: 0 0 588
queue 3: 0 0 0
Policer: Inprofile: 0 OutofProfile: 0 -
Cisco 3650 QoS design: "mls QoS" not supported
Dear colleagues,
I am currently testing a Cisco 3650 for various catalogue items. One key feature that we use on almost all our catalogue items, is Quality of Service (QoS).
On the old Cisco 3560 and 3750, we use "mls qos" and related commands. We use numbered ACLs for untrusted QoS policy that sits on the LAN / ingress port. I have raised a TAC case for this issue but is there a tool to help me convert the "mls QoS" design on the old 3560 platform to the new 3650 platform where "mls qos" is not supported?
Many thanks.Hi,
The new 3650 runs IOS-XE and the older Cisco 3560 and 3750 run IOS. So the QOS architecture on the new 3650 is different.
here is the link to the qos config for the 3650:
http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3650/software/release/3se/qos/configuration_guide/b_qos_3se_3650_cg/b_qos_3se_3650_cg_chapter_011.html
HTH -
Hi all,
I wanted to get to know more about QoS and thought that there was no better way than document and understand the output of auto qos.
However I want to verify some things to check that I understand it correctly.
The 2 commands I want to check on are the following:
mls qos queue-set output 1 buffers 15 25 40 20
mls qos queue-set output 1 threshold 4 60 150 50 200
mls qos queue-set output 1 buffers 15 25 40 20, this command divides the port buffer space between the 4 egress queues.
1. Does it always need to add up to 100%? Or if it doesn't, will the remaining percentages be added to the common pool?
mls qos queue-set output 1 threshold 4 60 150 50 200
Are the following statements correct?
2. packets belonging to queue 4 threshold 1, will be dropped when the port buffer for queue 4 is 60% full (60% of 20 buffers = 12 buffers)?
3. packets belonging to queue 4 threshold 2, will be dropped when the port buffer for queue 4 is 150% full (150% of 20 buffers = 30 buffers)?
3b. how does this work? since this are more buffers than reserved or available for the queue? what if no more buffers remain in the common pool?
4. packets belonging to queue 4 threshold 3, will be dropped when the port buffer for queue 4 is 100% full (100% of 20 buffers = 20 buffers)?
5.the queue can steal up to 200% buffers from the common pool, can this ever be reached? since we will be dropping at 60% (th1), 150% (th2) and 100% (th3) so we will max reach 150% and not 200%?Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
#1 It's recommended sum of all four queues buffers equal 100%. I don't know what happens if they they don't.
#2 Yes and no, it's 60% of 20%.
#3 Yes and no, it's 150% of 20%.
#3b If not buffers to borrow from common pool, it will drop.
#4 No, it's 200% of 20%.
#5 Yes, buffers are borrowed are (attempted) borrowed from common pool when reserve buffers are all used (and WTD not reached). Th3 is 200%, not 100% of 20%.
Great document on 3560/3750 buffering: https://supportforums.cisco.com/document/31581/egress-qos -
Enabling MLS QOS on 2960S seems to "throttle" bandwidth when using a specific Mitel 5320 phone. I have a PC behind the Mitel and the performance is way slower. Validated via a speed test. Once I remove the MLS QOS globally, the performance is greatly improved, about doubled. This is causing some issues as users with this particular phone attached with a PC behind the phone are starting to complain. What could be causing this or what settings to overcome this?
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Enabling QoS on a 2960/3560/3750, using defaults, often results in slow transfer performance. This because the default buffer settings often increase drop rates in the newly enabled egress queues. Manual buffer tuning might mitigate. -
Hello,
I have configured a new interface vlan, sometimes it work, sometimes not.
Is there a interface vlan limit on the Cisco 3750?
Here is my configuration:
Backbone, 3750 L3.
vlan 182
interface Vlan182
description USERS_EPFL
ip address 172.16.182.1 255.255.255.0
ip helper-address 172.16.2.4
ip helper-address 172.16.2.5
no ip redirects
no ip unreachables
On Cisco 3750 L2
interface FastEthernet2/0/15
switchport access vlan 182
switchport mode access
no logging event link-status
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
no snmp trap link-status
mls qos trust cos
no mdix auto
auto qos voip trust
spanning-tree portfast
spanning-tree bpduguard enable
When I ping the computer connected to the port 2/0/15, sometime I can reach it, sometime not.
It work with the other vlan (132, 134...). IP is fix.
Many thanks if you have any ideas, I've been testing a long time.
Gael
PS:
More config info:
3750 l2
interface GigabitEthernet1/0/1
description Link to NYLMRO0001
switchport trunk encapsulation dot1q
switchport trunk native vlan 129
switchport mode trunk
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
queue-set 2
mls qos trust cos
auto qos voip trust
channel-group 1 mode on
interface GigabitEthernet1/0/2
description Link to NYLMSW0002
switchport trunk encapsulation dot1q
switchport trunk native vlan 129
switchport mode trunk
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
queue-set 2
mls qos trust cos
auto qos voip trust
channel-group 2 mode onSome more info:
When I say that simetime it work sometime not, it like I plug the connector, then it work (the ping) if I replug, The ping won't work then maybe after a vary lonmg time, it will work again
info about show vlan:
3750 L3
sh vlan
VLAN Name Status Ports
1 default active Gi1/0/6, Gi1/0/10, Gi1/0/11, Gi2/0/6, Gi2/0/10, Gi2/0/11
129 MGMT active
130 SERVER active
132 USERS active
134 IP_TEL active
136 WIFI_DATA active
137 WIFI_IP_TEL active
138 WIFI_GUEST active
140 BATIMENT active
182 USERS_EPFL active
184 IP_PHONES_EPFL active
191 DMZ3 active
1002 fddi-default act/unsup
1003 trcrf-default act/unsup
1004 fddinet-default act/unsup
1005 trbrf-default act/unsup
3750 L2
sh vlan
VLAN Name Status Ports
1 default active Fa1/0/1, Fa1/0/14, Fa1/0/15, Fa1/0/24, Fa1/0/25, Fa1/0/26, Fa1/0/27, Fa1/0/28
Fa1/0/29, Fa1/0/30, Fa1/0/31, Fa1/0/32, Gi1/0/2, Gi1/0/3, Gi1/0/4, Fa2/0/2, Fa2/0/7
Fa2/0/11, Fa2/0/12, Fa2/0/16, Fa2/0/17, Fa2/0/18, Fa2/0/22, Fa2/0/28, Fa2/0/31
Fa2/0/32, Fa2/0/36, Fa2/0/37, Fa2/0/38, Fa2/0/40, Fa2/0/43, Fa2/0/45, Fa2/0/46
Gi2/0/2, Gi2/0/3, Gi2/0/4
129 MGMT active
130 SERVER active Fa1/0/43, Fa1/0/47, Fa1/0/48, Fa2/0/42
132 USERS active Fa1/0/33, Fa1/0/34, Fa1/0/35, Fa1/0/36, Fa1/0/37, Fa1/0/38, Fa1/0/40, Fa1/0/42
Fa1/0/44, Fa1/0/45, Fa1/0/46, Fa2/0/25, Fa2/0/26, Fa2/0/29, Fa2/0/30, Fa2/0/33
Fa2/0/34, Fa2/0/35, Fa2/0/44
134 IP_TEL active
136 WIFI_DATA active
137 WIFI_IP_TEL active
138 WIFI_GUEST active
140 BATIMENT active Fa1/0/39, Fa2/0/41, Fa2/0/47, Fa2/0/48
182 USERS_EPFL active Fa2/0/15, Fa2/0/27
184 IP_PHONES_EPFL active
191 DMZ3 active
1002 fddi-default act/unsup
1003 trcrf-default act/unsup
1004 fddinet-default act/unsup
1005 trbrf-default act/unsup
Maybe you are looking for
-
Trying to install Lightroom 5 with CC but getting error code 5 on initial startup of Lightroom.
Trying to install Lightroom 5 with CC but getting error code 5 on initial startup of Lightroom. Have uninstalled all adobe products including Creative Cloud CC. Followed the instructions on the forum by using the CC Cleaner App for OSX. Have restarte
-
Pls i would like to know if there is any software or application for Nokia asha 201 update ? because sometimes my phone freez and i think it might need an update. thanks
-
Third Party Billing Integration
Are there any guidelines for 3rd party billing integration?
-
Dear Support forums, I've install Desktop Manager ver 7.1 at my laptop with Win7 Enterprise 64-bit, all process went smooth. But when I start the Desktop Manager, all font/ text shown as "SQUARE", can not interpreted at all. Ow, BTW, this was happen
-
Hi Guys I am configuring company iPAD for sales guys and creating a profile using iPhone configuration utility but I am kind of stuck and I don't know how to do that. Try to acheive following if iPad are in company WiFi range it should automatically