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 101: Starting up 3 node(s) ONOS cluster - PASS
Set up ONOS with 3 node(s) ONOS cluster
- 101.1 Constructing test variables - No Result
- 101.2
Case 101: Setting up ONOS environment - PASS
- 101.1 Copying config files - PASS
- 101.2 Create cell file - No Result 101.3 Applying cell variable 3 Apply cell to environment - PASS
- 101.4 Verify cell connectivity Uninstalling Atomix - PASS
- 101.5 Uninstalling ONOS package - PASS
- 101.6 Creating ONOS package - PASS
- 101.7 Installing Atomix - PASS
- 101.8 Installing ONOS package - PASS
- 101.9 Set up ONOS secure SSH - PASS
- 101.10 Checking ONOS service - PASS
- 101.11 Starting ONOS CLI sessions - PASS
- 101.8 12 Checking if ONOS is up yet nodes - PASS
- 101.9 13 Checking if ONOS CLI is ready applications - PASS
- 101.10 14 Checking if ONOS CLI is ready for issuing commands - PASS
...
- 102.1 Set up tunnel from Mininet node 1.1.1.2:2000 to ONOS node 10.254128.199.20146:2000 - PASS
- 102.2 Set up tunnel from Mininet node 1.1.1.4:2000 to ONOS node 10.254128.199.20245:2000 - PASS
- 102.3 Set up tunnel from Mininet node 1.1.1.6:2000 to ONOS node 10.254128.199.20344:2000 - PASS
Case 1: Ping between BGP peers and speakers - PASS
...
- 1.1 BGP speakers ping peers, expect all tests to succeed - PASS
- 1.2 BGP speakers ping peers, expect all tests to succeed - PASS
- 1.3 BGP speakers ping peers, expect all tests to succeed - PASS
- 1.4 BGP speakers ping peers, expect all tests to succeed - PASS
Case 2: Check point-to-point intents -
...
FAIL
- 2.1 Check P2P intents number from ONOS CLI - PASS FAIL
- PointToPointIntent Intent Num is wrong!
Case 3: Check routes and M2S intents to all BGP peers -
...
FAIL
- 3.1 Check routes installed - No Result
- 3.2 Check routes installed - PASS
- 3.2 3 Check M2S intents installed - PASS FAIL
- MultiPointToSinglePoint Intent Num is wrong!
- 3.3 4 Check whether all flow status are ADDED - PASS
Case 4: Ping test for each route, all hosts behind BGP peers -
...
FAIL
- 4.1 Check ping between each host pair, expect all to succede=True - PASS
Case 5: Bring down links and check routes/intents - PASS
- FAIL
- Ping test results are Not expected
- 4.2 Check
- 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 installed - PASS
- 5.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.12 Check ping between each host pair, expect all to succede=False - PASS
Case 6: Bring up links and check routes/intents - FAIL
- True - FAIL
- Ping test results are Not expected
- 4.3 Check ping
- 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.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 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 Check ping between each host pair, expect all to succede=True - FAIL
- Ping test results are Not expected