Page History

...

commit d1cdd1953031452b200b80330382eb2889d3a067 4f4d25a4b829d8a9eacff3dafd13358855f011dc (HEAD, tag: 1.4.0-rc3origin/master, origin/HEAD, master)
Author: Brian O'Connor [bocon@onlab.ussamueljcc [jiangchuncheng@huawei.com]
AuthorDate: Tue Mon Dec 15 157 10:3652:45 28 2015 -+0800
Commit: Brian O'Connor [bocon@onlabGerrit Code Review [gerrit@onlab.us]
CommitDate: Tue Wed Dec 15 1516 20:3601:45 29 2015 -0800
Tagging 1.4.0-rc3+0000

[ONOS-2860] ONOSFW L3 uses ARP table as arp proxy. It need modify ARP

<iframe src="https://onos-jenkins.onlab.us/job/HAclusterRestart/plot/Plot-HA/getPlot?index=0&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe>

...

• 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

...

• 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 Get the intents and compare across all nodes - PASS
• 7.5 Check for consistency in Intents from each controller - PASS
• 7.6 Get the OF Table entries and compare to before component failure - FAIL
• Changes were found in the flow tables
• 7.7 Leadership Election is still functional - PASS

Case 4: Verify connectivity by sendind traffic across Intents -

...

FAIL

Ping across added host intents to check functionality and check the state of the intent

• 4.1 Ping across added host intents - PASS 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 - PASS FAIL
• Intents have not been installed correctly, pings failed.

Case 15: Check that Leadership Election is still functional - PASS

...

• 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 - PASS 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
• 8.6 There is only one SCC - PASS FAIL
• ONOS shows 3 SCCs
• 8.7 Device information is correct - PASS FAIL
• Device information is incorrect
• 8.8 Links are correct - PASS FAIL
• Links are incorrect
• 8.9 Checking ONOS nodes - PASS

Case 4: Verify connectivity by sendind traffic across Intents -

...

FAIL

Ping across added host intents to check functionality and check the state of the intent

• 4.1 Ping across added host intents - PASS 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 - PASS FAIL
• Intents have not been installed correctly, pings failed.

Case 10: Restore a link to ensure that Link Discovery is working properly - PASS

...

• 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 - PASS 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
• 8.6 There is only one SCC - PASS 8.7 Device information is correct - PASS - FAIL
• ONOS shows 3 SCCs
• 8.7 Device information is correct - FAIL
• Device information is incorrect
• 8.8 Links are correct - PASS FAIL
• Links are incorrect
• 8.9 Checking ONOS nodes - PASS

Case 4: Verify connectivity by sendind traffic across Intents -

...

FAIL

Ping across added host intents to check functionality and check the state of the intent

• 4.1 Ping across added host intents - PASS 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 - PASS 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 - PASS 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
• 8.6 There is only one SCC - PASS FAIL
• ONOS shows 3 SCCs
• 8.7 Device information is correct - PASS FAIL
• Device information is incorrect
• 8.8 Links are correct - PASS FAIL
• Links are incorrect
• 8.9 Checking ONOS nodes - PASS

Case 4: Verify connectivity by sendind traffic across Intents -

...

FAIL

Ping across added host intents to check functionality and check the state of the intent

• 4.1 Ping across added host intents - FAIL
• Intents have not been installed correctly, pings failed.
4.1 Ping across added host intents - PASS
• 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 - PASS 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 - PASS 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
• 8.6 There is only one SCC - PASS FAIL
• ONOS shows 3 SCCs
• 8.7 Device information is correct - PASS FAIL
• Device information is incorrect
• 8.8 Links are correct - PASS FAIL
• Links are incorrect
• 8.9 Checking ONOS nodes - PASS

Case 4: Verify connectivity by sendind traffic across Intents -

...

FAIL

Ping across added host intents to check functionality and check the state of the intent

• 4.1 Ping across added host intents - PASS 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 - PASS FAIL
• Intents have not been installed correctly, pings failed.

Case 13: Test Cleanup - PASS

...