PCQ issue

I use RB433AH as a main router. I use PCQ to shape speed of my users. I use address-lists.

example of address-list:

 9   abo4096                                    10.0.15.1                      
10   abo512                                     10.0.15.2                      
11   abo512                                     10.0.15.3                      
145   abo192                                     10.0.19.3                    
146   abo192                                     10.0.19.4                    
147   abo256                                     10.0.20.1                    
148   abo256                                     10.0.20.2

example of mangle:

 6   ;;; Abo 128-up
     chain=prerouting action=mark-packet new-packet-mark=abo128-up passthrough=no src-address-list=abo128 in-interface=eth2-DMZ 

 7   ;;; Abo 128-down
     chain=postrouting action=mark-packet new-packet-mark=abo128-down passthrough=no dst-address-list=abo128 out-interface=eth2-DMZ 

 8   ;;; Abo 192-up
     chain=prerouting action=mark-packet new-packet-mark=abo192-up passthrough=no src-address-list=abo192 in-interface=eth2-DMZ 

 9   ;;; Abo 192-down
     chain=postrouting action=mark-packet new-packet-mark=abo192-down passthrough=no dst-address-list=abo192 out-interface=eth2-DMZ

example of queue types:

 7 name="p128d" kind=pcq pcq-rate=128000 pcq-limit=25 pcq-classifier=dst-address pcq-total-limit=5000 

 8 name="p128u" kind=pcq pcq-rate=128000 pcq-limit=30 pcq-classifier=src-address pcq-total-limit=12000 

 9 name="p192d" kind=pcq pcq-rate=192000 pcq-limit=40 pcq-classifier=dst-address pcq-total-limit=8000 

10 name="p2048d" kind=pcq pcq-rate=2048000 pcq-limit=130 pcq-classifier=dst-address pcq-total-limit=39000 

11 name="p256d" kind=pcq pcq-rate=256000 pcq-limit=40 pcq-classifier=dst-address pcq-total-limit=8000

and all queues are in queue tree:

 0   name="!Upload" parent=global-in packet-mark="" limit-at=0 queue=sfq priority=8 max-limit=9600000 burst-limit=0 burst-threshold=0 burst-time=0s 

 1   name="128up" parent=!Upload packet-mark=abo128-up limit-at=0 queue=p64u priority=1 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s 

 2   name="192up" parent=!Upload packet-mark=abo192-up limit-at=0 queue=p64u priority=2 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s 

 3   name="256up" parent=!Upload packet-mark=abo256-up limit-at=0 queue=p128u priority=3 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s 

 4   name="384up" parent=!Upload packet-mark=abo384-up limit-at=0 queue=p128u priority=4 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s 

 5   name="512up" parent=!Upload packet-mark=abo512-up limit-at=0 queue=p128u priority=5 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s 

 6   name="768up" parent=!Upload packet-mark=abo768-up limit-at=0 queue=p128u priority=6 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s 

 7   name="1024up" parent=!Upload packet-mark=abo1024-up limit-at=0 queue=p256u priority=7 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s 

 8   name="2048up" parent=!Upload packet-mark=abo2048-up limit-at=0 queue=p256u priority=8 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s 

 9   name="4096up" parent=!Upload packet-mark=abo4096-up limit-at=0 queue=p256u priority=8 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s 

10   name="!Download" parent=eth2-DMZ packet-mark="" limit-at=0 queue=sfq priority=8 max-limit=9600000 burst-limit=0 burst-threshold=0 burst-time=0s 

11   name="128dn" parent=!Download packet-mark=abo128-down limit-at=0 queue=p128d priority=1 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s 

12   name="192dn" parent=!Download packet-mark=abo192-down limit-at=0 queue=p192d priority=2 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s 

13   name="256dn" parent=!Download packet-mark=abo256-down limit-at=0 queue=p256d priority=3 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s 

14   name="384dn" parent=!Download packet-mark=abo384-down limit-at=0 queue=p384d priority=4 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s 

