Page History

...

• 2.1 Assign switches to controllers - PASS

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

• 8.1 Create TestONTopology object - PASS
• 8.2 Comparing ONOS topology to MN - No Result
• 8.3 Collecting topology information from ONOS - PASS
• 8.4 Hosts view is consistent across all ONOS nodes - PASS
• 8.5 Hosts information is correct - PASS
• 8.6 Host attachment points to the network - PASS
• 8.7 Clusters view is consistent across all ONOS nodes - PASS
• 8.8 There is only one SCC - FAIL
• ONOS shows 15 SCCs
• PASS
• 8.9 Device information is correct - PASS
• 8.10 Port information is correct - FAIL
Port information is incorrect
• PASS
• 8.11 Links are correct - FAIL
Links are incorrect
• PASS
• 8.12 Checking ONOS nodes - PASS

Case 21: Assigning Controller roles for switches -

...

PASS

Check that ONOS is connected to each device. Then manually assign mastership to specific ONOS nodes using 'device-role'

• 21.1 Assign mastership of switches to specific controllers - PASS
• 21.2 Check mastership was correctly assigned - FAIL
• Switches were not successfully reassigned
• PASS

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

• 8.1 Create TestONTopology object - PASS
• 8.2 Comparing ONOS topology to MN - No Result
• 8.3 Collecting topology information from ONOS - PASS
• 8.4 Hosts view is consistent across all ONOS nodes - PASS
• 8.5 Hosts information is correct - PASS
• 8.6 Host attachment points to the network - PASS
• 8.7 Clusters view is consistent across all ONOS nodes - PASS
• 8.8 There is only one SCC - PASS
• 8.9 Device information is correct - PASS
• 8.10 Port information is correct - FAIL
Port information is incorrect
• PASS
• 8.11 Links are correct - PASS
• 8.12 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 ) - FAIL
Reactive Pingall failed, one or more ping pairs failed
• PASS
• 3.4 Uninstall reactive forwarding app - PASS
• 3.5 Check app ids - PASS
• 3.6 Add host intents via cli - PASS
• 3.7 Intent Anti-Entropy dispersion - FAIL
• Intent ECM anti-entropy took too long

...

• 4.1 Ping across added host intents - FAIL
• Intents have not been installed correctly, pings failed.
• PASS
• 4.2 Check Intent state - PASS FAIL
• Intents are not all in INSTALLED state
• 4.3 Check leadership of topics - FAIL
• Some topics were lost
• 4.4 Wait a minute then ping again - FAIL
Intents have not been installed correctly, pings failed.
• .4 Wait a minute then ping again - PASS

Case 5: Setting up and gathering data for current state - FAIL

...

• 5.1 Check that each switch has a master - PASS
• 5.2 Get the Mastership of each switch from each controller - PASS
• 5.3 Check for consistency in roles from each controller - PASS
• 5.4 Get the intents from each controller - PASS
• 5.5 Check for consistency in Intents from each controller - FAIL
• ONOS nodes have different views of intents
• 5.6 Get the flows from each controller - PASS
• 5.7 Check for consistency in Flows from each controller - PASS
• 5.8 Get the OF Table entries - No Result
• 5.9 Start continuous pings - No Result
• 5.10 Create TestONTopology object - No Result
• 5.11 Collecting topology information from ONOS - No Result
• 5.12 Host view is consistent across ONOS nodes - PASS
• 5.13 Each host has an IP address - PASS
• 5.14 Cluster view is consistent across ONOS nodes - PASS
• 5.15 Cluster view correct across ONOS nodes - PASS
• 5.16 Comparing ONOS topology to MN - FAIL
Topology Check Test NOT successful
• PASS

Case 14: Start Leadership Election app - PASS

...

Case 6: Wait 60 seconds instead of inducing a failure - PASS

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

• 8.1 Create TestONTopology object - PASS
• 8.2 Comparing ONOS topology to MN - No Result
• 8.3 Collecting topology information from ONOS - PASS
• 8.4 Hosts view is consistent across all ONOS nodes - PASS
• 8.5 Hosts information is correct - PASS
• 8.6 Host attachment points to the network - PASS
• 8.7 Clusters view is consistent across all ONOS nodes - PASS
• 8.8 There is only one SCC - PASS
• 8.9 Device information is correct - PASS
• 8.10 Port information is correct - FAIL
• Port information is incorrect
• PASS
• 8.11 Links are correct - PASS
• 8.12 Checking ONOS nodes - PASS

...

