RFC-1212 compilation issues - SNMP

This is a discussion on RFC-1212 compilation issues - SNMP ; Please can someone help verify if this is a valid MIB file. netsnmp throws the following error when I try to compile it but MG soft compiles it fine. Any help will be appreciated. Note: Mibble throws an error as ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: RFC-1212 compilation issues

  1. RFC-1212 compilation issues

    Please can someone help verify if this is a valid MIB file.
    netsnmp throws the following error when I try to compile it but MG soft
    compiles it fine. Any help will be appreciated.
    Note: Mibble throws an error as well.

    -----------------------------------------------------------------
    Bad format for OBJECT-TYPE (END): At line 79 in
    D:\SNMP\ucd-snmp-4.2.3-win32\usr

    \mibs/RFC-1212.my
    Bad parse of OBJECT-TYPE: At line 79 in
    D:\SNMP\ucd-snmp-4.2.3-win32\usr\mibs/RF
    C-1212.my
    -----------------------------------------------------------------
    This is the file we are working with

    -- file: RFC-1212.my
    -- changes:
    -- Removed IMPORTS.
    -- Commented out OBJECT-TYPE macro definition and replaced
    -- with SMIC directive to enable it.
    -- dperkins@scruznet.com



    RFC-1212 DEFINITIONS ::= BEGIN

    -- Make builtin items known
    SMI OBJECT-TYPE


    -- OBJECT-TYPE MACRO ::=
    -- BEGIN
    -- TYPE NOTATION ::=
    -- must conform to
    -- RFC1155's ObjectSyntax
    -- "SYNTAX" type(ObjectSyntax)
    -- "ACCESS" Access
    -- "STATUS" Status
    -- DescrPart
    -- ReferPart
    -- IndexPart
    -- DefValPart
    -- VALUE NOTATION ::= value (VALUE ObjectName)
    --
    -- Access ::= "read-only"
    -- | "read-write"
    -- | "write-only"
    -- | "not-accessible"
    -- Status ::= "mandatory"
    -- | "optional"
    -- | "obsolete"
    -- | "deprecated"
    --
    -- DescrPart ::=
    -- "DESCRIPTION" value (description
    DisplayString)
    -- | empty
    --
    -- ReferPart ::=
    -- "REFERENCE" value (reference DisplayString)
    -- | empty
    --
    -- IndexPart ::=
    -- "INDEX" "{" IndexTypes "}"
    -- | empty
    -- IndexTypes ::=
    -- IndexType | IndexTypes "," IndexType
    -- IndexType ::=
    -- if indexobject, use the SYNTAX
    -- value of the correspondent
    -- OBJECT-TYPE invocation
    -- value (indexobject ObjectName)
    -- otherwise use named SMI type
    -- must conform to IndexSyntax below
    -- | type (indextype)
    --
    -- DefValPart ::=
    -- "DEFVAL" "{" value (defvalue ObjectSyntax)
    "}"
    -- | empty
    -- END
    --
    -- IndexSyntax ::=
    -- CHOICE {
    -- number
    -- INTEGER (0..MAX),
    -- string
    -- OCTET STRING,
    -- object
    -- OBJECT IDENTIFIER,
    -- address
    -- NetworkAddress,
    -- ipAddress
    -- IpAddress
    -- }
    END


  2. Re: RFC-1212 compilation issues

    HI,

    This is not a "MIB file" nor is it an ASN.1 file.
    It is a file used by SMICng. You should not be using
    it directly.

    Regards,
    /david t. perkins

    On Mon, 11 Apr 2005 clyde_dsouza@yahoo.com wrote:

    > Please can someone help verify if this is a valid MIB file.
    > netsnmp throws the following error when I try to compile it but MG soft
    > compiles it fine. Any help will be appreciated.
    > Note: Mibble throws an error as well.
    >
    > -----------------------------------------------------------------
    > Bad format for OBJECT-TYPE (END): At line 79 in
    > D:\SNMP\ucd-snmp-4.2.3-win32\usr
    >
    > \mibs/RFC-1212.my
    > Bad parse of OBJECT-TYPE: At line 79 in
    > D:\SNMP\ucd-snmp-4.2.3-win32\usr\mibs/RF
    > C-1212.my
    > -----------------------------------------------------------------
    > This is the file we are working with
    >
    > -- file: RFC-1212.my
    > -- changes:
    > -- Removed IMPORTS.
    > -- Commented out OBJECT-TYPE macro definition and replaced
    > -- with SMIC directive to enable it.
    > -- dperkins@scruznet.com
    >
    >
    >
    > RFC-1212 DEFINITIONS ::= BEGIN
    >
    > -- Make builtin items known
    > SMI OBJECT-TYPE
    >
    >
    > -- OBJECT-TYPE MACRO ::=
    > -- BEGIN
    > -- TYPE NOTATION ::=
    > -- must conform to
    > -- RFC1155's ObjectSyntax
    > -- "SYNTAX" type(ObjectSyntax)
    > -- "ACCESS" Access
    > -- "STATUS" Status
    > -- DescrPart
    > -- ReferPart
    > -- IndexPart
    > -- DefValPart
    > -- VALUE NOTATION ::= value (VALUE ObjectName)
    > --
    > -- Access ::= "read-only"
    > -- | "read-write"
    > -- | "write-only"
    > -- | "not-accessible"
    > -- Status ::= "mandatory"
    > -- | "optional"
    > -- | "obsolete"
    > -- | "deprecated"
    > --
    > -- DescrPart ::=
    > -- "DESCRIPTION" value (description
    > DisplayString)
    > -- | empty
    > --
    > -- ReferPart ::=
    > -- "REFERENCE" value (reference DisplayString)
    > -- | empty
    > --
    > -- IndexPart ::=
    > -- "INDEX" "{" IndexTypes "}"
    > -- | empty
    > -- IndexTypes ::=
    > -- IndexType | IndexTypes "," IndexType
    > -- IndexType ::=
    > -- if indexobject, use the SYNTAX
    > -- value of the correspondent
    > -- OBJECT-TYPE invocation
    > -- value (indexobject ObjectName)
    > -- otherwise use named SMI type
    > -- must conform to IndexSyntax below
    > -- | type (indextype)
    > --
    > -- DefValPart ::=
    > -- "DEFVAL" "{" value (defvalue ObjectSyntax)
    > "}"
    > -- | empty
    > -- END
    > --
    > -- IndexSyntax ::=
    > -- CHOICE {
    > -- number
    > -- INTEGER (0..MAX),
    > -- string
    > -- OCTET STRING,
    > -- object
    > -- OBJECT IDENTIFIER,
    > -- address
    > -- NetworkAddress,
    > -- ipAddress
    > -- IpAddress
    > -- }
    > END
    >
    >


+ Reply to Thread