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

viru's profile - activity

2017-12-01 09:04:58 -0700 received badge  Famous Question (source)
2017-05-22 09:28:52 -0700 received badge  Popular Question (source)
2016-11-30 17:34:54 -0700 received badge  Famous Question (source)
2016-09-26 00:26:44 -0700 received badge  Notable Question (source)
2016-09-01 01:04:42 -0700 received badge  Popular Question (source)
2016-08-23 05:48:51 -0700 asked a question How to load netconf yang module in netconf server.

Hi All,

My netconf server send some default "Server Module capability" as yang file to netconf client running in ODL, but server is not exposing all yang files to client. so I have added remaning yang, manually using following step:-

  1. put these yang files in cache/schema folder of ODL.
  2. Add capability in device module of etc/opendaylight/current/controller.currentconfig.xml

My schema get generates but i don't know the netconf rest API to load these files in server so that i configure the yang file. if i load these file in server using yangcli . After that i am able to configuring these yang, please let me know how to load these files in server using ODL ?.

Thanks ! viru

2016-08-19 06:28:56 -0700 asked a question Not able to configure netconf device MIB.

Hi All, My netconf device is using openyuma and exposing some default "Server Module capability" as yang file while connecting with ODL. but server is not exposing one of the yang files which i require for device MIB update. i am able to set/get MIB object of this yang file using yangcli client. but i want to do the same using ODL so i have :-

1) put this file in cache/schema folder of ODL and rename as module_name at revision No. 2) i have added capability in device module xml file as :- </yang-module-capabilities> <capability xmlns="urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf"> urn:ietf:params:xml:ns:yang:smiv2:FutureNat-MIB?module=FutureNat-MIB&revision=2012-09-05 </capability> </yang-module-capabilities>

My device get successfully connected with ODL and able to see device in mount points of ODL GUI using http://127.0.0.1:8181/apidoc/explorer... and when i select device then i get API for only those yang file which were exposed to ODL while connecting but not for my FutureNat-MIB file. please let me know where i am doing wrong . My target is to update device MIB mentioned in FutureNat-MIB.yang file

Thanks !

2016-07-01 00:02:18 -0700 received badge  Famous Question (source)
2016-06-01 17:48:18 -0700 received badge  Famous Question (source)
2016-05-13 10:26:04 -0700 received badge  Notable Question (source)
2016-04-21 08:47:01 -0700 received badge  Notable Question (source)
2016-03-27 21:27:55 -0700 asked a question Unable to add queues using ovsdb

Hello everyone,

I am trying to add queues using REST api provided by OVSDB. I was able to create queues using following REST Api

http://127.0.0.1:8282/ovsdb/nb/v2/nod...

http://127.0.0.1:8282/ovsdb/nb/v2/nod...

Now if I do "ovs-vsctl list queue" it is showing queues properly but if I use "ovs-ofctl queue-stats br0" it is showing nothing. If I create queue using ovs-vsctl then it shows queue in both list queue and queue-stats. Please help me out.

Thank you Mayank

2016-03-26 20:25:57 -0700 received badge  Popular Question (source)
2016-03-16 06:40:00 -0700 asked a question facing issue while using ovsdb plugin

HI ,

we are trying to create queue on one of the port of mininet switch using ODL Restconf API and configuring it for rate limit. i am using stable Lithium release.so could anyone let me know:

  1. what are the module which we need to install on karaf console.
  2. what are the command to connect mininet (ovsdb server) with ODL which listen on port 6640
  3. What are REST API's and content of POST API to create/configure queue for helium release.

Thanks! vir

2015-12-16 00:59:02 -0700 received badge  Notable Question (source)
2015-12-15 03:49:34 -0700 received badge  Famous Question (source)
2015-09-30 23:17:51 -0700 received badge  Popular Question (source)
2015-08-25 05:41:04 -0700 asked a question OpenvSwitch is getting restarted

Hi Team,

We are using Open Daylight Controller and OVS switch. ODL – Helium OVS Version: 2.3.1

We are running UDP traffic. After some time we observed that switch is getting re-connected and it is sending Hello Message to ODL. On ODL logs getting printed are:

