Hi, When stack.sh is executed, I could see net.ipv4.ip_forward(2015-08-23 14:51:27.571 | net.ipv4.ip_forward = 1) being set in logs. Possible Issues in your setup: 1. In your setup all

This event has been changed. more details » OpenDaylight - OPNFV community sync meeting Changed: OpenDaylight - OPNFV monthly sync call ====================================== This is a monthly

adding ovsdb-dev to my response ---------- Forwarded message ---------- From: Sam Hague <shague@...> Date: Wed, Sep 9, 2015 at 9:34 AM Subject: Re: [ovsdb-dev] Bug 4229 - Stale OF entries retained in

Hi Anil, Are there any other log files besides karaf.log on the OpenDaylight side that might be of interest there? That worked, thanks! Regards.

Hi Ravi Thanks for sharing the configuration files, vll try and let you know Can you please tell me whether we need to enable Kernel IP Forwarding for L3 to work in ODL. FYI I don't have

​I don't see any reason except the connection flapped at the time of installation or openflowplugin forwarding rule manager not loaded before net-virt installed those flows (it's unlikely). ​

Hi Anil, The interesting thing is: If I DELETE the offending flows from the config inventory (using the REST api) and then PUT the exact same flows there again, they are correctly pushed to the

if that's the root cause then we probably need to fix unstack.sh. I think unstack probably deleting the bridge without deleting the port first. Ideally we should cleanup the openstack resources

Hi Can, comments inline.. ​Flows are not listed in Operational data store because those flows don't exist on the switch. The issue here is why flows are not installed on the switch. did you check

This is a cross post from the ovsdb-users mailing list [2] Hi, I'm currently trying to get migrations of virtual machines working in an OpenStack Juno installation that uses OpenDaylight as its SDN

Hi, I could see a Null pointer exception while programming tunnel rules and it is related to L2. In your case the missing flows are related to DVR and L3_forwarding. Please

Ok Luis i will also work on it. On Sep 8, 2015 5:07 AM, "Luis Gomez" <ecelgp@...> wrote:

Hi All, As per the bug (4229), when all the compute nodes are unstacked, stale entries exist in the control’s nodes br-int . The same scenario of stale entries can happen in the

FYI. https://bugs.opendaylight.org/show_bug.cgi?id=4282 FYI, found this when building from scratch and running the GBP SFC demo (./startdemo.sh demo-symmetry) I don't think there's any need to add

Hi Chaudhry, If you want to try, this is what I have done so far with Nicira extensions: 1) Match VxLAN incoming packet tunnel-src and tunnel-id: <flow xmlns="urn:opendaylight:flow:inventory">

You should only need the port update for vm3. NetVirt should see the vm3 port update and then it should add flows in both directions to direct traffic. NetVirt should see the vm3 port add, look for

So as far as i know, there is no proper support for new compute node addition as of now. So whenever a new VM spawns on a compute node, ideally net-virt should provision all the flows related to the

Hi Sam/Flavio/Anil, I have a query on adding a new compute node to an existing setup. I have the below setup, 1. One control node with a single VM1. 2.

Then i think there is no way as of now to match on the content. Until and unless you read all the flows from that switch table and find the required flow and use the flow-id from there. Anil --

Hi Anil, I am trying to delete the flow through the config data store. I want the flow to be removed from the data store and from the switch. Thanks and Regards Aswin