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.
...
commit a9017217068ec45ce29b467f9fba349112895375 (HEAD, origin/onos-1.10, onos-1.10)
Author: Andrea Campanella [andrea@opennetworking.org]
AuthorDate: Mon Oct 23 15:46:36 2017 +0200
Commit: Andrea Campanella [andrea@opennetworking.org]
CommitDate: Wed Nov 8 11:45:01 2017 -0800
Fixing Netconf Subscription session reopen
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 to environment - PASS
- 101.4 Verify cell connectivity Apply cell to environment - PASS
- 101.3 5 Uninstalling ONOS package - PASS
- 101.4 6 Creating ONOS package - PASS
- 101.5 7 Installing ONOS package - PASS
- 101.6 8 Set up ONOS secure SSH - PASS
- 101.7 Starting ONOS service 9 Checking if ONOS is up yet - PASS
- 101.8 Starting 10 Checking if ONOS CLI sessions is ready - PASS
- 101.9 11 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.254.1.201:2000 - PASS
- 102.2 Set up tunnel from Mininet node 1.1.1.4:2000 to ONOS node 10.254.1.202:2000 - PASS
- 102.3 Set up tunnel from Mininet node 1.1.1.6:2000 to ONOS node 10.254.1.203:2000 - PASS
- 102.4 Set up tunnel from Mininet node 1.1.1.8:2000 to ONOS node 10.254.1.204:2000 - PASS
- 102.5 Set up tunnel from Mininet node 1.1.1.10:2000 to ONOS node 10.254.1.205:2000 - PASS
- 102.6 Set up tunnel from Mininet node 1.1.1.12:2000 to ONOS node 10.254.1.206:2000 - PASS
- 102.7 Set up tunnel from Mininet node 1.1.1.14:2000 to ONOS node 10.254.1.207:2000 - PASS
Case 1: Ping between BGP peers and speakers - PASS
...
Case 3: Check routes and M2S intents to all BGP peers - PASS
- 3.1 Check routes installed - No Result 3.2 Check routes installed - PASS
- 3.3 2 Check M2S intents installed - PASS
- 3.4 3 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 - PASS
- 5.4 Bring down the link between sw8 and p64515 - PASS
- 5.5 Check routes installed - PASS
- 5.6 Check M2S intents installed - PASS
- 5.7 Bring down the link between sw28 and p64516 - 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 -
...
PASS
- 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 fail succeed - PASS
- 6.12 Check ping between each host pair, expect all to succede=False True - FAIL
- Ping test results are Not expected
- PASS
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 - FAIL
- M2S intent number is wrong!
- 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
...