Hi Ruchika.
Can you get a coredump from OVS, then a backtrace?
Thanks,
Ben.
On Thu, Feb 05, 2015 at 09:52:38AM +0530, Ruchika Verma wrote:
> hi Ben,
>
> I tried this with 2.0.2 as well and i see crash with that OVS-Vesion as
> well.
>
> As i am new to SDN and OVS-Controller I hope the setting
That's an antique. I'd upgrade.
On Fri, Feb 06, 2015 at 08:05:53PM -0800, masoom alam wrote:
> openvswitch version:
>
> ovs-vswitchd (Open vSwitch) 1.4.6
>
>
>
> On Fri, Feb 6, 2015 at 8:02 PM, masoom alam
> wrote:
>
> > Hi every one,
> >
> > Can any one spot why the following bug will appe
Unless you're very lucky no one here will be able to guess what's
wrong. An error from an OpenStack service is going to be meaningless to
most Open vSwitch experts. I'd start by trying an appropriate OpenStack
mailing list; once they've dug into the problem, they may direct you
back here with a m
openvswitch version:
ovs-vswitchd (Open vSwitch) 1.4.6
On Fri, Feb 6, 2015 at 8:02 PM, masoom alam
wrote:
> Hi every one,
>
> Can any one spot why the following bug will appear in Openstack leaving
> all services of Neutron to unusable state?
>
> To give you an idea that I was trying:
>
>
Hi every one,
Can any one spot why the following bug will appear in Openstack leaving all
services of Neutron to unusable state?
To give you an idea that I was trying:
"I tried to configure 173.39.237.0 ip to a VM, with the CIDR 173.39.236.0/23,
however the OVS gave error and now all the neu
On Fri, Feb 06, 2015 at 05:40:53PM -0500, Krishna Pratap wrote:
> Thanks for the help. that "ip" in the match fixed all the problems .
> this is the flow that i applied
> ovs-ofctl -O OpenFlow13 add-flow br0
> in_port=254,ip,actions=output:1,mod_nw_src:'192.1.1.1',controller:6633
>
> on a side no
Thanks for the help. that "ip" in the match fixed all the problems .
this is the flow that i applied
ovs-ofctl -O OpenFlow13 add-flow br0
in_port=254,ip,actions=output:1,mod_nw_src:'192.1.1.1',controller:6633
on a side note, you mentioned about "controller:6633". were you pointing
out the incorr
On Fri, Feb 06, 2015 at 04:37:42PM -0500, Krishna Pratap wrote:
> ovs-ofctl -O OpenFlow13 add-flow br0
> in_port=9,actions=output:1,mod_nw_src:'192.1.1.1',controller:663
>
>
> here is the message I get when i try to do it
>
> ovs-ofctl: none of the usable flow formats (OpenFlow10,NXM) is among t
Hi,
Im trying to add a flow which modifies the traffic source IP adress before
sending the packet-in to the controller and the flow wouldn't apply.
My switch is set to start with OF1.3 and im using ovs2.1 version. here are
the commands and the output .
ovs-vsctl add-br br
Hey,
Have you tried with this commit? Should be fine now,
commit 4ceb6c87968da7bcf025e4d4aef1a8da81eb24b4
Author: Thomas Graf
Date: Wed Feb 4 07:45:06 2015 -0800
datapath: Fix missing symbols when required to use own VXLAN stack
Fixes an insufficient ifdef in compat/vxlan.c which ca
Hi
I think OVS kernel module is already included /w a CentOS7's kernel.
You only need to build & install controls for openvswith ( don't need kmod)
Here is one of my systems as an example:
# uname -r
3.10.0-123.8.1.el7.x86_64
# lsmod |grep openv
openvswitch70743 0
vxlan
Folks,
I have a small testbed with 4 ubuntu servers, fully meshed with VXLAN. To avoid
loops I use Spanning-Tree.
The 4 servers run Ubuntu 14.10 fully updated.
I upgraded manually to openvswitch 2.3.1 with the vivid packages from ubuntu.
3 Servers run kvm and consume via rbd/ceph images. CEPH
Hi All,
We are new to Networking and we need to experiment how vxlans work.
So we need to have multiple interfaces to the outgoing port, so that each
interface can act
as a pipe for the packets for that virtual Lan.
Can you please give a good link from where we can get this info.
The man pag
OS: Centos7kernel: latest - 3.10.0-123.20.1.el7.x86_64OVS : 2.3.90 . the latest
master - openvswitch-ovs-4d9226a The H file
datapath/linux/compat/include/net/vxlan.h has :IFNDEF HAVE_VXLAN_METADATA
Which define prototype rpl_vxlan_xmit_skb. However the c file
datapath/linux/compat/vxlan.cDoesn
On Tue, Feb 3, 2015 at 8:21 PM, Andrey Korolyov wrote:
>> These patches are to enable DPDK 1.8 only. What 'bulk processing' are you
>> referring to?
>> By default there is a batch size of 192 in netdev-dpdk for rx from the NIC -
>> the linked
>> patch doesn't change this, just the DPDK version.
15 matches
Mail list logo