2015-08-25 16:43:28,965 | INFO | entLoopGroup-8-7 | ConnectionAdapterImpl | 252 - org.opendaylight.openflowjava.openflow-protocol-impl - 0.6.0.SNAPSHOT | Hello received / branch 2015-08-25 16:43:29,027 | WARN | entLoopGroup-8-7 | OFSessionUtil | 254 - org.opendaylight.openflowplugin - 0.1.0.SNAPSHOT | duplicate datapathId occured while registering new switch session: 5 2015-08-25 16:43:29,030 | WARN | entLoopGroup-8-7 | ConnectionConductorImpl | 254 - org.opendaylight.openflowplugin - 0.1.0.SNAPSHOT | Closing handshake context failed: null

We request you all to please help us to resolve this error.

Thanks in advance.

2015-08-02 07:34:12 -0700 received badge  Famous Question (source)
2015-07-28 08:51:04 -0700 received badge  Popular Question (source)
2015-07-03 01:47:21 -0700 asked a question How to push Valn-Id in ODL- Helium

HI All,

I am using below code to push vlan -ID in flows //Add Vlan-ID.

        PushVlanActionBuilder pushVlanActionBuilder9 = new PushVlanActionBuilder();
        pushVlanActionBuilder9.setEthernetType(0x8100);
        VlanId vlanId = new VlanId(2);
        pushVlanActionBuilder9.setVlanId(vlanId);
        ActionBuilder actionBuilder9 = new ActionBuilder();
        actionBuilder9.setAction(new PushVlanActionCaseBuilder().setPushVlanAction(pushVlanActionBuilder9.build()).build());
        actionBuilder9.setOrder(0);
        Action action9 = actionBuilder9.build();
        actionList.add(action9);

And it shows me this flow on switch:- cookie=0x2b00000000000001, duration=241.908s, table=0, npackets=11, nbytes=814, sendflowrem priority=65535,ip,nwsrc=10.0.0.2,nwdst=10.0.0.1 actions=setfield:10.0.0.1->ipdst,pushvlan:0x8100,setfield:10.0.0.2->ip_src,output:1

but it is not adding any VLAN-Id when packet pass through it. Please let me know the way to implent vlan -id and if possible strip the vlan-id also.

Regards, Virender

2015-06-19 03:50:28 -0700 received badge  Famous Question (source)
2015-05-21 01:31:25 -0700 received badge  Notable Question (source)
2015-05-13 04:53:47 -0700 received badge  Popular Question (source)
2015-05-13 03:46:01 -0700 commented answer Restconf API is not working to add BGP Rib

I am still facing the error while adding bgp Rib via rest conf. The rest client console gives error:- <errors xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf"><error><error-type>application</error-type><error-tag>operation-failed</error-tag><error-message>Error creating data</error-message></error></errors> The details logs can be seen at - http://pastebin.com/uxfATGdf Any help will be highly appreciated.

2015-05-12 05:46:14 -0700 commented answer Restconf API is not working to add BGP Rib

Hi Dana, Even if we try to delete the existing RIB(default). we are not able to do it.but still can get it using same restAPI. On deletion, we are getting warning on karaf console" opendaylight-user@root>Warning: org.apache.xerces.parsers.SAXParser: Property 'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized. Warning: org.apache.xerces.parsers.SAXParser: Property 'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not recognized." " please suggest me! Thanks !

2015-05-12 05:31:53 -0700 commented answer Restconf API is not working to add BGP Rib

Hi Dana, i am using same API. i am getting below error:- <errors xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf"><error><error-type>application</error-type><error-tag>operation-failed</error-tag><error-message>Error creating data</error-message></error></errors> i have install the below feature in ODL integration:- 1)feature:install odl-bgpcep-bgp-all 2)feature:install odl-bgpcep-pcep-all 3)feature:install odl-netconf-all 4)feature:install odl-netconf-connector-all Even i am able to get the respose using same Rest API

2015-05-11 05:26:12 -0700 answered a question Restconf API is not working to add BGP Rib

if we install feature like below series:-

