| 5 | | GENI offer access to hardware !OpenFlow switches. Each !OpenFlow switch in most cases can support only one controller. There are two ways of slicing the controller flowspace: |
| 6 | | 1. By VLAN id. This is used when each slice has its own VLANs. For instructions to use the !OpenFlow switches with private VLANs, see []. |
| 7 | | 2. By IP addresses or by Ethernet type. This is used when multiple slices share the same VLAN. For example, the GENI mesoscale VLAN. For instructions, see []. |
| | 5 | The topology used in this experiment is the same as the one used in the [wiki:GENIExperimenter/Tutorials/OpenFlowOVS Intro to OpenFlow using OVS] tutorial: Three virtual machines (VMs) connected by an !OpenFLow switch. However this tutorial uses the hardware !OpenFlow switch on the rack instead of a software OVS switch. |
| | 6 | |
| | 7 | GENI offers access to hardware !OpenFlow switches. Each !OpenFlow switch, in most cases, can support only one controller. There are two ways of slicing the controller flowspace: |
| | 8 | 1. By VLAN id. This is used when each slice has its own VLANs. |
| | 9 | 2. By IP addresses or by Ethernet type. This is used when multiple slices share the same VLAN. |
| | 10 | Both approaches to slicing are covered in this tutorial. |
| | 11 | |
| | 12 | To force the links between the VMs to go through the rack !OpenFlow switch, the three VMs must be on separate physical hosts on the rack. Since each InstaGENI rack has two hosts with Xen VMs and one with OpenVZ VMs, our experiment will: |
| | 13 | * Use 2 Xen VMs and 1 OpenVZ VM |
| | 14 | * Bind the Xen VMs to different physical hosts. |
| | 15 | |
| | 16 | |
| | 17 | For instructions to use the !OpenFlow switches with private VLANs, see []. |
| | 18 | |
| | 19 | For example, the GENI mesoscale VLAN. For instructions, see []. |
