Ask Your Question
0

Device not showing up on the ODL GUI after discovering ... Still waiting for help !

asked 2014-05-16 08:05:19 -0700

csadi gravatar image

updated 2014-05-16 12:43:45 -0700

Hello Experts

I created and modified "04-netconf-devices.xml" as per one of the posts to add a netconf device. I do see that there was netconf connection established and data exchanged.

What I dont see is the device in the GUI. Below are some additional information and logs.

On the browser, when I go to

http://ip-address:8080/restconf/config/opendaylight-inventory:nodes/opendaylight-inventory:node/Atlas7800Adi1/yang-ext:mount/

I get,

Mount point does not contain any schema with modules.

Also, below is the snippet of the debug log,

I enabled debug logging for netconf and below is a snippet of the same. I’m still not seeing the node in the GUI

&revision=2014-01-23, urn:ietf:params:netconf:capability:rollback-on-error:1.0, urn:ietf:params:xml:ns:yang:ietf-yang-types?m odule=ietf-yang-types&revision=2010-09-24, http://tail-f.com/yang/common-monitoring?module=tailf-common-monitoring&revision=2 012-11-08, urn:ietf:params:netconf:capability:url:1.0?scheme=ftp,sftp,file, http://btisystems.com/ns/atlas-products?module=at las-products, http://tail-f.com/ns/mibs/SNMPv2-SMI/1.0?module=SNMPv2-SMI 2014-05-16 10:00:19.517 EDT [pool-29-thread-1] DEBUG o.o.c.s.c.n.NetconfDevice#Atlas7800Adi1 – Update device state transactio n DOM-2 putting operational data started. 2014-05-16 10:00:19.517 EDT [pool-29-thread-1] DEBUG o.o.c.s.c.n.NetconfDevice#Atlas7800Adi1 – Update device state transactio n DOM-2 putting operational data ended. 2014-05-16 10:00:19.520 EDT [pool-29-thread-1] DEBUG o.o.c.s.c.n.NetconfDevice#Atlas7800Adi1 – Update device state transactio n DOM-2 SUCCESSFUL. 2014-05-16 10:00:44.663 EDT [http-bio-8080-exec-1] INFO o.o.c.u.internal.UserManager – Local Authentication Succeeded for Us er: “admin” 2014-05-16 10:00:44.665 EDT [http-bio-8080-exec-1] INFO o.o.c.u.internal.UserManager – User “admin” authorized for the follo wing role(s): [Network-Admin]

Would really appreciate if someone could help me here so that I can have a successful device discovery on my ODL

Regards

Adi

edit retag flag offensive close merge delete

3 answers

Sort by » oldest newest most voted
0

answered 2014-05-16 09:24:36 -0700

To add, we can see the restconf output using below api - that means node is getting discovered in md-sal:

http://localhost:8080/restconf/operational/opendaylight-inventory:nodes/

edit flag offensive delete publish link more
0

answered 2014-05-16 10:58:46 -0700

csadi gravatar image

updated 2014-05-16 14:56:59 -0700

I did check that [restconf output] and i got the below output on console and on the browser, I see the message "Restconf is not initialized yet. Please try again later"- How do I initialize restconf?

[root@bti-ma-sdn opendaylight]# 2014-05-16 17:50:52 EDT [com.sun.jersey.spi.container.ContainerResponse] SEVERE com.sun.jerse y.spi.container.ContainerResponse logException Mapped exception to response: 503 (Service Unavailable) org.opendaylight.controller.sal.restconf.impl.ResponseException at org.opendaylight.controller.sal.restconf.impl.ControllerContext.checkPreconditions(ControllerContext.java:147) at org.opendaylight.controller.sal.restconf.impl.ControllerContext.toInstanceIdentifier(ControllerContext.java:157) at org.opendaylight.controller.sal.restconf.impl.RestconfImpl.readConfigurationData(RestconfImpl.java:195) 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 com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker.dispatch(A bstractResourceMethodDispatchProvider.java:185) at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatche r.java:75) at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302) at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) at com.sun.jersey.server.impl.uri.rules.ResourceObjectRule.accept(ResourceObjectRule.java:100) at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147) at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84) at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1511) at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1442) at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1391) at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1381) at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416) at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:538) at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:716) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.filters.CorsFilter.handleNonCORS(CorsFilter.java:440) at org.apache.catalina.filters.CorsFilter.doFilter(CorsFilter.java:179) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:581) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:929) at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:336) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor ... (more)

edit flag offensive delete publish link more

Comments

Hi Adi, Seems you have to wait for controller to startup properly. -Kanika

kanika28 ( 2014-05-18 05:36:21 -0700 )edit

Hi Kanika Im still seeing the same error "Restconf is not initialized yet. Please try again later" Have you seen this working before? Have you been able to see your netconf device on the GUI? Regards Adi

csadi ( 2014-05-19 06:19:24 -0700 )edit

In the log, Im seeing opendaylight.log:2014-05-19 09:19:40.264 EDT [ConfigPersister-registrator] WARN o.o.c.c.p.s.d.a.AutodetectDirectoryPersister - Unable to restore configuration snapshot from configuration/initial/04-netconf-devices.xml Not sure why ...

csadi ( 2014-05-19 07:29:44 -0700 )edit

I fixed the above - again, some issue with the xml file. Now Im back to square one. I dont see the device on the GUI

csadi ( 2014-05-19 08:54:10 -0700 )edit

No, I have not tried visualizing my netconf device on ODL GUI, I was more interested in RESTCONF API output.

kanika28 ( 2014-05-19 22:08:10 -0700 )edit
0

answered 2014-05-19 02:36:48 -0700

Tony Tkacik gravatar image

If you are refering to existing GUI in Opendaylight, this GUI shows only Flow Capable devices, not Netconf Devices.

edit flag offensive delete publish link more

Comments

Thanks Tony Do you mean to say, when I add another node, I will be able to see both on the GUI?

csadi ( 2014-05-19 06:36:53 -0700 )edit

Tony means that devices managed through netconf-devices.xml will not be visible on ODL GUI at all. You can only visualize them through RESTCONF APIs.

kanika28 ( 2014-05-19 22:06:01 -0700 )edit

@Tony Tkacik Does it mean that ODL's GUI read FlowNode tree and not the Node treaa?

kanika28 ( 2014-05-20 02:40:35 -0700 )edit

@kanika28 Yes, that is correct - currently to GUI only Flow capable nodes are exported.

Tony Tkacik ( 2014-05-20 10:09:14 -0700 )edit
Login/Signup to Answer

Stats

Asked: 2014-05-16 08:05:19 -0700

Seen: 925 times

Last updated: May 19 '14