opendaylight-user@root>feature:install odl-bgpcep-bgp-all opendaylight-user@root>feature:install odl-bgpcep-pcep-all opendaylight-user@root>feature:install odl-restconf-noauth Refreshing bundles org.eclipse.persistence.moxy (144), org.eclipse.persistence.core (143), org.jboss.netty (184), com.google.guava (61) opendaylight-user@root>feature:install odl-netconf-connector-all opendaylight-user@root> opendaylight-user@root>

There is no "cofig-pusher" exception but i am getting below error.

applicationoperation-failedError creating data

2015-05-11 05:17:29 -0700 received badge  Notable Question (source)
2015-05-11 05:17:05 -0700 asked a question Restconf API is not working to add BGP Rib

Hi All,

I am using Opendaylight Integration version of Helium. when i use below API and feature:-

1) feature:install odl-bgpcep-bgp-all 2) feature:install odl-bgpcep-pcep-all 3) feature:install odl-restconf-noauth 4) feature:install odl-netconf-all. Rest API:- http://127.0.0.1:8181/restconf/config/opendaylight-inventory:nodes/node/controller-config/yang-ext:mount/config:modules/ authntication: admin:admin , Content-Type: text/xml and Body fomat:- <module xmlns="urn:opendaylight:params:xml:ns:yang:controller:config">
<type xmlns:x="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">x:rib-impl</type>
<name>example-bgpls-rib</name>
<bgp-rib-id xmlns="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">192.0.2.2</bgp-rib-id>
<local-as xmlns="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">64496</local-as> </module>

I am getting below error:

protocol invalid-value URI has bad format.

and exception on karaf console:-

opendaylight-user@root>Exception in thread "config-pusher" java.lang.IllegalStateException: Failed to send commit for configuration 39-pcep-provider.xml(odl-bgpcep-pcep-all,odl-bgpcep-pcep-topology-provider) at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.sendRequestGetResponseCheckIsOK(ConfigPusherImpl.java:285) at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.pushConfig(ConfigPusherImpl.java:239) at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.pushConfigWithConflictingVersionRetries(ConfigPusherImpl.java:128) at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.internalPushConfigs(ConfigPusherImpl.java:101) at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.process(ConfigPusherImpl.java:76) at org.opendaylight.controller.netconf.persist.impl.osgi.ConfigPersisterActivator$InnerCustomizer$1.run(ConfigPersisterActivator.java:181) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.IllegalStateException: Error - getInstance() failed for ModuleIdentifier{factoryName='pcep-topology-provider', instanceName='pcep-topology'} in transaction TransactionIdentifier{name='ConfigTransaction-95-97'} at org.opendaylight.controller.config.manager.impl.ConfigTransactionControllerImpl.secondPhaseCommit(ConfigTransactionControllerImpl.java:405) at org.opendaylight.controller.config.manager.impl.ConfigRegistryImpl.secondPhaseCommit(ConfigRegistryImpl.java:280) at org.opendaylight.controller.config.manager.impl.ConfigRegistryImpl.commitConfig(ConfigRegistryImpl.java:227) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:75) at sun.reflect.GeneratedMethodAccessor32.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:279) at com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenReturn(ConvertingMethod.java:193) at com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenReturn(ConvertingMethod.java:175) at com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIntrospector.java:117) at com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIntrospector.java:54) at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237) at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138) at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) at com.sun.jmx.mbeanserver.MXBeanProxy$InvokeHandler.invoke(MXBeanProxy.java:150) at com.sun.jmx.mbeanserver.MXBeanProxy.invoke(MXBeanProxy.java:167) at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:252) at com.sun.proxy.$Proxy17.commitConfig(Unknown Source) at org.opendaylight.controller.config ... (more)

2015-05-07 03:01:09 -0700 commented question RestConf API to add bgp peer give Error

Thanks Dana ! when I first configure the RIB . I am facing below error. <errors xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf"> <error> <error-type>application</error-type> <error-tag>operation-failed</error-tag> <error-message>Error creating data</error-message> <error-info> <operation_failed>{rib-impl={example-bgp-rib-1=BgpDispatcher is null, expected dependency implementing interface org.opendaylight.controller.config.yang.bgp.rib.impl.BGPDispatcherServiceInterface}}</operation_failed> </error-info> </error> </errors> Please let me know if I need to change code-base.

