Uploaded image for project: 'ONOS'
  1. ONOS
  2. ONOS-3562

port number conversion error in flow stats REST API

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Done
    • Affects Version/s: 1.4.0
    • Fix Version/s: 1.4.0
    • Component/s: None
    • Labels:
    • Story Points:
      3
    • Epic Link:
    • Sprint:
      Emu Sprint 4 (11/23-12/18), Dead Sprint (Pre-Falcon)

      Description

      The Port and EtherType Values do not appear correlctly when requesting the Flow Stats from REST API

      If I look at Wireshark I see for instance an LLDP Packet in the flow-stats-reply with
      ethertype : 35020 (0x88cc)
      port out : 4294967293
      [see attached picture]

      the information that I think is supposed to be related to that, from the REST API (http://10.1.0.16:8181/onos/v1/flows) gives
      ether type: -30516
      port out: -3
      [see JSON output from REST Request below]

      ARP packets show similar values, the ARP Ethertype shows up correct in the REST Response, but also with some negative port Value.

      "flows": [
      {
      "id": "10414575354596821",
      "appId": "org.onosproject.core",
      "groupId": 0,
      "priority": 40000,
      "timeout": 0,
      "isPermanent": true,
      "deviceId": "of:0000000000000001",
      "state": "ADDED",
      "life": 241,
      "packets": 0,
      "bytes": 0,
      "lastSeen": 1449400662116,
      "treatment": {
      "instructions": [

      { "type": "OUTPUT", "port": -3 }

      ],
      "deferred": []
      },
      "selector": {
      "criteria": [

      { "type": "ETH_TYPE", "ethType": -30516 }

      ]
      }
      },
      {

        Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

            Assignee:
            andrea Andrea Campanella
            Reporter:
            freni Franziska Corradi
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: