Ask is moving to Stack Overflow and Serverfault.com! Please use the "opendaylight" tag on either of these sites. This site is now in Read-Only mode

mehta.sagar04's profile - activity

2017-08-22 10:03:40 -0700 received badge  Famous Question (source)
2017-04-02 10:11:53 -0700 received badge  Notable Question (source)
2017-01-23 06:54:56 -0700 received badge  Popular Question (source)
2017-01-23 06:54:56 -0700 received badge  Notable Question (source)
2016-11-29 03:25:04 -0700 received badge  Famous Question (source)
2016-11-17 00:41:53 -0700 received badge  Notable Question (source)
2016-10-21 09:51:30 -0700 received badge  Popular Question (source)
2016-09-06 03:35:39 -0700 received badge  Popular Question (source)
2016-09-02 10:09:29 -0700 received badge  Editor (source)
2016-09-02 10:09:03 -0700 asked a question What is opendaylight controller version compatible with OVS2.5?

I am using Openday light Beryllium-SR3. I was using openvswitch v2.0.2 . But decttl feature was not working in OVS 2.0.2 so I updated it to OVS v 2.5.0. The decttl is working fine but i am getting lots of warning as below:

2016-09-02 12:16:51,517 | WARN | entLoopGroup-5-2 | ListDeserializer | 172 - org.opendaylight.openflowjava.openflow-protocol-impl - 0.7.3.Beryllium-SR3 | Problem during reading table feature property. Skipping unknown feature property: msgVersion: 4 objectClass: org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.oxm.rev150225.match.entries.grouping.MatchEntry msgType: 1 oxm_field: 31 experimenterID: null.If more information is needed, set org.opendaylight.openflowjava do DEBUG log level.

so can someone help me how to solve this error? I think it is the version mismatch. If not can someone point out what is wrong. Kindly let me know if more information is needed?

2016-09-01 12:23:29 -0700 received badge  Popular Question (source)
2016-08-11 07:48:01 -0700 asked a question Send notifications to Application external to opendaylight.

Hi, I have implemnted basic application named "xyz" in Opendaylight beryliium that receives notification for topology changes. I have extenal application say "pqr" that does some action if there is change in topology. The application "pqr" is developed using c++. Now I want to send notification from xyz to pqr whenever there is topology change.

I think that can be done using socket or by creating some rest interface between thses two applications.

Can someone give me better solution to implement these?

Thanks, Sagar

2016-08-10 12:58:39 -0700 received badge  Enthusiast
2016-08-02 13:02:04 -0700 asked a question Not getting Node change or deleted notification in Beryllium Snapshot version

I am following SDNHUB tutorial and implementing TAPapp application with Beryllium latest Snapshot version.

The problem is whenever I am adding switch or adding ports or removing ports , the OnNodeUpdated method implemented from OPenDayLightInventoryListener interface is not getting called in my impl class.

I have added following things in my blueprint.xml : <reference id="dataBroker" interface="org.opendaylight.controller.md.sal.binding.api.DataBroker" odl:type="default"/>

  <reference id="NotificationProviderService"
interface="org.opendaylight.controller.sal.binding.api.NotificationProviderService" odl:type="default" />

  <reference id="RpcProviderRegistry"
interface="org.opendaylight.controller.sal.binding.api.RpcProviderRegistry"
odl:type="default" />

<service id="OpendaylightInventoryListener" interface="org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.rev130819.OpendaylightInventoryListener" ref="provider"/> <service id="DataChangeListener" interface="org.opendaylight.controller.md.sal.binding.api.DataChangeListener" ref="provider"/>

<bean id="provider" class="org.sdnhub.odl.tutorial.tapapp.impl.TutorialTapProvider" init-method="init" destroy-method="close"> <argument ref="dataBroker"/> <argument ref="NotificationProviderService"/> <argument ref="RpcProviderRegistry"/>

</bean> <odl:notification-listener ref="provider"/>

Can someone let me know If I am missing something or if there is any mistake while doing that. Waiting for positive response.

2016-08-01 09:23:02 -0700 asked a question Error while starting latest Snapshot version of Opendaylight Controller

Hello All,

I have downloaded the latest 0.3.0 Snapshot version of opendaylight controller as I wanted to work with IPv6 Arbitrary Masking. The controller started succesfully when there was no application specific code added. Once I addedmy application specific code, I am getting below set of errors: Case 1: On removal of switch 2016-08-01 10:59:31,673 | INFO | entLoopGroup-5-1 | SystemNotificationsListenerImpl | 180 - org.opendaylight.openflowplugin.impl - 0.3.0.SNAPSHOT | ConnectionEvent: Connection closed by device, Device:/192.168.1.200:41230, NodeId:Uri [value=openflow:209406439410246] 2016-08-01 10:59:31,680 | INFO | entLoopGroup-5-1 | RpcManagerImpl | 180 - org.opendaylight.openflowplugin.impl - 0.3.0.SNAPSHOT | Unregister RPCs services for device context closure 2016-08-01 10:59:31,742 | INFO | lt-dispatcher-15 | SalRoleServiceImpl | 180 - org.opendaylight.openflowplugin.impl - 0.3.0.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:209406439410246]]]]}], augmentation=[]] 2016-08-01 10:59:31,743 | INFO | lt-dispatcher-15 | SalRoleServiceImpl | 180 - org.opendaylight.openflowplugin.impl - 0.3.0.SNAPSHOT | Device 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:209406439410246]]]]}] has been disconnected 2016-08-01 10:59:31,744 | ERROR | lt-dispatcher-15 | SalRoleServiceImpl | 180 - org.opendaylight.openflowplugin.impl - 0.3.0.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:209406439410246]]]]} fail . Reason java.lang.Exception: Device connection doesn't exist anymore. Primary connection status : RIP 2016-08-01 10:59:31,745 | WARN | lt-dispatcher-15 | RoleManagerImpl | 180 - org.opendaylight.openflowplugin.impl - 0.3.0.SNAPSHOT | Unable to set role BECOMESLAVE on device Uri [value=openflow:209406439410246] 2016-08-01 10:59:40,265 | WARN | lt-dispatcher-25 | RpcRegistry | 164 - org.opendaylight.controller.sal-remoterpc-connector - 1.4.0.SNAPSHOT | Timed out finding routers for RouteIdentifierImpl{context=null, type=(urn:opendaylight:packet:service?revision=2013-07-09)transmit-packet, route=/(urn:opendaylight:inventory?revision=2013-08-19)nodes/node/node[{(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:209406439410246}]} 2016-08-01 10:59:45,231 | WARN | lt-dispatcher-14 | RpcRegistry | 164 - org.opendaylight.controller.sal-remoterpc-connector - 1.4.0.SNAPSHOT | Timed out finding routers for RouteIdentifierImpl{context=null, type=(urn:opendaylight:packet:service?revision=2013-07-09)transmit-packet, route=/(urn:opendaylight:inventory?revision=2013-08-19)nodes/node/node[{(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:209406439410246}]} 2016-08-01 10:59:50,231 | WARN | lt-dispatcher-18 | RpcRegistry | 164 - org.opendaylight.controller.sal-remoterpc-connector - 1.4.0.SNAPSHOT | Timed out finding routers for RouteIdentifierImpl{context=null, type=(urn:opendaylight:packet:service?revision=2013-07-09)transmit-packet, route=/(urn:opendaylight:inventory?revision=2013-08-19)nodes/node/node ... (more)