Kind of service/VM/host/IP/location/asset register (and more)

Hi all, I am looking for an easy way to keep things in sync with reality.. Means: IP addresses, DNS, out of bounds IPs, blade centre, ESXi hosts etc. - and if possible physical location, asset register, monitor configuration, password safe etc. The current mix of DNS on Active Directory, Excel spreadsheets etc. "doesn't cut it". It's incomplete, it's redundant, it's not consistent.. and we spend sometimes too much time to find critical information just to get a few little things done, and things are overlooked etc. I had actually things in some "password-style" (with ":" as the separator) files before, and that was in version control and worked quite well, but from a certain point onwards it becomes a bit complex (I have much more variation in setup here, e.g) and you cannot convince other people that old-fashioned files are not that bad;-) So all ideas are welcome. Regards Peter

On 03/09/15 09:10, Peter Ross wrote:
Hi all,
I am looking for an easy way
Would be nice wouldn't it?
to keep things in sync with reality.. Means: IP addresses, DNS, out of bounds IPs, blade centre, ESXi hosts etc. - and if possible physical location, asset register, monitor configuration, password safe etc.
You could use nagios on each one and have them class home to s central server. Add some custom plug-ins to echo some other details (like address, asset tags, etc) and then you would have it all in one handy web control panel. I think nagios supports groups of hosts/networks so it might be that you can have network (out of bounds?) IP's set in there. Just an idea. P

On 3 September 2015 at 09:10, Peter Ross <petrosssit@gmail.com> wrote:
Hi all,
I am looking for an easy way to keep things in sync with reality.. Means: IP addresses, DNS, out of bounds IPs, blade centre, ESXi hosts etc. - and if possible physical location, asset register, monitor configuration, password safe etc.
I've found racktables to be very good at this: http://racktables.org/ You can import DNS records and match them to racks/servers/nics. For network discovery on it's own, netdisco isn't bad: https://metacpan.org/pod/App::Netdisco Along with rancid it helps keep track of network changes as they happen: http://www.shrubbery.net/rancid/ There's also observium which I've heard some good and bad things about. It looks like it's been forked recently, which may be a good thing: https://github.com/librenms/librenms Regards, Marcus.
participants (3)
-
Marcus Furlong
-
Peter Ross
-
Piers Rowan