Changes between Version 69 and Version 70 of OpenFlow/FOAM


Ignore:
Timestamp:
12/10/13 14:02:11 (6 years ago)
Author:
Josh Smift
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OpenFlow/FOAM

    v69 v70  
    341341In principle, traffic in GENI is sliced by VLAN, such that each slice has one or more private VLANs that carry traffic only for that slice. In practice, the current GENI mesoscale OpenFlow network consists mainly of VLAN-hybrid switches, and thus uses a single shared VLAN (colloquially "1750", the VLAN ID number used by many (but not all) sites), where traffic is then sliced by other features, such as MAC address, ethertype, or IP subnet. The [wiki:NetworkCore GENI network core page] has more details about that.
    342342
    343 The analysis engine differentiates between "exclusive" VLANs, "reserved" VLANs, and "shared" VLANs. The shared mesoscale VLAN (and other VLAN-hybrid datapaths) is effectively a special case of a shared VLAN, one in which no dl_vlan attribute is specified ("dl_vlan=none" is one way to think about it).
     343The analysis engine differentiates between "exclusive" VLANs (which are available for experimenters to reserve, but can only be in use by one sliver at a time), "reserved" VLANs (which the admin has configured to be unavailable for experimenters to reserve), and "shared" VLANs (which are available for experimenters to reserve flowspace within, but not the entire VLAN). VLAN-hybrid datapaths are is effectively a special case of shared VLANs, one in which no dl_vlan attribute is specified ("dl_vlan=none" is one way to think about it).
    344344
    345345By default, FOAM treates each VLAN as exclusive, unless a FOAM admin has added the VLAN to the list of reserved or shared VLANs. (A VLAN can be on both lists, although there's not really any reason to do that; but if you want to change a VLAN from one to the other, for example, you need to both remove it from the old list and add it to the new one.)