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.
USECASE_SdnipFunction at 26 Sep 2015 07:32:55
Case 100: - PASS
- 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 a3d1d1c9c5cd082ffe98df11d7c7d751f1726217 (HEAD, onos-1.3)
Author: samanwita pal [sam@onlab.us]
AuthorDate: Fri Sep 25 11:50:15 2015 -0700
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Sat Sep 26 00:35:03 2015 +0000
ONOS-2926 Sending DHCPNAKs to failed ASSIGN request
Case 101: Setting up test environment - PASS
- 101.1 Applying cell variable to environment - No Result
- 101.2 Git pull - No Result
- 101.3 Using mvn clean install - No Result
- 101.4 Creating ONOS package - No Result
- 101.5 Installing ONOS package - No Result
- 101.6 Checking if ONOS is up yet - PASS
- 101.7 Get links in the network - No Result
Case 102: Loading the methods from other Python file - PASS
Case 1: This case is to check ping between BGP peers and speakers - PASS
Case 2: This case is to check point-to-point intents - PASS
- 2.1 Get point-to-point intents from ONOS CLI - PASS
Case 3: This case is to check routes and intents to all BGP peers - PASS
- 3.1 Check routes installed - PASS
- 3.2 Check MultiPointToSinglePointIntent intents installed - PASS
- 3.3 Check whether all flow status are ADDED - PASS
Case 4: This case is to check ping for each route, all hosts behind BGP peers - PASS
Case 5: This case is to bring down links and check routes/intents - PASS
- 5.1 Check M2S intents installed - PASS
- 5.2 Check M2S intents installed - PASS
- 5.3 Check M2S intents installed - PASS
- 5.4 Check ping between each host pair - PASS
Case 6: This case is to bring up links and check routes/intents - PASS
- 6.1 Check M2S intents installed - PASS
- 6.2 Check M2S intents installed - PASS
- 6.3 Check M2S intents installed - PASS
- 6.4 Check ping between each host pair - PASS
Case 7: This case is to stop 1 edge switch,check P-2-P and M-2-S intents, ping test - 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