Hi everyone,
I'm concerned too by this because I'm using some unrecognized switches at my office, the Pronto Pica8 3290 (SDN Open Source big switch). I would love to have all parameters working in Observium so I'll planned to develop an OS for Pronto's OS named Xorplus (you can use Open vSwitch too on it).
Anybody have developped for that brand before ?
Kind regards,
Le 18/06/2013 21:58, Jon Auer a écrit :
- I have some devices that aren't known to Observium that I'd like to
track. I've followed the instructions at http://observium.org/wiki/Developing/NewOS and made a new OS type for Ubiquiti EdgeOS routers. Diff here: http://www.tapodi.net/~jda/dev/edgeos.diff http://www.tapodi.net/%7Ejda/dev/edgeos.diff Did I do that correctly, and if so, how do I contribute it back into Observium?
- Is there a preferred way to handle point to multipoint aggregation
devices such as DSLAMs, GPON OLTs, and Wireless APs where you have client signal levels, modulation, etc? In particular I'd like to add support for Ubiquiti and Canopy APs where one would track multiple metrics for each associated client in addition to metrics from the device itself. E.g. Stats for the downlink can be gathered from the AP, but uplink has to be gathered from the client radios. Clients are only loosely associated with APs (they are discovered through a AP, can migrate to other APs, and don't have a static IP address). Client devices like this break the hostname-required rule but perhaps it isn't mandatory if they are discovered via the AP?
http://observium.org/wiki/Developing/NewOS _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium