On Thu, Jan 17, 2013 at 2:49 PM, Ben Pfaff <b...@nicira.com> wrote: > On Thu, Jan 17, 2013 at 02:19:45PM -0800, Ben Pfaff wrote: >> On Fri, Jan 11, 2013 at 09:55:43AM -0800, Romain Lenglet wrote: >> > Signed-off-by: Romain Lenglet <rleng...@vmware.com> >> >> The schema limits each bridge to at most one IPFIX collector. Is >> there an a priori reason why this is limited? It seems to me that one >> could want to send some samples to one set of collectors and other >> samples to another set of collectors. > > One more thing. sFlow and NetFlow configuration work somewhat > differently from IPFIX configuration. For sFlow and NetFlow, when the > admin creates the configuration in the database, then it takes effect > immediately without further effort. IPFIX doesn't work like that, if > I'm reading the code correctly. Instead, you have to add some > OpenFlow actions to cause IPFIX to be sent to the collectors. I think > that's a fair way to do it, but I expect that it will surprise users > who are accustomed to the way we've done NetFlow and sFlow, so I would > like to document it in vswitch.xml. It might also be worthwhile to > mention it in the ovs-vsctl example, and possibly to add a FAQ entry > in the Basic Configuration section.
Can we avoid this difference between protocols altogether? It seems like for any of the protocols it's possible to use either a standard configuration (the way that we currently handle sFlow and NetFlow) or an OpenFlow configuration. That way someone could turn on IPFIX for the switch or use flows to generate NetFlow, all with a common set of tools. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
