On Mon, Nov 2, 2015 at 1:04 PM, wrote:
> Thanks for the reply. My main concern here is the set of default flows
> that must already be running in each OF-only Switch in order for the
> Controller to reach them and program them.
>
There are not necessarily any pre-existing flows - that is an
imp
On Mon, Nov 2, 2015 at 3:57 AM, Gerhard Stenzel
wrote:
> On 10/30/2015 07:33 PM, Andy Zhou wrote:
>>>
>>> Thanks for the information. I have never ran into this failure, but
>>> now I can see how it is possible. It seems we
>>> should also not match the exact value of recirc_id. I will post a
>>>
Hello All,
I am using openvswitch 2.4 version , compiled under centos 7 (kernel version
3.18.22) . I am sending double tagged traffic to one trunk port , the same
and coming out from the other trunk port (vswitchd is configured in normal mode
flow operation).
But somehow the vlan ID is becomin
Hi,
Could someone please clarify my doubt? I am really stuck on this issue?
Thanks,
Kals.
On Sat, Oct 31, 2015 at 9:55 AM, tech_kals Kals wrote:
> could someone have a look at this qury ?
>
> Hi Ben,
> Could you please clarify my doubt ?
>
> On Fri, Oct 30, 2015 at 1:29 PM, tech_kals Kals
Hi All,
I'm trying to install networking-ovs-dpdk with openstack (devstack) on Ubuntu
14.04 (3.13 kernel) on a single node.
Used following steps:
1. echo "stack ALL=(ALL) NOPASSWD: ALL" >> /etc/sudoers
2. apt-get install sudo -y
3. apt-get install sudo -y || yum install -y s
Hi Justin,
Thanks for the reply. Now I configured my controller to set output port
as OFPP_IN_PORT to take care of these frames and it worked.
Best,
Hans
On Thu, Oct 22, 2015 at 4:15 PM, Justin Pettit wrote:
>
> > On Oct 22, 2015, at 4:07 PM, Hans Yu wrote:
> >
> > Hi,
> >
> > I noticed that
Hi,
Could someone help me check this kernel crash?
I set ipfix to send report to a collector, and the kernel crashed after several
hours.
Thanks!
ovs-vsctl (Open vSwitch) 2.3.1
Compiled Aug 11 2015 05:18:30
DB Schema 7.6.2
kernel version:
3.10.0-123.el7.x86_64
crash> bt
PID: 1614 TASK:
On 10/30/2015 07:33 PM, Andy Zhou wrote:
Thanks for the information. I have never ran into this failure, but
now I can see how it is possible. It seems we
should also not match the exact value of recirc_id. I will post a
patch for this.
This is done, I have pushed the patch to master, branch-2
