I came across a solution to my problem, though I'm not sure if it is the
"correct" one.
I edited EVENT-MIB.my and made the following changes:
Commented out the line "Gauge32, mib-2, zeroDotZero FROM SNMPv2-SMI
under "IMPORTS" and created a new line that reads, "Gauge32, mib-2 FROM
SNMPv2-SMI"
I added the following definition for zeroDotZero under --Textual
Conventions:
zeroDotZero OBJECT-IDENTITY
STATUS current
DESCRIPTION
"A value used for null identifiers.
This definition, which is in compliance with RFC 1902, is a
temporary inclusion in the EVENT MIB until such time as MIB
compilers are upgraded and thereby can accept references to
the new definitions in RFC 1902."
REFERENCE
"RFC 1920"
::== {0 0 }
(I found this definition for zeroDotZero in one of Cisco's PNNI mib
files)
Since making this change to EVENT-MIB.my, the error message has gone
away.
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
_______________________________________________
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
