-
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
-
Labels:
-
Environment:
de64cce035b1620dc5dd225cd13942e700efec51
-
Story Points:3
-
Epic Link:
It takes longer time (25%~300%) for ONOS to discover switch/port up/down events after upgrading to Atomix 3.1
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 “topology-events-metrics” from CLI (e.g. delay between Device and Graph Event Timestamp)
- “s1 ifconfig s1-eth1 up”