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

controller port visualized uncorrectly into ONOS CLI

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Done
    • Affects Version/s: 1.0.0, 1.0.1
    • Fix Version/s: 1.0.1, 1.1.0
    • Component/s: None
    • Labels:
      None
    • Environment:

      all

    • Epic Link:
    • Sprint:
      Blackbird Sprint 2 (Jan 5-16)

      Description

      When typing "flows" in the ONOS CLI, the controller port is shown as following (do not consider in the output below the Ethernet type - which is clearly wrong):
      onos> flows
      deviceId=of:5e3e486e73000187, flowRuleCount=3
      id=10000da2e116d, state=ADDED, bytes=0, packets=-1, duration=546, priority=40000, appId=org.onosproject.net.proxyarp
      selector=[ETH_TYPE

      {ethType=806}

      ]
      treatment=[OUTPUT

      {port=18446744073709551613}]
      id=20000da1ea967, state=ADDED, bytes=0, packets=-1, duration=546, priority=40000, appId=org.onosproject.provider.lldp
      selector=[ETH_TYPE{ethType=ffffffffffff88cc}]
      treatment=[OUTPUT{port=18446744073709551613}

      ]
      id=20000da1eb7b1, state=ADDED, bytes=0, packets=-1, duration=546, priority=40000, appId=org.onosproject.provider.lldp
      selector=[ETH_TYPE

      {ethType=ffffffffffff8942}

      ]
      treatment=[OUTPUT

      {port=18446744073709551613}

      ]

      We need to translate this number into something like "to controller".
      This is just for cosmetic. The port number is anyway "correct" on the switches.

        Attachments

        # Subject Branch Project Status CR V

          Activity

            People

            Assignee:
            ray Ray Milkey
            Reporter:
            luca Luca Prete
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: