Using NBAR for QoS Config

[jjcollaguazo]

Hi,

Just wanted to confirm which interface NBAR needs to be configured on when QoS is applied on the outbound interface (WAN). To be safe I configured it on both the LAN and WAN interfaces, but to save processing power I'd rather have it configured on one if this still allows the protocols to be matched correctly.

Here's the config 'm applying.

class-map match-any Multimedia
match protocol rtp audio
class-map match-any Interactive
match protocol skinny
match protocol h323
match protocol telnet
class-map match-any CM_Citrix
match access-group name Citrix_Traffic
!
!
policy-map ShapeandQueue
class CM_Citrix
    bandwidth 256
  set ip dscp af41
class Multimedia
    priority 64
  set ip dscp ef
class Interactive
    bandwidth 64
  set ip dscp af31
class class-default
    fair-queue
     random-detect dscp-based
policy-map QOSOut
class class-default
    shape average 512000
  service-policy ShapeandQueue

!

!

interface FastEthernet0/0
description LAN LAN
ip address X

ip nbar protocol-discovery
duplex full
speed 100
!
interface FastEthernet0/1
description WAN bandwidth 512
ip address X

ip nbar protocol-discovery
ip flow ingress
duplex full
speed 100
service-policy output QOSOut

Cheers,

[Thotsaphon Lueangwattanaphong]

Hi,

  Actually you will be fine without enabling "ip nbar protocol discovery" on the interfaces for "match protocol" in MQC. However,if you want to monitor what types of traffics are runing on the interfaces you can enable it and use a "show ip nbar protocol-discovery" command.

  Edit: You are doing "queuing" so it has to be applied on the outbound interface. In your case is WAN. 

HTH,

Toshi

[ashok_boin]

Hi,

If your requirement is to match on just protocol basis and perform the necessary QoS, then it's absolutely NOT necessary to have "ip nbar protocol-discovery" command on any interface. In addition to performing QoS, if you want protocol specific inbound/outbound statistics, then you need to enable this command.

Regards...

-Ashok.