2015-05-07 02:58:35 -0700 received badge  Popular Question (source)
2015-05-07 00:56:44 -0700 commented question RestConf API to add bgp peer give Error

Hi, After installing the "odl-netconf-all feature" i am able to get the BGP peer details but when i (POST) create the peer i am getting the below error: <errors xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf"> <error> <error-type>application</error-type> <error-tag>operation-failed</error-tag> <error-message>Error creating data</error-message> <error-info> <error>java.lang.IllegalStateException: Unable to resolve value AttributeConfigElement [defaultValue=null, value=MappedDependency{namespace='urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:cfg', serviceName='rib', refName='example-bgpls-rib'}] to attribute rib</error> </error-info> </error> </error->

2015-05-06 05:49:10 -0700 asked a question RestConf API to add bgp peer give Error

Hi All,

I am using firefox rest client to add the bgp peers , i set below parameter in that:-

Method:- POST URL:- http://127.0.0.1:8181/restconf/config/opendaylight-inventory:nodes/node/controller-config/yang-ext:mount/config:modules/ Authentication: username: admin , Passowrd: admin

Body:-

<module xmlns="urn:opendaylight:params:xml:ns:yang:controller:config">
<type xmlns:x="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">x:bgp-peer</type>
<name>example-bgp-peer</name>
<host xmlns="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">192.0.2.1</host> <holdtimer xmlns="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">180</holdtimer>
<rib xmlns="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">
<type xmlns:x="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:cfg">x:rib</type> <name>example-bgpls-rib</name>
</rib>
<peer-registry xmlns="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl"> <type xmlns:x="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">x:bgp-peer-registry</type>
<name>global-bgp-peer-registry</name>
</peer-registry>
<advertized-table xmlns="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl"> <type xmlns:x="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">x:bgp-table-type</type>
<name>ipv4-unicast</name>
</advertized-table>
<advertized-table xmlns="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl"> <type xmlns:x="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">x:bgp-table-type</type>
<name>ipv6-unicast</name>
</advertized-table>
<advertized-table xmlns="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl"> <type xmlns:x="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">x:bgp-table-type</type>
<name>linkstate</name>
</advertized-table> </module>

But i am getting the below error :-

<errors xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf"> <error> <error-type>protocol</error-type> <error-tag>invalid-value</error-tag> <error-message>URI has bad format</error-message> </error> </errors>

Please let me know where i am doing wrong.

2015-04-11 03:01:59 -0700 received badge  Popular Question (source)
2015-04-11 03:01:59 -0700 received badge  Notable Question (source)
2015-04-11 03:01:59 -0700 received badge  Famous Question (source)
2015-04-08 00:59:36 -0700 asked a question Restconf API output is weired with mininet switch.

Hi,

We are using l2switch code with mininet topology (created with below command) .

sudo mn --topo linear,2 --controller=remote,ip=127.0.0.1,port=6633 --switch ovsk,protocols=openFlow13

but when we ping h1 to h2 then we noticed the restconf API ( localhost:8181/restconf/operational/opendaylight-inventory:nodes) output

1) it shows both host(h1,h2) connected on both the switch.(it means h1,h2 are connected on s1 and s2 both but on mininet topology connetion are different). 2) it is not showing the node IP.

please let me know why it shows like this and how host tracker interpreting mininet topology.

Thanks !

2015-03-16 14:58:55 -0700 received badge  Popular Question (source)
2015-03-16 14:58:55 -0700 received badge  Notable Question (source)
2015-03-16 14:58:55 -0700 received badge  Famous Question (source)
2015-02-18 08:21:29 -0700 received badge  Famous Question (source)
2015-02-11 06:39:55 -0700 received badge  Famous Question (source)
2015-02-09 21:52:29 -0700 received badge  Famous Question (source)
2015-01-27 08:24:30 -0700 received badge  Notable Question (source)