A New Spin on NetFlow

Netflow as a technology originally seemed to be really cool: You could identify who’s hogging the bandwidth and then go clobber them.

The problem is that Netflow (and all of the other flow protocols jflow, sflow, etc.) are “after the fact” reporting mechanisms:  The router only transmits a flow record after the 40gig download has completed (2 hours after the network slowdown started).

Some products claim to show “real-time” netflow records, but they’re only showing you the records as they arrive in their system (still after-the-fact).

Thus, when the network slows down, Network engineers still have to set up analyzers and a span ports to hunt down who’s stealing the bandwidth and what they are doing.  This process takes a skilled engineer and at least 10 minutes to set up and start analyzing packets.

Since the problem of “why is the network slow” isn’t solved with existing Netflow implementations, I figured there has to be a better way.  With a bit of poking, prodding, and painstaking research, I discovered that there WAS a better way: Read the LIVE flow-table INSIDE the router!

That’s how we coded SwitchMonitor’s Netflow solution.  This gives you a number of advantages over the “netflow collector” type of solution:

  1. You get to see LIVE flows and instantly know who’s stealing the bandwidth and what they are doing
  2. You can monitor HUNDREDS of interfaces with our Netflow solution (other “collectors” require gobs of disk space, CPU performance, and RAM to be able to monitor just 5 interfaces!)
  3. When we send a high utilization alert email, we send the Netflow information along with the alert.  This gives you the alert as well as WHO is taking the bandwidth and WHAT they are doing

We posted a video explaining how this solution can benefit your network on our website: www.pathsolutions.com/products/video.htm

We do recognize that some companies may still want the historical Netflow records.  That’s fine.  There’s tons of historical Netflow solutions on the market.

When you’re interested in solving the problem for live flows, or for many interfaces, we’re the only game in town because all of the other solutions seem to have missed answering the original question: “What’s slowing down the network RIGHT NOW?”

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


%d bloggers like this: