Changes between Version 2 and Version 3 of 2012/Projects/OpenFlowMF


Ignore:
Timestamp:
Aug 14, 2012, 9:00:01 PM (5 years ago)
Author:
aravind
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • 2012/Projects/OpenFlowMF

    v2 v3  
    88Traditionally, routing protocols are implemented as distributed algorithms running on several network devices that communicate with each other to keep the routing information converged. This has certain drawbacks such as the time it takes to recompute routes in case of link failures and the performance limitation of software implementations (such as ones using Click). However, if we can program the switching fabric to route packets based on rules that conform to the desired routing protocol, then a much higher throughput can be achieved. This is the idea behind OpenFlow. A central controller which can see a map of the entire network, runs the routing algorithms, and installs appropriate flow rules on the switches to make them act like routers. Hence the architecture is one where a central intelligent controller defines how packets are handled by several dumb network elements, instead of the traditional method of using several intelligent network devices working in conjunction with each other. In this way, we can not only implement routing protocols on a switch, but also program the controller such that back up flows are installed immediately if links or devices in the network go down.  
    99 
    10                                            [[Image (OPENFLOWARCH.png)]] 
     10                                           [[Image(OPENFLOWARCH.png)]] 
    1111 
    1212== Limitations of OpenFlow v1.0 Standards: ==