Changes between Version 5 and Version 6 of Layer1Transport


Ignore:
Timestamp:
07/31/13 15:36:27 (11 years ago)
Author:
tupty@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Layer1Transport

    v5 v6  
    11[[PageOutline]]
    2 = layer1transport =
     2= GENI layer1transport service =
    33
    44== Introduction ==
    5 These pages explain how to install and use the layer1transport service.  This service is used to implement layer-1-style forwarding through OpenFlow-enabled switches using user-defined match criteria.  Think along the lines of a service that sets up and maintains pseudowires based on some combination of ingress-port/egress-port, DPID, VLAN ID, subnet, etc.  The flows for forwarding this traffic are statically defined in files for the service to manage.
     5These pages explain how to install and use the layer1transport service.  This service is used to implement layer-1-style forwarding through OpenFlow-enabled switches using user-defined match criteria.  Think along the lines of an operator-facing service that sets up and maintains pseudowires based on some combination of ingress-port/egress-port, DPID, VLAN ID, subnet, etc.  The flows for forwarding this traffic are statically defined in files for the service to manage.
    66
    7 The GPO wants to provide the experimenter with a view of a pure !OpenFlow network on the mesoscale VLANs. MAC address learning on point-to-point VLANs that pass through non-OF switches can interfere with certain forwarding patterns that are possible in pure !OpenFlow network. One specific place we see this problem is on non-OF VLANs that are used for VLAN translation on the !OpenFlow Backbone switches.
     7The GPO wants to provide GENI experimenters with a view of a pure !OpenFlow network on the mesoscale VLANs, and the layer1transport package is one tool that administrators can use to provide such a view of the network to experimenters. MAC address learning on point-to-point VLANs that pass through non-OF switches can interfere with certain forwarding patterns that are possible in pure !OpenFlow network. One specific place we see this problem is on non-OF VLANs that are used for VLAN translation on the !OpenFlow Backbone switches.
    88
    99The current implementation of this service uses Floodlight and the Static Flow Pusher service that is distributed with Floodlight.