Ingress QoS on 887VA router

[CSCO11949108]

Hello

Can anyone shed any light on the correct interface for LLQ service policy and also ingress QoS on an 887VA router using VDSL...

I have the requirement for Voice to have QoS as the device will have a small number of hosted IP phones connected to a L3 switch that has QoS enabled. QoS is enabled on the phones and switch ports. The switch then is connected to the 887VA.

I have enabled LLQ with priority percent 30, with parent and child policy-maps and have DSCP 46 (EF) set in the nested class-map and the shape average set to a few mb lower that the upload average.

The service policy output is set against the eth0.101 interface.

This appears to be okay for my outbound prioritisation.

However after a lot of reading I have a few questions that I would be very greatful if someone could clear up for me.

1. Using LLQ on the 887VA router with VDSL - should the service policy be configured on Dialer1 or Eth0.101?

2. I know that ingress QoS is hard to achieve and without ISP configuration even more so. But, If I want to configure an ACL or service policy containing e.g. Policy/Class/ACL for VoIP and SIP signaling. Can anyone give an example of a good inbound QoS configuration.

I have spent many hours searching but can't really find any definitives for these questions.

Many Thanks

d

[Georg Pauwen]

Hello,

here is an example. I would just configure it outbound though...

class-map match-all VOICE
 match ip dscp ef
class-map match-any SIGNALING
 match ip dscp cs3
 match ip dscp af31

policy-map QOS_VOICE
 class VOICE
  priority percent 30
class SIGNALING
 bandwidth percent 5
class class-default
 fair-queue
random-detect dscp-based

interface Dialer1
 service-policy output QOS_VOICE

[CSCO11949108]

Hi Georg

Many thanks for your response.

I had not mentioned this was a BT UK VDSL circuit, probably should have.

Going by your example I am assuming that the Dialer1 is the correct interface to apply the service policy and not subinterface eth1.101 which is the interface to create/use with BT UK VDSL? 

It makes more sense to me to have the policy against the Dialer1 interface as this interface is the one used in the zbf etc. Also that this Dialer1 interface is the one that eth1.101 uses anyway.

Also I completely understand that this LLQ example is for service-policy output only for the interface as the queueing can only be done outbound.

Is there anyway to police or ACL etc for ingress on the WAN interface so that torrents/updates and the like, do not consume all the download bandwidth and stop the voice/signalling?

Kind Regards

[Georg Pauwen]

Hello,

you could add a class matching torrent traffic to your existing policy:

class-map match-any P2P_TORRENT
 match protocol fasttrack
 match protocol kazaa2
 match protocol edonkey
 match protocol gnutella
 match protocol bittorrent
class-map match-all VOICE
 match ip dscp ef
class-map match-any SIGNALING
 match ip dscp cs3
 match ip dscp af31

policy-map QOS_VOICE
 class VOICE
  priority percent 30
class SIGNALING
 bandwidth percent 5
class P2P_TORRENT
 police 10000000 8000 8000 conform-action transmit exceed-action drop
class class-default
fair-queue
 random-detect dscp-based

[daniel.mckinney]

Hi Georg

Thanks for your response.

I have used your example for Dialer1 service-policy output, slight renaming as I needed a parent policy for it to apply:

OUTBOUND

policy-map CHILD_QOS_VOICE
class VOICE
priority percent 30
class SIGNALING
bandwidth percent 5
class class-default
fair-queue
random-detect dscp-based
policy-map PARENT_QOS_VOICE
class class-default
shape average 15000000
service-policy CHILD_QOS_VOICE

interface Dialer1
service-policy output PARENT_QOS_VOICE

Adding the P2P_TORRENT class-map that I wanted to use for ingress/download conflicted as it stated "Queuing features not supported in input policy" - It worked okay for outbound but not inbound as there is queueing involved...

I tried this but it did not work stating "Queuing features not supported in input policy"

INBOUND

policy-map INGRESS_QOS
 class VOICE
  police 10000000 8000 8000 conform-action transmit exceed-action drop
class SIGNALING
 police 10000000 8000 8000 conform-action transmit exceed-action drop
class P2P_TORRENT
 police 10000000 8000 8000 conform-action transmit exceed-action drop
class class-default
fair-queue
 random-detect dscp-based

interface Dialer1

service-policy input INGRESS_QOS

I tried removing the fair-queue statement but get the same error message"Queuing features not supported in input policy"

Can I add a inbound policy for the Dialer1 interface that will achieve the policing for torrent and a level of QOS?

Is there anyway to create a policy-map for "ingress" on the Dialer1 interface so that torrents/updates etc do not consume all the download bandwidth and stop the voice/signalling?

Kind Regards

[Georg Pauwen · Accepted solution]

Hello,

I think the 'fair-queue' under the default is the culprit, what happens when you remove that ? Either way, the outbound policing should be sufficient. I would combine both policies and just apply them outbound. Once you do that, check the utilization with 'show service-policy interface dialer1'...

[daniel.mckinney]

Hello Georg

Sorry for not getting back sooner.

I combined both policies and applied them outbound. That seems to work for me.

Thank you for your help

Kind Regards

[Georg Pauwen]

Daniel,

good stuff ! Glad it worked...