QoS - Interface Hold Queue

Hi,
In IOS 12000 router, interface can configure to increase the hold-queue.
Once upgrade to IOX , the command is no longer available.
I am facing the interface input drops, in IOS I can increased the input hold-queue to solve the problem.
But in IOX, no such command available. How can increased the interface hold-queue ?
In IOS:
interface GigabitEthernet2/0/7
hold-queue 1500 in
hold-queue 1500 out

Hi Chon,
I am afraid, but this feature is not yet supported in IOX. I hope it is feasible to somehow shape the traffic before that box.
FYI, we have launched the dedicated IOX forum -
https://supportforums.cisco.com/community/netpro/service-providers/ios-xr?view=discussions
so be our guest!
Cheers,
Ivan.

Similar Messages

Hold queue on AP interface

On an autonomous 1131 AP, I'm working with someone else's config and trying to understand why a hold queue would be placed on this interface and if it is helpful or detrimental for this AP to have it enabled.
interface FastEthernet0
no ip address
no ip route-cache
duplex auto
speed auto
hold-queue 160 in
Any recommendations either way--keep it--remove it?

this link answers my question
http://www.cisco.com/en/US/products/hw/routers/ps133/products_tech_note09186a0080094791.shtml

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
Andy

Hi, 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

WAAS interface - Input queue: output drops

