This is an archive of the ONOS 1.5 wiki. For the current ONOS wiki, look here.

DEMO_SDNIP at 17 Mar 2016 14:29:32

Case 101: Setting up ONOS environment - PASS

  • 101.1 Applying cell variable to environment - PASS (tick)
  • 101.2 Checking if ONOS CLI is ready to start - PASS (tick)
  • 101.3 Checking if ONOS CLI is ready for issuing commands - PASS (tick)

Case 100: Setup the Mininet testbed - PASS

  • 100.1 Starting Mininet Topology - PASS (tick)
  • 100.2 Connect switches to controllers - PASS (tick)

Case 199: Verify topology discovery - PASS

  • 199.1 Get links in the network - PASS (tick)

Case 200: Activate sdn-ip application - PASS

  • 200.1 Activate sdn-ip application - PASS (tick)

Case 102: Create tunnels between Quagga and SDNIP Application - PASS

  • 102.1 Set up tunnel from Mininet node 1.1.1.2:2000 to ONOS node 10.128.174.1:2000 - PASS (tick)
  • 102.2 Set up tunnel from Mininet node 1.1.1.4:2000 to ONOS node 10.128.174.2:2000 - PASS (tick)
  • 102.3 Set up tunnel from Mininet node 1.1.1.6:2000 to ONOS node 10.128.174.3:2000 - PASS (tick)

Case 1: Ping between BGP peers and speakers - PASS

  • 1.1 BGP speakers ping peers, expect all tests to succeed - PASS (tick)
  • 1.2 BGP speakers ping peers, expect all tests to succeed - PASS (tick)

Case 3: Check routes and M2S intents to all BGP peers - PASS

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

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 (tick)

Case 1001: Checking onos logs for ERRORs... - FAIL

  • 1001.1 Checking onos logs for ERRORs ... - FAIL (error)
    • onos has WARNINGs/ERRORs/Exceptions at the end of the test!
  • No labels