[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

sFlow vs netFlow/IPFIX

Subject: sFlow vs netFlow/IPFIX
From: nick at foobar.org (Nick Hilliard)
Date: Wed, 02 Mar 2016 17:30:51 +0000
In-reply-to: <[email protected]>
References: <[email protected]> <[email protected]> <CAPkb-7ApSOtGJg_E+LECSA83qVmVEeG82cbrfX_5M22KPGr57Q@mail.gmail.com> <[email protected]> <[email protected]> <CALgsdbfkth3YXg6xzUoOhRzkobgGie5i0f4uq-f2cjFFSF8dWg@mail.gmail.com> <[email protected]> <[email protected]> <CAB8g2zy0otuuXYPTw=ts4YDox-Q+Y-RMgjFatLVWuttR0g2Cxg@mail.gmail.com> <[email protected]> <[email protected]> <[email protected]>

Peter Phaal wrote:
> The Nexus 3200 should work well with 100G flows - I believe it's
> based on the latest Broadcom Tomahawk ASIC. The older Trident II
> ASICs in the Nexus 9k are 40g parts

does nx-os still force ingress-and-egress sflow?  sflow is pretty
useless you can define an accounting perimeter, which means that you
need either ingress across the board, or egress.  ingress-and-egress is
basically useless because you end up double counting everything.

Nick

Follow-Ups:
- sFlow vs netFlow/IPFIX
  - From: peter.phaal at gmail.com (Peter Phaal)

References:
- sFlow vs netFlow/IPFIX
  - From: mark.tinka at seacom.mu (Mark Tinka)
- sFlow vs netFlow/IPFIX
  - From: peter.phaal at gmail.com (Peter Phaal)
- sFlow vs netFlow/IPFIX
  - From: mark.tinka at seacom.mu (Mark Tinka)
- sFlow vs netFlow/IPFIX
  - From: mark.tinka at seacom.mu (Mark Tinka)
- sFlow vs netFlow/IPFIX
  - From: peter.phaal at gmail.com (Peter Phaal)

Prev by Date: Any large IPv4 space brokers?
Next by Date: Juniper PTX1000
Previous by thread: sFlow vs netFlow/IPFIX
Next by thread: sFlow vs netFlow/IPFIX
Index(es):
- Date
- Thread