Traffic not showing as Queued under DSL policy-map

[exonetinf1nity]

Greetings, i have an 2801 router terminating an SDSL connection, i have configured both class maps and a policy map for voice traffic and applied it to the dialer interface, however when i do a "sh policy-map int output" it shows that voice packets are being matched but not queued.

Config and output attatched, would anyone be able to shed any light on why this is happening?

Regards

[lejoe.thomas]

Hi Mark,

Packets are unlikely to queued if the link is not experiencing any form of congestion. Perhaps you could also try reducing the load-interval under dialer interface to 30 (for testing) seconds and post the results of show policy-map interface command.

HTH

Lejoe

[Joseph W. Doherty]

As Lejoe notes, you only see queued packet stats if the class packets actually queue. You class stats do show the packets matching the class criteria.

One possible reason for this, if your physical interface is Ethernet (and it appears to be) and your SDSL offers much less bandwidth, traffic might be unable to hit interface port speed. What you want to do is define a hierarchal policy which shapes the bandwidth to correspond with your SDSL's actual provided egress bandwidth.

[exonetinf1nity]

Cheers for the replies guys, The only thing that concerns me is that no packets have been matched over the last week, and im confident that the link has been fully utilised during this period.

Queueing

Strict Priority

Output Queue: Conversation 264

Bandwidth 192 (kbps) Burst 4800 (Bytes)

(pkts matched/bytes matched) 0/0

(total drops/bytes drops) 0/0

I have altered the policy as below.

class-map match-any Voice-Media

match ip dscp ef

class-map match-any Voice-Signalling

match ip dscp cs3

match ip dscp af31

!

policy-map SDSL-WAN-OUT

class Voice-Media

priority 192

class Voice-Signalling

bandwidth 8

class class-default

set ip dscp default

fair-queue

!

policy-map SHAPE-SDSL-WAN-OUT

class class-default

shape average 1000000

service-policy SDSL-WAN-OUT

!

interface Dialer 1

service-policy output SHAPE-SDSL-WAN-OUT

!

Do you think this would be sufficient?

Regards

[paolo bevilacqua]

Seems like packets are not marked, you may want to check with an analyzer if indeed they are.

[lejoe.thomas]

Hi,

Seems good to me, try also reducing the load-interval to 30 (for testing) under the dialer interface and then take a look at the show policy-map int command.

HTH

Lejoe

[Joseph W. Doherty]

"The only thing that concerns me is that no packets have been matched over the last week, and im confident that the link has been fully utilised during this period."

I've highlighted, below, you stats that show packets have been matching.

sh policy-map interface output

Dialer1

Service-policy output: SDSL-WAN-OUT

Class-map: Voice-Media (match-any)

2465273 packets, 159838046 bytes

5 minute offered rate 0 bps, drop rate 0 bps

Match: ip dscp ef (46)

2465272 packets, 159837980 bytes

5 minute rate 0 bps

Queueing

Strict Priority

Output Queue: Conversation 264

Bandwidth 192 (kbps) Burst 4800 (Bytes)

(pkts matched/bytes matched) 0/0

(total drops/bytes drops) 0/0

Class-map: Voice-Signalling (match-any)

1906714 packets, 109596710 bytes

5 minute offered rate 0 bps, drop rate 0 bps

Match: ip dscp cs3 (24)

1898667 packets, 104347832 bytes

5 minute rate 0 bps

Match: ip dscp af31 (26)

8047 packets, 5248878 bytes

5 minute rate 0 bps

Queueing

Output Queue: Conversation 265

Bandwidth 8 (kbps)Max Threshold 64 (packets)

(pkts matched/bytes matched) 0/0

(depth/total drops/no-buffer drops) 0/0/0

Class-map: class-default (match-any)

6698271 packets, 2259849247 bytes

5 minute offered rate 0 bps, drop rate 0 bps

Match: any

QoS Set

dscp default

Packets marked 6698273

Queueing

Flow Based Fair Queueing

Maximum Number of Hashed Queues 256

(total queued/total drops/no-buffer drops) 0/0/0

[exonetinf1nity]

Appologies i meant under the "Queueing" section.

Queueing

Strict Priority

Output Queue: Conversation 264

Bandwidth 192 (kbps) Burst 4800 (Bytes)

(pkts matched/bytes matched) 0/0

(total drops/bytes drops) 0/0

[royalblues]

As said in earlier posts, if the pkts matched/bytes matched are non zero only when the class experienced coongestion

Have a look at the foll link

http://www.cisco.com/en/US/tech/tk543/tk760/technologies_tech_note09186a0080108e2d.shtml

Narayan

[Joseph W. Doherty]

Yes, and as both I and Narayan have mentioned, you shouldn't see any count there unless there's enough interface congestion to cause packets to queue.

[exonetinf1nity]

Thank you all for your time, it's cleared up any concerns i was having.

Regards