Scrutinizer v7.6 has been released with several best at NetFlow improvements for network traffic analysis. You will find the upgrade available for download now.

New Features include:

+ Flow View now has a Date Selector
+ Users can name their templates exported from flow devices
+ Time frames for 3, 7, and 30 days have been added to the date selector
+ Volume reports have an option to toggle rate vs. totals
+ A new LDAP wizard has been added to simplify LDAP and LDAPS configuration
+ More definition labels have been added for ICMP Traffic
+ NBAR descriptions will no longer be blank if no template has been received
+ Fixed issue when performing an SNMP update for a PC with nprobe installed
+ Users can now configure thresholds based on a per row or report total basis
+ A new report type of IP Next Hop has been added to the status tab
+ Users who are part of an administrator group can copy myview tabs
+ A new report filter has been added for SUBNET TO SUBNET
+ The interface instance column is wider for high interface numbers
+ A Plixer Tools icon will now be visible when Plixer Tools is installed
+ Users can now add very long community strings
+ Added the ability in mapping to filter Denika reports for Denika connections
+ For new installs, users will automatically be licensed for 30 days
+ Updated the Japanese Translation
+ Improved IPFIX support in the NetFlow and sFlow collector
- Dozens of bug fixes

We are very excited about this new release of our network traffic analyzer. Contact us if you have any questions.

Jon Mills
Marketing & Public Relations Manager
Follow Me On Twitter

Scrutinizer v7.6 has been released.  One of my favorite features is the ability to rename NetFlow v9 templates, IPFIX templates and Flexible NetFlow Templates. We had to provide this feature since Cisco NetFlow does not export the template name.  Do you know why this is such a cool feature? Read more »

Michael Patterson
Scrutinizer Product Manager
Follow Me on Twitter

Working in technical support I get asked a lot, “I enabled NetFlow on my router, why don’t I see outbound traffic?” This is because NetFlow version 5 only supports ingress flow monitoring and they don’t have NetFlow enabled on all interfaces. In NetFlow v5 outbound traffic is calculated by the idea what goes in must go out (or stop at the router) so, it’s necessary that all interfaces are monitoring ingress traffic to get an accurate representation of outgoing traffic. So, if ingress monitoring has been working great all along why enable egress monitoring?

Read more »

Paul Dube
Technical Support
Follow me on Twitter

I was scouring the web looking for information on NetFlow v9 the other day and came across this document on NetFlow.   I thought these slides on ‘show ip cache flow’ and ‘show ip cache verbose flow’ were interesting.  If you are trouble shooting with a customer, they can be pretty useful.  Read more »

Michael Patterson
Scrutinizer Product Manager
Follow Me on Twitter

At Plixer International’s Technical Support desk we often take calls in support of our NetFlow and sFlow analysis tool that deal with disk space and disk performance issues. In the world of NetFlow and sFlow collector appliances, the name of the game is to have sufficient available disk space and minimize disk I/O. Read more »

We had a customer approach us the other day with an nprobe issue. Apparently, he could see the NetFlow v9 data in Flow View of Scrutinizer, but he couldn’t report on the data. How come?

He sent us a Wireshark packet capture and brought up Flow View. Flow View is a way to see the raw flows (inclusive of all columns) being exported by a device.

Anyway, in Flow View everything looked normal, but then one of our developers spotted the word ‘post’ in front of a couple of import column names. We (and Scrutinizer) expect to see ‘octetDeltaCount’ and instead, the customer had configured nProbe to kick out ‘postOctetDeltaCount’.

Read more »

Jon Mills
Marketing & Public Relations Manager
Follow Me On Twitter

SUNY Geneseo Network Manager Rick Coloccia found that analyzing Cisco NetFlow packets was the key to network traffic management and monitoring internet use and abuse.

Using Scrutinizer NetFlow Analyzer, he was able to respond to the RIAA’s (Recording Industry Association of America) allegations of students illegally downloading or sharing of music.
Read more »

I don’t remember where we saw it, but there was a report that stated there were 102 unique vendors that released a NetFlow tool in 2008.

I don’t know how accurate that is, but I can definitely confirm that if you go to Google.com and search the key word NetFlow, you’re going to get a LONGGGGGGGG list.

So with a plethora of options and little time to evaluate, what does Scrutinizer offer that might make it worth…scrutinizing? (Sorry, couldn’t help it)

Here’s five compelling reasons to take a look at my product:

Read more »

Do you ever need to see the NetFlow or sFlow data down to the actual second interval?  Did you know you can do it with your NetFlow Analyzer?  Sub minute visibility is only a click away for the Network Admin. Below I zoomed in on a two minute interval that I want to take a closer look at.  Read more »

Michael Patterson
Scrutinizer Product Manager
Follow Me on Twitter

You’ve installed Scrutinizer only to find out that your network hardware doesn’t support NetFlow or sFlow; what now? If you’re in this situation then you’ve come to the right place. I’ve put together a guide on how to configure a Windows nProbe to send NetFlow v5 to your favorite NetFlow collector and analyzer.

Read more »

Paul Dube
Technical Support
Follow me on Twitter