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.
...
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
PASS
commit a3d1d1c9c5cd082ffe98df11d7c7d751f1726217 dd415c31d8a0d57fbe4a3ab721e2a95d7afa4495 (HEAD, origin/onos-1.3, onos-1.3)
Author: samanwita pal Jonathan Hart [sam@onlabjono@onlab.us]
AuthorDate: Fri Sep 25 11:50:15 2015 -0700Mon Nov 16 10:56:20 2015 -0800
Commit: Gerrit Code Review [gerrit@onlabJonathan Hart [jono@onlab.us]
CommitDate: Sat Sep 26 00:35:03 2015 +0000
ONOS-2926 Sending DHCPNAKs to failed ASSIGN requestMon Nov 16 14:14:24 2015 -0800
Protect against exceptions thrown in application's packet processors.
Case 101: Setting up test environment - PASS
- 101.1 Applying cell variable to environment - No Result
PASS
- 101.2 Git pull - No Result
Creating ONOS package - PASS
- 101.3 Using mvn clean install - No Result
Installing ONOS package - PASS
- 101.4 Creating ONOS package - No Result
Checking if ONOS is up yet - PASS
- 101.5 Installing ONOS package - No Result
101.6 Checking if ONOS CLI is up yet ready - PASS
- 101.7 Get links in the network - No Result
6 Activate sdn-ip application - PASS
Case 102: Loading
...
methods from other Python file - PASS
Case 1:
...
Ping tests between BGP peers and speakers - PASS
- 1.1 BGP speakers ping peers, expect all tests to succeed - PASS
Case 2:
...
Check point-to-point intents - PASS
- 2.1 Get point-to-point intents Check P2P intents number from ONOS CLI - PASS
Case 3:
...
Check routes and M2S intents to all BGP peers - PASS
- 3.1 Check routes installed - PASS
- 3.2 Check MultiPointToSinglePointIntent M2S intents installed - PASS
- 3.3 Check whether all flow status are ADDED - PASS
Case 4:
...
Ping test for each route, all hosts behind BGP peers - PASS
- 4.1 Check ping between each host pair - PASS
Case 5:
...
Bring down links and check routes/intents - PASS
- 5.1 Bring down the link between sw32 and peer64514 - PASS
- 5.2 Check routes installed - PASS
- 5.3 Check M2S intents installed - PASS
- 5.4 Bring down the link between sw8 and peer64515 - PASS
- 5.5 Check routes installed - PASS
- 5.6 Check M2S intents installed - PASS
- 5.7 Bring down the link between sw28 and peer64516 - PASS
- 5.8 Check routes 2 Check M2S intents installed - PASS
- 5.3 9 Check M2S intents installed - PASS
- 5.10 Check whether all flow status are ADDED - PASS
- 5.11 BGP speakers ping peers, expect all tests to fail - PASS
- 5.4 12 Check ping between each host pair - PASS
Case 6:
...
Bring up links and check routes/intents - PASS
- 6.1 Bring up the link between sw32 and peer64514 - PASS
- 6.2 Check routes installed - PASS
- 6.3 Check M2S intents installed - PASS
- 6.4 Bring up the link between sw8 and peer64515 - PASS
- 6.5 Check routes installed - PASS
- 6.2 6 Check M2S intents installed - PASS
- 6.7 Bring up the link between sw28 and peer64516 - PASS
- 6.8 Check routes installed - PASS
- 6.9 3 Check M2S intents installed - PASS
- 6.10 Check whether all flow status are ADDED - PASS
- 6.11 BGP speakers ping peers, expect all tests to succeed - PASS
- 6.12 4 Check ping between each host pair - PASS
Case 7:
...
Stop edge sw32,check P-2-P and M-2-S intents, ping test - PASS
- 7.1 Stop sw32 - PASS
- 7.2 Check routes installed - PASS
- 7.3 Check M2S intents installed - PASS
- 7.4 Check P2P intents installed - PASS
- 7.2 5 Check ping between hosts behind BGP peers - PASS
- 7.3 6 Check ping between BGP peers and speakers - PASS
- 7.4 7 Check whether all flow status are ADDED - PASS
Case 8:
...
Start the edge sw32, check P-2-P and M-2-S intents, ping test - PASS
- 8.1 Start sw32 - PASS
- 8.2 Check routes installed - PASS
- 8.3 Check M2S intents installed - PASS
- 8.4 Check P2P intents installed - PASS
- 8.5 Check whether all flow status are ADDED - PASS
- 8.6 BGP speakers ping peers, expect all tests to succeed - PASS
- 8.7 2 Check ping between each host pair - PASS
Case 9:
...
Stop sw11 located in best path, check route number, P2P intent number, M2S intent number, ping test - PASS
- 9.1 Check flow entry number in sw11 - PASS
- 9.2 Check flow entry number in sw1 - PASS
- 9.3 Check flow entry number in sw7 - PASS
- 9.4 Stop sw11 - PASS
- 9.5 Check routes installed - PASS
- 9.6 Check M2S intents installed - PASS
- 9.7 2 Check P2P intents installed - PASS
- 9.8 Check whether all flow status are ADDED - PASS
- 9.9 BGP speakers ping peers, expect all tests to succeed - PASS
- 9.3 10 Check ping between each host pair - PASS
Case 10:
...
Start sw11 which was stopped in CASE9, check route number, P2P intent number, M2S intent number, ping test - PASS
- 10.1 Check flow entry number in sw1 - PASS
- 10.2 Check flow entry number in sw7 - PASS
- 10.3 Start sw11 - PASS
- 10.4 Check routes installed - PASS
- 10.5 Check M2S intents installed - PASS
- 10.6 Check P2P intents installed - PASS
- 10.7 Check whether all flow status are ADDED - PASS
- 10.8 BGP speakers ping peers, expect all tests to succeed - PASS
- 10.9 2 Check ping between each host pair - PASS