Home > Hyper-V, MS Technologies > InMon SFlow extension for Hyper-V 3 Part 1

InMon SFlow extension for Hyper-V 3 Part 1




Today the IT infrastructures trend is to be virtual oriented. In this case, we have to monitor some typical aspects.

One of the most important elements to manage is the network health as it is the basis of the machines communication. However, our main purpose is to analyze the bandwidth used by the machines. For this reason some new protocols are defined like NetFlow and SFlow.

What about SNMP? A very interesting response can be found here :

  • SNMP can be used for real-time (i.e. every second) and although NetFlow provides beginning and end times for each flow, it isn’t nearly as real-time as SNMP. In fact, due to the active timeout issue, NetFlow really can’t provide granularity finer than 1 minute else, it sort of defeats the idea of NetFlow’s awesome aggregation. I think we are all learning about how important the active timeout is with the Cisco ASA.
  • NetFlow tells you who and with what is consuming the bandwidth, it is also much more verbose than SNMP and therefore NetFlow exports consume much more disk space for historical information
  • SNMP can be used to collect CPU and memory utilization and that just isn’t available yet using NetFlow. Notice I used the word ‘yet’. The future of NetFlow is very optimistic.

I have recently worked on a very interesting project involving Hyper-V 2 and ESXi 5.0. I have applied some best practices on the virtual machines to improve the performances like increasing the VMbus buffer size. As a switch presents some problems, I noticed a big number of dropped packets and I searched some solutions that can help me to find the origins issue.

Here I have encountered the SFlow protocol which is used to monitor and analyze the flow networks. A definition of this protocol is described by this video :

As Hyper-V3 defines an extensible structure of the VSwitch, InMon has developed SFlow extension that can be integrated n the VSwitch pipeline. In this case, we can analyze the flow networks of the machines connected to Sflow activated switches.

In the Part 2, InchaEllah, I will describe the steps to install SFlow on Hyper-V3.

Categories: Hyper-V, MS Technologies Tags: ,
  1. No comments yet.
  1. August 26, 2012 at 1:47 pm

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 )

Google+ photo

You are commenting using your Google+ 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 )


Connecting to %s

%d bloggers like this: