<HTML>
<HEAD>
<TITLE>Advice: monitoring GPS based clock</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>We have some ntp clocks that provide snmp monitoring. Unfortunately, the data presented is not structured nicely in a mib:<BR>
<BR>
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"<BR>
[...time passes]<BR>
<BR>
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"<BR>
<BR>
The format of the string is:<BR>
N, x1,y1,z1,x2,y2,z2...xn,yn,zn<BR>
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.<BR>
<BR>
N seems pretty easy to graph. I can use either a ConversionCode parser or a simple perl script to gather the requisite info.<BR>
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.<BR>
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.<BR>
<BR>
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.<BR>
<BR>
I’d appreciate some suggestions.</SPAN></FONT>
</BODY>
</HTML>