Changes between Version 28 and Version 29 of GENIExperimenter/Tutorials/OpenFlowOVS-Floodlight/DesignSetup

Timestamp:

12/16/16 10:46:42 (7 years ago)

Author:

lnevers@bbn.com

Comment:

--

GENIExperimenter/Tutorials/OpenFlowOVS-Floodlight/DesignSetup

@@ -106 +106 @@
 }}} 
  iii. Prepare the interfaces to be added as ports to the OVS switch
-   * Your OVS bridge will be a Layer 2 switch and your ports do not need IP addresses. Before we remove them let's keep some information
+   * Your OVS bridge will be a Layer 2 switch and your ports do not need IP addresses. Before we remove them let's keep track of some information
      * Run  {{{ ifconfig }}} 
      * Write down the interface names that correspond to the connections to your hosts. You will see three interfaces with IP's '''10.10.*.*''', one for each host. These are the data plane interfaces.
@@ -123 +123 @@
  sudo  ovs-vsctl add-port br0 ethZ 
 }}}
- v. Trust but verify. Congratulations! You have configured your software switch. To verify the three ports configured run:
+ v. Trust but verify. Congratulations! You have configured your software switch. To verify the three ports are configured run:
  {{{
 sudo ovs-vsctl list-ports br0
@@ -158 +158 @@
 === 2c. `standalone` vs `secure` mode ===
 
-''The !OpenFlow controller is responsible for setting up all flows on the switch, which means that when the controller is not running there should be no packet switching at all. Depending on the setup of your network, such a behavior might not be desired. It might be best that when the controller is down, the switch should default back to being a learning layer 2 switch. In other circumstances however this might be undesirable. In OVS this is a tunable parameter, called `fail-safe-mode` which can be set to the following parameters:''
+The !OpenFlow controller is responsible for setting up all flows on the switch, which means that when the controller is not running there should be no packet switching at all. Depending on the setup of your network, such behavior might not be desired. It might be best that when the controller is down, the switch should default back to being a learning layer 2 switch. In other circumstances however this might be undesirable. In OVS this is a tunable parameter, called `fail-safe-mode` which can be set to the following parameters:
+
   * `standalone` ''[default]: in this case OVS will take responsibility for forwarding the packets if the controller fails''
   * `secure`: ''in this case only the controller is responsible for forwarding packets, and if the controller is down all packets are dropped. ''
 
-''In OVS when the parameter is not set it falls back to the `standalone` mode. For the purpose of this tutorial we will set the `fail-safe-mode` to `secure`, since we want to be the ones controlling the forwarding.''
+
+In OVS when the parameter is not set it defaults to the `standalone` mode. For the purpose of this tutorial we will set the `fail-safe-mode` to `secure`, since we want to be the ones controlling the forwarding.
+
  
 ----