[mrtg] Re: 'did not eval into defined data' when querying explicit OIDs

[Brian Stiff]

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
superfluous?

Thanks again for the help.

Best Regards,
Brian

On 7/6/06, Steve Shipway <s.shipway at auckland.ac.nz> wrote:
>
> ...
> > Target[192.168.0.254_fw-act]:
>
> 1.3.6.1.4.1.9.9.491.1.1.1.6&1.3.6.1.4.1.9.9.491.1.1.1.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
>
> Target[192.168.0.254_fw-act]:
>
> 1.3.6.1.4.1.9.9.491.1.1.1.6.0&1.3.6.1.4.1.9.9.491.1.1.1.11.0:xxxxx at 192.168.0
> .254
>
> and see if it works.
>
> Steve
>
> (note - I removed your community string for security reasons)
>
>
>


--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
Archive     http://lists.ee.ethz.ch/mrtg
FAQ         http://faq.mrtg.org    Homepage     http://www.mrtg.org
WebAdmin    http://lists.ee.ethz.ch/lsg2.cgi