[c-nsp] WARNING: Netflow Data Export & Hardware assisted NAT not supported on 76xx/65xx on the same interface

[Harold 'Buz' Dale]

Another problem with a SPAN is that you can get two gigs of data heading to a gig port if the port you are mirroring is (full duplex - as it should be and)running wide open.

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Andrew Miehs
Sent: Monday, August 29, 2011 11:11 AM
To: Matthew Huff
Cc: 'cisco-nsp at puck.nether.net'
Subject: Re: [c-nsp] WARNING: Netflow Data Export & Hardware assisted NAT not supported on 76xx/65xx on the same interface


On 26/08/2011, at 6:25 PM, Matthew Huff wrote:
> I'm looking at using SPAN to replicate the data and send it to a linux box to then create netflow data exports, however, given the nature of the data (high bandwidth and microburst), I'm not sure that the Linux box will work accurately. I assumed the PFC would be doing the exports in hardware giving us the most accurate realtime look at the market data. Evidently I was wrong.

Why does everyone want to use SPAN ports to do this sort of thing? Buy a TAP(ethernet), thats what they are there for!
SPAN ports are great for a quick debugging session, but you are (iirc) limited to 2 of them. You will be stuck if you ever need this functionality in future and you are using the SPAN for production purposes.

Regards

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