Re: pulling snr data error

Steve Shipway <[email protected]>
Newsgroups gmane.network.mrtg.user
Message-ID <7294716191A1E142B80615ED2C633BCA0109F877@uxcn10-2.UoA.auckland.ac.nz>
> Target[Gauge32]:.1.3.6.1.2.1.10.­
> 94.1.1.3.1.4.12&.1.3.6.1.2.1.10.94­.1.1.2.1.4.12:[email protected]:::::2

You DEFINTELY need to remove the leading '.' on the OID.  I'm guessing the '-' was added by your mail client because it shouldn’t be there either.  Note that the identifier between the [] is not an indication of what the data is; it is only a unique identifier to MRTG (routers2 calls this the 'targetname'), and it is used to create the RRD filename.  You might also want to amend your legends as below.

Target[Cisco-snr]: 1.3.6.1.2.1.10.94.1.1.3.1.4.12&1.3.6.1.2.1.10.94.1.1.2.1.4.12:[email protected]:::::2
Title[Cisco-snr]: Cisco 887 SNR Analysis
PNGTitle[Cisco-snr]: Cisco 887 SNR Analysis
Background[Cisco-snr]: #ffffff
PageTop[Cisco-snr]: <H1>Cisco 887 SNR Analysis</H1>
WithPeak[Cisco-snr]: wmy
MaxBytes[Cisco-snr]: 200000
Options[Cisco-snr]: gauge, nopercent
YLegend[Cisco-snr]: decibels
ShortLegend[Cisco-snr]: dB
Legend1[Cisco-snr]: Local SNR
Legend2[Cisco-snr]: Remote SNR
Legend3[Cisco-snr]: Peak local SNR
Legend4[Cisco-snr]: Peak remote SNR
LegendI[Cisco-snr]: Local :
LegendO[Cisco-snr]: Remote:
routers.cgi*Options[Cisco-snr]: scaled fixunit nomax

The extended options directive will help Routers2 display the data better (preventing 1000dB appearing as 1kdB for example)

Steve

Steve Shipway
ITS Unix Services Design Lead
University of Auckland, New Zealand
Floor 1, 58 Symonds Street, Auckland
Phone: +64 (0)9 3737599 ext 86487
DDI: +64 (0)9 924 6487
Mobile: +64 (0)21 753 189
Email: [email protected]
 Please consider the environment before printing this e-mail

_______________________________________________
mrtg mailing list
[email protected]
https://lists.oetiker.ch/cgi-bin/listinfo/mrtg
smime.p7s (application/x-pkcs7-signature, 5.9 KB) - not displayed
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.