Bandwidth monitoring hasn’t been as big a concern for as long as some of us might think. Ethernet was founded in 1973 by Bob Metcalfe and David Boggs. Read more »
Michael Patterson
Yes, you can use NetFlow to monitor traffic and bandwidth usage on an ASA.
One of the primary uses for NetFlow on a Cisco ASA is as a transport protocol for security events. But if you are using the right NetFlow Analysis tool, you can also analyze traffic using NetFlow sent from the Cisco ASA.
This is really important as I have seen many companies that have remote sites that are connected with a Cisco ASA, but had no devices behind the ASA’s that supported NetFlow. This meant that they couldn’t leverage NetFlow to analyze traffic.
Any internet service providers out there interested in MPLS NetFlow reports for network traffic analysis? I was reading this document on NetFlow MPLS Label Export and thought it might be interesting data to report on. Read more »
Michael Patterson
The following article, “Scrutinizer Brings Flow Analytics to SMBs“, written by David Diaz, was recently featured on TechCrunchIT.
David points out that with the low initial cost for Scrutinizer NetFlow & sFlow Analyzer, it is a very affordable Flow Analytics solution for small and medium-sized businesses.
This flow analysis tool can also be deployed centrally and accessed globally via the web interface. What this means is that one install of Scrutinizer can provide network management information for your entire network and accessible by everyone on the network management team, regardless of geographical location.
Plixer International, your team of friendly neighborhood NetFlow specialists, has just released the newest version of Flowalyzer, our NetFlow and sFlow configuration tool. In addition to some performance and usability enhancements, version 2.0 adds a new tab to the Flowalyzer interface.
The latest addition to the Flowalyzer tool is the Trender tab, which creates graphs for critical Windows resources, all done in real-time (a configurable update period that defaults to once every second). The Trender uses SNMP information gathered from your compliant gear to measure metrics from interface utilization to CPU or memory consumption. There is no limit to the number of metrics you can trend simultaneously (aside from the obvious limitation of screen real estate).
Hi there everyone! I hope you’ve had productive week and I wish you all a fantastic weekend.
This week, we’ve had two successful webinars that highlighted some of the fun new features for Scrutinizer v7.5 and I’d like to make the replay available to everyone who wasn’t able to be in attendance.
So if you’d like to get the inside scoop on some of the new goodies like NBAR reporting, the new Matrix connections report and the Flow Expert toolset ; take a seat, grab some popcorn and enjoy the movie.
Oh, to take advantage of these new features, be sure to upgrade your copy of Scrutinizer to v7.5.
Here’s the link to the latest download: Scrutinizer v7.5 update
If there are any questions that come up during the webinar, please feel free to contact us and we’ll be happy to help.
(207) 324-8805
Nate
Most of my blogs are related to NetFlow or sFlow. This weekend I’m taking a break from network traffic monitoring. My father in law, some friends and I took off snowmobiling up in Sherman, Maine.
I have so many trade show shirts that I end up wearing them on events like this from time to time. I couldn’t resist this picture below. Funny thing is, I’ve had people approach me in restaurants when they see my t-shirts for Cisco, Nortel, etc. Read more »
Michael PattersonHave you heard about exporting egress NetFlow? Do you want to know why it is different from ingress NetFlow or more importantly, when to implement it for network traffic monitoring? I’ll cover this topic in today’s blog. Read more »
Michael PattersonHello everybody! My name is Paul Dube and I have recently graduated from the University of Maine in Orono with a degree in Computer Science and joined the support team here at Plixer International. Over the course of the past few weeks I’ve been trying to learn everything there is to know about Scrutinizer, NetFlow, sFlow and network traffic analysis. During this process I’ve come across a lot of great resources that I would like to consolidate into one place to help you get started.
Read more »
Most people collecting NetFlow use it in a very traditional fashion (i.e. NetFlow v5 with ingress flows). Ingress flow means that only inbound (i.e. received) traffic is collected and exported in NetFlow datagrams. This may sound like you won’t know what is going ‘out’ an interface, but have no fear. There is any easy way to calculate outbound traffic using ingress NetFlow.
Above, out bound utilization on interface 1 is determined by looking at the flows from interfaces 2,3 & 4 that are destined for interface 1. Since an ingress flow contains the source and destination interface (i.e. port of the router). Out bound traffic is determined by using ingress flows from the other interfaces. For this reason, it is important to enable NetFlow on all interfaces of the switch or router. This trick is common practice in all NetFlow reporting tools. But, what about NetFlow v9 and its support for ‘Egress’ NetFlow (i.e. traffic going out an interface)?
