In larger environments it is useful to document networks and servers along with monitoring them. For example, we can use Zabbix to user SNMP and detect whether a cable has been unplugged from a switch. But how do we document whether that cable should be plugged in at all?
I've found it hard to locate good open source (or even commercial) network and server documentation tools. And I don't mean Visio for drawing pretty pictures, but something that goes right down to tracking IP addresses assigned to servers, physical ethernet ports and cable patching, etc.
Now Zabbix seems like it is 80% of the way there.
* I can document which switches exist on my network
* I can discover and document the name/ip of all my workstations, plus track serial numbers, CPU, memory and other configuration of each
* I can (sort of) track dependencies and create a network graph. I say 'sort of' since the UI is a bit rubbish and we can't easily draw a graph/tree automatically.
* we can add all sorts of parameters to each device and add notes
But what we cannot do are things like:
* document patching and switch ports. Zabbix can monitor them easily, but where do I notate the existing patching structure? Or print out a patch sheet to stick on the rack door?
* store passwords (with appropriate security and auditing of course)
* easily graph the relationship between objects in a network (be those relationships physical cabling or virtual network dependencies).
Zabbix tries so hard to make everything generic (a BIND application, switch, server, router, etc are all just hosts with no distinguishing customisable features) so I wonder if this will ever be possible.
So what do other people do? Are there tools that can be made to play with Zabbix and avoid entering mostly the same information twice? Or will Zabbix itself head in that direction one day?
I've found it hard to locate good open source (or even commercial) network and server documentation tools. And I don't mean Visio for drawing pretty pictures, but something that goes right down to tracking IP addresses assigned to servers, physical ethernet ports and cable patching, etc.
Now Zabbix seems like it is 80% of the way there.
* I can document which switches exist on my network
* I can discover and document the name/ip of all my workstations, plus track serial numbers, CPU, memory and other configuration of each
* I can (sort of) track dependencies and create a network graph. I say 'sort of' since the UI is a bit rubbish and we can't easily draw a graph/tree automatically.
* we can add all sorts of parameters to each device and add notes
But what we cannot do are things like:
* document patching and switch ports. Zabbix can monitor them easily, but where do I notate the existing patching structure? Or print out a patch sheet to stick on the rack door?
* store passwords (with appropriate security and auditing of course)
* easily graph the relationship between objects in a network (be those relationships physical cabling or virtual network dependencies).
Zabbix tries so hard to make everything generic (a BIND application, switch, server, router, etc are all just hosts with no distinguishing customisable features) so I wonder if this will ever be possible.
So what do other people do? Are there tools that can be made to play with Zabbix and avoid entering mostly the same information twice? Or will Zabbix itself head in that direction one day?
Comment