Ask Your Question
0

Issues when mounting junos 17.2 in ODL

asked 2017-07-10 00:25:39 -0700

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.

What is the meaning of "Unexpected response to get-schema, expected response with one child (urn:ietf:params:xml:ns:yang:ietf-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,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.yangtools.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:ietf-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.yangtools.yang.model.repo.spi.PotentialSchemaSource@5e08e193} org.opendaylight.yangtools.yang.model.repo.api.MissingSchemaSourceException: All available providers exhausted

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2017-08-15 11:33:46 -0700

Contact your Juniper representative to obtain the JunOS 17.4 build (or whatever newer build that is recommended at that time).

The configuration yang model is vastly improved, and mounting time into a new directory / new mount will complete within minutes. Tip: be absolutely certain that there are no identically-named yang models in the cache directory you're mounting to. (i.e., never use the default; always use a named directory)

...add to your node body when first mounting...

<schema-cache-directory xmlns="urn:opendaylight:netconf-node-topology">YOUR-NODE-DIR-NAME-HERE</schema-cache-directory>

...

edit flag offensive delete publish link more
Login/Signup to Answer

Question Tools

Follow
1 follower

Stats

Asked: 2017-07-10 00:25:39 -0700

Seen: 18 times

Last updated: Aug 15