[c-nsp] Risk of enabling ip accounting

[Mike Louis]

4948s support netflow in later versions of code. Couldnt' you use that instead.
________________________________________
From: cisco-nsp-bounces at puck.nether.net [cisco-nsp-bounces at puck.nether.net] On Behalf Of Gert Doering [gert at greenie.muc.de]
Sent: Wednesday, October 24, 2007 5:27 PM
To: Vincent De Keyzer
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] Risk of enabling ip accounting

Hi,

On Tue, Oct 23, 2007 at 10:37:56PM +0200, Vincent De Keyzer wrote:
> what is the level of risk involved in enabling IP accounting on an
> interface?

Instant CPU death...

> More specifically, this is about a Catalyst 4948 doing L2/L3 and
> switching a total of 100 Mbits in and out (CPU is around 15%).

I can't speak for the 4948, but my gut feeling is that you won't
see proper numbers in there - most likely it will permit it, but then
only count packets that the CPU sees, but none of the packets being
forwarde by hardware.  (Which is what happens in 12.1 on the 3750s).

gert
--
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert at greenie.muc.de
fax: +49-89-35655025                        gert at net.informatik.tu-muenchen.de
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Note: This message and any attachments is intended solely for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, legally privileged, confidential, and/or exempt from disclosure.  If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited.  If you have received this communication in error, please notify the original sender immediately by telephone or return email and destroy or delete this message along with any attachments immediately.