15   name="512dn" parent=!Download packet-mark=abo512-down limit-at=0 queue=p512d priority=5 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s 

16   name="768dn" parent=!Download packet-mark=abo768-down limit-at=0 queue=p768d priority=6 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s 

17   name="1024dn" parent=!Download packet-mark=abo1024-down limit-at=0 queue=p1024d priority=7 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s 

18   name="2048dn" parent=!Download packet-mark=abo2048-down limit-at=0 queue=p2048d priority=7 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s 

19   name="4096dn" parent=!Download packet-mark=abo4096-down limit-at=0 queue=p4096d priority=8 max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s

And now about problem :smiley:
From time to time I cannot define how often, PCQ queues freeze. Not all of them but those one without traffic.
For example I have small amount of users who has 128k UP - 64 Down. So PCQ quueue is not in use. When the user with this speed assigned, wants to get Internet traffic - cannot. When I try to ping your IP from RB - I cannot. When I try to ping the main route from your CPE - I cannot.

Solution - disable all queues including parents and enable it again. Voila it works. I can ping CPE I can ping main router from CPE.

My question is why I have to do that. Why PCQ queues freeze so often. Why can I do to repair my situation. Maybe it is a MT bug?

what version do you use? as I remember, I had this kind of problem in about v3.7

I use 3.14.

Support, are any changes in ROS 3.15 in PCQ?

I’ve the same problem on PC machine :frowning:

True. On PC I Have had the same. Then I have planned to change to RB. And… Nothing has changed. On RB PCQ queues still freeze.


Support HELP!


I see I’m not alone :frowning: When this will happen again I will send to support@mt suppout file. Will see.

Hi, Running 3.14 and have the same issue with clients freezing and unable to ping. Disable and re-enable the queue and works again. Have been working with Mikrotik on this issue for quite a while and I am getting little or or feedback from them. I sent them a support.rif file while it was happening on 3.14 and heard nothing back from them. Its quite frustrating to have an issue and Mikrotik ignoring the issue.
E-mailed support on this issue on 6/6/08 “[Ticket#2008060666000537] Major Bug with queue” Have sent them numerous support files.
Just about to click send on this message forum and Mikrotik sent me an e-mail saying that if it is still happening on 3.15 I should send them login details of the AP.

Brendan

I have exactly the same problem.
I’m testing now 3.15 … but it seems to have some addictional bugs.

Regards…

Support! Are Ypu there? Why don’t You do anything? Even simple answer about it?

v3.15 seems to be OK, but I’m still testing

RB 433AH uptime: 5d8h39s and …

I have no problems with PCQ so far :smiley: . I have turned off syn-cookies too. I don’t know is any interrelation between PCQ and syn-cookies, but maybe … MT Support can You confirm od deny between these two things?

itfutura, what did you do diferently? You stated that you were having issues and now say that you have have been running for X number of days without problems. What is the change?

When I started this post there was ROS version 3.14. Currently is 3.15. The change is ROS version :slight_smile:

got the exacatly same problem on 3.15, after 6 days of working with no problem today it’s hanged out :frowning:
turn on and off these queue and working good

Anyone got any update on this problem ?

I am also having this problem.
Has anyone got a fix?

Thanks

Are you running Masq/Nat on the routers with problems?

I wonder if this is a connection tracking problem.

Yes, I use masq on the router. ROS 3.15 hasn’t changed the issue :frowning:

i don’t have connection tracking and i still got the problem..
ros 3.16 is out maybe in this version it will be fixed

v3.15 and I have still the same problem, from time to time PCQ queues freeze !!! Not all of them but those one without traffic:(
For me the last (PCQ) working version was v3.2 ( v2.9.xx works OK too)

SUPPORT do something or explain this problem, v3.3 - v3.15 have a PCQ bug !!!

…I found similar post: http://forum.mikrotik.com/t/problem-with-pcq-queues/24510/1 Support didn’t answer :confused: What is going on ??? It’s a BIG bug !!!