[c-nsp] NETFLOW or Alternatives??

Earls, Michael Michael.Earls at 53.com
Thu Jan 6 10:34:31 EST 2005


Check out http://vermeer.org/display_doc.php?doc_id=6
	
Graphing Cisco Systems (NBAR) Network-based application recognition with
MRTG:

Michael

PGP Info: KeyID 0x0DFD993C
Fingerprint F903 0325 5105 2CDB 4BF4 C88B 72F7 BA7A 28CC 598A 


-----Original Message-----
From: RH Lists [mailto:lists at 101.net]
Sent: Thursday, January 06, 2005 9:56 AM
To: cisco-nsp at puck.nether.net
Subject: RE: [c-nsp] NETFLOW or Alternatives??


NBAR protocol discovery may also help in this situation.

On Jan 3, 2005, at 6:13 PM, Vandy Hamidi wrote:

> All,
> I'm looking for a way to determine the type of traffic and the amounts
> of each Flow (SIP, DIP, Sport, DPort).
>
> When my internet traffic or WAN traffic hits 99%, I want to be able to
> identify the cause.  Right now, it's a total uneducated guess.
>
> Requirements:
> 1) Identify traffic flows
> 2) Flow Kbps
> 3) Preferably use a Windows Server for collection and reporting
> 4) Prefer Trending
> 5) Easy ramp up (trying to avoid needing to learn a whole no 
> discipline)
>
> I'm not very familiar with NetFlow, but it looks like it needs a 
> Solaris
> Data Collector.
>
> Equipment will range from 6500, 4500, 3745, 7206, etc.
> Thanks in advance,
>
> 	-=Vandy=-
>

_______________________________________________
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/


This e-mail transmission contains information that is confidential and may be privileged.   It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated.


More information about the cisco-nsp mailing list