Changes between Version 3 and Version 4 of Internal/OpenFlow/VirtualSwitch
- Timestamp:
- Jun 29, 2009, 6:17:44 PM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Internal/OpenFlow/VirtualSwitch
v3 v4 1 1 = The virtual switch = 2 Not to be mistaken for [wiki:Documentation/OpenFlow/VartualSwitch vartual switches], virtual switches, or !OpenFlow switches, are a example of the virtualization capabilities of !OpenFlow. They are similar to VLANs in both configuration and behavior but are dictated by !OpenFlow controllers and flow tables.2 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. 3 3 4 4 Several virtual switches may exist on a single physical device, or a single virtual switch may encompass a whole switch. In the latter case the switch will just be referred to as an !OpenFlow switch. … … 7 7 8 8 == Overview == 9 This article covers the following topics: 9 This article contains the following topics: 10 * Definitions of Legacy VLANs, !OpenFlow VLANs, and virtual switches 10 11 * CLI commands used in virtual switching 11 12 * Virtual switch setup 13 * The official NEC guide for the !OpenFlow capable IP8800/S3640 (attachment) 12 14 15 == Legacy VLANs, !OpenFlow VLANs, and virtual switches == 16 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. 17 18 * '' Legacy VLANs '' are the familiar technology usually associated with 802.1q, and can be configured in any standard switch. 19 * '' !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 switch's information using the `showswitch` or `showflow` commands. 20 * '' 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. 21 13 22 == CLI Commands == 14 23 The commands regarding virtual switching will not be found among the usual list of commands when you type `?` at the terminal. 15 24 This is the list of commands used in virtual switching that is accessible from the CLI: 16 25 17 * ''' setvsi ''' - Creates an instance of virtual switch. Comes with parameters. 18 * ''' deletevsi <vlan ID> ''' - Deletes an instance of virtual switch. 19 * ''' showswitch <vlan ID> <detail> ''' - Gives you a list of virtual switches running on your switch. 20 * ''' showflow <vlan ID> <detail> ''' - Gives you information about the flow tables applied to the virtual switches. 26 * ` setvsi ` - Creates an instance of virtual switch. Comes with parameters. 27 * ` deletevsi <vlan ID> ` - Deletes an instance of virtual switch. 28 * ` showswitch <vlan ID> <detail> ` - Gives you a list of virtual switches running on your switch. 29 * ` showflow <vlan ID> <detail> ` - Gives you information about the flow tables applied to the virtual switches. 30 31 ''' The !OpenFlow commands can be used even when you aren't in privileged mode. This may be a security issue worth considering. ''' 21 32 22 33 == Setup == 23 34 The following list can be followed as a guideline for setting up virtual switches. 24 35 25 1. Disable spanning tree protocol 36 1. Disable spanning tree protocol 26 37 1. Create VLANs 27 38 1. Assign ports to VLANs 28 39 1. Use `setvsi` to create virtual switches from the ports assigned to VLANs 29 40 30 == Example setup == 31 One method to rewrite the !OpenFlow configuration is to delete openflow.conf directly through the switch, then use the `setvsi` command to set the new virtual switches up. 41 The details can be found in the NEC !OpenFlow capable switch guide attached to this article. 42 43 == Example Setup - the weird .conf file incident == 44 One method to rewrite the !OpenFlow configuration is to delete openflow.conf directly through the switch, then use the `setvsi` command to set the new virtual switches up. Usually this is unnecessary, but it happened to be effective when old configurations did not seem to go away despite editing the .conf file using a PC. 32 45 33 46 1. Delete the old .conf file.
