You are right, NBAR is IOS dependent. To configure NBAR, use one command 'auto qos discovery' on the interface, so its pretty simple. Class mapping is a bit complex but is easily be done to monitor one class of traffic. Well, I think NBAR is the cheapest option to monitor one router since all is required is the console (no server required).

On Thu, Oct 1, 2009 at 4:58 PM, Steve Muchai <smuchai@gmail.com> wrote:
On Thu, Oct 1, 2009 at 4:54 PM, techi <myskunkworks@gmail.com> wrote:
> Hi Lydiah,
>
> If u just want to monitor one Cisco router, u can use QoS on the interface.
> Just configure NBAR to recognize all applications coming in the interface,
> classify the traffic using protocols then use the sho command to see the no.
> of packects mapped to a particular class. You can even map URLs and monitor
> them using the 'match protocol http url '*123.com*" command'.
>

Hi techi,

1. Isn't NBAR, or the lack of it, IOS/platform dependent?
2. Wouldn't NBAR be unnecessarily complex to configure and use, and
its output rather cryptic if she'll have to use CLI?

BR,
S
_______________________________________________
Skunkworks mailing list
Skunkworks@lists.my.co.ke
http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks
Other services @ http://my.co.ke
Other lists
-------------
Announce: http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks-announce
Science:  http://lists.my.co.ke/cgi-bin/mailman/listinfo/science
kazi:     http://lists.my.co.ke/cgi-bin/mailman/admin/kazi/general