Just the other day, Brad Reese from Network World wrote a nice blog reflecting on the recent announcement of H.P. acquiring 3Com.
With a huge announcement like this, naturally there are a lot of reactions and opinions. This kind of move may impact a lot of people and their current network strategies.
But coming from a NetFlow, sFlow and Netstream vendor perspective, I think this could be good news.
I love that title. It sounds so dramatic.
I’ve been seeing this issue lately and I think it’s worth talking about, since I can imagine it affects the way you see flows within just about any NetFlow traffic analyzer.
Within a NetFlow v5 packet, there are two rows that define the inbound and the outbound interface for every conversation. Those interface numbers are really just the ifindex interface ID assigned by your router.
The inbound/outbound interface fields are crucial to being able to calculate where your traffic stream is going.
Lets look at a couple screenshots:
It’s here!
We said it would come, and now it has been delivered.
With the availability of the new migration function, which comes with the latest release of Plixer’s own NetFlow monitoring application, we can now make your conversion from Scrutinizer NetFlow & sFlow Analyzer v6 to v7 smoother than ever.
Now, with the assistance of this new tool, your historical NetFlow data and elaborate Flash maps will be moved right on over to your new install.
Please know that there will be some limitations to this NetFlow data migration process. If you are still using Scrutinizer version 6 for your network traffic analysis and would like to know more about them, please contact Plixer support. Also, if you are interested to know what other new features and fixes are available in the latest release, take a look at the Scrutinizer version 7.2 release notes.
So, if you are eager to start running the most revolutionary Windows NetFlow Collector on the market, give our Support Team a call and we will assist you in getting your migration started!
Plixer Support
(207) 324-8805 ext: 4
One of the challenges that we sometimes face when integrating 3rd party applications within our NetFlow analysis tool is that they work until the 3rd party vendor decides to change something…
With that in mind, I wanted to let our customer base know that as of a couple days ago, Google made some changes to the way that they handle API keys. More specifically, any geocoding requests that are made from 3rd party vendors are required to pass an API key.
What does that mean for us?
“What do I get with the enterprise version of Scrutinizer?”
I’ve been getting this question frequently, so I figured: Why not write a quick blog?
Since Flow Analytics and Scrutinizer v7 have a fantastic symbiotic relationship, lets consider seven reasons to upgrade your free version to include a licensed copy of Flow Analytics.