Changes between Version 22 and Version 23 of Documentation/fSDN/OpenFlow

Timestamp:

Nov 19, 2013, 7:13:30 PM (11 years ago)

Author:

nkiran

Comment:

—

Documentation/fSDN/OpenFlow

@@ -27 +27 @@
 
 
-Preparing the switch for !OpenFlow mode includes: assigning h/w resources for !OpenFlow flows, enabling !OpenFlow mode and enabling specific versions (e.g., 1.1, 1.2 or 1.3), setting ports as crossflow, and lastly adding the 'match' and 'action' rules for expected flow. As an alternative to locally introduced flow rules using the CLI, a remote !OpenFlow controller can be configured which will then receive OpenFlow notifications (PacketIns) for flows not handled locally. The following CLI session excerpt details the commands required to accomplish the above steps:
+Preparing the switch for !OpenFlow mode includes: assigning h/w resources for !OpenFlow flows, enabling !OpenFlow mode and enabling specific versions (e.g., 1.1, 1.2 or 1.3), setting ports as crossflow, and lastly adding the 'match' and 'action' rules for expected flow. As an alternative to locally introduced flow rules using the CLI, a remote !OpenFlow controller can be configured which will then receive !OpenFlow notifications (!PacketIns) for flows not handled locally. The following CLI session excerpt details the commands required to accomplish the above steps:
 
 {{{
@@ -100 +100 @@
 
 
-=== 2. Openflow in OVS Mode ===
+=== B. OpenFlow in OVS Mode ===
 
 
-=== 3. Openflow through Network Boot (of custom image) ===
+=== C. OpenFlow through Network Boot (of custom image) ===
 
 === Switching Modes using Web Service ===
@@ -123 +123 @@
 === Loading and Saving Switch Configurations ===
 
-While in L2/L3 mode, the XorPlus CLI under the above account grants complete control to configure the switch and also to load/store configuration files on the root file system. However, it is suggested that experimenters preserve their configs by copying out their configurations (using tftp, etc.) to external locations, and to load them back when required. Below are the relevant CLI commands with further details in the attached PicOS configuration guide from Pica8. Please exercise prudence and caution when saving or moving configuration files in/out of the root file system. 
+While in L2/L3 mode, the !XorPlus CLI under the above account grants complete control to configure the switch and also to load/store configuration files on the root file system. However, it is suggested that experimenters preserve their configs by copying out their configurations (using tftp, etc.) to external locations, and to load them back when required. Below are the relevant CLI commands with further details in the attached PicOS configuration guide from Pica8. Please exercise prudence and caution when saving or moving configuration files in/out of the root file system. 
 
 {{{
@@ -156 +156 @@
 
  * [http://www.openflow.org/ OpenFlow]
- * [http://www.pica8.org Pica8's Pronto 3290 (now simply P-3290)] | [http://pica8.com/support/resources.php Documentation on Installation/Configuration]
+ * [http://www.pica8.org Pica8's Pronto 3290 (now simply P-3290)] | [http://pica8.com/support/resources.php Installation/Configuration Guides]
  * [http://www.netfpga.org NetFPGA 1G and 10G cards]