> 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. [...] > 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.
Guessing only: 1 to 32 http://en.wikipedia.org/wiki/List_of_GPS_satellite_launches#Cross_reference_of_PRNs_to_satellite_blocks _______________________________________________ mrtg mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/mrtg