• 7.1 Check that each switch has a master - PASS
• 7.2 Read device roles from ONOS - PASS
• 7.3 Check for consistency in roles from each controller - PASS
• 7.4 Compare switch roles from before failure - FAIL
• Mastership of some switches changed
• PASS
• 7.5 Get the intents and compare across all nodes - PASS
• 7.6 Check for consistency in Intents from each controller - FAIL
• ONOS nodes have different views of intents
• 7.7 Compare current intents with intents before the failure - FAIL
• The Intents changed during failure
• 7.8 Get the OF Table entries and compare to before component failure - FAIL
• Changes were found in the flow tables
• PASS
• 7.9 Check the continuous pings to ensure that no packets were dropped during component failure - FAIL
Loss of dataplane connectivity detected
• PASS
• 7.10 Leadership Election is still functional - PASS

...

• 15.1 Check that each node shows the same leader - PASS
• 15.2 Find current leader and withdraw - PASS
• 15.3 Make sure new leader is elected - PASS
• 15.4 Run for election on old leader( just so everyone is in the hat ) - PASS
• 15.5 Leader did not change when old leader re-ran - PASS

Case 17: Check for basic functionality with distributed primitives -

...

PASS

Test the methods of the distributed primitives (counters and sets) throught the cli

• 17.1 Increment and get a default counter on each node - FAIL
Error incrementing default counter
• PASS
• 17.2 Increment and get an in memory counter on each node - PASS
• 17.3 Check counters are consistant across nodes - PASS
• 17.4 Counters we added have the correct values - PASS
• 17.5 Distributed Set get - PASS
• 17.6 Distributed Set size - PASS
• 17.7 Distributed Set add() - PASS
• 17.8 Distributed Set addAll() - PASS
• 17.9 Distributed Set contains() - PASS
• 17.10 Distributed Set containsAll() - PASS
• 17.11 Distributed Set remove() - PASS
• 17.12 Distributed Set removeAll() - PASS
• 17.13 Distributed Set addAll() - PASS
• 17.14 Distributed Set clear() - PASS
• 17.15 Distributed Set addAll() - PASS
• 17.16 Distributed Set retain() - PASS

...

• 9.1 Kill Link between s3 and s28 - PASS

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

• 8.1 Create TestONTopology object - PASS
• 8.2 Comparing ONOS topology to MN - No Result
• 8.3 Collecting topology information from ONOS - PASS
• 8.4 Hosts view is consistent across all ONOS nodes - PASS
• 8.5 Hosts information is correct - PASS
• 8.6 Host attachment points to the network - PASS
• 8.7 Clusters view is consistent across all ONOS nodes - PASS
• 8.8 There is only one SCC - PASS
• 8.9 Device information is correct - PASS
• 8.10 Port information is correct - FAIL
• Port information is incorrect
• PASS
• 8.11 Links are correct - PASS
• 8.12 Checking ONOS nodes - PASS

...

• 10.1 Bring link between s3 and s28 back up - PASS

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

• 8.1 Create TestONTopology object - PASS
• 8.2 Comparing ONOS topology to MN - No Result
• 8.3 Collecting topology information from ONOS - PASS
• 8.4 Hosts view is consistent across all ONOS nodes - PASS
• 8.5 Hosts information is correct - PASS
• 8.6 Host attachment points to the network - PASS
• 8.7 Clusters view is consistent across all ONOS nodes - PASS
• 8.8 There is only one SCC - PASS
• 8.9 Device information is correct - PASS
• 8.10 Port information is correct - FAIL
Port information is incorrect
• PASS
• 8.11 Links are correct - PASS
• 8.12 Checking ONOS nodes - PASS

...

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 -

...

PASS

Compare topology objects between Mininet and ONOS

• 8.1 Create TestONTopology object - PASS
• 8.2 Comparing ONOS topology to MN - No Result
• 8.3 Collecting topology information from ONOS - PASS
• 8.4 Hosts view is consistent across all ONOS nodes - PASS
• 8.5 Hosts information is correct - PASS
• 8.6 Host attachment points to the network - PASS
• 8.7 Clusters view is consistent across all ONOS nodes - PASS
• 8.8 There is only one SCC - PASS
• 8.9 Device information is correct - PASS
• 8.10 Port information is correct - FAIL
• Port information is incorrect
• PASS
• 8.11 Links are correct - PASS
• 8.12 Checking ONOS nodes - PASS

...

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 -

...

PASS

Compare topology objects between Mininet and ONOS

• 8.1 Create TestONTopology object - PASS
• 8.2 Comparing ONOS topology to MN - No Result
• 8.3 Collecting topology information from ONOS - PASS
• 8.4 Hosts view is consistent across all ONOS nodes - PASS
• 8.5 Hosts information is correct - PASS
• 8.6 Host attachment points to the network - PASS
• 8.7 Clusters view is consistent across all ONOS nodes - PASS
• 8.8 There is only one SCC - PASS
• 8.9 Device information is correct - PASS
• 8.10 Port information is correct - FAIL
Port information is incorrect
• PASS
• 8.11 Links are correct - PASS
• 8.12 Checking ONOS nodes - PASS

...