Changes between Version 9 and Version 10 of Internal/OpenFlow/Controllers/FlowVisor


Ignore:
Timestamp:
May 30, 2012, 6:41:07 AM (12 years ago)
Author:
akoshibe
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Internal/OpenFlow/Controllers/FlowVisor

    v9 v10  
    6565
    6666=== The testrun Setup ===
    67 In this setup, !FlowVisor is started on port 6655, with an instance of nox listening on port 6656. A !FlowVisor slice is created to listen to any controllers using port 6656 (in this case, our test NOX instance). A single virtual switch was made to listen for controllers on port 6655, whereby its control is given to NOX by flowvisor. Everything, unless specified, is done in the flowvisor directory. 
     67In this setup, !FlowVisor is started on port 6655, with an instance of nox listening on port 6656. A !FlowVisor slice is created to listen to any controllers using port 6656 (in this case, our test NOX instance). A single virtual switch was made to listen for controllers on port 6655, whereby its control is given to NOX by flowvisor. Everything, unless specified, is done in the flowvisor directory.   
    6868
    69  1. ''set up config file.'' The config file should be located in your flowvisor directory. Basing it on the default-config.xml file that comes with the flowvisor install:
     69 1. ''start !FlowVisor.'' Unlike nox, there are no flags to throw it into the background. Here it is started on port 6655: 
    7070{{{
    71 cp default-config.xml config.xml
    72 config-gen-default config.xml (Input: root passwd)
    73 }}}
    74 
    75  Here, we created a new instance of the configuration file from the sample !FlowVisor already has. config-gen-default will also prompt you to create a "root password" that you will be using to make changes to the config file through fvctl.
    76 
    77  2. ''start !FlowVisor.'' Unlike nox, there are no flags to throw it into the background. Here it is started on port 6655: 
    78 {{{
    79 flowvisor config.xml 6655 &
     71flowvisor -p 6655 &
    8072}}}
    8173
    82 Since !FlowVisor is still buggy as of now, it may be recommended to start !FlowVisor with `screen` to capture any errors. There is also a ''flowvisor-wrapper'' that restarts !FlowVisor if it dies.
     74flowvisor has several options, although config.xml is now irrelevant:
     75{{{
     76r$ flowvisor -v
     77Starting FlowVisor
     78FlowVisor version: flowvisor-0.8.3
     79Rob Sherwood: rsherwood@telekom.com/rob.sherwood@stanford.edu
     80---------------------------------------------------------------
     81err: ParseException: org.openflow.example.cli.ParseException: unknown option: v
     82FlowVisor [options] config.xml
     83        option        type [default]      usage
     84        -d|--debug    String [NOTE]       Override default logging threshold in config
     85        -p|--port     Integer [0]         Override port from config
     86        -l|--logging                      Log to stderr instead of syslog
     87        -j|--jetty portInteger [-1]        Override jetty port from config
     88        -h|--help                         Print help
     89}}}
    8390
    84  3. ''delete sample slices.'' After inspecting them with ''getSliceInfo'', remove them with ''deleteSlice''. There are two slices, "alice" and "bob". Each action usually requires authentication using the password you created in step 1.
     91 2. ''delete sample slices.'' After inspecting them with ''getSliceInfo'', remove them with ''deleteSlice''. There are two slices, "alice" and "bob". Each action usually requires authentication using the password you created in step 1.
    8592{{{
    8693fvctl getSliceInfo alice