If you were subscribed to the IPFIX mailing list in 2006/2007, you probably remember some of the controversy surrounding the adoption of the IPFIX standard you can can go back and read some of this in the IETF archives, as well. IPFIX versions effectively begin at version 10 "version 9" of IPFIX references Cisco NetFlow v9, and is not implemented as "IPFIX" by any vendor I'm aware of. Both are extensible through templates, which can be composed to include additional fields of information.Ĭisco's latest version of NetFlow is V9. While IPFIX built on many of the features and concepts in NetFlow v9 proposed by the Cisco participants, the standard that was adopted for IPFIX is distinct from NetFlow v9, and embodies different information elements, reports volumes differently, and includes some different concepts of observation sources. You can see the Informational draft published as the Cisco NetFlow v9 description in RFC3954. SolarWinds NetFlow Traffic Analyzer Module for SolarWinds NPM SLX - subscri. I can appreciate there's some confusion about the relationship between NetFlow and IPFIX Cisco participated in the IETF IPFIX working group, and brought NetFlow v9 to the table as a proposal to standardize or build upon for the IPFIX standard. We don't support all of the information elements in both the NetFlow and IPFIX standards, but we support the basic flow records. NTA supports NetFlow v9, and also supports IPFIX - among other flow-export protocols. Rohan, DM me with some times/date that work for you next week, and we can discuss some work we're doing now that may be interesting to you.
0 kommentar(er)