I'm seeing total output drops increment every now and then. We are using 3750E stack switch and are configured for WCCP L2 forward and return. Anyone know why I'm seeing out drops on the WAAS connected interface? The WAAS interfaces are setup as standby. The model is 7371...
interface GigabitEthernet1/0/4
description ****WAAS1 GIG 1/0****
switchport access vlan 738
mls qos trust dscp
spanning-tree portfast
end
GigabitEthernet1/0/4 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is 0022.be97.9804 (bia 0022.be97.9804)
Description: ****WAAS1 GIG 1/0****
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/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:03, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 281
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 5967000 bits/sec, 1691 packets/sec
5 minute output rate 5785000 bits/sec, 1606 packets/sec
9301822868 packets input, 3537902554734 bytes, 0 no buffer
Received 179580 broadcasts (172889 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 172889 multicast, 0 pause input
0 input packets with dribble condition detected
7661948806 packets output, 2639805900461 bytes, 0 underruns
0 output errors, 0 collisions, 5 interface resets
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

It looks like this could be related:
CSCtf27580 Ethernet interface input queue wedge from broadcast/uniGRE traffic
Is there any GRE traffic going through this AP?
The workarounds are:
Reboot APs to bring APs back up for time being.
OR
go back to 6.0.188.0 code on WLC.
OR
Route GRE traffic away from AP's.
It appears that it definitely exists in your code:
12.4(21a)JHA 12.4(21a)JA01 006.000(196.000)

Quick UCM/Unity 7.x Hold Queue Question

I was wondering if it was possible to create an automated "hold queue" in either UCM or Unity? Specifically, we would like to have a call automatically placed in a queue if no one picks it up in a given amount of time. We would prefer to have some kind of greeting also played to notify the callers they are being placed in the queue. The other challenge would be notifying the individuals fielding the calls that there were calls in the queue.
Can this be done natively in UCM or Unity or is this advanced functionality I would only get in say Contact Center?
Will rate posts.
Thanks!

Hi
Realistically this is the kind of thing you need Contact Center for I'm afraid.
You can do *some* of this with Call Handlers in Unity / Unity Connection - but this basically goes as far as playing a message to callers, and then sending the call somewhere else (for example back around a hunt group).
A relatively common implementation that I've done for customers is to:
1. Route the call into a hunt group.
2. If the call isn't picked up by the hunt group it diverts to a Unity Connection Call Handler.
3. The caller is then played a message, and given the choice of continuing to hold (call is sent back to the hunt pilot) or leave a VM (call is transferred to a VM box).
Queuing it isn't, but it does some of what you are after.
It's nowhere near as sophisticated as what you get with Contact Centre. If you want real queuing, with real stats with real agent availability, then UCCX is the way to go.
HTH. Barry

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
Shaun

I 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.

Ethernet interface input queue 81/80 (size/max)

Hello,
Does anyone had the problem that the Gigabit interface of a C1140-K9W7 (or C1135)
sometimes "hangs" due to queue problems (from what I understood it was queue problems)?
I've got this AP, C1140-K9W7 with IOS 12.4(21a)JA1 and noticed it was not processing
any input packets at the Gigabit interface, the drop count was 0 but strangely the input queue
information was that it had size 81 and max 80... looks to me that the queue processing
code hanged somewhere...
The interface output is OK however (the AP is sending arp requests..) .
I've done some search but was not able to find any information about it, also followed the
steps in [1] to try troubleshoot what was causing that, no success. The IP traffic listing
shows that the interface is receiving packets but they aren't being processed and "aren't"
droped also (at least the drop count is 0).
If I reboot the AP it does work OK yes... I can still access the console (via serial) and it
still is at that state in case there's any suggestion of procedure.
Thanks for your time.
Jean Mousinho
[1] http://www.cisco.com/en/US/products/hw/routers/ps133/products_tech_note09186a0080094791.shtml

It looks like this could be related:
CSCtf27580 Ethernet interface input queue wedge from broadcast/uniGRE traffic
Is there any GRE traffic going through this AP?
The workarounds are:
Reboot APs to bring APs back up for time being.
OR
go back to 6.0.188.0 code on WLC.
OR
Route GRE traffic away from AP's.
It appears that it definitely exists in your code:
12.4(21a)JHA 12.4(21a)JA01 006.000(196.000)

Qos using priority queue drops

I have following config for Qos.
Basically Access-list match the voip/signalling traffic & put that in High queue. I am trying to figure without hight utilization why I am seeing output drops in high queue.
7206#sh int s5/1/5:0
Serial5/1/5:0 is up, line protocol is up
Hardware is PA-MC-2T3+
Description: T1
Internet address is 172.17.133.105/30
MTU 1500 bytes, BW 1536 Kbit, DLY 20000 usec,
reliability 255/255, txload 24/255, rxload 23/255
Encapsulation HDLC, crc 16, loopback not set
Keepalive set (10 sec)
Last input 00:00:06, output 00:00:00, output hang never
Last clearing of "show interface" counters 01:58:03
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 1800
Queueing strategy: priority-list 4
Output queue (queue priority: size/max/drops):
high: 0/20/1764, medium: 0/20/0, normal: 0/15/36, low: 0/15/0
5 minute input rate 143000 bits/sec, 82 packets/sec
5 minute output rate 145000 bits/sec, 83 packets/sec
734269 packets input, 148368640 bytes, 0 no buffer
Received 708 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
734855 packets output, 148838576 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions no alarm present
Timeslot(s) Used: 1-24, subrate: 1536Kb/s, transmit delay is 0 flags
non-inverted data
==============================================================================
7200#sh run int s2/1/5:0
Building configuration...
Current configuration : 254 bytes
interface Serial2/1/5:0
description T1
ip address x.x.x.x
no ip redirects
no ip unreachables
no ip proxy-arp
no snmp trap link-status
priority-group 4
no cdp enable
end
====================================================================================
Define access-list to match voice/signalling traffic
access-list 140 permit udp any any range 1024 1151
access-list 140 permit udp any any range 16384 32767
access-list 140 permit udp any any eq 2427
access-list 140 permit udp any any eq 2429
access-list 140 permit udp any any eq 5060
priority-list 4 protocol ip high list 140
priority-list 4 queue-limit 20 20 15 15

Hi,
your queue limit is 20 packets. This can explain the behaviour. If there are 20 packets in the queueing system waiting to be serviced any newly arriving packet will be dropped.
Basically you can have drops in any queue in any queueing system if there is a permanent overload situation. There is no magic trick, if you f.e. permanently send 2 Mbps voip towards a T1. There will be drops.
QoS does not create resources, it just distributes them among your important traffic classes.
Besides this I also would suggest you to use class based queueing based on Modular QoS CLI (MQC). It is more flexible and precise than the old legacy methods like priority queueing, which you are using. On the other hand, if this is sufficient for you, why not.
Regards, Martin

How to keep messages in sequence of different interfaces (using queues?)

Dear experts,
I'm running a scenario in which a job in one system creates and deletes orders in another system via XI (using idocs). I'm sending 100 times more creations than deletions.
These are two different interfaces. Therefore they use different queues.
My problem now is that sometimes a deletion enters the target system before the the creation of this order has taken place. Because the queue is much shorter for deletion, these are processed earlier.
How can I make sure that message from two different interfaces enter and then exit xi in the same sequence? Is it possible to assign them to the same outbound queue?
Please advice.
Thanks in advance.

hai
check the below link
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/20bb9649-e86e-2910-7aa9-88ed4972a5f6
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b0401ea9-0be5-2910-b389-ce9675ab8af9
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d0111fef-d311-2a10-c0b9-f33a49c1f2e5
note:reward points if solution found helpfull.....
regards
chandrakanth.k

Messages remain in "HOLD" Queue in J2EE engine

Hi
Message in the Java stack are in the "HOLD" status. .and if i try to resend the same , they still remain in the HOLD status..
What could be the pblm in this case?
Regards
XA

Hi,
I hope you are referring HOLDING status and you have EOIO.
This status comes when the first message in the AE queue is in error ststus
In the runtime work bench message monitoring, run the query to get all SYSTEM ERROR STATUS message for EOIO and cancel all of them.
Then you should be able to resend this HOLDING STATSU message.
To know which queue, please configure the following columns in configure table column option.
Sequential Number
Serialization Context
Correlation ID
In the output you can see these details .
Thanks
Rajesh

Interface for queuing disparate commands

Hello,
I am writing LV code for a Keithley 2400 instrument. The user interface includes 4 options that can then be queued up - including apply a current, apply a voltage, monitor open-circuit potential, and loop to another spot in the queue. The way I am handling the user input currently is with a table. Users can enter parameters for each of the 4 options, the use buttons to add steps to the table (ie: my command queue). The program then reads each line out of the table and decides what to do. Since the commands are different (including different termination options, such as wait time, max voltage, min. current, etc), the way I handle it is for the table to group them by control variable, etc, such that one column might have very different values. For instance, the control variable might be 4 V or 350 mA. This basically makes the table unreadable, and the code for interpreting the table isn't exactly the cleanest...
The outer control loop continuously executes, and on each pass it checks to see if any buttons have been pressed and updates the table (or not) accordingly. I have attached the part I use as a sub-vi, written in LV 2010.
There is surely a better way to do this, but I haven't found it. Any suggestions would be most welcome.
Scott
Attachments:
2400C build command queue.vi ‏30 KB

What you need is a Producer Consumer architecture. Do a search in LV help for more details, also there is a producer consumer with event template you can use. I don't remember the exact path but it is something like new, vi from template, ..design framework...(I don't have LV on this machine).
The Producer loop contain an event structure, use it to detect the GUI events. Usually you queue an enum with the value of the operation to perform. You can bundle this enum value with a variant (that will be your queue data type: a cluster contaning an enum and a variant) to also pass different data types to the consumer loop.
In the consumer loop you unbundle the enum to a case structure to manage cases for the different enum values (don't forget to make your enum a type def) and you unbundle the variant data to pass as a parameter.
Ben64

QoS - Ingress Port Queuing (SP or default) based on CoS?

Guys,
the following URL is excellent for the QoS flow through a 6500. Also had an excellent briefing off a mate in my team :)
http://www.cisco.com/en/US/customer/tech/tk543/tk762/technologies_white_paper09186a00800b0828.shtml
One question on this. It states the following :-
A frame enters the switch and is initially processed by the port ASIC that received the frame. It will place the frame into a Rx queue. Depending on the Catalyst 6000 family line card, there will be one or two Rx queues.
The port ASIC will use the CoS bits as an indicator of which queue to place the frame into (if multiple input queues are present). If the port is classified as untrusted, the port ASIC can overwrite the existing CoS bits based on a predefined value.
The statement "The port ASIC will use the CoS bits as an indicator of which queue to place the frame into"
does this mean that the frame can only be put into the Rx queue based on an L2 (isl, dot1q) CoS value, OR can the frame be place in an Rx queue based on an L3 DSCP or ip prec value? ALSO, what if there is no CoS value, (ie the frame is not from a trunk, ie untagged)
then it goes off for internal DSCP markings (which I understand all about now I hope) :)
Could someone please clear this small point up for me.
Many thx indeed,
Ken

