It's not at all surprising that you would not have noticed yet, because
IPFIX support has not yet appeared in any released version of OVS.
Anyway, it is on the way, and may be useful.
On Wed, May 01, 2013 at 02:23:17PM +0900, Motonori Shindo wrote:
> Ben,
>
> Sorry. I should have read the FAQ:
>
Ben,
Sorry. I should have read the FAQ:
Q: What Linux kernel versions does IPFIX flow monitoring work with?
A: IPFIX flow monitoring requires the Linux kernel module from Open
vSwitch version 1.10.90 or later.
Regards,
On 2013/05/01, at 14:05, Ben Pfaff wrote:
> OVS also has very new supp
OVS also has very new support for IPFIX.
On Wed, May 01, 2013 at 02:04:39PM +0900, Motonori Shindo wrote:
> Rafael,
>
> As of today, Open vSwitch supports NetFlow v5 only.
>
> Having said that, if your network is using NetFlow v7, it doesn't necessarily
> mean that you must use NetFlow v7 in yo
Rafael,
As of today, Open vSwitch supports NetFlow v5 only.
Having said that, if your network is using NetFlow v7, it doesn't necessarily
mean that you must use NetFlow v7 in your entire network. If NetFlow collector
you are using can understand NetFlow v7, it is highly likely it can understand
On Tue, Apr 30, 2013 at 12:49:26PM +0200, Tmusic wrote:
> Let me post some more debug information then:
[...]
> Does this provides more useful information?
It gets me past the "I don't really believe this, it must be some
misunderstanding" hurdle ;-)
Are you willing to do a few experiments? He
On Thu, Apr 25, 2013 at 12:28:46PM +, pengyi Peng(Yi) wrote:
> I find the reason why ovs commits so many transactions.
>
> In bridge_run, ovs-vswitchd would refresh interface statistic if
> necessary. If the number of ports is big enough such as 500, it will
> take a long time to check every p
On Tue, Apr 30, 2013 at 03:02:46PM +0900, Hiroshi Miyata wrote:
> I am now trying to run OVS of Kernel module with
> Trema-edge(learning_switch code).
> Both are in a box. (Ubuntu 12.10)
>
> When I see the of13 packets, the buffer_id in packet_in messages are
> 0x(OPF_NO_BUFFER)
> for both
On Tue, Apr 30, 2013 at 03:08:34PM +0100, Rafael Gomes wrote:
> Another question because in my search about information about how i can
> configure the netflow, I've read in mailing list of openvswitch that not
> possible configure netflow to specific port, can you explain me what is
> mean?
Op
On Apr 30, 2013, at 1:54 AM, david zhang wrote:
> I'd like to know more details about "It can be more aggressive if the flow
> table becomes large (Are 7000 flows considered as large?)."?
There is a key called "flow-eviction-threshold" described in the
ovs-vswitchd.conf.db man page that affect
Sorry finally i found the answer about how i configure.
In this page:
http://www.admin-magazine.com/CloudAge/Articles/Virtual-switching-with-Open-vSwitch
But if you can help me about:
Another question because in my search about information about how i can
configure the netflow, I've read in mail
Let me post some more debug information then:
so the traffic is a udp stream from 10.1.4.1 port 20 to 10.1.6.2 port 1000
(3000 packet/s with 1024 bytes packet size)
Original situation (last line is the relevant flow):
NXST_FLOW reply (xid=0x4):
cookie=0x3ea, duration=10.568s, table=0, n_packets=
Hi everyone,
How are you?
I hope you're fine.
Sorry for bother you, but I'm new in the monitoring world, and I would like to
experience the netflow v7 in my network.
My network right now is two host and two openvswitch. I know that openvswitch
don't supported netflow 9, and what about netflow
We are using OVS for our VDI solution based Citrix Xenserver to provide
15000 virtual desktop.
Recently, we have built a script to monitor the size of OVS flow table. We
found the number of flow entries in flow table jumps up and down between
1500 and 7000 in one heavily used OVS. So we want to un
13 matches
Mail list logo
