not referenced in an OBJECT-GROUP??
Frank Fock
Frank.Fock____t-online.de
Mon Jun 5 08:42:36 CEST 2000
Hi,
in SMIv2 every object type with a value for the MAX-ACCESS clause other than
not-accessible must be a member of at least one object group. The same rule
applies to notification types and notification groups.
Best regards,
Frank
CK Ng wrote:
> Hi,
> Can anyone give me a clue what's wrong with the below mib??
> tq.
>
> - ck ng
>
> ERROR: (by AgentGen)
> ======
> A-MIB: aData is not referenced in an OBJECT-GROUP or a NOTIFICATION-GROUP
> definition
>
> THE MIB
> =======
>
> A-MIB DEFINITIONS ::= BEGIN
>
> IMPORTS
> MODULE-IDENTITY,
> OBJECT-TYPE,
> experimental FROM SNMPv2-SMI
>
> aMib MODULE-IDENTITY
>
> LAST-UPDATED "0006021600Z"
>
> ORGANIZATION "xxx"
>
> CONTACT-INFO
> " xxx
> Postal: xxx
> E-mail: xxx"
>
> DESCRIPTION
> "The MIB module for entities implementing the
> xxx protocol."
>
> REVISION "0006021600Z"
>
> DESCRIPTION
> "The initial version of this MIB module."
>
> ::= { experimental xx }
>
> aData OBJECT-TYPE
> SYNTAX OCTET STRING (SIZE(0..255))
> MAX-ACCESS read-write
> STATUS current
> DESCRIPTION
> "The data for display."
> ::= { aMib 1 }
> END
More information about the AGENTPP
mailing list