Changes between Version 12 and Version 13 of OpenFlow/CampusTopology
- Timestamp:
- 04/19/11 09:41:09 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
OpenFlow/CampusTopology
v12 v13 1 1 [[PageOutline]] 2 2 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: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 describes a single topology for connecting resources at campuses to a local OpenFlow network, which then offers three options for experimenters to link those resources to inter-campus VLANs. 4 4 5 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. 5 Those options for experimenters are: 6 6 7 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.7 1. Link 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. 8 8 9 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). 9 2. Use !OpenFlow to link 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. 10 11 3. Use !OpenFlow to link 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). 10 12 11 13 Most !OpenFlow experiments will probably be able to use the second option, which offers a good combination of performance, features, and ease of use. … … 15 17 = Diagram = 16 18 17 The following is a minimalist diagram of a n !OpenFlow switch configuration that implementsall three of these options:19 The following is a minimalist diagram of a single !OpenFlow switch configuration that implements the infrastructure to support all three of these options: 18 20 19 21 {{{