cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
582
Views
0
Helpful
1
Replies

LLQ: confusing "debug priority" output

mogli
Level 1
Level 1

hello,

we've got an installation at a customer with two sites connected via a 1Mbit/sec serial link using llq for voice priorisation. after having problems with the voice quality and debugging around i a get very interesting output when using the "debug priority" command:

26w2d: now 3093345544 tokens 95488 pak_size 592 max_token_limit 100000

26w2d: now 3093345544 tokens 94896 pak_size 592 max_token_limit 100000

26w2d: now 3093345544 tokens 94304 pak_size 592 max_token_limit 100000

26w2d: now 3093345548 tokens 95712 pak_size 592 max_token_limit 100000

26w2d: now 3093345548 tokens 95120 pak_size 592 max_token_limit 100000

26w2d: now 3093345548 tokens 94528 pak_size 592 max_token_limit 100000

26w2d: now 3093345548 tokens 93936 pak_size 592 max_token_limit 100000

26w2d: now 3093345548 tokens 93344 pak_size 592 max_token_limit 100000

so after reconfiguring the match clause for my priority queue the voice problems stop, but the messages still appear.

now my question: does these debug output actually show a problem or is this a normal output from this debug command?

the only references i found regarding this output where in combination with following lines:

3d01h: WFQ: dropping a packet from the priority queue 1

but in my scenario this information that a packet from the pq has been dropped never appears.

never mind, every idea how to handle the first shown output is very welcome!

thank's for your time,

kind regards,

bernhard

1 Reply 1

Not applicable