[mrtg] Advice: monitoring GPS based clock
McDonald, Dan
Dan.McDonald at austinenergy.com
Fri Sep 2 18:51:34 CEST 2011
We have some ntp clocks that provide snmp monitoring. Unfortunately, the
data presented is not structured nicely in a mib:
SYMM-SMI::gpsSatlist.0
"9,3,-156,C,6,-158,C,7,-154,C,8,-161,C,10,-159,C,11,-156,C,16,-159,C,19,-152
,C,23,-153,C"
[...time passes]
SYMM-SMI::gpsSatlist.0
"8,3,-158,C,6,-160,C,7,-153,C,8,-159,C,10,-158,C,11,-157,C,19,-153,C,23,-152
,C"
The format of the string is:
N, x1,y1,z1,x2,y2,z2...xn,yn,zn
Where N is the number of currently visible satellites , the x,y,z are
specific information about each satellite. X is a unique number associated
with the satellite, Y is the dB loss talking to it, and Z is a flag
indicating whether the time protocol considers the satellite or is just
tracking it for later.
N seems pretty easy to graph. I can use either a ConversionCode parser or a
simple perl script to gather the requisite info.
Building a separate target for each possible value of X (with a value of Y)
seems possible. I¹d then use a routers2.cgi stacked graph to display them.
The negative value is only slightly challenging just an rrdtune and I
should be able to provide the information. I¹m not certain what the max is
I cold probably get away with 1. The minimum is 200.
However, I don¹t know what the possible X values are, so pre-loading that
seems challenging. I think adding targets on the fly in mrtg (by adding
them to the $$targ array) would be a tad challenging.
I¹d appreciate some suggestions.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/mrtg/attachments/20110902/dc8fcdf4/attachment.htm
More information about the mrtg
mailing list