Paul> I obtained the MIB files from Intel's site. Withe Perl::SNMP
Paul> they seem to work fine. When scotty parses the file
Paul> INT_GEN.MIB, I get an error messdage. I have indicated the
Paul> offending line. If I comment it out it seems to work.
Paul> sysConfEntry OBJECT-TYPE
Paul> SYNTAX SysConfEntry
Paul> ACCESS not-accessible
Paul> STATUS mandatory
Paul> DESCRIPTION
Paul> "Configuration information entry:
Paul> Index 1 is the active configuration.
Paul>
Paul> Index 2 is the backup configuration (if it exists)."
Paul> -> INDEX { INTEGER }
Paul> ::= { sysConfTable 1 }
This definition is illegal. Scotty therefore rejects this
definition. The intention here is probably:
INDEX { confStatus }
But you have to check whether the DESCRIPTION of sysConfEntry matches
the DESCRIPTION of confStatus. (They probably mean something else and
the MIB is more seriously broken.)
In case you want to complain to Intel: The relevant text is in RFC
1902 section 7.7 second paragraph:
: The instance identification information in an INDEX clause must
: specify object(s) such that value(s) of those object(s) will
: unambiguously distinguish a conceptual row.
This makes it pretty clear that you specify object(s) and not ASN.1
types in the INDEX clause.
Juergen
-- Juergen Schoenwaelder schoenw@ibr.cs.tu-bs.de http://www.cs.tu-bs.de/~schoenw Technical University Braunschweig, Dept. Operating Systems & Computer Networks Bueltenweg 74/75, 38106 Braunschweig, Germany. (Tel. +49 531 / 391 3289)-- !! This message is brought to you via the `tkined & scotty' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>. !! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.