Just checked, First the SLAVE ROLE is set, then switches to MASTER role.
How long is it stuck in this state?

From: Srikanth Lingala [mailto:[email protected]]
Sent: 06 April 2017 11:18
To: Venkatrangan G - ERS, HCL Tech <[email protected]>; odl netvirt dev 
<[email protected]>; [email protected]
Subject: RE: br-int become slave and disconnect from ODL

Yes, I installed the feature odl-ovsdb-openstack. And, thanks, I will try that.

Regards,
Srikanth.

From: Venkatrangan G - ERS, HCL Tech [mailto:[email protected]]
Sent: Thursday, April 06, 2017 11:13 AM
To: Srikanth Lingala 
<[email protected]<mailto:[email protected]>>; odl netvirt dev 
<[email protected]<mailto:[email protected]>>;
 [email protected]<mailto:[email protected]>
Subject: RE: br-int become slave and disconnect from ODL

Hi,

What ODL feature have you installed? Odl-ovsdb-openstack?
In your log, the role message from openflowplugin seems to have failed, related 
issues have been fixed recently in openflow. You can try using the latest 
stable release (SR3)  should be out in a couple of days.
Please use SR3 release.


Regards,
Venkat G

From: 
[email protected]<mailto:[email protected]>
 [mailto:[email protected]] On Behalf Of Srikanth 
Lingala
Sent: 04 April 2017 23:25
To: odl netvirt dev 
<[email protected]<mailto:[email protected]>>;
 [email protected]<mailto:[email protected]>
Subject: [netvirt-dev] FW: br-int become slave and disconnect from ODL

+netvirt-dev and ovs-discuss

From: Srikanth Lingala
Sent: Tuesday, April 04, 2017 11:11 PM
To: '[email protected]' 
<[email protected]<mailto:[email protected]>>;
 [email protected]<mailto:[email protected]>
Subject: br-int become slave and disconnect from ODL

Hi,
I am trying to integrate Openstack with ODL.
I am using ODL Boron stable release and OVS 2.6.1. I started ODL karaf using 
the below command:

/opt/distribution-karaf-0.5.3-SNAPSHOT/bin# ./karaf -of13 clean
Apache Karaf starting up. Press Enter to open the shell now...
100% [========================================================================]
Karaf started in 273s. Bundle stats: 389 active, 401 total

    ________                       ________                .__  .__       .__   
  __
    \_____  \ ______   ____   ____ \______ \ _____  ___.__.|  | |__| ____ |  
|___/  |_
     /   |   \\____ \_/ __ \ /    \ |    |  \\__  \<   |  ||  | |  |/ ___\|  |  
