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

Port latency regression after upgrading Karaf to 4.2.2

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 2.0.0
    • Fix Version/s: 2.0.0
    • Component/s: None
    • Environment:

      3770b0815702cd1a7a1f4e2dada63cbc37fc109d

    • Story Points:
      2

      Description

      Port down latency got doubled after Karaf 4.2.2 upgrade. Specifically:

      • Latency between OF handshake and DEVICE event increased by 2-3ms
      • Latency between DEVICE event to LINK event doesn't seem to be affected
      • Latency between LINK event to GRAPH event increased by 2-3ms

      Steps to reproduce on BMs:
      1. Start ONOS with “drivers,openflow,metrics”

      2. Configure ONOS

      • cfg set org.onosproject.net.topology.impl.DefaultTopologyProvider maxEvents 1
      • cfg set org.onosproject.net.topology.impl.DefaultTopologyProvider maxBatchMs 0
      • cfg set org.onosproject.net.topology.impl.DefaultTopologyProvider maxIdleMs 0

      3. Start Mininet

      • sudo mn --custom ~/mininet/custom/topo-perf-2sw.py --topo mytopo --controller remote
      • sudo ovs-vsctl set-controller s1 tcp:10.192.19.68:6653
      • sudo ovs-vsctl set-controller s2 tcp:10.192.19.68:6653

      4. Link up/down

      • “s1 ifconfig s1-eth1 down”
      • Check latency from "Received port status message" in karaf.log to Graph Event timestamp in “topology-events-metrics" CLI command
      • “s1 ifconfig s1-eth1 up”

        Attachments

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

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            You You Wang (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: