LMS 3.0 Health and Utilization (HUM)

Unanswered Question
Jan 24th, 2008


Was just curious if anybody piloted this new product and has some info about the issues, advantages over MRTG.

Is it using rrdtool or a regular DB, can the historic reports be generated, let's say going back 2 months into a particular day / hour.


I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (1 ratings)
Joe Clarke Thu, 01/24/2008 - 16:00

I find it a lot easier to configure than both cacti and MRTG. The reports are also nicer looking, and you can email reports.

The backend is using a homegrown poller (not RRDTool) with a Sybase database (same type of database as the rest of LMS uses). Historic reports can be generated, but to save space, the data is rolled up, so the further back you go, the more normalized the data becomes.

dmitry Thu, 01/24/2008 - 16:07

Thanks for the feedback. I'm still trying to makeup my mind. The fact that the portal allows to create the custom portlets is very attractive in terms of getting the same Cacti or MRTG interfaces on the same dashboard and again, with a bit of scripting the LMS managed devices can be exported and configured within these external apps.

Joe Clarke Thu, 01/24/2008 - 16:29

If you have LMS 3.0, you can download the 3.0.1 update for free which comes with a free 90-day eval license for HUM. If you haven't tried it out, you really should before making up your mind. The HUM portlets are kind of nice.

In my experience you need to install HUM on a box with only CS. I tested it out on a sun 240 dual proc 8G RAM, 16G swap with CS, RME, and HUM and had 50 6509's polled for the defaults. Beautiful information without the associated per polled element cost you see in Concord, but even with a polling interval of 1 hour, the box turned into a rock in a rack over the course of 6 hours. It stopped responding even at the OS level. Turned HUM off and sanity returned.


This Discussion