QoS - Hardware Queue
Hello people!
Got a quick Q on QoS.
What is the difference between txload and tx-ring, and is txload = hardware queue?
I want to find out the limit of the hardware queue on our sw6506 but I'm having no luck
try to use command sh controllers int g1/1 - nothing referring to tx-ring
I'm trying to check if there's any congestion - sh int g1/1 - not sure what to look at!
Any one got ideas?
=[
Andy-
I'm no expert on QoS, I only get to play with on occasion and I took the class a few years ago. I do believe I can answer your questions though.
1. That is correct, if the Tx ring is not full the router will use the default queueing mechanism to transfer packets.
2. I realize this is an example, but here it would be best to set the links speed to 100MB. Hardly realistic I know. You would need to police the traffic and possibly shape it.
3. It's up to you. You can drop them, create a burst and forward them, remark them, there are a bunch of options you can do.
An excellent resource for QoS is the SRND. Actually the QoS class offered by GK uses the SRND for the training manual. You can find it here-
http://www.cisco.com/en/US/docs/solutions/Enterprise/WAN_and_MAN/QoS_SRND/QoS-SRND-Book.html
Hope that helps.
Similar Messages
-
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! -
Hi, i have a phone thats no working fine, it unregister all the time from the sip server.
The port connected to the phone has output queues dropped on queue 1. ¿That's normal? ¿What could be the cause that there drop packet?
Thanks!
I have this configuration for Qos on the switch port:
interface FastEthernet0/15
switchport mode access
switchport voice vlan 15
priority-queue out
mls qos trust cos
spanning-tree portfast
sh mls qos int fa0/15 st
FastEthernet0/15 (All statistics are in packets)
dscp: incoming
0 - 4 : 184994 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 2298420 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 4806226 0 16934 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 : 8134930 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 : 861 0 0 0 0
45 - 49 : 0 0 0 5 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 : 875001 0 0 0 0
5 - 7 : 6544104 0 0
cos: outgoing
0 - 4 : 8781009 3 6 1 2
5 - 7 : 275463 5 17983
output queues enqueued:
queue: threshold1 threshold2 threshold3
queue 0: 292615 0 0
queue 1: 8562114 44049 5388502
queue 2: 0 0 0
queue 3: 17982 0 183824
output queues dropped:
queue: threshold1 threshold2 threshold3
queue 0: 0 0 0
queue 1: 5349 0 0
queue 2: 0 0 0
queue 3: 0 0 0
Policer: Inprofile: 0 OutofProfile: 0Martin,
Refer to this link you need to modify your buffers etc. :http://www.cisco.com/c/en/us/support/docs/switches/catalyst-3750-series-switches/116089-technote-switches-output-drops-qos-00.html
-Terry
Please rate all helpful posts -
QOS fair queue on fast ethernet
I started with a company and they have fair queue 64 256 0 configured on fast ethernet. I beleive that fair queue was only meant for WAN links 2mps or less. I have noticed many output drops and thought that it was relate to the fair queueing tail drops. Was I correct by removing the fair queueing and just defaulting to FIFO?
Totally agreed on the simple is the best. Simplify the configuration, remove the unused commmand may also improve the performance. Due to lowe CPU process required.
Moreove, if there is not many tunnel, ipsec, ip accounting, etc. CPU intensive process, then the 3660 should be good enough.
I can't comment why the management purchase new model (but not the high end) to replace 3660. There should be some reasons behind. Don't worry about the new hardware, just try to explore new feature and benefit from the new box that can provide to your company.
Did you checked the CPU loading of the 3660 ? If it is not high (>50%) then it shouldn't be the hardware problem.
Hope this helps. -
Cisco 7600 Series Ethernet Services cards types & queue values
Hello,
There is different types for the Cisco 7600 Series Ethernet Services cards.
( More expensive cards with high queue values and less expensive cards with
low queue values.)
http://www.cisco.com/en/US/prod/collateral/routers/ps368/data_sheet_c78-549419.html
Hardware queues
ES Plus XT 40G line cards
• 128,000 ingress queues
• 256,000 egress queues
ES Plus XT 20G line cards
*• 64,000 ingress queues*
• 128,000 egress queues
Hierarchical QoS (H-QoS)
http://www.cisco.com/en/US/prod/collateral/routers/ps368/data_sheet_c78-570730.html
Hardware queues
Cisco 7600 Series ES Plus Transport 40G and 20G Line Cards
*Supporting up to 16 level 4 queues per physical port*
Hierarchical QoS (H-QoS)
Low queue cards have got only 4 queues per physical port. High queue cards
have got minimum 64.000 queue. This is very huge difference. In what kind
of scenario do we have to use the High queue cards ? Could you give some
examples please ? Kind Regards.
BurakHI Burak,
Each time you configure a class with bandwidth allocation or shaping,.. a queue will be used so if you use such card to provide QoS for a lot of subscribers sharing the same interface, you will need a lot of them !!
HTH
Laurent. -
I am working on my masters project and have simulated a network which is a an integration of cellular and ad hoc i.e. nodes have the ability to talk amongst themselves and base station. The overall delay and quality of service is very poor from the statistics. (mainly delay). I need to know if there is a QoS algorithm that I can use in my simulation to improve QoS. I am using OPNET for my simulations. I was thinking of parameters such as Delay, BER and a priority bit depending on class of traffic.
The QoS systems in Cisco´s devices are more hardware dependent than the Universities queries theory ( Erlangs ...). This is a big question that I wondering since I learn the Cisco´s Queues functions (RED ...) so if you want to properly study for QoS and queues you have to know how the Cisco´s hardware treat the traffic inside ( ASICs... ). This is my opinion after considering it for some time.
-
MPLS QoS - SUP720BXL GE Port not supporting Strict Priority & Priority %
Hi Sir,
My customer have few C7609s with SUP720 3BXL and running IOS image s72033-advipservicesk9_wan-mz.122-18.SXF6.bin within the MPLS network.
What I experienced is that I can't configured the built-in GE port of the SUP720 for Strict Priority & Priority Percent QoS.
Is there anyone outside there know what is the equivalent or alternative to above mentioned two QoS features ? This is mainly to priortize the voice traffic.
Thanks in advance.
Ray.The below has been recommended for a customer using 7600 in the
Core with GiGs as normal core facing links.
The implementation goes as below:
i) Enabling the MLS on the 7600 chassis.
mls qos
ii) Configuring Trust Boundary on all Interfaces.
interface GigabitEthernet1/1
mls qos trust
<--By default the Trust Command trusts the incoming DSCP/TOS.
When the ports are configured with the Trust Boundary as given above,
all incoming packets are mapped into Initial Internal DSCP values.
These values are used purely as a reference MAP for Internal QOS
processing on the 7600.
Internal DSCP Output COS
DSCP 0 7 COS 0
DSCP 8 15 COS 1
DSCP 16 23 COS 2
DSCP 24 31 COS 3
DSCP 32 39 COS 4
DSCP 40 47 COS 5
DSCP 48 55 COS 6
DSCP 56 63 COS 7
This deafault mapping can be modified by modifying the DSCP-COS MAP
within the MLS QOS. The the default mapping are as per standards,
and hence it is not recommended to change the mapping.
iii) Directing Traffic into the appropriate Egress Queue.
Once the incoming traffic is mapped to the Initial Internal DSCP,
and the same gets mapped to the Output COS, these values need to
be directed to the appropriate Queues for the desired QOS behavior
on the MPLS EXP packets.
interface x/x
wrr-queue cos-map
priority-queue cos-map
For Eg:
interface gigabitethernet 1/10
wrr-queue cos-map 2 threshold 2 0
wrr-queue cos-map 3 threshold 2 1 2
wrr-queue cos-map 4 threshold 2 3 4
priority-queue cos-map 1 5 6 7
iv) Defining Queue Bandwidth Limits.
After directing the COS to appropriate queues and then assigning them
to appropriate drop threshold values, it is required to define the
bandwidth allocation per queue. This can be done as below.
!<-- To Set minimum assured bandwidth to COS Queue 1,2 & 3
Use the Bandwdith Percentage command as below.
interface GigabitEthernet 1/1
wrr-queue bandwidth percent !
<--Total of Queue Weights should be =100%
To evenly distribute the available bandwidth during congestion for
all the 4 queues, it is required to set the Queue Scheduling Weights
between all the four Queues. This is done by assigning the queues
weights which are used during WRR scheduling.
!<--Set the Queue-Limit Weights of WRR Scheduling as below
interface GigabitEthernet 1/1
wrr-queue queue-limit
priority-queue queue-limit xx
!<--For Example:
interface GigabitEthernet 1/1
wrr-queue queue-limit 25 20 22
priority-queue queue-limit 33
!<-- The example above does a Queue scheduling for Queue 1 for 25% of BW,
Queue 2 for 20% and Queue 3 for 22 % and Priority Queue has 33 %.
To conclude if you want to use the conventional MQC based toggles,
you will need to use FlexWans with WAN ports or OSM's. Where you can
apply the conventional MQC based toggles.
FOr all the LAN ports in 7600 only hardware queues are supported which
can be controlled using MLS, the difference between SUP and Module based
LAN ports is withing the Scheduling alogirthms supported, the Egress and Ingress
buffers, and the number of queues and drop thresholds available.
For Reference use this link:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis7600/software/122sr/swcg/qos.htm
HTH-Cheers,
Swaroop
PS:
Policy Map Class Command Restrictions
PFC QoS does not support these policy map class commands:
?bandwidth
?priority
?queue-limit
?random-detect
?set qos-group
?service-policy -
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 -
I am configuring QOS for some 2960-X's for a new deployment that also has some 2960's. The current 2960's already have auto qos configured. When I configured auto qos voip trust for the 2960-X, I noticed there were not any ingress queues and the all of the numbers for the queues were different. Should this be a concern at all if the switches are trunked together or even if they aren't? I am not that proficient with QOS yet. See below for configs.
Thanks for your help!
From 2960
mls qos map cos-dscp 0 8 16 24 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 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
interface FastEthernet0/2
switchport access vlan 100
switchport mode access
switchport voice vlan 110
srr-queue bandwidth share 10 10 60 20
queue-set 2
priority-queue out
mls qos trust cos
auto qos voip trust
spanning-tree portfast
From 2960-X
mls qos map cos-dscp 0 8 16 24 32 46 48 56
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 400
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
interface GigabitEthernet1/0/1
switchport access vlan 100
switchport mode access
switchport voice vlan 110
srr-queue bandwidth share 1 30 35 5
priority-queue out
mls qos trust cos
auto qos trust
spanning-tree portfastDisclaimer
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
IMO, AutoQoS is always a concern (as are device defaults, without it).
If you're doing to "do" QoS, you should have a policy that serves your service needs, and configurations to support it. AutoQoS might, or might not, be exactly what you need.
If you're not proficient with QoS, on most LANs, you might actually be better off disabling it. -
Hi All,
I have the following scenario that i attached a jpg for !!
My router (RouterB) is connected to my ISPs router (RouterA) All my incoming traffic is through routerA.
After my RouterB i have a PIX515 with inside network and DMZ on the DMZ i have aproxy for internet access.
My connection between routers is only 256kbps, and the internet usage is hogging the line most of the time.
im not interested in other methods of controlling traffic on the proxy etc but rather perform QoS to allocate PRIORITY traffic to the PC1 and to a specific port for an aplication its using, as it becomes dead slow because the FR (256kbps) is hogged by internet traffic.
I do not have access to routerA. i have access to RouterB and PIX515.
My question is:
Router B is not aware of my QoS problems. if i configure QoS to prioritize traffic for PC1 where should i configure it..on routerB or on PIX515 !!! and which interface is the most effective.
I cannot help of thinking that routerA will send traffic to routerB as it is requested by the internet users and the appicaton of PC1. the internet users being more demanging than the PC1 application wont they stil hog up the bandwidth...or when i configure QoS on either of my machines will 'somehow tell' router A to limit its traffic to the proxy ???
with the above i mean that...if i have internet traffic of 200kbps and my application traffic is needing 200 kbps as well..Router A will send the internet traffic and application traffic as it comes on its interfaces (without QoS) and spitting it out the FR link with the same rates...so if it is already sending streams of 200kbps internet traffic. i will still only get 56 kbps for my application, untill the internet traffic dies down ??? (im confused)
please let me know if i am not clear with my request !!!
Thank you,
GeorgeHi jon,
so...in a few words theres nothing that can be done !!!! :( (on the QoS side) ...
so..in order for the QoS to work efficiently it should be configured at the source, where a HIGH BANDWIDTH Input is present (like 100Mbps ) and a smaller bandwidth output interface (2Mbps lets say ) in order for a QUEUE to be created !!! RIGHT !!! ???? so if in the node i want to apply QoS, a QUEUE is not created for traffic towards my machines i can only pray !!! So i would have to talk to the guys on RouterA ??? to apply QoS and prioritize traffic on their router (where a queue is being created !!!)
Did i get this right then ???
Thanks for the help,
George -
when i configure WFQ on an interface, i see a parameter called available bandwidth on the sh interface command which is less than the actual interface bandwidth. And if the traffic exceeds the available bandwidth then will result in output queue drops.
also i found that changing the interface bandwidth to any arbitrary value changes these parameters as well. ( eg. if i ahve a 1 MB interface and i configure the bandwidht statement as 10 MB, the available bandwidth shows around 8MB) . will it mean then, it will not show drops till the traffic exceeds 8 MB.
please make me understand how this is calculated and how does it affect the interface parameters like queuing etc.Hello,
in case you use WFQ configured on an interface, the configured "bandwidth" has no influence on the queueing behaviour. Software based queueing (like WFQ in a router) will be involved, when the hardware queue is full, i.e. when there is more traffic than the interface can send at the time. You can never send more traffic than the layer1 clock rate allows you to send - no matter what you configure with the interface command "bandwidth".
In case you configure CBWFQ through a policy-map, then the configured interface "bandwidth" is used to calculate the bandwidth per class within percent based CBWFQ. Again this will only make sense if you adjust the interface "bandwidth" to the clock rate.
Hope tis helps! Please rate all posts.
Regards, Martin -
After going through the config on one of our switches I noticed some QoS settings that I have no idea what they mean and was wondering if someone could help me understand what these settings mean. Here is the config I found plus the config on one of the ports:
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
vlan internal allocation policy ascending
interface GigabitEthernet0/2
switchport access vlan 40
switchport mode access
switchport voice vlan 100
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
queue-set 2
mls qos trust device cisco-phone
mls qos trust cos
auto qos voip cisco-phone
spanning-tree portfast
Sorry for my ignorance.
Thanks
BrianIn order for networking device to classify traffic, there is certain information within a frame or packet to identify the importance of a frame or packet. CoS, IP Precedence, and DSCP are widely used nowadays.
CoS is in layer 2. IP Precedence and DSCP are in IP header.
In a dot1q tag, there are 3 bit used to identify the importance of the frame. As CoS is 3-bit, the range is between 0 to 7. In normal Cisco VOIP implementation, Cisco IP phones mark CoS 5 on RTP frames. Data traffic is put on native VLAN; so that there is no 802.1q tag on data traffic. By default, Cisco switches put any traffic without 802.1q to be CoS 0 and DSCP 0.
Before DSCP is used, the second byte in IP header is called ToS (Type of Service). It was used to classify IP traffic. Like CoS, IP precedence is 3 bits. Thus, the range for IP precedence is 0 to 7. After a while, we find out that 3 bit is not long enough. We expand IP precedence from 3 bites to 6 bits. It is called DSCP. As DSCP is 6 bits, the range is 0 to 63. Normally, Cisco IP phones mark EF (DSCP value 46) on RTP packets.
QoS on campus switching is different than router. In router, we normally mark and police the traffic just before going to ISP. As a result, you determine what traffic is dropped if the traffic going to ISP exceeds the bandwidth of the circuit.
We normally classify traffic on ports connecting to phones and end devices. To simplify configuration, Cisco switches allow you to trust CoS; so that VOIP traffic is classify with CoS 5. Different switches have difference queues. However, all Cisco switches put CoS 5 or DSCP 46 into priority queue. Once traffic is classified on the access switches, we can simply trust DSCP or CoS on the links between switches. We should use trust DSCP on any layer 3 links. Also, make sure that voice VLAN is not used as native VLAN.
The last question is what happens if a users put a data device on the voice VLAN and construst frames with CoS 5. Here comes extended trust. Switches have to receive CDP on the port before trusting the device on the voice VLAN is a VOIP phone. Not sure if I miss anything. -
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? -
QoS on pvc or virtual interfaces
Suppose you have some pvc configured on a physical interface, or some subinterfaces, point-to-point with an associated pvc.
All the traffic comes out from the same physical interface, so same buffer and hardware queue for all pvcs.
If you send all voip traffic using one pvc, interactive traffic with anether pvc, best-effort traffic with another pvc, how can you reserve bandwidth for different classess ?
I mean, how can you be sure that voice pvc will be dequeued before others pvc ?"If you send all voip traffic using one pvc, interactive traffic with anether pvc, best-effort traffic with another pvc, how can you reserve bandwidth for different classess ? "
If using CBWFQ, first, insure your PVCs' bandwidths don't oversubscribe the physical interface bandwidth. Second, enforce the PVCs bandwidth allowances. (For FR, can be done with shapers, for ATM, can be done by the hardware.)
You might also want dedicated PVCs for real-time traffic so that your CIR is the same as the expected real-time traffic demand.
PS:
I also recall there's a technique to use a special two level queue for FR to insure multiple PVCs real-time traffic always goes first, but I haven't used that feature. -
Egress queueing - priority-queues and queue-sets
If I use the priority-queue out command on an interface 3750 does this treat queue1 as the priority queue?
How can I tell which traffic is sent to each queue by default? Or do I have to specifically define it such as
mls qos srr-queue output dscp-map queue 1 threshold 3 40 41 42 43 44 45 46 47
I really want dscp 40-47 to go priority and the rest to be spread evenly across the other 3 queues as the vast majority of the rest of the traffic will be 0. Is there a command that lets the other 3 queues be best effort?
Also, is this an OK config to use with priority-queueing? I don't actually want a large amount of bandwidth for the priority traffic, just for it to be expidited.
Queueset: 2
Queue : 1 2 3 4
buffers : 10 30 30 30
threshold1: 100 200 100 100
threshold2: 100 200 100 100
reserved : 50 50 50 50
maximum : 400 400 400 400
Any help very gratefully received.
Thanks, JSorry, just bouncing this to see if anyone around today can help :)
Maybe you are looking for
-
Hi All, Following questions restrict to use of functionalities of XMLP: 1. What could be functionality of Delivery manager of XMLP? 2. How could process Delivery manager an user request? 3. Delivery manager is full of Java API's that means apps devel
-
How can I easily set up Mac lab to access windows 2008 server directory user files?
I am wanting to start shifting our school to Apple computers. The problem is that we have already invested significant time and money into windows and we need to run them side-by-side. My initial plan would be to set up an open lab of computers with
-
My Leopard install DVD is getting caught in a loop
I'm having a problem with my Leopard install DVD. I'm running Leopard 10.5.7, and I wanted to use Disk Utility, so I inserted the intall DVD, double clicked the icon, and pressed enter to restart using the disk. What happened next was the computer re
-
I am new to using the Beta version of Safari for Windows. Everything is working fine so far except when I try to play some games in Yahoo there is no sound. The game loads and plays fine, but no sound. I have installed all of the plug-ins as recommen
-
Hi Everyone, I've only been using iTunes for a few weeks, but so far I really like it. But I am having one small problem... I downloaded a couple of albums, and was very happy to see that iTunes groups them according to album in the Library. I would