David Erickson wrote:
Jesse Gross wrote:
David Erickson wrote:
The crux is the netflow message is matching the flow expiration.
There was nothing in the ovs-vswitchd.log file other than messages
about connecting to NOX and exiting fail-open mode, which was well
before this test was perfo
Jesse Gross wrote:
David Erickson wrote:
The crux is the netflow message is matching the flow expiration.
There was nothing in the ovs-vswitchd.log file other than messages
about connecting to NOX and exiting fail-open mode, which was well
before this test was performed.
Can you try turni
Hi,
I'm trying to use ovs-vswitchd and NOX together to control my
switches. I am not sure if I am doing this correctly, but it doesn't
work. So I was wondering if somebody could shed some light.
I use Ubuntu with 2.6.26 kernel. Everything compiles well and loads
well. Here's my ovs-vswitchd.conf
David Erickson wrote:
The crux is the netflow message is matching the flow expiration.
There was nothing in the ovs-vswitchd.log file other than messages
about connecting to NOX and exiting fail-open mode, which was well
before this test was performed.
Can you try turning off segmentation
I am thinking about the DHCP broadcast issue across the multi-tenant cloud
switching fabric. This includes intra-host openvswitch, the multi-host
openvswitch, and openvswitch+real switch scenarios. The objective is
obviously to constrain the ability of any entity besides the desired server
to ans
Jesse Gross wrote:
Jesse Gross wrote:
David Erickson wrote:
I've attached the packet dump of the netflow message from the switch
causing the problems. Also as an aside, I was only able to get it to
send one netflow message because my machine returned an icmp error
back to ovs since I am n
Jesse Gross wrote:
David Erickson wrote:
I've attached the packet dump of the netflow message from the switch
causing the problems. Also as an aside, I was only able to get it to
send one netflow message because my machine returned an icmp error
back to ovs since I am not listening on that
Justin Pettit wrote:
On Nov 13, 2009, at 11:28 AM, David Erickson wrote:
I've attached the packet dump of the netflow message from the switch causing
the problems. Also as an aside, I was only able to get it to send one netflow
message because my machine returned an icmp error back to ovs sin
David Erickson wrote:
I've attached the packet dump of the netflow message from the switch
causing the problems. Also as an aside, I was only able to get it to
send one netflow message because my machine returned an icmp error
back to ovs since I am not listening on that port.. is there a way
On Nov 13, 2009, at 11:28 AM, David Erickson wrote:
> I've attached the packet dump of the netflow message from the switch causing
> the problems. Also as an aside, I was only able to get it to send one netflow
> message because my machine returned an icmp error back to ovs since I am not
> lis
Jesse Gross wrote:
David Erickson wrote:
1. If you query the flow stats before the expiration message, do you
get the right results? You mentioned that this was true before but
these flows are less than your 10 second polling interval.
The values still look wrong from the stats message,
11 matches
Mail list logo
