RE: Monitor using !=OID

"Emlyn Purvis" <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <[email protected]>
Hi Dave,

I am building in MSDEV using the psdk workspace.
The disman folder in the netsnmpmibssdk project does include files from
the mibgroup/disman folder rather than the mibgroup/disman/event folder.
I'll change things around to try and use the mibgroup/disman/event files
and let you know how I get on.

Regards,
Emlyn

-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of Dave Shield
Sent: 01 March 2007 13:00
To: Emlyn Purvis
Cc: [email protected]
Subject: Re: Monitor using !=OID

On 01/03/07, Emlyn Purvis <[email protected]> wrote:
> registered debug token disman:event:conf, 1
> snmpd.conf: line 21: Error: unable to parse oid:!=scisysInteger

Hmmm....
  I'd expect to see a bit more than that.  Something of the form
"Parsing disman monitor config (....)", at the very least.

<tap, tap, tap>

Aha!
You're using the older Event MIB implementation.
No - that code does *not* support the !=OID test.

You'll need to recompile the agent to use the newer
'disman/event' module, rather than the 'disman/event-mib'
(or 'disman/old-event-mib') module.

I'm a little surprised, since I thought the newer version
was the default for the 5.3.x line.   But the error message
above is definitely coming from the older code.

Dave


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
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.