Network Monitoring Tools Review
A review of various Network Monitoring Tools and my opinion on them.
Pretty old tool now. But fairly simple to setup. An agent need to be installed on each machine and run as a daemon service. Unix centric, newer version has a windows agent. No reporting tool, interface is simple but not fancy.
Recently Quest Software aquired Big Brother. Moneyware vs Freeware versions still exist.
Newer than Big Brother. Still use a daemon process that run as a user process. Maybe worthwhile to look into if something lightweight is desired.
This is probably the best open source monitoring tool. Very flexible, though setup would be significantly more time consuming. Linux origin. Originally agent based, but SNMP capable now. Everything is possible, you just need to configure it :)
Newer network monitoring tool. SNMP centric, Unix based. If you don't like the security model of SNMP,
then this would not be the tool for you. But this is targeted at the enterprise user, to compete with HP Open View and
Better know as What's Down.
Windows based tool. SNMP centric.
Kinda pretty looking with reasonable graphics, but the GUI is actually rather clumbsy interface. Lot of click for saving and going back before one can drill into other details, instead of using a more simple tab-based interface for faster navigation. The discovery tool leave much to be desired. It can find all the machines in the vlan, but it does not use nmap fingerprinting tech to guess what kind of OS a given node is, so leaving everything as generic.
What's Up itself need to be monitored by another server as it seems to die often. Not recommended unless a simple tool to monitor ping availability of the machines in the network.
Another windows centric tool. It relies heavily on VB Script to do monitoring. It needs to run as a windows domain administrator user so that it can remotely login to other machines and gather info. If this is not acceptable, look elsewhere.
The behemonth. Really big, plan to get an admin or two to maintain it. I know of a company that bought it but never deployed it. Go figure.
Different tools have different strengths and weakness. But some seems to be rather much a waste of time or money :)
For something lightweight, check Big Sister. If you have a bit more time, look into Nagioes, it is my favorite.
Specialty Monitoring Tool
This isn't exactly a specific tool, but I evaluated it specifically for monitoring NetApp filers.Works pretty well, butter than the NetApp DFM tool. Allow logging of file usage so admin
can get an idea what files are hardly used anymore. Lot of reports, but if customization
is desired, it may not be trivial (DB schema not published).
As usual, MS product is only for working with MS Windows. But this is a very powerful tool when
the number of windows machines is substantial to warrant its own island of administration.
It is probably should not be used so much as monitoring machine availability per se, but a
very good tool to keep track of MS windows setup, push out updates, keep inventory, etc.
Ver 3.0 is actually pretty robust and much better than the old stuff. Reports are extensive,
and the internal DB now present standardized VIEWS so that custom reports can created easily
(and hopefully still work with the next major release, one level up ;-P ).
It is not easy to configure or use, must read the manual. Taking the class Managing Microsoft System Management Server 2003 (2596B) would go a really long way to understanding this monster tool. Though some third party installer packaging tool and understanding of International Language Support on different Windows would also be useful.