Re: "Holes" in oid sequence.

Dave Shield wrote:

> The cardinal rule of MIB design is that you should never have two 
> definitions with different behaviour sharing the same OID. 

    We're continually adding new features to our product, and that's in 
conflict with the cardinal rule above. The process that I'm considering 
is to leave holes in the OID sequence, and new features will use those 
holes. Dropped features will also leave holes in the OID's. I can't ever 
want to use them again (because I'm sure someone out there will assume 
it's the old feature, not a new one).

     Does this make sense? Is it the "right" way to do it?

>How did you register the RaidControllerTable?
>The simplest form of specifying the valid columns in a
>'netsnmp_table_registration_info' structure is to give
>the first and last columns:
>
>    tinfo->min_column = MY_FIRST;
>    tinfo->max_column = MY_LAST;
>  
>
     Won't work, because some of my missing columns are in the, "middle" 
of a sequence. This is because I group like features together (say, a 
battery backup feature will be followed by some missing OID's so that 
new battery backup features can be added).

>But this structure also includes a field
>
>    netsnmp_column_info *valid_columns;
>  
>
      I didn't know about this guy. I'll follow up on it.

      BTW., I guess it would be legal to put, "filler" OID's in the MIB 
definition that aren't accessible. What would be even cooler, would be 
to have mib2c (I'm using mfd) to understand the filler OID definition's, 
and automatically invalidate those columns.

     Thanx!!!!!

     tom.c
--------------------------------------------------------

CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and contains information that is confidential and proprietary to Applied Micro Circuits Corporation or its subsidiaries. It is to be used solely for the purpose of furthering the parties' business relationship. All unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. 
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
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