why netconf connector rpc call failed?

asked 2015-07-14 05:01:41 -0800

yyang13 gravatar image

Hi, All

I found netconf-connector netconf rpc call failure,

2015-07-15 01:55:55,515 | WARN | oupCloseable-6-8 | KeepaliveSalFacade | 319 - org.opendaylight.controller.sal-netconf-connector - 1.3.0.SNAPSHOT | RemoteDevice{netopeer}: Rpc failure detected. Reconnecting netconf session java.lang.IllegalStateException: Unknown child(ren) node(s) detected, identified by: (urn:ietf:params:xml:ns:netconf:base:1.0)data, in: container output

Anybody knows why it failed? What are the possible root causes? It makes me scratch my head all day, sincerely appreciate your help in advance. The details are following.

I developed a netopeer module for netconf server, it implemented two RPCs, I can use netopeer client to call these two APIs, the output is below.

netopeer-server[28628]: Received message (session 3): <rpc message-id="1" xmlns="urn.intel.params:xml:ns:sf-desc-mon-rpt"> <get-sf-description> </get-sf-description></rpc> netopeer-server[28628]: Calling get-SF-description RPC function netopeer-server[28628]: Writing message (session 3): <rpc-reply message-id="1" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <data> <description-info xmlns="urn.intel.params:xml:ns:sf-desc-mon-rpt"> <sf-description> <capabilities> <ports-bandwidth> <port-bandwidth> <port-id>1</port-id> <ipaddress>10.0.0.1</ipaddress> <macaddress>00:1e:67:a2:5f:f4</macaddress> <supported-bandwidth>20</supported-bandwidth> </port-bandwidth> <port-bandwidth> <port-id>2</port-id> <ipaddress>10.0.0.2</ipaddress> <macaddress>01:1e:67:a2:5f:f6</macaddress> <supported-bandwidth>10</supported-bandwidth> </port-bandwidth> </ports-bandwidth> <supported-packet-rate>5</supported-packet-rate> <supported-bandwidth>10</supported-bandwidth> <supported-acl-number>2000</supported-acl-number> <fib-size>100</fib-size> <rib-size>200</rib-size> </capabilities> <mgt-ip-address>10.0.0.2</mgt-ip-address> <type>DPI</type> <number-of-dataports>2</number-of-dataports> </sf-description> </description-info> </data> </rpc-reply>

netopeer-server[28628]: Received message (session 3): <rpc message-id="2" xmlns="urn.intel.params:xml:ns:sf-desc-mon-rpt"> <get-sf-monitoring-info> </get-sf-monitoring-info></rpc> netopeer-server[28628]: Calling get-SF-monitoring-info RPC function netopeer-server[28628]: Writing message (session 3): <rpc-reply message-id="2" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <data> <monitoring-info xmlns="urn.intel.params:xml:ns:sf-desc-mon-rpt"> <sf-monitoring-info> <resource-utilization> <sf-ports-bandwidth-utilization> <port-bandwidth-utilization> <port-id>1</port-id> <bandwidth-utilization>20</bandwidth-utilization> </port-bandwidth-utilization> <port-bandwidth-utilization> <port-id>2</port-id> <bandwidth-utilization>30</bandwidth-utilization> </port-bandwidth-utilization> </sf-ports-bandwidth-utilization> <packet-rate-utilization>10</packet-rate-utilization> <bandwidth-utilization>15</bandwidth-utilization> <cpu-utilization>12</cpu-utilization> <memory-utilization>17</memory-utilization> <available-memory>8</available-memory> <rib-utilization>20</rib-utilization> <fib-utilization>25</fib-utilization> <power-utilization>30</power-utilization> </resource-utilization> <liveness>true</liveness> </sf-monitoring-info> </monitoring-info> </data> </rpc-reply>

But when I called netconf rpc get-SF-description in SFC, I found netopeer showed the below info after output reply message:

Input channel error

This indicated ssh connection is broken, I checked SFC karaf log, found the blow log:

319 - org.opendaylight.controller.sal-netconf-connector - 1.3.0.SNAPSHOT | RemoteDevice{netopeer}: Rpc failure detected. Reconnecting netconf session java.lang.IllegalStateException: Unknown child(ren) node(s) detected, identified by: (urn:ietf:params:xml:ns:netconf:base:1.0)data, in: container output at com.google.common.base.Preconditions.checkState(Preconditions.java:197)[97:com.google.guava:18.0.0] at org.opendaylight.yangtools.yang.data.impl.schema.SchemaUtils.findSchemaForChild(SchemaUtils.java:109)[121:org.opendaylight.yangtools.yang-data-impl:0.8.0.SNAPSHOT] at org.opendaylight.yangtools.yang.data.impl.schema.SchemaUtils.findSchemaForChild(SchemaUtils.java:91)[121:org.opendaylight.yangtools.yang-data-impl:0.8.0.SNAPSHOT] at org.opendaylight.yangtools.yang.data.impl.schema.SchemaUtils ... (more)

edit retag flag offensive close merge delete