close Warning: Can't synchronize with repository "(default)" ("(default)" is not readable or not a Git repository.). Look in the Trac log for more information.

Changes between Version 13 and Version 14 of Proto/cModules/e0SDN/a0OpenFlow/a0Floodlight/a0SoftwareDesign


Ignore:
Timestamp:
Jul 29, 2013, 4:43:42 PM (11 years ago)
Author:
aravind
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Proto/cModules/e0SDN/a0OpenFlow/a0Floodlight/a0SoftwareDesign

    v13 v14  
    1515
    1616 All OpenFlow switches that are to perform the functions of a MobilityFirst router are connected to a central controller. As the sender starts to transmit data, the first packet of the chunk is sent to the controller since there is no matching flow rule as of yet. The controller uses the GUID  map it created using link probe messages to compute the out port on the switch and sends an appropriate flow rule. The rest of the packets are then forwarded by the switch. Chunks that have to be stored are sent to a software CLICK based router which can handle chunk storage.
     17
     18 The figure below shows the the controller learning GUIDs from link probe messages.
     19
     20[[Image(guidLearning.jpg)]]
    1721 
    18  The flow rules are set up using VLAN tags. Every host that wants to send MobilityFirst chunks inserts the hop ID of the packet as a VLAN tag. The controller uses this tag to set up a matching flow rule on the switch.
     22 The flow rules are set up using VLAN tags. Every host that wants to send MobilityFirst chunks inserts the hop ID of the packet as a VLAN tag. The controller uses this tag to set up a matching flow rule on the switch. The figure below shows the flow of a MobilityFirst chunk, with the first packet initiating the flow set up.
     23
     24[[Image(chunkFlow.jpg)]]
    1925
    2026== 2. Installation ==