Cool was thinking of ping you today to ask the same ☺

From: Manuel Buil
Sent: Thursday, October 13, 2016 2:19 PM
To: Jozef Bacigál; 'openflowplugin-dev'
Cc: Abhijit Kumbhare; Shuva Jyoti Kar; Tomáš Slušný
Subject: RE: [openflowplugin-dev] Problem when adding openflow switch

Hi guys,

Let me confirm you that I haven’t seen this problem anymore in the official 
Boron release and on the latest build from ODL SR1 branch. Great!


From: Jozef Bacigál []
Sent: Tuesday, September 27, 2016 2:16 PM
To: Manuel Buil; 'openflowplugin-dev'
Cc: Abhijit Kumbhare; Shuva Jyoti Kar; Tomáš Slušný
Subject: RE: [openflowplugin-dev] Problem when adding openflow switch

Hi Manuel, Abhijit,

Sorry about that, I missed it somehow in the plugin mailing list, even now I 
can’t find it in my folder. Anyway this was a bug before release and I am 
pretty sure we have been solved it. The timeout for the propagating device was 
too small to change the device state. I need to check it, but if you can try 
with the latest build it would be most appreciate.

I’ll let you know if I find something.


From: Abhijit Kumbhare []
Sent: Tuesday, September 27, 2016 2:03 PM
To: Jozef Bacigál 
<<>>; Shuva Jyoti 
Kar <<>>; Tomáš 
Slušný <<>>
Subject: Fwd: [openflowplugin-dev] Problem when adding openflow switch

Any thoughts on this? Can you respond on the thread?

---------- Forwarded message ----------
From: Manuel Buil <<>>
Date: Fri, Sep 23, 2016 at 2:17 AM
Subject: [openflowplugin-dev] Problem when adding openflow switch
Cc: Jaime Caamaño Ruiz 
Brady Allen Johnson 

I am trying to deploy our SFC OPNFV which is using ODL Boron RC3.5. Very often 
the deployment fails because the OVS in the compute or in the controller gets 
no openflow tables at all. I have been investigating why and I think I found 
the reason and perhaps it is a problem in openflow plugin.

First of all, the br-int brige tries to connect to ODL but it does not as you 
can see in this output (“is_connected: true” is missing under br-int bridge):

    Manager "tcp:<>"
        is_connected: true
    Bridge br-int
        Controller "tcp:<>"
        fail_mode: secure
        Port "tap3da73bd8-74"
            Interface "tap3da73bd8-74"
                type: internal
        Port "qr-483c4c6e-b3"
            Interface "qr-483c4c6e-b3"
                type: internal
        Port br-int
            Interface br-int
                type: internal
        Port "vxlan-"
            Interface "vxlan-"
                type: vxlan
                options: {key=flow, local_ip="", 

Then, in the logs, I can see that:

1.       It tries to change the state of my bridge to BECOMESLAVE , and I can 
see things like: RoleChangeTask called on device:openflow:251377037639930 

2.       Then there are some Netvirt logs

3.       Then, I start seeing worrying messages like: New role BECOMESLAVE was 
not propagated to device openflow:251377037639930 during 5 sec and finally Was 
not able to set role SLAVE to device on node openflow:251377037639930

When I have it working, I get very quickly after the first step messages like: 
“submitRoleChange onSuccess for device:Uri [_value=openflow:88846557454217], 
role:BECOMEMASTER”, even before the Netvirt logs.

I pasted the logs here:

Have you experienced anything like that? Any guesses what might be happening? 
Could that be a bug?


openflowplugin-dev mailing list<>

Software Engineer

Sídlo / Mlynské Nivy 56 / 821 05 Bratislava / Slovakia
R&D centrum / Janka Kráľa 9 /  974 01 Banská Bystrica / Slovakia
+421 908 766 972 /<>
reception: +421 2 206 65 114 /<>


openflowplugin-dev mailing list

Reply via email to