Hey dude, (also thx Simon also)
This is the thing, according to the documentation, the DSCP-COS mappings are for mapping the internal DSCP value on the PFC (i think) which come well after the input queue assignment phase so i would like to think that the input ASIC says what you are implying.
The extrat from the doc is
As mentioned earlier, the switch uses a DSCP value internally to assign a predetermined level of service to that frame. As a frame enters a trusted port, the administrator can configure the port to look at either the existing CoS, IP precedence, or DSCP value to set the internal DSCP value. Alternatively, the administrator can set a predefined DSCP to every packet that enters the port.
it says "the administrator can configure the port to look at either the existing CoS, IP precedence, or DSCP value to set the internal DSCP value" It does not say that it will look at the COS, IPPREC or DSCP to move the incoming packet into the relevant Rx Q?
Am I being a little silly here? Sorry if I am :)
I suppose what I am trying to say is. A frame comes into a switchport that has two queues, SP and default. If it comes in on a non-trunk port (has no CoS marking) how would you determine how to get a frame into a specific Rx queue (if you have two of them) based on CoS?
Kind regards,
Ken

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.

3750 QoS - egress interface

Please guide me to understand the 3750 QoS mechanism.
Q1) DOC say "priority-queue out" is ignore shape and share command. is it meaning always give priority to cos=5(or dscp=ef) traffic regardless the shape command?
Q2) I want to give 10% guaranteed bandwidth to voice traffic. what's best command in the 3750 egress interface? shape only or combine with priority-queue?
Q3) Any doc explained the output for the command "show mls qos interface f1/0/1 statistics"? the meaning of the each field.
Thanks in advance,

Hi,
1. That is correct. The expedite queue is a priority queue, and it is serviced until empty before the other queues are serviced. This has the potential to hog all the bandwidth on an interface....
2. I would use the priorty-queue command as it will give the best jitter and latency characteristics for your voice traffic. If you want to limit this bandwidth, you should do it via policing on ingress interfaces.
3. Check out this link:
http://www.cisco.com/en/US/products/hw/switches/ps5023/products_command_reference_chapter09186a00805023be.html#wp1947019
Hope that helps - pls rate the post if it does.
Regards,
Paresh

QoS - Interface Hold Queue

Similar Messages

Maybe you are looking for