Le lundi 10 juillet 2017, Abdelmuhaimen Seaudi <asea...@gmail.com <javascript:_e(%7B%7D,'cvml','asea...@gmail.com');>> a écrit :
> Hi, > > When I try to mount Junos 17.2 in ODL, Java process experiences very high > CPU utilization and I see the following logs in karaf. > If I'm not mistaking, That version of Junos contains a lot of schemas to be downloaded be ODL during session establishment, I faced the a similar issue reported here https://bugs.opendaylight.org/show_bug.cgi?id=8569 It boils down to the fact Yangtools is using a lot à resources to dynamically generate SchemaContext for the NETCONF device. > > What is the meaning of "Unexpected response to get-schema, expected > response with one child (urn:ietf:params:xml:ns:yang:i > etf-netconf-monitoring?revision=2010-10-04)data, but was > ImmutableContainerNode{nodeIdentifier=(urn:ietf:params:xml: > ns:yang:ietf-netconf-monitoring?revision=2010-10-04)output, value=[], > attributes={()message-id=m-61}}" ? > > Looks like ietf-netconf-monitoring get-schema rpc contatct was not respect by the device. The Roc defining is expecting one child node being "data" in the reply, but the device returns something different, in this case "output". This would be a Junos problem. HTH, Alexis > > > > > 2017-07-09 18:46:29,850 | WARN | oupCloseable-3-6 | > NetconfXMLToMessageDecoder | 124 - org.opendaylight.netconf.netty-util > - 1.1.3.Boron-SR3 | XML message with unwanted leading bytes detected. > Discarded the 1 leading byte(s): '0a' > > 2017-07-09 18:46:29,855 | DEBUG | oupCloseable-3-6 | > AbstractProtocolSession | 84 - > org.opendaylight.controller.protocol-framework > - 0.8.3.Boron-SR3 | Message was received: <rpc-reply > xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:junos=" > http://xml.juniper.net/junos/17.2R1/junos"; message-id="m-61"> > ...cut... > > 2017-07-09 18:46:29,855 | DEBUG | oupCloseable-3-6 | > AbstractNetconfSession | 124 - org.opendaylight.netconf.netty-util > - 1.1.3.Boron-SR3 | handling incoming message > > 2017-07-09 18:46:29,858 | DEBUG | oupCloseable-3-6 | > NetconfDeviceCommunicator | 289 - > org.opendaylight.netconf.sal-netconf-connector > - 1.4.3.Boron-SR3 | RemoteDevice{R1}: Message received <rpc-reply > xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:junos=" > http://xml.juniper.net/junos/17.2R1/junos"; message-id="m-61"> > ...cut... > > 2017-07-09 18:46:29,859 | DEBUG | oupCloseable-3-6 | > AbstractSchemaRepository | 87 - > org.opendaylight.yangtools.yang-model-util > - 1.0.3.Boron-SR3 | Failed to acquire source from > AbstractObjectRegistration{instance=org.opendaylight.yangtoo > ls.yang.model.repo.spi.PotentialSchemaSource@10147885} > java.lang.IllegalStateException: RemoteDevice{R1} Unexpected response to > get-schema, expected response with one child (urn:ietf:params:xml:ns:yang:i > etf-netconf-monitoring?revision=2010-10-04)data, but was > ImmutableContainerNode{nodeIdentifier=(urn:ietf:params:xml: > ns:yang:ietf-netconf-monitoring?revision=2010-10-04)output, value=[], > attributes={()message-id=m-61}} > > 2017-07-09 18:46:29,859 | DEBUG | oupCloseable-3-6 | > AbstractSchemaRepository | 87 - > org.opendaylight.yangtools.yang-model-util > - 1.0.3.Boron-SR3 | Failed to acquire source from > AbstractObjectRegistration{instance=org.opendaylight.yangtoo > ls.yang.model.repo.spi.PotentialSchemaSource@5e08e193} > org.opendaylight.yangtools.yang.model.repo.api.MissingSchemaSourceException: > All available providers exhausted > > > Abdelmuhaimen Seaudi, CCIE # 25265 > Email: asea...@gmail.com > Skype: aseaudi > LinkedIn: www.linkedin.com/in/aseaudi > Telephone: +2012 84644 733 > >
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
