Screencast and Review

Monitoring your enterprise network with Solarwinds' ipMonitor

In this short screencast and tip, David Davis demonstrates how Solarwinds' ipMonitor can help you monitor your enterprise network.

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
One of the first things I look at when considering any software application is its price. I was pleased to see that ipMonitor starts at a reasonable price point of $1,495 for 100 monitored devices. For that price, the tool comes with several features "out of the box." For example, ipMonitor can monitor network devices in 50 different ways, including specific infrastructure services such as Windows performance, Exchange, SQL, site and transaction servers, Cisco routers, switches, and more. In addition, ipMonitor's System Resource Monitor (SRM) can monitor network bandwidth, battery consumption of UPS systems, CPU load, hard drive availability, and RAM utilization. And because ipMonitor is agentless, there are no software agents to install on your servers.

Installing and using ipMonitor
First, I downloaded the ipMonitor 21-day demo from the Solarwinds ipMonitor website. To use ipMonitor, you open your Web browser and point it to your localhost, port 443.

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.

ipMonitor monitor services
Figure 1

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.

ipMonitor add all devices
Figure 2 (Click image to view larger)

In Figure 3, you can see that I am about to add 13 monitors -- one or two for each device.

ipMonitor adding monitors
Figure 3

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.

alert wizard
Figure 4

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.

wizard summary
Figure 5

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.

ipMonitor new devices added
Figure 6 (Click image to view larger)

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.

custom dash
Figure 7 (Click image to view larger)

My impression of Solarwinds' ipMonitor
I'll admit that I was initially skeptical about ipMonitor. However, after installing, configuring and using it for some time, I was pleasantly surprised that ipMonitor does all that it claims -- and more. To see ipMonitor in action, watch my video screencast at the top of this page.

In conclusion
As network engineers, what we are looking for is knowledge and, hopefully, some kind of automation, because both of these would make our lives easier. This knowledge and automation of network monitoring, alerting, and recovery of network devices is what ipMonitor provides. Better yet, ipMonitor does that with minimal configuration and at a reasonable price point. I would highly recommend Solarwinds' ipMonitor.

About the author:
David Davis (CCIE #9369, VCP, CWNA, MCSE, CISSP, Linux+, CEH) is the Director of Infrastructure at Train Signal, Inc. He has written hundreds of articles and six video training courses, including the Train Signal VMware ESX Server video training series. His websites are Happy Router.com and VMwareVideos.com.

This was first published in October 2008

Join the conversation Comment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.