Page History

...

• 100.1 Starting Mininet Topology - PASS
• 100.2 Connect switches to controller - PASS
• 100.3 Set up tunnel from Mininet node to onos node - No Result

commit b0e1dd018a160134bc8fdd874a787f2bad3fc6dd a3d1d1c9c5cd082ffe98df11d7c7d751f1726217 (HEAD, origin/ onos-1.3, onos-1.3)
Author: Jonathan Hart samanwita pal [jono@onlabsam@onlab.us]
AuthorDate: Wed Fri Sep 23 1725 11:5450:11 15 2015 -0700
Commit: Jonathan Hart [jono@onlabGerrit Code Review [gerrit@onlab.us]
CommitDate: Thu Sat Sep 24 1326 00:2235:23 03 2015 -0700
IntentManager: Don't compile all failed intents on every event+0000

ONOS-2926 Sending DHCPNAKs to failed ASSIGN request

Case 101: Setting up test environment - PASS

...

• 7.1 Check P2P intents installed - PASS
• 7.2 Check ping between hosts behind BGP peers - PASS
• 7.3 Check ping between BGP peers and speakers - PASS
• 7.4 Check whether all flow status are ADDED - PASS

Case 8: This case is to start the switch which was shut down in CASE7,check P-2-P and M-2-S intents, ping test - PASS

• 8.1 Check P2P intents installed - PASS
• 8.2 Check ping between each host pair - PASS

Case 9: This case is to stop switch in best path, check route number, P2P intent number, M2S intent number, ping test - PASS

• 9.1 Check flow entry number in sw7 - PASS
• 9.2 Check P2P intents installed - PASS
• 9.3 Check ping between each host pair - PASS

Case 10: This case is to start switch which was stopped in CASE9, check route number, P2P intent number, M2S intent number, ping test - PASS

• 10.1 Check flow entry number in sw7 - PASS
• 10.2 Check ping between each host pair - PASS