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?
Aaron
I 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.
Similar Messages
-
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 -
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 -
Show mls qos interface statistics equivalent command on Cat6500 SUP720-3B?
Hi all
Is there a command on the SUP720-3B that is similar to the show mls qos interface gi0/x statistics command on the access-layer series switches (3560 etc.)?
I'd like to see the incoming and outgoing DSCP/COS values in number of packets.
Thx :)Hi,
You can use this command:
SUP720#show queueing interface xx
You should be able to see all that information there.
Hope this helps. -
3560 mls qos - output queues counters?
Hi!
I have WS-C3560G-24TS 15.0(2)SE4.
In gi0/10 we received IPTV multicast traffic only.
interface GigabitEthernet0/10
description IPTV
switchport access vlan 929
switchport mode access
switchport nonegotiate
mls qos trust dscp
channel-protocol lacp
channel-group 3 mode active
service-policy input iptv-cos
end
on port input - 350mbit - output 2000 Bit/s!
Queueing strategy: fifo
5 minute input rate 348797000 bits/sec, 32008 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
Then i send command:
clear counters
clear mlq qos int stat
and
sh mls qos int gi0/10 st
after 5-10 seconds i see:
GigabitEthernet0/10 (All statistics are in packets)
dscp: incoming
0 - 4 : 156657 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 : 4 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
cos: incoming
0 - 4 : 156661 0 0 0 0
5 - 7 : 0 0 0
cos: outgoing
0 - 4 : 4 0 0 0 0
5 - 7 : 0 0 0
output queues enqueued:
queue: threshold1 threshold2 threshold3
queue 0: 0 0 0
queue 1: 4 0 0
queue 2: 0 0 0
queue 3: 0 0 112066
output queues dropped:
queue: threshold1 threshold2 threshold3
queue 0: 0 0 0
queue 1: 0 0 0
queue 2: 0 0 0
queue 3: 0 0 0
Policer: Inprofile: 0 OutofProfile: 0
Question!
Why i have 112066 packets in output queue 3, then bitrate output - 5 minute output rate 0 bits/sec, 0 packets/sec and 7 packets output, 576 bytes after clear.I have any time this bitrate.
a few hours later I see:
bm18.lan#sh mls q int gi0/10 st
GigabitEthernet0/10 (All statistics are in packets)
dscp: incoming
0 - 4 : 849303034 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 3517 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 : 45265 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
cos: incoming
0 - 4 : 849324148 0 0 0 0
5 - 7 : 0 0 0
cos: outgoing
0 - 4 : 45265 0 0 0 0
5 - 7 : 0 0 0
output queues enqueued:
queue: threshold1 threshold2 threshold3
queue 0: 0 0 0
queue 1: 45265 0 4071
queue 2: 0 0 0
queue 3: 0 0 605666519
output queues dropped:
queue: threshold1 threshold2 threshold3
queue 0: 0 0 0
queue 1: 0 0 0
queue 2: 0 0 0
queue 3: 0 0 0
Policer: Inprofile: 0 OutofProfile: 0
send:
bm18.lan#sh mls q int gi0/10 st
GigabitEthernet0/10 (All statistics are in packets)
dscp: incoming
0 - 4 : 849303034 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 3517 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 : 45265 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
cos: incoming
0 - 4 : 849324148 0 0 0 0
5 - 7 : 0 0 0
cos: outgoing
0 - 4 : 45265 0 0 0 0
5 - 7 : 0 0 0
output queues enqueued:
queue: threshold1 threshold2 threshold3
queue 0: 0 0 0
queue 1: 45265 0 4071
queue 2: 0 0 0
queue 3: 0 0 605666519
output queues dropped:
queue: threshold1 threshold2 threshold3
queue 0: 0 0 0
queue 1: 0 0 0
queue 2: 0 0 0
queue 3: 0 0 0
Policer: Inprofile: 0 OutofProfile: 0
bm18.lan#
bm18.lan#
bm18.lan#
bm18.lan#
bm18.lan#
bm18.lan#
bm18.lan#
bm18.lan#
bm18.lan#
bm18.lan#
bm18.lan#
bm18.lan#
bm18.lan#
bm18.lan#
bm18.lan#clear mls qos int st
bm18.lan#
bm18.lan#
bm18.lan#clear counters
Clear "show interface" counters on all interfaces [confirm]
bm18.lan#
bm18.lan#
bm18.lan#
bm18.lan#sh mls qos int gi0/10 st
GigabitEthernet0/10 (All statistics are in packets)
dscp: incoming
0 - 4 : 1141981 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 3 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 : 92 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
cos: incoming
0 - 4 : 1142010 0 0 0 0
5 - 7 : 0 0 0
cos: outgoing
0 - 4 : 92 0 0 0 0
5 - 7 : 0 0 0
output queues enqueued:
queue: threshold1 threshold2 threshold3
queue 0: 0 0 0
queue 1: 92 0 5
queue 2: 0 0 0
queue 3: 0 0 810894
output queues dropped:
queue: threshold1 threshold2 threshold3
queue 0: 0 0 0
queue 1: 0 0 0
queue 2: 0 0 0
queue 3: 0 0 0
Policer: Inprofile: 0 OutofProfile: 0
bm18.lan#
bm18.lan#
bm18.lan#sh int gi0/10
GigabitEthernet0/10 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is 0019.e7b1.c68a (bia 0019.e7b1.c68a)
Description: IPTV
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 89/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 1000Mb/s, media type is 10/100/1000BaseTX
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:07, output 00:00:06, output hang never
Last clearing of "show interface" counters 00:00:37
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 351051000 bits/sec, 32219 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
1202212 packets input, 1637377057 bytes, 0 no buffer
Received 1202205 broadcasts (1202205 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 1202205 multicast, 0 pause input
0 input packets with dribble condition detected
83 packets output, 6682 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out
bm18.lan#
bm18.lan#
Queue counter is reset to 0, and after 10-15 seconds I see 810,894 packets, although a sh Int gi0/10 I see only 83 outgoing packet! -
Question about 3750 mls qos map dscp-output-q and cos-output-q
1. If a egress packet has both Cos and Dscp setting, which map should this packet used to put into queue?
2. The 3750 is doing ip route. After the packet is routed, will the packet keep the DSCP and COS? Or it will just keep the DSCP and using the dscp-cos map to create a new COS.Apologies for the confusion with the terminalogy.
The question is where you have configured the trust boundaries, do you necessarily trust the DSCP value prior to being routed across your network?
Therefore, although you have explicity trusted the DSCP value, do you still trust the value at the remote peer.
For example, you connect into an MPLS with QoS enabled, you know that the values you are trusting are correct within your network, however at the remote peer/branch they could be remarked by the provider. Therefore do you 'believe' the values, or do you simply not trust them and then reclassify on ingress.
Regards
Allan.
Hope this makes sense.. -
3750 - mls qos queue-set output threshold
In the IOS command, http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/release/12.2_44_se/command/reference/cli1.html#wp2144505. The drop-threshold1 and 2 is in the range from 1 3200%. Can somebody elaborate on the 3200%. How do they determine that number and what that number means to my threshold? Thanks
The drop threshold should be lower than the shutdown threshold (if configured) and should be based on the maximum
amount of PDUs you expect to receive on a port and on the CPU utilization during peaks hours. These values usually determine what is a normal peak condition and therefore what could be an abnormal peak condition. Then you can set the threshold between the two to avoid excessive spikes of PDUs on a port -
Cat. 3750 QoS Queue statistics
Hi all:
Does anyone know a way to see input and output queue statistics like occupation, number of frames discarded due to threshold reached etc ... on a Cat 3750
May be there exists a MIB...
Best regs.the command "show mls qos interface" should help.
check out the following link for the command reference :
http://www.cisco.com/en/US/products/hw/switches/ps5023/products_command_reference_chapter09186a008017f8ed.html#2418190 -
4500 Sup7E Show QoS packet statistics
Hi,
I am trying to identify what QoS marked packets are hitting an interface on my 4500E
Previously with the likes of the 2900 / 3500 I could collect the below information which was a great insight into the packets going through the interface. Is there anything like this for the 4500E on a Sup7? I've not been able to find anything.so far.
xxx-C2960S-1#sh mls qos interface gi 1/0/7 statistics
GigabitEthernet1/0/7 (All statistics are in packets)
dscp: incoming
0 - 4 : 1302269597 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 5423748 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 : 468742 0 0 0 2
5 - 9 : 0 0 0 0 0
10 - 14 : 0 0 0 0 0
15 - 19 : 0 0 0 88 0
20 - 24 : 0 0 0 0 0
25 - 29 : 0 1 0 0 0
30 - 34 : 0 0 0 0 0
35 - 39 : 0 0 0 0 0
40 - 44 : 712552 0 0 0 0
45 - 49 : 0 103878 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 : 1308766828 0 0 0 0
5 - 7 : 0 0 0
cos: outgoing
0 - 4 : 798470028 5273 27854 4668 26113
5 - 7 : 1528536 3100 6624488
output queues enqueued:
queue: threshold1 threshold2 threshold3
queue 0: 1524413 0 0
queue 1: 804613095 1111802 6650008
queue 2: 89 0 0
queue 3: 0 0 0
output queues dropped:
queue: threshold1 threshold2 threshold3
queue 0: 706 0 0
queue 1: 4426 0 0
queue 2: 0 0 0
queue 3: 0 0 0
Policer: Inprofile: 0 OutofProfile: 0
xxxx-C2960S-1#Hi,
I believe 4500E uses MQC style. if you have a policy map attached to the interface, you could use
sh policy-map interface <> <direction>
Hope this helps and Kindly rate all helpful posts.
Thanks,
M -
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.. -
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 -
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? -
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.. -
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. -
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
Maybe you are looking for
-
Other types of payments processing.
I know Paypal don't support e-check payments unless the customer have an account with them to transfer funds. There is any way ACH Direct will be supported? They do process payments via Credit Cards or E-check. Also i tried to setup the form to do
-
JPG exported from Photoshop looks different in Dreamweaver
Hello everyone. I've checked the FAQ section on this forum, and I read the "Save For Web" posting, but that doesn't seem to have answered my question. When I "Save For Web" in Photoshop, and import the resulting photo into Dreamweaver - which is supp
-
What is the meaning of APPROVE,SIGNOFF in Hyperion Planning
Hi Gurus, Please elaborate the difference between APPROVE and SIGNOFF in Hyperion Planning. Your efforts are highly appreciated. Thanks and Regards JYothi.
-
RFC Indentification in R/3 from web dynpro
hi experts, Could u tell me Wether there is any system variable SY-* or any function in sapr/3.so that we can easily know that which model from web dynpro means wether it is rfc or web service model? thanx in advance. regards, pp
-
Flash 10.1 unstable in Safari 5
Five crash reports were automatically generated to Apple today, all of them pointing to the latest version of Shockwave Flash as the cause. Chrome and Firefox are playing nice. No problems at all. Is the latest Flash version causing anyone else crash