Thanks Jozef. I was giving wrong node id. 

 

Now, with "get-flow-statistics",  I am observing error as given below with
some of the flows (flows having fields like "actions=resubmit(,17),
ct_state=+inv+trk"). This works fine with other flows.

 

Problem is observed with below flows and "get-flow-statistics" POST request
as specified below:

 

cookie=0x1080000, duration=1622.682s, table=19, n_packets=0, n_bytes=0,
priority=100,arp,arp_op=2 actions=CONTROLLER:65535,resubmit(,17)

cookie=0x1080000, duration=1622.679s, table=19, n_packets=0, n_bytes=0,
priority=100,arp,arp_op=1 actions=CONTROLLER:65535,resubmit(,17)

cookie=0x1080000, duration=1622.681s, table=19, n_packets=0, n_bytes=0,
priority=0 actions=resubmit(,17)

 

POST
http://localhost:8181/restconf/operations/opendaylight-direct-statistics:get
-flow-statistics

             {

    "input": 

    { 

        "node" :
"/opendaylight-inventory:nodes/opendaylight-inventory:node[opendaylight-inve
ntory:id=\"openflow:229348208920213\"]" ,

"table_id":19,

        "store-stats" : false

    } 

}

 

Error observed is as below:

org.opendaylight.yangtools.binding.data.codec.impl.IncorrectNestingException
: Supplied class interface
org.opendaylight.yang.gen.v1.urn.opendaylight.openflowplugin.extension.nicir
a.action.rev140714.flows.statistics.update.flow.and.statistics.map.list.inst
ructions.instruction.instruction.apply.actions._case.apply.actions.action.ac
tion.NxActionResubmitNotifFlowsStatisticsUpdateApplyActionsCase is not valid
case

               at
org.opendaylight.yangtools.binding.data.codec.impl.IncorrectNestingException
.create(IncorrectNestingException.java:28)

               at
org.opendaylight.yangtools.binding.data.codec.impl.DataContainerCodecContext
.childNonNull(DataContainerCodecContext.java:180)

               at
org.opendaylight.yangtools.binding.data.codec.impl.ChoiceNodeCodecContext.st
reamChild(ChoiceNodeCodecContext.java:110)

               at
org.opendaylight.yangtools.binding.data.codec.impl.BindingToNormalizedStream
Writer.enter(BindingToNormalizedStreamWriter.java:74)

               at
org.opendaylight.yangtools.binding.data.codec.impl.BindingToNormalizedStream
Writer.startCase(BindingToNormalizedStreamWriter.java:144)

               at
org.opendaylight.yang.gen.v1.urn.opendaylight.openflowplugin.extension.nicir
a.action.rev140714.flows.statistics.update.flow.and.statistics.map.list.inst
ructions.instruction.instruction.apply.actions._case.apply.actions.action.ac
tion.NxActionResubmitNotifFlowsStatisticsUpdateApplyActionsCase$StreamWriter
.serialize(DataObjectSerializerPrototype.java)

               at
org.opendaylight.yangtools.binding.data.codec.impl.BindingNormalizedNodeCode
cRegistry$DataObjectSerializerProxy.serialize(BindingNormalizedNodeCodecRegi
stry.java:295)

               at
org.opendaylight.yangtools.binding.data.codec.util.ChoiceDispatchSerializer.
serialize(ChoiceDispatchSerializer.java:47)

               at
org.opendaylight.yang.gen.v1.urn.opendaylight.action.types.rev131112.action.
list.Action$StreamWriter.serialize(DataObjectSerializerPrototype.java)

               at
org.opendaylight.yang.gen.v1.urn.opendaylight.flow.types.rev131026.instructi
on.instruction.apply.actions._case.ApplyActions$StreamWriter.serialize(DataO
bjectSerializerPrototype.java)

               at
org.opendaylight.yang.gen.v1.urn.opendaylight.flow.types.rev131026.instructi
on.instruction.ApplyActionsCase$StreamWriter.serialize(DataObjectSerializerP
rototype.java)

               at
org.opendaylight.yangtools.binding.data.codec.impl.BindingNormalizedNodeCode
cRegistry$DataObjectSerializerProxy.serialize(BindingNormalizedNodeCodecRegi
stry.java:295)

               at
org.opendaylight.yangtools.binding.data.codec.util.ChoiceDispatchSerializer.
serialize(ChoiceDispatchSerializer.java:47)

               at
org.opendaylight.yang.gen.v1.urn.opendaylight.flow.types.rev131026.instructi
on.list.Instruction$StreamWriter.serialize(DataObjectSerializerPrototype.jav
a)

               at
org.opendaylight.yang.gen.v1.urn.opendaylight.flow.types.rev131026.flow.Inst
ructions$StreamWriter.serialize(DataObjectSerializerPrototype.java)

               at
org.opendaylight.yang.gen.v1.urn.opendaylight.flow.statistics.rev130819.flow
.and.statistics.map.list.FlowAndStatisticsMapList$StreamWriter.serialize(Dat
aObjectSerializerPrototype.java)

               at
org.opendaylight.yang.gen.v1.urn.opendaylight.direct.statistics.rev160511.Ge
tFlowStatisticsOutput$StreamWriter.serialize(DataObjectSerializerPrototype.j
ava)

               at
org.opendaylight.yangtools.binding.data.codec.impl.BindingNormalizedNodeCode
cRegistry$DataObjectSerializerProxy.serialize(BindingNormalizedNodeCodecRegi
stry.java:295)

 

Thanks,

Shashidhar

 

From: Jozef Bacigál [mailto:[email protected]] 
Sent: 10 November 2016 18:51
To: Shashidhar R <[email protected]>;
[email protected]
Subject: RE: [openflowplugin-dev] opendaylight-direct-statistics REST calls
are not working

 

I tried it out and you probably used wrong node id. If I send this request
with wrong node id I get the same error that you got, otherwise it is
working.

 

Jozef

 

From: Shashidhar R [mailto:[email protected]] 
Sent: Thursday, November 10, 2016 11:30 AM
To: [email protected]
<mailto:[email protected]> 
Subject: [openflowplugin-dev] opendaylight-direct-statistics REST calls are
not working

 

Hello,

 

I am trying to get "node-connector-statistics" using below RPC call with
latest ODL/boron:

 

POST
http://localhost:8181/restconf/operations/opendaylight-direct-statistics:get
-node-connector-statistics

{

    "input": 

    { 

        "node" :
"/opendaylight-inventory:nodes/opendaylight-inventory:node[opendaylight-inve
ntory:id='openflow:159256663026689']" ,

        "store-stats" : false

    } 

}

 

Response is always as shown below:

 

{

  "errors": {

    "error": [

      {

        "error-type": "application",

        "error-tag": "operation-not-supported",

        "error-message": "No local or remote implementation available for
rpc
AbsoluteSchemaPath{path=[(urn:opendaylight:direct:statistics?revision=2016-0
5-11) get-node-connector-statistics]}"

      }

    ]

  }

}

 

Same behaviour is observed with "get-flow-statistics" and
"get-group-statistics" RPC calls.  

 

Am I missing something here? Or any configurations need to be done?

 

Thanks,

Shashidhar

JozefBacigál

Software Engineer


Sídlo / Mlynské Nivy 56 / 821 05 Bratislava / Slovakia
R&D centrum / Janka Kráľa 9 /  974 01 Banská Bystrica / Slovakia
+421 908 766 972 / [email protected]
<mailto:[email protected]> 
reception: +421 2 206 65 114 / www.pantheon.sk <http://www.pantheon.sk> 

  <http://www.pantheon.sk/fileadmin/templates/img/logo.png> 

 

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
openflowplugin-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev

Reply via email to