low latency queuing feature not supported in input policy

[dc-csa-blr]

Dear Experts,

I getting error when i apply service-policy input name " low latency queuing feature not supported in input policy" on LAN interface.

I need priority for VC (vedio conference) traffic.

My configuration as given bellow.

R1(config)#ip access-list extended VOICE-TRAFFIC

R1(config-ext-nacl)#permit  ip host  10.40.17.10  any

R1(config)#class-map match-all VOICE

R1(config-cmap)#match access-group name VOICE-TRAFFIC

R1(config-cmap)#exit

R1(config)#policy-map CBWFQ

R1(config-pmap)#class VOICE

R1(config-pmap-c)#  priority 3072

R1(config-pmap-c)# class class-default

R1(config-pmap-c)#  fair-queue

R1(config-pmap-c)#

R1(config)#int fa0/0 (LAN interface)

R1(config-if)#service-policy input CBWFQ

how  can i acheive our requirement.

Thanks in ADV,

[mfurnival]

Think about what you are asking the router to do. A priority queue is used in the outbound direction and says that packets in this queue will always get dispatched first. So it is illogical to try and configure this in the inbound direction - your router sits there receiving packets and has no control over what order they arrive in - they arrive when they arrive. You can't change something that has already happened.

The solution here is to configure the priority queue on the other end of the link. Now this can be easy if it is something under your control but more complex if it is a link provided by a service provider.

[Joseph W. Doherty]

Disclaimer

The   Author of this posting offers the information contained within this   posting without consideration and with the reader's understanding that   there's no implied or expressed suitability or fitness for any purpose.   Information provided is for informational purposes only and should not   be construed as rendering professional advice of any kind. Usage of  this  posting's information is solely at reader's own risk.

Liability Disclaimer

In   no event shall Author be liable for any damages whatsoever (including,   without limitation, damages for loss of use, data or profit) arising  out  of the use or inability to use the posting's information even if  Author  has been advised of the possibility of such damage.

Posting

For an ingress policy you can analyze the traffic and mark it differently.  Also for ingress, you might also police non-critical traffic to guarantee bandwidth for your critical traffic.

Queuing QoS feature only apply to egress.