Changes between Version 5 and Version 6 of Internal/OpenFlow/VirtualSwitch

Timestamp:

Aug 10, 2009, 11:02:02 PM (15 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/VirtualSwitch

@@ -1 +1 @@
 = The virtual switch = 
-Not to be mistaken for [wiki:Documentation/OpenFlow/VartualSwitch vartual switches], virtual switches, or !OpenFlow switches, are the main service offered by the !OpenFlow capable switch. 
-
-Each virtual switch can be assigned a controller and a set of flow tables, and are associated with their !OpenFlow VLANs. 
+Virtual switches are the main service offered by the !OpenFlow capable switch that make overlay networks possible. When created, a virtual switch will behave as an !OpenFlow device, manipulating packets according to the flow tables it is given from the controller. by default, there are no virtual switches set up on the IP8800. You have to create them either by specifying them in openflow.conf or by using the command `setvsi` through the CLI. Here we talk about the latter way of creating virtual switches.    
 
 == Overview ==
-This article contains the following topics:
- * Definitions of Legacy VLANs, !OpenFlow VLANs, and virtual switches
+This article covers:
  * Summary of CLI commands used in virtual switching
  * Virtual switch setup from CLI (as opposed to directly editing openflow.conf)
@@ -12 +9 @@
  * The official NEC guide for the !OpenFlow capable IP8800/S3640 (attachment) 
    
-== Legacy VLANs, !OpenFlow VLANs, and virtual switches ==
-Legacy VLANs, !OpenFlow VLANs, and virtual switches all seem to serve a similar function: to provide a means to split up broadcast domains at the data link layer. This may cause some confusion as to what the exact differences are between these things without having definitions, so before going on, definitions had to be established. 
+== CLI Commands ==
+The commands for virtual switching will not be found among the usual list of commands when you type `?` at the terminal. Command completion doesn't work either, so you have to type out the whole command. 
+ 
+The full list of commands, along with their flags, are found on the NEC guide. 
 
- * '' Legacy VLANs '' are the familiar technology usually associated with 802.1q, and can be configured in any standard switch.
 
- * '' !OpenFlow VLANs '' are legacy VLANs on which the virtual switches will run as overlay infrastructure. the VLAN number becomes the virtual switch's '' VLAN ID '' that can be used to pull up a specific virtual switch's information using the `showswitch` or  `showflow` commands.  
-
- * '' Virtual switches '' are VLANs that implement !OpenFlow protocol and have !OpenFlow controllers, flow tables, and '' datapath identifiers '' (basically the virtual switch's "name," the 12-digit hex number labeled as the dpid in the manual) associated with them. they will not function without the controller. 
- 
-== CLI Commands ==
-The commands regarding virtual switching will not be found among the usual list of commands when you type `?` at the terminal. 
-This is the list of commands used in virtual switching that is accessible from the CLI:
-
- * ` setvsi ` -  Creates an instance of virtual switch. Comes with a bunch of parameters. 
- * ` deletevsi <vlan ID> ` - Deletes an instance of virtual switch.  
- * ` showswitch <vlan ID> <detail> ` - Gives you a list of virtual switches running on your switch.
- * ` showflow <vlan ID> <detail> ` - Gives you information about the flow tables applied to the virtual switches.
-
-The !OpenFlow commands can be used even when you aren't in privileged mode. 
-
-== Setup ==
-The following list can be followed as a guideline for setting up virtual switches after your switch is booted into !OpenFlow capable firmware. 
-
- 1. Create VLANs 
- 1. Assign ports to VLANs
- 1. Use `setvsi` to create virtual switches from the ports assigned to VLANs
-
-The details can be found in the NEC !OpenFlow capable switch guide attached to this article. 
 
 === when openflow.conf gets messed up (6/22) ===