Have questions? Stuck? Please check our FAQ for some common questions and answers.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 50 Next »

USECASE_SdnipFunction at 28 Sep 2015 08:27:16

Case 100: - PASS

  • 100.1 Starting Mininet Topology - PASS (tick)
  • 100.2 Connect switches to controller - PASS (tick)
  • 100.3 Set up tunnel from Mininet node to onos node - No Result (warning)
commit 5196e863928bb78a096b5c69cf873d0687fbc877 (HEAD, origin/master, origin/HEAD, master)
Author: alshabib [alshabibi.ali@gmail.com]
AuthorDate: Sun Sep 27 10:59:50 2015 +0200
Commit: alshabib [alshabibi.ali@gmail.com]
CommitDate: Sun Sep 27 10:59:50 2015 +0200

cleaning up some meter code

Case 101: Setting up test environment - PASS

  • 101.1 Applying cell variable to environment - No Result (warning)
  • 101.2 Git pull - No Result (warning)
  • 101.3 Using mvn clean install - No Result (warning)
  • 101.4 Creating ONOS package - No Result (warning)
  • 101.5 Installing ONOS package - No Result (warning)
  • 101.6 Checking if ONOS is up yet - PASS (tick)
  • 101.7 Get links in the network - No Result (warning)

Case 102: Loading the methods from other Python file - PASS

Case 1: This case is to check ping between BGP peers and speakers - PASS

Case 2: This case is to check point-to-point intents - PASS

  • 2.1 Get point-to-point intents from ONOS CLI - PASS (tick)

Case 3: This case is to check routes and intents to all BGP peers - PASS

  • 3.1 Check routes installed - PASS (tick)
  • 3.2 Check MultiPointToSinglePointIntent intents installed - PASS (tick)
  • 3.3 Check whether all flow status are ADDED - PASS (tick)

Case 4: This case is to check ping for each route, all hosts behind BGP peers - PASS

Case 5: This case is to bring down links and check routes/intents - PASS

  • 5.1 Check M2S intents installed - PASS (tick)
  • 5.2 Check M2S intents installed - PASS (tick)
  • 5.3 Check M2S intents installed - PASS (tick)
  • 5.4 Check ping between each host pair - PASS (tick)

Case 6: This case is to bring up links and check routes/intents - PASS

  • 6.1 Check M2S intents installed - PASS (tick)
  • 6.2 Check M2S intents installed - PASS (tick)
  • 6.3 Check M2S intents installed - PASS (tick)
  • 6.4 Check ping between each host pair - PASS (tick)

Case 7: This case is to stop 1 edge switch,check P-2-P and M-2-S intents, ping test - PASS

  • 7.1 Check P2P intents installed - PASS (tick)
  • 7.2 Check ping between hosts behind BGP peers - PASS (tick)
  • 7.3 Check ping between BGP peers and speakers - PASS (tick)
  • 7.4 Check whether all flow status are ADDED - PASS (tick)

Case 8: This case is to start the switch which was shut down in CASE7,check P-2-P and M-2-S intents, ping test - PASS

  • 8.1 Check P2P intents installed - PASS (tick)
  • 8.2 Check ping between each host pair - PASS (tick)

Case 9: This case is to stop switch in best path, check route number, P2P intent number, M2S intent number, ping test - PASS

  • 9.1 Check flow entry number in sw7 - PASS (tick)
  • 9.2 Check P2P intents installed - PASS (tick)
  • 9.3 Check ping between each host pair - PASS (tick)

Case 10: This case is to start switch which was stopped in CASE9, check route number, P2P intent number, M2S intent number, ping test - PASS

  • 10.1 Check flow entry number in sw7 - PASS (tick)
  • 10.2 Check ping between each host pair - PASS (tick)
  • No labels