Simple Network Management Protocol (SNMP) gives a high-level view of aggregate traffic on the network. Packet sniffers provide an in-depth view of packet content. What most enterprises are missing is the middle view: network flows. Most switches and routers are designed to generate information on exactly what traffic is passing through each port, but accessing this data requires additional software. Enterprise Strategies interviewed Michael Patterson, product manager for the Scrutinizer NetFlow and sFlow Analyzer at Plixer International to find out how to leverage the data available through flow monitoring.
Ingress or Egress, That is the Question Are you considering a NetFlow export configuration with egress flows? Do you know why you would or wouldn’t want to export egress flows?
For a small technology company like Sanford, Maine’s Plixer International Inc., landing giant customers such as Raytheon Co. or The Coca-Cola Co. means that CEO and president Michael Patterson can no longer just step out into his backyard and get in some rifle target practice during lunch, as he often did when the company was a startup.
Network performance vendor – Plixer International believes that Cisco’s Flexible NetFlow (FNF) is the future of NetFlow technology. Continuing its role as “NetFlow’s technology evangelist,” Plixer developed the following tutorial on how to setup standard fields in FNF for inclusion in my ever growing collection of Cisco How-To Tutorials. However, please keep in mind that Plixer is keenly aware I lack any kind of “technical aptitude” whatsoever, and that’s why Plixer made a few LEGO Block comparisons along the way in order to help me achieve a better understanding of FNF: Here are the 4 steps of an FNF configuration:
Keeping tabs on the performance of an SMB’s network is a necessary, and often laborious, task. System admins need to be able to know if and where problems are occurring on their network.
There’s more than data flowing through your network: Your infrastructure is also likely kicking out a mass of data about that data. Some network managers have a tough time corralling it all. That’s where NetFlow and sFlow analyzing software comes in. Read more: http://www.itworldcanada.com/article/scrutinizer-adds-unusual-map-to-flow-analyzer/40257#ixzz3aoQ9YGuq or visit http://www.itworldcanada.com for more Canadian IT News
Sniffing out the root of network congestion without the right tools can eat up time and resources. A NetFlow traffic analysis tool helped one nonprofit pinpoint what was choking its Cisco gear and put an end to the guessing games.
As network complexity has grown, network monitoring methods have evolved. Originally, network monitoring for most companies simply meant making sure the connections were live. A utility would regularly ping all of the critical devices on the network, and if one didn’t respond, it sent out a notification. In the early 90s, these utilities started generating synthetic transactions to ensure, not only that there was a connection, and that the actual application was running. This enabled the generation of response time and availability reports. Now, most network monitoring applications are even providing SNMP (Simple Network Management Protocol) trends.
Below, network performance measuring vendor – Plixer International, gives the Cisco Subnet its How-To Tutorial on guaranteeing QOS with network traffic: “As timely transmission of data across the network becomes increasingly important, so too does the science of QoS. How do we know for sure that millisecond sensitive packets are getting the priority we want them to receive as they traverse the IT infrastructure?” Cisco DiffServ to the rescue?