SNMP: ASN.1 MIB Definitions. Referencing a table within a table

Posted by Doug on Stack Overflow See other posts from Stack Overflow or by Doug
Published on 2010-03-24T17:58:21Z Indexed on 2010/03/24 18:23 UTC
Read the original article Hit count: 430

Filed under:
|

Its's been a while since I've written ASN.1 so..

Our data model is comprised of several table definitions within a table. This is not workable in SNMP, so we need to flatten the definitions. The easiest way to do this would be to have the embedded table indexed by the same OID as the parent table. Thus

someTableEntry ::= SEQUENCE {
   someTableIndex
        Integer32,
   someTableDomain
        Integer32,
   someTableFooTable
        SEQUENCE OF SomeTableFooTable
} 

becomes

    someTableEntry ::= SEQUENCE {
       someTableIndex
            Integer32,
       someTableDomain
            Integer32,
    } 

someTableFooTable ::= SEQUENCE {
    someTableIndex
       Integer32,
....
} 

The good thing is that in our application there will NEVER be any kind of SET, GET or GET NEXT so no need for SNMP walk (there are some very good reasons for this that supersede the need for network management elegance. All attributes will be reported via traps only. I think this is a valid SNMP MIB definitions but wanted to get some feedback.

Thanks in advance.

© Stack Overflow or respective owner

Related posts about snmp

Related posts about asn.1