From: Jonathan Hays (nomad@gfoyle.org)
Date: Mon Mar 01 2004 - 21:48:13 GMT-3
you wrote:
>-----Original Message-----
>From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On
>Behalf Of Michael Snyder
>Sent: Monday, March 01, 2004 7:24 PM
>To: ccielab@groupstudy.com
>Subject: a Cynical Viewpoint
>
>
>http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products
>_configur
>ation_guide_chapter09186a00800c75d0.html#52645
>
>
>What's missing in this link?
>
>1) In version 12.2 Mainline the `ip nbar protocol-discovery` is
>automatic?
>2) Something is purposely left out.
>
>How could the author remember `ip cef` and not
>protocol-discovery in the
>task list?
= = =
The command `ip nbar protocol-discovery` does not need to be configured
to use NBAR.
This link and the excerpt below indicate that the command is configured
to keep traffic statistics.
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/
fqos_r/qrfcmd3.htm#1096745
Usage Guidelines
Use the ip nbar protocol-discovery command to configure NBAR to keep
traffic statistics for all protocols known to NBAR. Protocol discovery
provides an easy way to discover application protocols transiting an
interface so that QoS policies can be developed and applied. The
Protocol Discovery feature discovers any protocol traffic supported by
NBAR. Protocol discovery can be used to monitor both input and output
traffic and may be applied with or without a service policy enabled.
This archive was generated by hypermail 2.1.4 : Thu Apr 01 2004 - 08:15:11 GMT-3