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

VPLSfailsafe at 21 Mar 2018 05:17:33

VPLSfailsafe

commit 32b42208e0bf4fee0e05291f4dcd12178be7b794 (HEAD, origin/master, origin/HEAD, master)
Author: daniel park [dan.park@sk.com]
AuthorDate: Wed Mar 14 16:53:44 2018 +0900
Commit: Jian Li [pyguni@gmail.com]
CommitDate: Wed Mar 21 08:31:23 2018 +0000

[ONOS-7444] Optimize SONA gw doesn't use vrouter app and quagga anymore

Case 1: Starting up 3 node(s) ONOS cluster - PASS

Set up ONOS with 3 node(s) ONOS cluster

  • 1.1 Constructing test variables - PASS (tick)
  • 1.2 Apply cell to environment - PASS (tick)
  • 1.3 Uninstalling ONOS package - PASS (tick)
  • 1.4 Creating ONOS package - PASS (tick)
  • 1.5 Installing ONOS package - PASS (tick)
  • 1.6 Set up ONOS secure SSH - PASS (tick)
  • 1.7 Checking ONOS service - PASS (tick)
  • 1.8 Starting ONOS CLI sessions - PASS (tick)
  • 1.9 Starting Mininet - PASS (tick)
  • 1.10 Activate apps defined in the params file - No Result (warning)
  • 1.11 Set ONOS configurations - No Result (warning)
  • 1.12 App Ids check - PASS (tick)

Case 2: - FAIL

  • 2.1 Discover hosts using pings - No Result (warning)
  • 2.2 Load VPLS configurations - PASS (tick)
  • 2.3 Check VPLS configurations - PASS (tick)
  • 2.4 Check interface configurations - PASS (tick)
  • 2.5 Check network configurations for vpls application - PASS (tick)
  • 2.6 Check vpls app configurations - PASS (tick)
  • 2.7 Check connectivity - FAIL (error)
    • Connectivity is not as expected
  • 2.8 Loading vpls configuration in case any configuration was missed. - PASS (tick)

Case 50: Check connectivity before running all other tests. - FAIL

  • 50.1 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 50.2 Testing connectivity... - FAIL (error)
    • Connectivity is NOT as expected.

Case 100: Bring down one host at a time and test connectivity. - FAIL

  • 100.1 Kill link between s1 and h1. - PASS (tick)
  • 100.2 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 100.3 Testing connectivity... - FAIL (error)
    • Connectivity failed.
  • 100.4 Re-adding link between s1 and h1. - PASS (tick)
  • 100.5 Discover h1 using ping. - No Result (warning)
  • 100.6 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 100.7 Testing connectivity... - FAIL (error)
    • Connectivity is NOT as expected.

Case 200: Bring down one switch at a time and test connectivity. - FAIL

  • No labels