A Protocol Analyser is an invaluable piece of software that takes the strain out of managing a network. Using an easy to use interface you can 'see' where your packets are going... and where they're not. Using features such as top-talker, a Protocol Analyser will tell you who or what is using up valuable network resources, when, where and why.
Protocol Analysers capture conversations between two or more systems or devices. A Protocol Analyser not only captures the traffic, it also decodes (interprets) the traffic. Decoding allows you to view the conversation in English, as opposed to binary language. A sophisticated Protocol Analyser will also provide statistics and trend information on the captured traffic. Protocol Analysers provide information about the traffic flow on your LAN/WAN, from which you can view device-specific information. Unlike SNMP-based management consoles, Protocol Analysers are device independent.
Why use a NetFlow Analyser instead of a Protocol Analyser ?
Who, What, When and Where: Scrutinizer provides historical trends of the company's critical network interfaces as well as the details on:
Who: The end system causing the traffic
What: The application/protocol that is being used
When: The time frame it has been occurring for
Where: The network connection that is affected
Result: If something is consuming excessive bandwidth the end system can be identified quickly, without utilising a packet analyser.
Today, NetFlow Analysis is the ideal solution
Scrutinizer uses your existing NetFlow capable routers and switches to report on top applications and top hosts on specific interfaces. It provides details on how much bandwidth is being consumed by each of these variables from protocols per user to users per protocol. Because Scrutinizer uses NetFlow technology on your existing routers, you never have to deploy or maintain probes. Scrutinizer goes beyond simple utilization graphs and tools like MRTG.
How Protocol Analysers are Useful
A Protocol Analyser is a tool that shows you exactly what is happening on your LAN. Once a problem is isolated and recorded, there can be no denying which vendor, or which system is the cause.
For example, if your TCP/IP sessions are "hanging", a Protocol Analyser can show which system sent the last packet, and which system failed to respond. If you are experiencing slow screen updates, a Protocol Analyser can display delta time stamps and show which system is waiting for packets, and which system is slow to respond.
In an NT environment, a Protocol Analyser can show runaway traffic (broadcast or multicast storms) and its origin, system errors and retries, and whether a station is sending, trying to send, or only seeming to communicate. You will get information that is otherwise unavailable, which results in more efficient troubleshooting and better LAN health.