\   __\
    /    |    \  |_> >  ___/|   |  \|    `   \/ __ \\___  ||  |_|  / /_/  >   Y 
 \  |
    \_______  /   __/ \___  >___|  /_______  (____  / ____||____/__\___  /|___| 
 /__|
            \/|__|        \/     \/        \/     \/\/            /_____/      
\/


Hit '<tab>' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '<ctrl-d>' or type 'system:shutdown' or 'logout' to shutdown OpenDaylight.
opendaylight-user@root>

And, executed below command to set manager to ODL:

#> ovs-vsctl set-manager tcp:10.20.0.26:6640

ODL able to add br-int to OVS. Following are the OVS details:

root@node-4446ubuntu:~# ovs-vsctl show
9bf5a6cb-e906-4205-afb2-14bb31510a51
    Manager "tcp:10.20.0.26:6640"
        is_connected: true
    Bridge br-int
        Controller "tcp:10.20.0.26:6653"
        fail_mode: secure
        Port br-int
            Interface br-int
                type: internal

Following are the ovs-vswitchd logs:

2017-04-04T22:30:46.005Z|01281|connmgr|INFO|br-int: added primary controller 
"tcp:10.20.0.26:6653"
2017-04-04T22:30:46.005Z|01282|rconn|INFO|br-int<->tcp:10.20.0.26:6653: 
connecting...
2017-04-04T22:30:46.009Z|01283|netdev_linux|WARN|br-int: removing policing 
failed: Operation not supported
2017-04-04T22:30:46.576Z|01284|rconn|INFO|br-int<->tcp:10.20.0.26:6653: 
connected
2017-04-04T22:31:51.646Z|01300|rconn|ERR|br-int<->tcp:10.20.0.26:6653: no 
response to inactivity probe after 5 seconds, disconnecting
2017-04-04T22:31:52.646Z|01301|rconn|INFO|br-int<->tcp:10.20.0.26:6653: 
connecting...
2017-04-04T22:31:52.675Z|01302|rconn|INFO|br-int<->tcp:10.20.0.26:6653: 
connected
2017-04-04T22:32:02.646Z|01303|rconn|ERR|br-int<->tcp:10.20.0.26:6653: no 
response to inactivity probe after 5 seconds, disconnecting
2017-04-04T22:32:03.645Z|01304|rconn|INFO|br-int<->tcp:10.20.0.26:6653: 
connecting...
2017-04-04T22:32:03.665Z|01305|rconn|INFO|br-int<->tcp:10.20.0.26:6653: 
connected
2017-04-04T22:32:13.646Z|01306|rconn|ERR|br-int<->tcp:10.20.0.26:6653: no 
response to inactivity probe after 5 seconds, disconnecting
2017-04-04T22:32:14.646Z|01307|rconn|INFO|br-int<->tcp:10.20.0.26:6653: 
connecting...
2017-04-04T22:32:15.645Z|01308|rconn|INFO|br-int<->tcp:10.20.0.26:6653: 
connection timed out
2017-04-04T22:32:15.646Z|01309|rconn|INFO|br-int<->tcp:10.20.0.26:6653: waiting 
2 seconds before reconnect
2017-04-04T22:32:17.646Z|01310|rconn|INFO|br-int<->tcp:10.20.0.26:6653: 
connecting...
2017-04-04T22:32:19.646Z|01311|rconn|INFO|br-int<->tcp:10.20.0.26:6653: 
connection timed out
2017-04-04T22:32:19.647Z|01312|rconn|INFO|br-int<->tcp:10.20.0.26:6653: waiting 
4 seconds before reconnect
2017-04-04T22:32:23.646Z|01313|rconn|INFO|br-int<->tcp:10.20.0.26:6653: 
connecting...
2017-04-04T22:32:27.646Z|01314|rconn|INFO|br-int<->tcp:10.20.0.26:6653: 
connection timed out
2017-04-04T22:32:27.647Z|01315|rconn|INFO|br-int<->tcp:10.20.0.26:6653: 
continuing to retry connections in the background but suppressing further 
logging

I am able to see the following ODL errors in the Karaf logs:

2017-04-05 04:01:08,675 | INFO  | entLoopGroup-7-3 | ConnectionAdapterImpl      
      | 363 - org.opendaylight.openflowjava.openflow-protocol-impl - 
0.8.3.SNAPSHOT | Hello received / branch
2017-04-05 04:01:08,684 | INFO  | entLoopGroup-7-3 | DeviceManagerImpl          
      | 368 - org.opendaylight.openflowplugin.impl - 0.3.3.SNAPSHOT | 
ConnectionEvent: Device connected to controller, Device:/10.20.0.26:54319, 
NodeId:Uri [_value=openflow:167725479026029]
2017-04-05 04:01:08,685 | INFO  | entLoopGroup-7-3 | SalRoleServiceImpl         
      | 368 - org.opendaylight.openflowplugin.impl - 0.3.3.SNAPSHOT | SetRole 
called with input:SetRoleInput [_controllerRole=BECOMESLAVE, _node=NodeRef 
[_value=KeyedInstanceIdentifier{targetType=interface 
org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.rev130819.nodes.Node, 
path=[org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.rev130819.Nodes, 
org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.rev130819.nodes.Node[key=NodeKey
 [_id=Uri [_value=openflow:167725479026029]]]]}], augmentation=[]]
2017-04-05 04:01:08,685 | INFO  | entLoopGroup-7-3 | SalRoleServiceImpl         
      | 368 - org.opendaylight.openflowplugin.impl - 0.3.3.SNAPSHOT | 
Requesting state change to BECOMESLAVE
2017-04-05 04:01:08,685 | INFO  | entLoopGroup-7-3 | SalRoleServiceImpl         
      | 368 - org.opendaylight.openflowplugin.impl - 0.3.3.SNAPSHOT | 
RoleChangeTask called on device:openflow:167725479026029 OFPRole:BECOMESLAVE
2017-04-05 04:01:08,685 | INFO  | entLoopGroup-7-3 | RoleService                
      | 368 - org.opendaylight.openflowplugin.impl - 0.3.3.SNAPSHOT | 
getGenerationIdFromDevice called for device: openflow:167725479026029
2017-04-05 04:01:18,695 | WARN  | pool-36-thread-1 | DeviceContextImpl          
      | 368 - org.opendaylight.openflowplugin.impl - 0.3.3.SNAPSHOT | New role 
BECOMESLAVE was not propagated to device openflow:167725479026029 during 10 sec
2017-04-05 04:01:18,695 | ERROR | pool-36-thread-1 | SalRoleServiceImpl         
      | 368 - org.opendaylight.openflowplugin.impl - 0.3.3.SNAPSHOT | 
SetRoleService set Role BECOMESLAVE for Node: 
KeyedInstanceIdentifier{targetType=interface 
org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.rev130819.nodes.Node, 
path=[org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.rev130819.Nodes, 
org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.rev130819.nodes.Node[key=NodeKey
 [_id=Uri [_value=openflow:167725479026029]]]]} fail . Reason 
java.util.concurrent.CancellationException: Task was cancelled.
2017-04-05 04:01:18,696 | WARN  | pool-36-thread-1 | DeviceManagerImpl          
      | 368 - org.opendaylight.openflowplugin.impl - 0.3.3.SNAPSHOT | Was not 
able to set role SLAVE to device on node openflow:167725479026029

Can anyone let me know what could be the issue?

Regards,
Srikanth.


::DISCLAIMER::
----------------------------------------------------------------------------------------------------------------------------------------------------
The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information 
could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in 
transmission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability on 
the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the 
author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, 
dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written 
consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please 
delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and 
other defects.
----------------------------------------------------------------------------------------------------------------------------------------------------
_______________________________________________
discuss mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Reply via email to