[mrtg] Re: 'did not eval into defined data' when querying explicit OIDs
bstiff at gmail.com
Fri Jul 7 07:06:58 MEST 2006
That's the correct answer! Thanks for the reply (and for scrubbing the
community string. Thought I'd gotten them all. :-| ). Adding trailing .0s
to both OIDs got mrtg to pick up the numbers.
Do I need to load the MIB, or does the explicit OIDs make the MIB
Thanks again for the help.
On 7/6/06, Steve Shipway <s.shipway at auckland.ac.nz> wrote:
> > Target[192.168.0.254_fw-act]:
> 126.96.36.199.188.8.131.52.4184.108.40.206.6&220.127.116.11.18.104.22.168.422.214.171.124.11:xxxxx at 192.168.0.254
> I might be wrong, but are you sure these are the exact OIDs? Quite often
> you need a .0 suffix for some OIDs that are not in a table. Try using
> 126.96.36.199.188.8.131.52.4184.108.40.206.6.0&220.127.116.11.18.104.22.168.422.214.171.124.11.0:xxxxx at 192.168.0
> and see if it works.
> (note - I removed your community string for security reasons)
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
FAQ http://faq.mrtg.org Homepage http://www.mrtg.org
More information about the mrtg