Thanks Gurucharan and Jesse for your thoughtful advices. We will try both
approaches.
Thanks,
Jian
On Fri, Aug 23, 2013 at 12:26 AM, Gurucharan Shetty wrote:
> On Wed, Aug 21, 2013 at 6:23 PM, Jian Qiu wrote:
>
>> Thanks Gurucharan!
>>
>> It sounds interesting. We'd like to try this approach.
On Wed, Aug 21, 2013 at 6:23 PM, Jian Qiu wrote:
> Thanks Gurucharan!
>
> It sounds interesting. We'd like to try this approach. But could you
> please point out where I could find OVS kernel-userspace compatibility
> information? Is there any more detailed guide to upgrade ovs kernel without
> r
Yes, setting it too high can also increase CPU consumption. You should
pick a value that reflects your working set of flows.
On Wed, Aug 21, 2013 at 6:16 PM, Jian Qiu wrote:
> Thanks Jesse! I will try to upgrade the userspace to 1.9.0, the current LTS
> version.
>
> With regard to flow-eviction-t
Thanks Gurucharan!
It sounds interesting. We'd like to try this approach. But could you please
point out where I could find OVS kernel-userspace compatibility
information? Is there any more detailed guide to upgrade ovs kernel without
reboot?
Many thanks,
Jian
On Thu, Aug 22, 2013 at 5:04 AM,
Thanks Jesse! I will try to upgrade the userspace to 1.9.0, the current LTS
version.
With regard to flow-eviction-threshold, what is the recommended value? Is
there any side-effect if we increase the threshold to its maximal, say
65535?
Many thanks!
Jian
On Thu, Aug 22, 2013 at 4:52 AM, Jesse
On Mon, Aug 19, 2013 at 4:45 PM, Jian Qiu wrote:
> Jesse,
>
> Thanks for your quick response.
>
> Which version would you recommend upgrade to? As you know, this is our
> production environment, stability is the first priority.
>
> May I upgrade the userspace programs only? We might not be able t
Depending on exact source of the problem, it may still be useful to
update the userspace utilities and/or look at increasing the
flow-eviction-threshold parameter.
On Mon, Aug 19, 2013 at 8:03 PM, Jian Qiu wrote:
> Got it.
>
> If we stick to 1.4.6 kernel, is there any parameter we can tune to mit
Got it.
If we stick to 1.4.6 kernel, is there any parameter we can tune to mitigate
the situation?
Many thanks!
Jian Qiu
On Tue, Aug 20, 2013 at 9:00 AM, Jesse Gross wrote:
> On Mon, Aug 19, 2013 at 4:45 PM, Jian Qiu wrote:
> > Jesse,
> >
> > Thanks for your quick response.
> >
> > Which v
On Mon, Aug 19, 2013 at 4:45 PM, Jian Qiu wrote:
> Jesse,
>
> Thanks for your quick response.
>
> Which version would you recommend upgrade to? As you know, this is our
> production environment, stability is the first priority.
>
> May I upgrade the userspace programs only? We might not be able to
Jesse,
Thanks for your quick response.
Which version would you recommend upgrade to? As you know, this is our
production environment, stability is the first priority.
May I upgrade the userspace programs only? We might not be able to upgrade
kernel module as replacing kernel module may require a
On Mon, Aug 19, 2013 at 6:39 AM, Jian Qiu wrote:
> Hi,
>
> We deployed openvswitch 1.4.6 on CentOS 6.4 in our production envioronment.
> OVS were used to bridge KVM VMs.
>
> Recently, we found some VMs lost network connections randomly. When the
> event happened, we login into the VMs through VNC
Hi,
We deployed openvswitch 1.4.6 on CentOS 6.4 in our production envioronment.
OVS were used to bridge KVM VMs.
Recently, we found some VMs lost network connections randomly. When the
event happened, we login into the VMs through VNC console and found the ARP
tables were full of incomplete entri
12 matches
Mail list logo
