How do you know if the NetFlow collector is saving or even getting all of the NetFlow datagrams that are being sent to it or that it is receiving? It is important to know if any flows are missing.

Why do we care?

This is a great question. We care because a loss of flow exports is usually caused by one of three things:

1. The network dropped some packets
2. The router can’t keep up
3. The NetFlow receiver / collector can’t keep up

NetFlow sequence numbers are becoming increasingly important. When building a NetFlow collector it is important that the engine scales while staying accountable. If you look at the NetFlow v9 packet format you will notice something called the package_sequence.

Read more »

NetFlow impact on hardware performance carries a common misconception. Competitors of Cisco would like you to believe that enabling NetFlow will often bring the router or switch to its knees. The sFlow founders would also like you to believe this. Although we are sFlow supporters, I thought I would take an opportunity to set the record straight.  Read more »

Michael Patterson
Scrutinizer Product Manager
Follow Me on Twitter

We’ve noticed that HP is definitely making inroads into the switch market. People are still buying Cisco routers, but consumers are realizing that they can use less expensive switches on the periphery. The list of features on the HP Procurve is impressive, however, their promptness to market a feature doesn’t mean it was implemented well, or even free of bugs. Read more »

Michael Patterson
Scrutinizer Product Manager
Follow Me on Twitter