|
|
||||||||||||||||||||
| Home > Monitoring your enterprise network with Solarwinds' ipMonitor | |
| Screencast and Review: |
|
||
As a network engineer, you probably associate Solarwinds with its popular Engineer's toolset. That toolkit offers a plethora of tools that you can use to diagnose problems on an ailing network. When it comes to network monitoring, ipMonitor is Solarwinds' entry-level fault and performance management solution. Besides monitoring your network, ipMonitor gives you a graphical view of it. It can alert when critical network services or servers go down and can recover those critical servers to make them available again.
Pricing and features
Installing and using ipMonitor Once inside ipMonitor, one of the first things you will want to do is discover your network devices so that you can monitor them. To do this, I used one of the many ipMonitor wizards. These wizards make ipMonitor much easier to use. This wizard is the Device Discovery Wizard. I started with a basic auto discovery for my IP subnet (there are various ways to do it). Once the devices on my subnet were found, I was asked which services I wanted to monitor. In Figure 1, below, you see how I can monitor different services -- memory usage, CPU, bandwidth, battery, temperature, humidity, fan, drive space, Exchange, SQL, and many more.
In Figure 2, below, you see all the devices that were found and the different monitors that can be added for each device. I chose to add all the devices that were found.
In Figure 3, you can see that I am about to add 13 monitors -- one or two for each device.
In Figure 4, I moved into the Alert Wizard. This wizard is here to automatically create alerts for each new device added. This way, if the monitored devices cannot be communicated with, ipMonitor will notify me via email. I can configure the alert to be sent to me using an availability calendar. I can also choose to be alerted on recovery of the device.
Figure 5 shows the Alert Wizard summary. At this point, I chose to create an alert for all these new devices and go to the dashboard.
Back at the dashboard, Figure 6 shows the new devices that are added. You can see these devices in a number of places, such as in the network map and the summary counts for devices and monitors. That summary count quickly shows the counts for devices with warnings -- devices that are down, offline, or have another status.
In Figure 7, you can see more of the dashboard. For example, devices grouped by properties, monitors by properties, my reports, top 10 devices by CPU utilization, top 10 devices by ping response time, and top 10 devices by disk utilization. The dashboard is completely customizable.
My impression of Solarwinds' ipMonitor
In conclusion
About the author:
'); // -->
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
| About Us | Contact Us | For Advertisers | For Business Partners | Site Index | RSS |
|
|
|
|||||||