Changes between Version 3 and Version 4 of Internal/OpenFlow/Firmware

Timestamp:

Jun 26, 2009, 6:37:59 PM (15 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/Firmware

@@ -1 +1 @@
 = Flashing NEC Switches =
+
 
 NEC provides two models of switch that supports !OpenFlow, the IP8800/S3640-24T2XW and the IP8800/S3640-48T2XW.
 The switches must be manually flashed with !OpenFlow capable firmware to make them !OpenFlow capable. This page explains how to flash the switch to make it !OpenFlow capable. 
+
+
+== Overview ==
+This article is part summary of the !OpenFlow manual NEC provides with the switches, and a documentation of some details that might be worth mentioning.   
 
 
@@ -13 +18 @@
 
 
-== Overview ==
+== General steps ==
 These are the general steps required to get the switch up and running as an !OpenFlow device:
-
+ 
+ 1. Log into switch (this assumes you have already configured everything so you can talk to your switch)
  1. Create VLANs
  1. Create openflow.conf
  1. Save k.img, license.dat, and openflow.conf onto SD card
- 1. Cold boot switch off of SD card 
+ 1. Cold boot switch off of SD card (the manual says a reboot is sufficient, but this was not the case) 
  1. Enjoy
 
+The VLANs can also be configured after the switch has been booted off of the !OpenFlow firmware.  
 
 
-= Some Caveats = 
+= The Caveats = 
+Although the manual does a pretty good job at explaining how to do things, some things might be worth mentioning. The following are a summary of things that might be sort of important.
 
 == The SD card ==
 NEC provides a certified SD card with the switch. They recommend that you only use this card.
-
-
 
 == The License ==
@@ -49 +55 @@
 }}}
 
-In this case, "WA03CL48T2XWS0E0693K007" is the serial number and should match the name of the correct license for this specific switch.  
+In this case, "WA03CL48T2XWS0E0693K007" (in the first entry under "H/W: Main board) is the serial number and matches the name of the correct license for this specific switch.  
 
-'''Note: ''' If the license is named after the switch's serial number, the license must be renamed to "license.dat."      
+'''Note: ''' If the license is named after the switch's serial number, the license must be renamed to "license.dat" before saving onto the SD card .
 
 
-== Creating the openflow.conf file ==
+== openflow.conf ==
 
-openflow.conf is a simple text file that contains !OpenFlow specific configurations. The following are the three parameters you can specify in the file.
+openflow.conf is a text file that contains configurations specific to !OpenFlow switching, or [wiki:Documentation/OpenFlow/VirtualSwitch virtual switching]. The details about the commands that can be used in the file are on pages 12-13 of the NEC manual. Following are a few notes about the commands. 
 
 === `no-save` === 
-when specified in the .conf file, configuration changes won't be saved to the SD card. ''' Specifying this parameter in openflow.conf will prevent you from creating and removing virtual switches from the CLI. ''' 
+Specifying this parameter in openflow.conf will prevent you from configuring virtual switches through the CLI (i.e, create new virtual switches). Because the firmware does not include text editors, once you have this parameter on your .conf file you will have to edit your file on a PC if you want to change anything. Basically, if you are planning to change things around after the switch has been booted into !OpenFlow, it is better not to specify this command.   
 
 === `double-wide-mode` ===
-When specified, all ten !OpenFlow specific header fields will be matched. 
+When specified, all ten !OpenFlow specific header fields will be matched.   
 
 === `setvsi` ===
-'' more detailed use of this parameter can be found in the [wiki:Documentation/OpenFlow/VirtualSwitch virtual switch] article. ''
-
-Creates an instance of a [wiki:Documentation/OpenFlow/VirtualSwitch virtual switch]. You can also use this configuration command from the CLI. 
+Creates an instance of a [wiki:Documentation/OpenFlow/VirtualSwitch virtual switch] on a VLAN. You can also use this configuration command from the CLI. 
 
 `setvsi` is followed by several parameters:      
@@ -73 +77 @@
 `setvsi <vlan id> <list of ports> <tcp|ssl> <controller ip address[:port]> [<cacert> <my cert> <my private key>] [dpid <datapath id>] [hwlimit <max entrynum>] [max-backoff <backoff time>] [echo-interval <interval time>]`
 
-to get `setvsi` working at minimal, you need only the following parameters:
+not all parameters need to be used with `setvsi`. The following are the minimal parameters you need to get a virtual switch going:
 
 `setvsi <vlan id> <list of ports> <tcp|ssl> <controller ip address[:port]> [dpid <datapath id>]`
 
 
+== Example openflow.conf file ==
 
-== Example openflow.conf file ==
-openflow.conf resides in /mnt/ once the switch is booted. 
+openflow.conf resides in /mnt/ . 
 
 {{{
@@ -91 +95 @@
 }}}
 
-Note that the `no-save` option is omitted to make editing from the CLI easier.  
 
+
+