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 - PASS 101.5 Uninstalling ONOS package - PASS
- 101.6 5 Creating ONOS package - PASS
- 101.7 6 Installing ONOS package - PASS
- 101.8 7 Set up ONOS secure SSH - PASS
- 101.9 8 Checking if ONOS is up yet service - PASS
- 101.10 Checking if 9 Starting ONOS CLI is ready sessions - PASS
- 101.11 10 Checking if ONOS CLI is ready for issuing commands - PASS
...
- 3.1 Check routes installed - No Result
- 3.2 Check routes installed - PASS
- 3.2 3 Check M2S intents installed - PASS
- 3.3 4 Check whether all flow status are ADDED - PASS
...
- 5.1 Bring down the link between sw32 and p64514 - PASS
- 5.2 Check routes installed - PASS
- 5.3 Check M2S intents installed - FAIL
- M2S intent number is wrong!
- 5.4 Bring down the link between sw8 and p64515 - PASS
- 5.5 Check routes installed - PASS
- 5.6 Check M2S intents installed - FAIL
- M2S intent number is wrong!
- 5.7 Bring down the link between sw28 and p64516 - PASS
- 5.8 Check routes installed - PASS
- 5.9 Check M2S intents installed - FAIL
- M2S intent number is wrong!
- 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
- 6.1 Bring up the link between sw32 and p64514 - PASS
- 6.2 Check routes installed - PASS
- 6.3 Check M2S intents installed - PASS
- 6.4 Bring up the link between sw8 and p64515 - PASS
- 6.5 Check routes installed - PASS
- 6.6 Check M2S intents installed - PASS
- 6.7 Bring up the link between sw28 and p64516 - 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 fail - PASS
- 6.12 Check ping between each host pair, expect all to succede=True - PASS False - FAIL
- Ping test results are Not expected
Case 7: Stop edge sw32,check P-2-P and M-2-S intents, ping test - PASS
...
- 9.1 Check flow entry number in sw11 - PASS
- 9.2 Check flow entry number in sw1 - FAIL
- Flow number in sw1 is wrong!
- 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 Check P2P intents installed - FAIL P2P intent number is wrong!
- PASS
- 9.8 Check whether all flow status are ADDED - PASS
- 9.9 BGP speakers ping peers, expect all tests to succeed - PASS
- 9.10 BGP speakers ping peers, expect all tests to succeed - PASS
- 9.11 Check ping between each host pair, expect all to succede=True - PASS
...
- 10.1 Check flow entry number in sw1 - FAIL
- Flow number in sw1 is wrong!
- 10.2 Check flow entry number in sw7 - FAIL
- Flow number in sw7 is wrong!
- 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 BGP speakers ping peers, expect all tests to succeed - PASS
- 10.10 Check ping between each host pair, expect all to succede=True - PASS