Hey Ryan!
I was looking at adding some more support for Arbor Peakflow SP and TMS like CPU, memory and disk-graphs.
The information seems to be able to be found in PEAKFLOW-TMS-MIB and PEAKFLOW-SP-MIB.
However, having per-device MIB for the same product family is rather bad, that means we need to write new code for every different Arbor-product for every sensor we want to graph.
And in addition to that, the values used in the different MIBs are totally different.
https://pastee.org/jkbuq

notice the difference of the reported values for deviceCpuLoadAvg5min. This means we cant even reuse the same code for the device at all.
Writing support for Arbor products will be very messy.
If you have any good contact with your developers I would appreciate if you could suggest to start working towards using a single MIB for all standard values like CPU, memory and disk space :)

/Markus

2015-02-09 10:35 GMT+01:00 Peter Persson <peter.persson@bredband2.se>:
The biggest problem i've seen is that Arbor MIB's is only for traps, not for polling.
But since you have seen it, we may get our hope back :D

/Peter

2015-02-08 18:27 GMT+01:00 Ryan, Spencer <sryan@arbor.net>:
Great to see Arbor MIB's getting updated in the SVN checkouts :)

I don't monitor any of our own products, but I'm going to talk to the Peakflow guys and see if I can get access to some of the lab gear. We have at least one setup (not sure if it's TMS or SP) that gets about ~8Gb/s of anonymous traffic from a few ISPs. Should give me some useful data in Observium.

Keep up the good work guys!

Spencer Ryan
| Senior Systems Administrator | sryan@arbor.net
Arbor Networks

_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium



_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium