OpenFlow vs NetFlow | Data story
1

OpenFlow vs NetFlow

In the BigData area we never speak about the new network requirements and new challenges those new technologies bring, but along with NoSQL solution new network technologies have also rise, this post will provide you an insight.

While those acronym might sound familiar and similar,  OpenFlow and NetFlow are two different technologies used for different purposes.

The differences are explained below:

OpenFlow is a methodology used to forward packets across network devices like routers or switches. OpenFlow provides an open protocol to design the flow table in switches and routers. It is helps in research on flows and control them.OpenFlow helps design a high speed, reliable network with accurate packets forwarding to desired receivers.

NetFlow is a Cisco proprietary protocol which helps in network audit of transactions (Traffic) that took place in network devices. NetFlow(and other flow formats like sFlow, IPFIX) helps in identifying top talkers on the network, top applications, port and protocol utilizing the bandwidth. The benefits of using NetFlow  export are as follows:

  • Traffic Analytics
  • Network Forensics
  • Bandwidth Monitoring
  • Capacity Planning
  • Trend Analysis
  • Application performance monitoring

Difference between NetFlow and OpenFlow:

OpenFlow uses fields like Source Address, Destination, Soruce MAC, Destination MAC, port, protocol to perform effective packet forwarding across switches.

Whereas the NetFlow uses the flows with above mentioned fields for traffic monitoring, auditing and capacity planning.

The purpose is entirely different.

If you are looking for an effective packet forwarding technique on the network , the right option would be OpenFlow. If traffic monitoring and security analytics is your goal, the NetFlow based analysis is the answer for you.

 

Find out more information:

OpenFlow

NetFlow

Article Global Facebook Twitter Myspace Friendfeed Technorati del.icio.us Digg Google StumbleUpon Eli Pets

Comments are closed.

Follow LuxNoSQL on Twitter
 
Join the LuxNoSQL Community on LinkedIn