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 2 Next »

SRSwitchFailure at 06 Jul 2016 11:22:56

Case 1: Package and start ONOS using apps:drivers,segmentrouting,openflow-base,netcfghostprovider,netcfglinksprovider - PASS

  • 1.1 Constructing test variables - PASS (tick)
  • 1.2 Create and Apply cell file - PASS (tick)
  • 1.3 Create and Install ONOS package - PASS (tick)
  • 1.4 Starting ONOS service - PASS (tick)
  • 1.5 Checking if ONOS CLI is ready - PASS (tick)
  • 1.6 Starting Mininet Topology - PASS (tick)
  • 1.7 Check whether the flow count is bigger than 116 - PASS (tick)
  • 1.8 Check whether all flow status are ADDED - PASS (tick)
  • 1.9 Check full connectivity - PASS (tick)
  • 1.10 Kill spine101 - PASS (tick)
  • 1.11 Check full connectivity CASE1_Failure - PASS (tick)
  • 1.12 Recovering spine101 - PASS (tick)
  • 1.13 Check whether the flow count is bigger than 116 - PASS (tick)
  • 1.14 Check whether all flow status are ADDED - PASS (tick)
  • 1.15 Check full connectivity CASE1_Recovery - PASS (tick)

Case 2: Package and start ONOS using apps:drivers,segmentrouting,openflow-base,netcfghostprovider,netcfglinksprovider - FAIL

  • 2.1 Create and Apply cell file - PASS (tick)
  • 2.2 Create and Install ONOS package - PASS (tick)
  • 2.3 Starting ONOS service - PASS (tick)
  • 2.4 Checking if ONOS CLI is ready - PASS (tick)
  • 2.5 Starting Mininet Topology - PASS (tick)
  • 2.6 Check whether the flow count is bigger than 350 - PASS (tick)
  • 2.7 Check whether all flow status are ADDED - PASS (tick)
  • 2.8 Check full connectivity - PASS (tick)
  • 2.9 Kill spine101 - PASS (tick)
  • 2.10 Check full connectivity CASE2_Failure - FAIL (error)
    • Full connectivity failed
  • 2.11 Recovering spine101 - PASS (tick)
  • 2.12 Check whether the flow count is bigger than 350 - PASS (tick)
  • 2.13 Check whether all flow status are ADDED - PASS (tick)
  • 2.14 Check full connectivity CASE2_Recovery - PASS (tick)

Case 4: Package and start ONOS using apps:drivers,segmentrouting,openflow-base,netcfghostprovider,netcfglinksprovider - PASS

  • 4.1 Create and Apply cell file - PASS (tick)
  • 4.2 Create and Install ONOS package - PASS (tick)
  • 4.3 Starting ONOS service - PASS (tick)
  • 4.4 Checking if ONOS CLI is ready - PASS (tick)
  • 4.5 Starting Mininet Topology - PASS (tick)
  • 4.6 Check whether the flow count is bigger than 116 - PASS (tick)
  • 4.7 Check whether all flow status are ADDED - PASS (tick)
  • 4.8 Check full connectivity - PASS (tick)
  • 4.9 Kill spine101 - PASS (tick)
  • 4.10 Check full connectivity CASE3_Failure - PASS (tick)
  • 4.11 Recovering spine101 - PASS (tick)
  • 4.12 Check whether the flow count is bigger than 116 - PASS (tick)
  • 4.13 Check whether all flow status are ADDED - PASS (tick)
  • 4.14 Check full connectivity CASE3_Recovery - PASS (tick)

Case 5: Package and start ONOS using apps:drivers,segmentrouting,openflow-base,netcfghostprovider,netcfglinksprovider - FAIL

  • 5.1 Create and Apply cell file - PASS (tick)
  • 5.2 Create and Install ONOS package - PASS (tick)
  • 5.3 Starting ONOS service - PASS (tick)
  • 5.4 Checking if ONOS CLI is ready - PASS (tick)
  • 5.5 Starting Mininet Topology - PASS (tick)
  • 5.6 Check whether the flow count is bigger than 350 - PASS (tick)
  • 5.7 Check whether all flow status are ADDED - PASS (tick)
  • 5.8 Check full connectivity - PASS (tick)
  • 5.9 Kill spine101 - PASS (tick)
  • 5.10 Check full connectivity CASE4_Failure - FAIL (error)
    • Full connectivity failed
  • 5.11 Recovering spine101 - PASS (tick)
  • 5.12 Check whether the flow count is bigger than 350 - PASS (tick)
  • 5.13 Check whether all flow status are ADDED - PASS (tick)
  • 5.14 Check full connectivity CASE4_Recovery - PASS (tick)
  • No labels