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 08 Jun 2016 11:18:05
commit f57eee3e1d741200a05e70e7f4f0dd5f1f2f5e9b (HEAD, origin/onos-1.6, onos-1.6)
Author: Saurav Das [sauravdas@alumni.stanford.edu]
AuthorDate: Fri May 27 13:54:07 2016 -0700
Commit: Ray Milkey [ray@onlab.us]
CommitDate: Wed Jun 8 10:02:44 2016 -0700
In this commit:
Bug fix where filtering objectives are not installed due to available ports becoming enabled later.
Bug fix where flow objective store had no listener for notifications from drivers across multiple instances of the controller.
NPE fix in ofdpa driver for non-existing groups.
Preventing ofdpa driver from sending spurious pass notification to app.
Incrementing retry filter timer from 1 to 5 secs in default routing handler.
Made several debug messages clearer.
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 - PASS
- 101.5 Creating ONOS package - PASS
- 101.6 Installing ONOS package - PASS
- 101.7 Checking if ONOS is up yet - PASS
- 101.8 Checking if ONOS CLI is ready - PASS
Case 100: Setup the Mininet testbed - 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 - PASS
Case 200: Activate sdn-ip application - PASS
- 200.1 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 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 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, expect all to succede=True - 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 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 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 - 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.5 Check ping between hosts behind BGP peers - PASS
- 7.6 Check ping between BGP peers and speakers - PASS
- 7.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 Check ping between each host pair, expect all to succede=True - 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 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.10 Check ping between each host pair, expect all to succede=True - 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 Check ping between each host pair, expect all to succede=True - PASS