Changes between Version 18 and Version 19 of OpenFlow/CampusTopology


Ignore:
Timestamp:
08/29/11 15:11:37 (10 years ago)
Author:
Josh Smift
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OpenFlow/CampusTopology

    v18 v19  
    22
    33This 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
     5Note 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.
     6
     7= Options =
    48
    59Those options for experimenters are:
     
    1317Most !OpenFlow experiments will probably be able to use the second option, which offers a good combination of performance, features, and ease of use.
    1418
    15 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.
     19= Operations =
     20
     21Once you have this set up, experimenters will be able to create !OpenFlow slivers to use in their experiments. Before they can actually use those slivers, though, you'll need to approve them (or "opt them in", in Expedient's terminology). Here are some things to think about when doing that:
     22
     23 * Does the sliver seem to accomplish what the experimenter is trying to accomplish? For example, if they tell you that they want traffic to and from a particular IP subnet for your MyPLC plnodes, you should confirm that this is actually what they've requested. If you aren't familiar with what the experimenter is trying to, you should probably ask them for more information about their experiment, since it's easier to evaluate their request if you know what their intended effect is.
     24
     25 * Is the experimenter requesting a safe topology? In particular, if they request a topology that includes more than one of the ports that cross-connect VLAN 1750 and the inter-campus VLANs, this can cause traffic leaks and broadcast storms. Some experimenters have good reasons for wanting a topology with multiple paths into the core, but you should confirm that they understand what they're doing, and that they know how to ensure that the controller for their sliver won't leak traffic or cause storms.
     26
     27 * Does their sliver include an IP subnet? If so, check the [wiki:NetworkCore/SubnetReservations network core subnet reservations page] and confirm that they've reserved the subnet they've requested.
     28
     29 * Does their sliver include an entire experimental (non-standard) ethertype? If so, check the [wiki:NetworkCore/EthertypeReservations network core ethertype reservations page] and confirm that they've reserved the ethertype they've requested.
     30
     31 * Does their sliver include an entire port on a switch? If so, confirm that they have an exclusive reservation for the entire device (or interface) connected to that port. (If the device is a MyPLC plnode, for example, they ''don't'' have an exclusive reservation for it; they should be requesting only an IP subnet or ethertype or some such, not all traffic to the entire port. If it's a Wide-Area ProtoGENI node (wapgnode), they might -- although you may need a Utah ProtoGENI admin to confirm that.)
     32
     33When in doubt, don't hesitate to ask the experimenter for more information about what they're trying to do. They're using your campus's resources, and it's important that you understand how they're going to use them -- and it makes it easier for you to help them if they have questions or run into problems.
    1634
    1735= Diagram =
     
    3957}}}
    4058
    41 ''(FIXME: A draft version of the diagram follow, which will replace the ASCII diagram above soon.)''
    42 
    4359[[Image(OF-CampusDiagram.jpg)]]
    4460
     
    4763VLANs starting with "17" are local to each campus, and are OpenFlow-controlled; the ones starting with "37" are inter-campus VLANs, which may be OpenFlow-controlled on campuses, or not. (This is up to each campus, and doesn't materially affect the topology.)
    4864
    49 See below for examples of how to configure the interfaces on NEC and HP switches to implement the above topology. (But note that the HP example isn't fully functional -- in particular, the configuration for ports 7 and 8 doesn't correctly implement option 3 above. We're working on developing a working configuration now.)
     65See below for examples of how to configure the interfaces on NEC and HP switches to implement the above topology. (But note that the HP example isn't fully functional -- in particular, the configuration for ports 7 and 8 doesn't correctly implement option 3 above.)
    5066
    5167= Uplink =