Changes between Version 5 and Version 6 of OpenFlow/CampusTopology

Timestamp:

04/05/11 17:15:40 (14 years ago)

Author:

Josh Smift

Comment:

--

OpenFlow/CampusTopology

@@ -3 +3 @@
 This is an example topology of a campus OpenFlow network, designed to allow experimenters to access the GENI network core in a variety of ways depending on their needs. In particular, it offers three main options for connecting resources at campuses to inter-campus VLANs:
 
- 1. Connect directly to one or more pre-provisioned core VLANs, without using any campus OpenFlow resources. This is a very simple option for experiments that don't need to use OpenFlow campus resources at all, and merely want to access the GENI network core.
+ 1. Connect directly to one or more pre-provisioned [wiki:ConnectivityHome core VLANs], without using any campus OpenFlow resources. This is a very simple option for experiments that don't need to use OpenFlow campus resources at all, and merely want to access the GENI network core.
 
- 2. Use OpenFlow to connect to one or more pre-provisioned core VLANs, via a cross-connect cable that translates from a campus OpenFlow VLAN onto the core VLANs. This is a fairly simple option for experiments that want to use OpenFlow campus resources, and can use existing core VLANs.
+ 2. Use OpenFlow to connect to one or more pre-provisioned [wiki:ConnectivityHome core VLANs], via a cross-connect cable that translates from a campus OpenFlow VLAN onto the core VLANs. This is a fairly simple option for experiments that want to use OpenFlow campus resources, and can use existing core VLANs.
 
- 3. Use OpenFlow to connect to any core VLAN, by having OpenFlow configure the switch to do VLAN translation. This is a more complicated option for experiments that want to use OpenFlow campus resources, and need to use VLANs that aren't provisioned with a physical cross-connect for whatever reason (e.g. large numbers of VLANs, dynamically provisioned VLANs, etc).
+ 3. Use OpenFlow to connect to any [wiki:ConnectivityHome core VLANs], by having OpenFlow configure the switch to do VLAN translation. This is a more complicated option for experiments that want to use OpenFlow campus resources, and need to use VLANs that aren't provisioned with a physical cross-connect for whatever reason (e.g. large numbers of VLANs, dynamically provisioned VLANs, etc).
 
 Most OpenFlow experiments will probably be able to use the second option, which offers a good combination of performance, features, and ease of use.
+
+Note that this page assumes that your campus is already connected to the GENI network core. The [wiki:ConnectivityHome GENI Connectivity] page has more information about how to get connected to the GENI core, how to get connected to other campuses through the core, etc.
 
 = Diagram =