Why use ipMonitor? Here is actual use data to tell you why.
- ipMonitor is well suited to use SNMP sources to monitor up states and usage such as network interfaces
- ipMonitor does a great job of measuring bandwidth usage and delivering a long term 'picture' of usage
- ipMonitor has an exceptional interface that is easy to use and simple to navigate
Cons
- ipMonitor network maps could be simpler to manage and have more options for device representation
- ipMonitor saves time and effort when measuring usage and monitoring up/down time, freeing you for other projects
- the ability to demonstrate long term usage, with reports, of given resources makes the process of justifying upgrades vastly simpler
- ipMonitor is primarily used to alert IT staff to a downed device
- ipMonitor is also used to to record up/down conditions of specific devices and groups of devices
- ipMonitor is also used to to record usage and bandwidth requirements of specific devices and groups of devices
- The main value we have found with ipMonitor is knowing when a device is down, we get alerts fast and get very few false alerts
- The ability to have usage history is also valuable, this lets us know if a piece of equipment is under utilized and can be moved or over utilized and needs more
- Reports that tell us the up/down conditions of devices or groups of devices show us the reliability of a given device/group in a given area
- We have plans to use ipMonitor in conjunction with netflow software to get flow data when a device is down and get historical flow data on groups of devices