Page History

...

Case 101: Starting

...

up

...

3 node(s) ONOS cluster

...

• 101.1 Constructing test variables - No Result
• 101.2 Copying config files - PASS
• 101.3 Apply cell to environment - PASS
• 101.4 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.12 Checking ONOS nodes - PASS
• 101.13 Checking ONOS applications - PASS
• 101.14 Checking if ONOS CLI is ready for issuing commands - 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
• 1.2 BGP speakers ping peers, expect all tests to succeed - PASS
• 1.3 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 - FAIL

• 3.1 Check routes installed - FAIL
• Routes are wrong!
• 3.2 Check M2S intents installed - FAIL
• MultiPointToSinglePoint Intent Num is wrong!
• 3.3 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 - FAIL
• Ping test results are Not expected
• 4.2 Check ping between each host pair, expect all to succede=True - FAIL
• Ping test results are Not expected
• 4.3 Check ping between each host pair, expect all to succede=True - FAIL
• Ping test results are Not expected

Case 5: Bring down links and check routes/intents - FAIL

• 5.1 Bring down the link between sw32 and p64514 - PASS
• 5.2 Check routes installed - FAIL
• Route number is wrong!
• 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 - FAIL
• Route number is wrong!
• 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 - FAIL
• Route number is wrong!
• 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 - FAIL
• Route number is wrong!
• 6.3 Check M2S intents installed - FAIL
• M2S intent number is wrong!
• 6.4 Bring up the link between sw8 and p64515 - PASS
• 6.5 Check routes installed - FAIL
• Route number is wrong!
• 6.6 Check M2S intents installed - FAIL
• M2S intent number is wrong!
• 6.7 Bring up the link between sw28 and p64516 - PASS
• 6.8 Check routes installed - FAIL
• Route number is wrong!
• 6.9 Check M2S intents installed - FAIL
• M2S intent number is wrong!
• 6.10 Check whether all flow status are ADDED - PASS
• 6.11 BGP speakers ping peers, expect all tests to fail - PASS
• 6.12 Check ping between each host pair, expect all to succede=False - PASS

...

- FAIL