Changes between Version 19 and Version 20 of OpenFlow/CampusTopology
- Timestamp:
- 08/29/11 15:19:16 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
OpenFlow/CampusTopology
v19 v20 21 21 Once 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 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.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 do, 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 24 25 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. … … 35 35 = Diagram = 36 36 37 The following is a minimalist diagram of a single !OpenFlow switch configuration that implements the infrastructure to support all three of these options: 37 Here's a minimalist diagram of a single !OpenFlow switch configuration that implements the infrastructure to support all three of these options. 38 39 In text form: 38 40 39 41 {{{ … … 56 58 12+ more hosts T 1700 1750 3715 3716 57 59 }}} 60 61 Visually: 58 62 59 63 [[Image(OF-CampusDiagram.jpg)]]
