Slashdot Mirror


Best Tools For Network Inventory Management?

jra writes "Once every month or so, people ask here about backups, network management, and so on, but one topic I don't see come up too often is network inventory management — machines, serial numbers, license keys, user assignments, IP addresses, and the like. This level of tracking is starting to get out of hand in my facility as we approach 100 workstations and 40 servers, and I'm looking for something to automate it. I'm using RT (because I'm not a good enough Web coder to replace it, not because I especially like it) and Nagios 3. I've looked at Asset Tracker, but it seems too much like a toolkit for building things to do the job, and I don't want my ticket tracking users to have to be hackers (having to specify a URL for an asset is too hackish for my crew). I'd prefer something standalone, so I don't have to dump RT or Nagios, but if something sufficiently good looking comes by, I'd consider it. I'd like to be able to hack a bit here and there, if I must. Perl and Python, along with C, are the preferred implementation languages; least favorite is Java. Anyone care to share their firsthand experiences with this topic, and what tools they use (or built) to deal with it? "

15 of 251 comments (clear)

  1. OpenNMS by spun · · Score: 5, Informative

    It's open source, it's free, it's a complete network management system, and you can import existing asset information as well as populate through network discovery. We use it here at the New Mexico Child Youth and Family Development Department, with 53 offices, 2500 workstations, and 80 servers.

    http://opennms.org/

    --
    - None can love freedom heartily, but good men; the rest love not freedom, but license. -- John Milton
    1. Re:OpenNMS by Z00L00K · · Score: 4, Informative

      I can agree that OpenNMS is a good choice. It contains most of the features you want for IT administration.

      The only disadvantage I have discovered with OpenNMS is that it is a bit heavy on resources, so I would recommend a dedicated server for the monitoring.

      --
      If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
  2. Do you want it to be open source or not? by GPLDAN · · Score: 4, Informative

    Open Source use OpenNMS: http://www.opennms.org/wiki/Main_Page

    Want commercial software?: Solarwinds Orion with IP Monitor.

  3. Roll your own... by Fallen+Kell · · Score: 3, Interesting

    We finally made our own. We created a mysql database and table schema storing the hardware information along with the schema for locations in the facility (typically cubicles, offices, labs, and server rooms). Wrote up a website using PHP with proper forms to insert new hardware, move hardware from one location to another, or remove hardware, and search functions to find hardware. We went a little further as well by getting floor and building plans and made clickable image maps for all the locations so that you can just browse to the building/floor/cubicle, see what is in there already, and add new stuff or move existing stuff etc., as well as have a way to highlight the location of a particular piece of hardware if you looked for it based on hostname, etc.

    It really isn't that hard to do. And if you setup your database tables and schema correctly so that you can easily expand for new hardware types, buildings/locations, it isn't too hard to maintain. The hardest thing that we deal with is when we move into a new building and we have to generate the floor map, but it doesn't usually take more then a few hours at most.

    --
    We were all warned a long time ago that MS products sucked, remember the Magic 8 Ball said, "Outlook not so good"
    1. Re:Roll your own... by Fallen+Kell · · Score: 3, Informative

      Took a couple weeks to hash out the database schema. Doing "what if", scenarios and the like to try and take into account future needs. We did a pretty darn good job since it has lasted 10 years now with only very minor changes to the database (adding a field here or there for other data that we felt was pertinent). The main idea is to make sure that it is robust in the sense that anything which could grow or change in the future is in its own table and you simply have a foreign key to easily get the values. Another big deal is to remove as much human input as possible, doing things like pull-down menus or choose from things so that you don't have something like "Sun", "Sun Microsystems", "SunMicro", "sun", "SUn Microsystmes" in a field...

      As I said with ours, since we have the building/floor maps, we do not let you physically type in a location, you have to click on the location from the maps. Again, this removes the chances of someone entering strange data. We do as much pattern matching/validity testing as we can do on the data to make sure it is correct, and have a verification page before data is actually input or changed in the database (with highlighting exactly what is changing). It also keeps a "history" of the hardware, along with who updated the data and when. It sounds a lot more involved then it is. A good schema for the database can easily take care of all these things. History is simply a table that is 3 fields, "id", "item_id", and "value", with "id" and auto increment primary key, item_id a foreign key which corresponds to the particular item, and value a text blob which stores HTML formatted text output of the fields that were changed, the old values, the new values, the date, and by whom. The information that gets placed in that is handled by the PHP webpage.

      I think we have something like 6-7 tables in our schema. Separating anything that we wanted to keep uniform into its own table which we have an administration front end to modify or add to those tables (things like manufacturers, models, etc). Again the idea is to make as little as possible be up to the human inputting the data so that the data will be consistent which will allow you to actually search for things and be sure that you find all of them, and not miss something because someone made a typo when entering the manufacturer name.

      It took probably 4 months from soup to nuts. But at the time, we had to compile everything from source code (something like a LAMP server wasn't really there yet, and you had to compile mysql, apache, and PHP to get them all to work properly back then). Now its a push of a button and it is basically done. In fact we had to compile the compilers before we could compile the LAMP software. A lot has changed in the last 10 years...

      --
      We were all warned a long time ago that MS products sucked, remember the Magic 8 Ball said, "Outlook not so good"
  4. GLPI by ZERO1ZERO · · Score: 4, Interesting
    http://www.glpi-project.org/?lang=en

    This might be the sort of thing, coupled with the OCNS agent it'll scan your network and log all the data into a myql database. Ticket system which allows users to report stuff attached to an asset, reporting, contracts, and stuff. Worth a look.

  5. To the toolboxes... by f8l_0e · · Score: 4, Insightful

    who keep tagging stories like these and especially 'Ask Slashdot' submissions with the domyjobforme tag, please STFU. Quite often, the submitter has done extensive research on the matter and shared his or her observations and is looking for people to share their ideas or experiences. Your attitude does not fit in with the open source spirit that the readers of Slashdot enjoy being a part of. If done as a joke, it is no longer funny.

    1. Re:To the toolboxes... by the_weasel · · Score: 3, Insightful

      Amen. Unfortunately there will always be elitist arses who think that just because they know a little bit about some obscure topic, anyone who doesn't is a lazy slacker. I don't have any need for asset tracking of this nature at the moment, but i found the topic interesting, and learned something from the few comments that have appeared so far. The politics and YRO topics bore me to tears. These topics are why I still bother to visit this site.

      --
      - sarcasm is just one more service we offer -
    2. Re:To the toolboxes... by Anonymous Coward · · Score: 3, Funny

      The submitter should try a forum, this is a news site.

      Dear Slashdot Forum,

      you're never going to believe this, but every word of it is true.

      Last Tuesday, me and my network inventory specialist, I'll call her Sally, were managing a little inventory, if you get my drift, when our assistant IT admin Veronica walked in unannounced. Well, from there things got a little freaky....to be continued....

    3. Re:To the toolboxes... by onkelonkel · · Score: 5, Funny

      There is a right way and a wrong way to ask for help in an open source forum.

      Wrong way..

      Q. How do I get my HP all-in-one printer to work in Red Hat?
      A. STFU Noob. RTFM.....

      Right Way..

      Q. Red Hat Sucks. It won't even print to my HP all-in one printer. I'm going to install Windows XP. At least it works.
      A. Oh my god, don't do that. All you need to do is edit foobar.print.cfg and change edrtflg$ = 0 ...PM me if you need any more help...

      --
      None of them can see the clouds; The polished wings don't care.
    4. Re:To the toolboxes... by Bigjeff5 · · Score: 5, Insightful

      Or he could try the Ask Slashdot section.

      Oh wait...

      P.S.: Slashdot is not really a news site. It looks like it is, but it isn't. It's a news aggregation site who'd primary "feature" is the opinions of fellow slashdotters. Most news sites don't recieve or want comments on their stories. Slashdot does, and the entire site is built around facilitating that. Go check out a slashdot story sometime to see what I mean. There will be a 200 word summary post and 150 comments, most of them centered on three or four discussions. That's Slashdot's added value to the news they serve. Hell, half the time the news here is stone cold, broke out days weeks or months before Slashdot got ahold of it, but the discussions make it interesting.

      --
      Security is mostly a superstition... Avoiding danger is no safer in the long run than outright exposure. - Helen Keller
  6. Open-AudIT by bman1978 · · Score: 3, Informative

    Open-AudIT is pretty good for cross platform but it doesn't cover all of your requirements. I'm yet to find anything that is an IP database plus complete system inventory. Open-AudIT is very good at the inventory side. I run it in Windows since I was trying to replace TrackIT. There's a Linux agent and it'd be pretty easy to customize it for other OSes. It does licensing as well. Want to know how many computers have Office and what version? Who has outdated Antivirus? It even gives you license keys used. Getting it up and running with XAMPP for Windows is quick for testing. I haven't used it as much on the server side. We use IBM Director for that.

  7. Nagios? by Darth_brooks · · Score: 4, Interesting

    Nagios? For asset tracking? "I was trying to check my e-mail using using apache, and it just wasn't living up to my expectations at all...." I guess when all you have is a hammer, everything looks like a nail.

    http://www.open-audit.org/ does a nice job of tracking on the windows side. Set up xampp, unzip the contents of the openaudit zip file into the htdocs directory, visit the side, move on with your life. Open Audit as a project is a little hackish and informal for my tastes, but it does pass the JFW (just fucking works) test. Tracks assets, installed software, license keys. It's just a PHP frontend for WMI results, so if WMI is acting funny, then open audit will be funny too. I also doubt it'll do much for network device inventory other than identifying approximately what the device is. (Printers show up ok, I doubt switches or routers will appear as anything other than "other".)

    My suggestion for integrating Nagios would be to set an action URL for each of your hosts that in turn points to the Open Audit page for that particular host, unless you're already using the action URL for PNP (and if you're not, you should be for some of your hosts.)

    --
    There are some people that if they don't know, you can't tell 'em.
  8. Re:you track your IP addresses? by afidel · · Score: 3, Insightful

    Servers=static
    Printers=static
    network gear=static
    random network devices=static

    In any non-trivial network you will have a significant percentage of your IP space utilized by static devices. Then you get into tracking multiple sites and their associated network information and it starts to get fairly complicated. We're small enough with a couple dozen sites and a dozen or so subnets at our corporate campus that we use a multi-tabbed excel document with the first tab being a table of contents.

    --
    There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
  9. Re:you track your IP addresses? by Em+Ellel · · Score: 4, Insightful

    There is no reason to add the dependency of a DHCP server to many of those services. Reserved DHCP works great under some situations but if you're talking about a static set of servers or equipment, static ip is more reliable.

    Depends on your situation and your resources. A while ago I did a favor for a friend in a mid size office (300 people or so) lacking a real sysadmin where they asked me to re-ip the entire network on a short notice. Luckily I had the foresight to make sure just about everything was on DHCP or static DHCP. With renewal time lowered to 24 hours - this gave me a 12 hour window - perfect for overnight reset. During the day I wrote a quick script to dump out, massage and re-write the static IPs in DHCP DB. After everyone gone home that night, all I had to do is change IPs on a the few static servers (DHCP server mostly) - activate the new DHCP scope and go home. 1/2 hour worth of work. Next morning everything was up and running, and for the few people who complained(there are always a few), a reboot fixed everything.

    So yes, static IPs are more reliable on small network or if you are well staffed and have time to burn. But there is value in static DHCP when you are understaffed. Of course it makes it much more important to keep the DHCP server up, but hey, you still have at least 1/2 your renewal time to fix it and hopefully you are monitoring your DHCP server.

    -Em

    --
    RelevantElephants: A Somatic WebComic...