MLS QOS on 2960S
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.
Similar Messages
-
Why does mls qos trust dscp dissapear after reboot?
The command takes but after reboot, Invlaid inputs detected show up and "mls qos tust dscp" is gone from every interface.
Happens on both 2960-24PC-S / 2960-48PST-S switches.Hi,
thanks for your reply.
mls qos
interface GigabitEthernet3/34
description *** DATA VLAN 35 - VOICE VLAN 34 ***
switchport
switchport trunk native vlan 36
switchport trunk allowed vlan 34,36
switchport mode trunk
mls qos trust dscp
no cdp enable
spanning-tree portfast trunk
If i don't include the global 'mls qos' command then the voice packets keep the dscp 46 value. If I add the mls qos command this causes the switch to set the dscp values to zero.
Thanks again
ps. there are some other mls commands on the switch... i don't know if these could interfere but they were already on there so i'm reluctant to remove them.. -
Mls qos trust{cos/ip-precedence/dscp} command
Hi every body!
I have few questions
1)
The command " mls qos trust dscp" is only valid on mulilayer switch or it is also valid for layer 2 switch? If layer 2 switch is configured with that command, can it modify the dcsp value based on policy?
2)is the following correct:
switch(config-if) mls qos trust dscp
switch will set the cos value to set default. If the default set is zero, then frame will be processed by best-effort delivery.
But the egress-queue will be decided by dscp value in the packet. A dscp to cos map will be used to drive the cos value and then frame will be placed in the queue that corresponds to cos value.( off course if egress port is configured for trunk)
thanks a lot and I wish America and all of you a happy new year!
thanks a lot!Sarah
1) L2 switches can trust the dscp marking as well. The 2960 is a layer 2 only switch and the default is untrusted but if you then enter
"mls qos trusted" you have a choice of 'cos|dscp|ip-precedence'. The default if no choice is entered is DSCP.
2) If "mls qos trust dscp" is entered then the switch will use the DSCP marking found in the packet. This will then be used as the internal DSCP marking that all switches use. Unless you have a DSCP-DSCP mutation map the value used will be the value received in the packet.
Jon -
Mls qos trust cos vs mls qos cos in cat6k
Hello
I am trying to configure basic qos topology with two 6k connected to each other by the trunk port.
According to the documentation, if I set the mls qos cos value at the interface level I should modify the default cos on it, and all packets leaving incoming to this port, should be marked with the new cos value.
http://www.cisco.com/c/en/us/support/docs/switches/catalyst-6000-series-switches/24055-173.html
Unfortunately, when I set such config, all incoming packets transmitted through this interface was tagged with cos = 0 until I set the "mls qos trust cos" on the same interface.
Does anybody can explain to me this strange behavior?
I would like to mention that both 6k was connected to each other with ws-x6548-GE-TX modules.
Thank you in advance.
Ragards
LukasSarah
1) L2 switches can trust the dscp marking as well. The 2960 is a layer 2 only switch and the default is untrusted but if you then enter
"mls qos trusted" you have a choice of 'cos|dscp|ip-precedence'. The default if no choice is entered is DSCP.
2) If "mls qos trust dscp" is entered then the switch will use the DSCP marking found in the packet. This will then be used as the internal DSCP marking that all switches use. Unless you have a DSCP-DSCP mutation map the value used will be the value received in the packet.
Jon -
Mls qos enabled globally and disabled for only one interface
Hello !
My switch is Cisco IOS Software, C2960X Software (C2960X-UNIVERSALK9-M), Version 15.0(2)EX5, RELEASE SOFTWARE (fc1)
I try to disabled mls qos only for one interface, but when i do it, mls qos is globally disabled. Is it possible to do it ?
XXX#show mls qos
QoS is enabled
QoS ip packet dscp rewrite is enabled
XXX#conf t
Enter configuration commands, one per line. End with CNTL/Z.
XXX(config)#interface gigabitEthernet 1/0/5
XXX(config-if)#no mls qos
XXX(config)#exit
XXX#
XXX#show mls qos
QoS is disabled
QoS ip packet dscp rewrite is enabled
Thanks in advance for your help !!
DenisHi Denis,
You cant disable the QOS on per interface on 2960 devices.
By default, QoS is disabled. When we enable QoS all ports
will be assigned to queue-set 1. We can configure up to two
different queue-sets.
Hence if you remove the qos out of the interface it would be disabled globally as well.
HTH -
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? -
Cisco 3560 switch| mls qos trust dscp question
Hi everybody
Hi everybody .
Please consider the following example:
3560 sw f1/1--------trunk---SW2
3560 sw
f1/1
mls qos trust dscp
3560 is using default cos-dscp map, assume a 3560 receives a frame carrying IP packet on f1/1 with COS 4, what will 3560 switch do?
1) will it use its default cos --dscp map ( cos 4--.dscp 32) and rewrite 32 in dscp field of the packet in the frame and provide PHB for dscp 32 ?
Much appreciated!!
Have a great weekend.Hi
No it will not trust the cos value, because You have configured to trust dcsp. So, the switch will trust the dcsp value in the incoming frame.
/Mikael -
Hello world!
I want to enable qos on a 3560 switch,
So, I put:
Overall setup mode "mls qos"
Question:
is what it is Verily nessaiire to interface configuration mode: "mls qos trust"?
Regards,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
Generally, on many Catalyst switches, once you enable QoS, they will erase an ingress CoS/ToS markings unless your trust it or otherwise (i.e. policy) maintain it.
I.e. the answer to your question is an "it depends"; but unless you want the markings reset to zero, the answer is probably yes (you want to trust). -
Mls qos trust dscp??? is setting my DSCP values to zero!?
Hi,
I was just doing some testing to ensure that the command 'mls qos trust dscp' is working on my 6509 switches before rolling out QoS.
Before adding any configuration I could see using wireshark that traffic from my Avaya 9608 handset was coming through with a DSCP value of 46 (as it is supposed to).
I then added the command 'mls qos' (at global level)
on examining the wireshark output this time, the DSCP value had been set to zero (i.e. it defaulted it to best effort)
I then expected by adding the commmand 'mls qos trust dscp' on the interface the phone is connected to that the DSCP value would would again be left alone?
does anybody know why this is happening?
Many thanks in advance.
AndyHi,
thanks for your reply.
mls qos
interface GigabitEthernet3/34
description *** DATA VLAN 35 - VOICE VLAN 34 ***
switchport
switchport trunk native vlan 36
switchport trunk allowed vlan 34,36
switchport mode trunk
mls qos trust dscp
no cdp enable
spanning-tree portfast trunk
If i don't include the global 'mls qos' command then the voice packets keep the dscp 46 value. If I add the mls qos command this causes the switch to set the dscp values to zero.
Thanks again
ps. there are some other mls commands on the switch... i don't know if these could interfere but they were already on there so i'm reluctant to remove them.. -
Hello, if the command 'mls qos trust xxxxx' is not issued, and qos is turned on for the interface, does this mean the switch will erase all cos and dscp markings received, therefore preventing me from testing packets/frames against these cos/dscp values ?
So if I want to set up class maps, policy maps, and then service policies, it is essential that I:
1. turn on mls qos ?
2. enter a trust statement in order to preserve the cos or dscp values that I want to test against ?
3. now I can test against against cos or dscp values ?
Thanks for clarification.That is correct, when you would use for instance mls qos trust cos. You would need to define you cos<>dscp mappings on the switch and the switch will apply qos accordingly.
So really if you have an ingress switch port and you trust cos or dscp, you can still have egress policies on a port (on the same switch), using these cos or dscp values.
the mls qos trus command is just a way to make it easier to rely on existing cos/dscp values that a phone sends (based on your CUCM configuration,), without the need for you having to configure it explicitly on each access port.
=============================
Please remember to rate useful posts, by clicking on the stars below.
============================= -
"mls qos trust dscp" vs. "mls qos trust cos"
Are these statements correct ?
1. If using QoS profile without setting "wired qos protocol", always use "mls qos trust dscp" on the WLC trunk port
- downstream wmm traffic will be policed down to "?" (this one I'm not sure, is it "not policed" or "policed down to cos 6 for platinum, etc")
2. If using QoS profile with setting "wired qos protocol",
- use "mls qos trust cos" on the WLC trunk port if you want outgoing LWAPP traffic COS/DSCP to reflect QoS profile setting and if you want to rewrite DSCP in the outgoing upstream traffic to QoS profile setting
- use "mls qos trust dscp" on the WLC trunk port if you want LWAPP traffic COS/DSCP to reflect original DSCP setting and if you want to leave DSCP alone in the outgoing upstream traffic
3. With either "mls qos trust cos" or "mls qos trust dscp" on WLC trunk port, downstream wmm traffic will be policed down to "wired qos protocol" setting (What if "wired qos protocol" is not set, will it be policed down to, for example, cos 6 for Platinum?)
4. Always use "mls qos trust dscp" on non-HREAP AP ports
Use "mls qos trust dscp" on HREAP AP ports, if you want to preserve upstream DSCP for locally switched WLANs
Use "mls qos trust cos" on HREAP AP ports, if you want to QoS profile 802.1p to override upstream DSCP for locally switched WLANs
5. Use either "mls qos trust dscp" or "mls qos trust cos" on switch-to-switch trunksAre these statements correct ?
1. If using QoS profile without setting "wired qos protocol", always use "mls qos trust dscp" on the WLC trunk port
- downstream wmm traffic will be policed down to "?" (this one I'm not sure, is it "not policed" or "policed down to cos 6 for platinum, etc")
Ans: Not sure about always. you can use both 'mls qos trust dscp' and 'mls qos trust cos'. Since it is a trunk port the packets will have a cos value (802.1p tag) and hence you can trust cos. Downstream and upstream traffic both are capped to the WLAN max QoS value. for example if Wlan is set to silver, and if a packet comes in at platinum QoS, the AP will cap it to silver in upstream direction. Same holds true for a cos 5 / dscp 46 packet coming in from the wired side.
2. If using QoS profile with setting "wired qos protocol",
- use "mls qos trust cos" on the WLC trunk port if you want outgoing LWAPP traffic COS/DSCP to reflect QoS profile setting and if you want to rewrite DSCP in the outgoing upstream traffic to QoS profile setting
- use "mls qos trust dscp" on the WLC trunk port if you want LWAPP traffic COS/DSCP to reflect original DSCP setting and if you want to leave DSCP alone in the outgoing upstream traffic
Ans:
3. With either "mls qos trust cos" or "mls qos trust dscp" on WLC trunk port, downstream wmm traffic will be policed down to "wired qos protocol" setting (What if "wired qos protocol" is not set, will it be policed down to, for example, cos 6 for Platinum?)
Ans: Traffic in both direction wil always get capped to WLAN max QoS. Untagged (802.1p = 0) traffic will be treated as best effort.
4. Always use "mls qos trust dscp" on non-HREAP AP ports
Use "mls qos trust dscp" on HREAP AP ports, if you want to preserve upstream DSCP for locally switched WLANs
Use "mls qos trust cos" on HREAP AP ports, if you want to QoS profile 802.1p to override upstream DSCP for locally switched WLANs
Ans:
5. Use either "mls qos trust dscp" or "mls qos trust cos" on switch-to-switch trunks
Ans: I think on purely layer 2 switches you can trust dscp, but am not 100% sure. -
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 -
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. -
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
Maybe you are looking for
-
Iphone 3s hardware not supported by Windows xp
I plugged in my wife's iphone 3gs phone to update in Itunes. I got a message from Windows that the hardware driver was not recognized. I was able to get in Itunes and record my device. It started updating. I came back to an error message and now
-
Error in applciation server starting up
HI Folks, i am trying to restart application server (ABAP), and it is giving me below error, can someone please help me phu344gb:p16adm 149> pg dev_disp.new trc file: "dev_disp.new", trc level: 1, release: "701" sysno 18 sid P16 systemid
-
IMac late-2013 not working as external display to t430s with thunderbolt cable
Can anyone confirm wether this actually works? - TP: Bios is at the latest upgrade-level - TP: thunderbolt is enabled in bios - TP: OS is Win7 - I know how to boot in Target Display Mode on the iMac (pressing T during boot - the thunderbolt-log is s
-
Uploading a file to Portal server
Hello all: First question: I'm creating an HTML page that uploads a file to the server using a form like this: When user fills the form and sends the file and error is showed: Application error occurred during request processing. Details: Error [
-
Reuse of context in ACE module
Hi all, just have a question about som reuse of resources in a ACE module context. I don't want to make a new context, and can reuse most of the existing configuration in one of my context. The config is not complex and difficult, but I'm not sure