[Interop-dev] Common node managment template

[Gioacchino Mazzurco]

Hi all!

I have tried zabbix to monitor nodes but the problem is that zabbix
agent suffer memory leak on MIPS !!

More over it is not inter-operable with the map server so you have to
add same data (ipv6 address) more times,

So in the end trying to use zabbix was a failure but i learned a very
good thing from it

zabbix have is own monitoring protocol but it try to support also others
protocol(sadly a very little set), and moreover it uses template!!

In our networks we have a lot of devices with similar information so
having templating capabilities would be a killer feature for the common
map server, more over we can do them in a way that we use what kind of
firmware we want, openwrt, airos, mikrotik ecc ecc the template will
just teach the map server how to get the info from the device, i have
done a little prof of concept example for an openwrt device that is very
minimal, that device have nothing ( no snmp, no http ) just dropbear so
the template teach the map server to take info from it

so that i have attached is just a prof of concept but i think we have to
talk about that, keep in mind that you can use what you want inside that
template for example you can do


<property name="interfaces">
	<method name="get">
	<?bash
		#!/bin/bash
		snmp_get $host interfacces_oid
	?>
	</method>
</property>

or

<property name="interfaces">
	<method name="get">
	<?python
		#!/usr/env/python
		some_snmp_library_call(host,interfaces_oid)
	?>
	</method>
</property>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: picostation_opewrt.xml
Type: text/xml
Size: 2646 bytes
Desc: not available
URL: <http://lists.funkfeuer.at/pipermail/interop-dev/attachments/20120425/c1f4e038/attachment.xml>