Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
...
- 2.1 Apply cell to environment - PASS
- 2.2 Uninstalling Atomix - PASS
- 2.3 Uninstalling ONOS package - PASS
- 2.4 Building ONOS Docker image - PASS
- 2.5 Create Cluster Config - PASS
- 2.6 Installing Atomix via docker containers - PASS
- 2.7 Installing ONOS via docker containers - PASS
- 2.8 Set up ONOS secure SSH - PASS
- 2.9 Starting ONOS CLI sessions - PASS
- 2.10 Checking ONOS nodes - PASS
- 2.11 Checking ONOS applications - PASS
- 2.12 Set logging levels - PASS
- 2.13 Set ONOS configurations - PASS
- 2.14 Starting Mininet Topology - PASS
- 2.15 Configure switches in ONOS - PASS
- 2.16 Check number of topology elements - FAIL
- Unexpected number of links, switches, and/or controllers: The number of links, switches, nodes, and SCCs does not match what was expected
- ONOS sees 8 devices (8 expected) and 24 links (32 expected) and 1 controllers (1 expected) and 3 SCCs (1 expected)
- 2.17 Check whether the flow count is >= 350 - FAIL
- Flow count looks wrong; found 0, expecting at least 350
- 2.18 Check whether all flow status are ADDED - FAIL
- Flow status is wrong!
- 2.19 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4', u'h5', u'h6', u'h7', u'h8'] with tag CASE2 - PASS FAIL
- IP connectivity failed
- 2.20 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE2 - FAIL
- IP connectivity failed
- 2.21 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE2 - FAIL
- IP connectivity failed
- 2.22 Kill link between spine101 and leaf2 - PASS
- 2.23 Checking topology after link down - FAIL
- Topology after link down is incorrect
- 2.24 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4', u'h5', u'h6', u'h7', u'h8'] with tag CASE2_Failure - FAIL
- IP connectivity failed
- 2.25 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE2_Failure - FAIL
- IP connectivity failed
- 2.26 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE2_Failure - FAIL
- IP connectivity failed
- 2.27 Restore link between spine101 and leaf2 - FAIL
- Failed to bring link up
- 2.28 Check whether the flow count is >= 350 - FAIL
- Flow count looks wrong; found 0, expecting at least 350
- 2.29 Check whether all flow status are ADDED - FAIL
- Flow status is wrong!
- 2.30 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4', u'h5', u'h6', u'h7', u'h8'] with tag CASE2_Recovery - PASS
- 2.31 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE2_Recovery - FAIL
- IP connectivity failed
- 2.32 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE2_Recovery - FAIL
- IP connectivity failed
- 2.33 Check number of topology elements - FAIL
- Unexpected number of links, switches, and/or controllers: The number of links, switches, nodes, and SCCs does not match what was expected
- ONOS sees 8 devices (8 expected) and 24 links (32 expected) and 1 controllers (1 expected) and 3 SCCs (1 expected)
- 2.34 Stopping Mininet - PASS
- 2.35 Copying karaf logs - PASS
...