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.
...
- 6.1 Checking ONOS Logs for errors - No Result
- 6.2 Killing ONOS nodes - PASS
- 6.3 Checking if ONOS is up yet - PASS
Case 8: Compare ONOS Topology view to Mininet topology -
...
FAIL
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - PASS
- 8.2 Hosts view is consistent across all ONOS nodes - PASS
- 8.3 Hosts information is correct - PASS
- 8.4 Host attachment points to the network - PASS
- 8.5 Clusters view is consistent across all ONOS nodes - PASS FAIL
- ONOS nodes have different views of clusters
- 8.6 There is only one SCC - PASS
- 8.7 Device information is correct - PASS
- 8.8 Links are correct - PASS
- 8.9 Checking ONOS nodes - PASS
...
- 3.1 Install reactive forwarding app - PASS
- 3.2 Check app ids - PASS
- 3.3 Discovering Hosts( Via pingall for now ) - PASS
- 3.4 Uninstall reactive forwarding app - PASS
- 3.5 Check app ids - PASS
- 3.6 Add host intents via cli - FAIL Error looking up host ids
- PASS
- 3.7 Intent Anti-Entropy dispersion - PASS FAIL
Case 7: Running ONOS Constant State Tests - FAIL
...
- 4.1 Ping across added host intents - FAIL
- Intents have not been installed correctly, pings failed.
- 4.2 Check Intent state - PASS FAIL
- Intents are not all in INSTALLED state
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - FAIL
- Intents have not been installed correctly, pings failed.
...
- 9.1 Kill Link between s3 and s28 - PASS
Case 8: Compare ONOS Topology view to Mininet topology - FAIL
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - FAIL
- ONOS topology don't match Mininet
- 8.2 Hosts view is consistent across all ONOS nodes - PASS
- 8.3 Hosts information is correct - PASS
- 8.4 Host attachment points to the network - PASS
- 8.5 Clusters view is consistent across all ONOS nodes - PASS FAIL
- ONOS nodes have different views of clusters
- 8.6 There is only one SCC - FAIL
- ONOS shows 2 3 SCCs
- 8.7 Device information is correct - FAIL
- Device information is incorrect
- 8.8 Links are correct - FAIL
- Links are incorrect
- 8.9 Checking ONOS nodes - PASS
...
- 4.1 Ping across added host intents - FAIL
- Intents have not been installed correctly, pings failed.
- 4.2 Check Intent state - PASS FAIL
- Intents are not all in INSTALLED state
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - FAIL
- Intents have not been installed correctly, pings failed.
...
- 10.1 Bring link between s3 and s28 back up - PASS
Case 8: Compare ONOS Topology view to Mininet topology - FAIL
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - FAIL
- ONOS topology don't match Mininet
- 8.2 Hosts view is consistent across all ONOS nodes - PASS
- 8.3 Hosts information is correct - PASS
- 8.4 Host attachment points to the network - PASS
- 8.5 Clusters view is consistent across all ONOS nodes - PASS FAIL
- ONOS nodes have different views of clusters
- 8.6 There is only one SCC - FAIL
- ONOS shows 2 3 SCCs
- 8.7 Device information is correct - FAIL
- Device information is incorrect
- 8.8 Links are correct - FAIL
- Links are incorrect
- 8.9 Checking ONOS nodes - PASS
...
- 4.1 Ping across added host intents - FAIL
- Intents have not been installed correctly, pings failed.
- 4.2 Check Intent state - PASS FAIL
- Intents are not all in INSTALLED state
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - FAIL
- Intents have not been installed correctly, pings failed.
Case 11: Killing a switch to ensure it is discovered correctly - PASS
- 11.1 Kill s5 - PASS
Case 8: Compare ONOS Topology view to Mininet topology - FAIL
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - FAIL
- ONOS topology don't match Mininet
- 8.2 Hosts view is consistent across all ONOS nodes - PASS
- 8.3 Hosts information is correct - PASS
- 8.4 Host attachment points to the network - PASS
- 8.5 Clusters view is consistent across all ONOS nodes - PASS FAIL
- ONOS nodes have different views of clusters
- 8.6 There is only one SCC - FAIL
- ONOS shows 2 3 SCCs
- 8.7 Device information is correct - FAIL
- Device information is incorrect
- 8.8 Links are correct - FAIL
- Links are incorrect
- 8.9 Checking ONOS nodes - PASS
...
- 4.1 Ping across added host intents - FAIL
- Intents have not been installed correctly, pings failed.
- 4.2 Check Intent state - PASS FAIL
- Intents are not all in INSTALLED state
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - FAIL
- Intents have not been installed correctly, pings failed.
Case 12: Adding a switch to ensure it is discovered correctly - PASS
- 12.1 Add back s5 - PASS
Case 8: Compare ONOS Topology view to Mininet topology - FAIL
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - FAIL
- ONOS topology don't match Mininet
- 8.2 Hosts view is consistent across all ONOS nodes - PASS
- 8.3 Hosts information is correct - PASS
- 8.4 Host attachment points to the network - PASS
- 8.5 Clusters view is consistent across all ONOS nodes - PASS FAIL
- ONOS nodes have different views of clusters
- 8.6 There is only one SCC - FAIL
- ONOS shows 2 3 SCCs
- 8.7 Device information is correct - FAIL
- Device information is incorrect
- 8.8 Links are correct - FAIL
- Links are incorrect
- 8.9 Checking ONOS nodes - PASS
...
- 4.1 Ping across added host intents - FAIL
- Intents have not been installed correctly, pings failed.
- 4.2 Check Intent state - PASS FAIL
- Intents are not all in INSTALLED state
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - FAIL
- Intents have not been installed correctly, pings failed.
...