Trying to get RESTCONF/MD-SAL notification "packet-in-message"

asked 2017-08-29 12:23:06 -0800

mdeazley gravatar image

I observe the the file openflow-protocol.yang contains the the notification for what I hope is OpenFlow PACKET_IN messages:

notification packet-in-message {
            uses packet-in;
         /* Async message */
 }

But when I try to POST a create-data-change-event-subscription ...

POST: http://localhost:8181/restconf/operations/sal-remote:create-data-change-event-subscription

Request Headers:
  Content-Type:application/json
  Authorization:Basic YWRtaW46YWRtaW4=
  Accept:application/json

Body:
{
    "input": {
        "path": "/openflow-protocol:openflow-protocol/packet-in-message",
        "sal-remote-augment:datastore": "OPERATIONAL",
        "sal-remote-augment:scope": "SUBTREE",
        "sal-remote-augment:notification-output-type": "JSON"
    }
}

I get a 404 "Bad Request" with the response:

"errors": {
        "error": [
            {
                "error-type": "protocol",
                "error-tag": "malformed-message",
                "error-message": "Error parsing input: Could not parse Instance Identifier '/openflow-protocol:openflow-protocol/packet-in-message'. Offset: 36 : Reason: (urn:opendaylight:openflow:protocol?revision=2013-07-31)openflow-protocol is not correct schema node identifier.",
                "error-info": "java.lang.IllegalArgumentException: Could not parse Instance Identifier '/openflow-protocol:openflow-protocol/packet-in-message'. Offset: 36 : Reason: (urn:opendaylight:openflow:protocol?revision=2013-07-31)openflow-protocol is not correct schema node identifier.   ... <Stack dump left out>"
            }
         ]
   }
  • Is this notification exposed in RESTCONF?
  • If so, what is the correct "Instance Identifier" in this case?
edit retag flag offensive close merge delete