[SNMP4J] Help with MIB Design

[Frank Fock]

Hi Jothi,

You should use the sparse table expansion instead
augmenting Module_A table. Instead of specifying

..
AUGMENTS { Module_A }
..

you would write

..
INDEX { Indx }
..

in the Entry OBJECT-TYPE definition of table Module_B.

Then you can either not add those missing rows to
Module_B table (in SNMP4J-Agent) or set their value
to <null> (=not-accessible).

Best regards,
Frank

Jothi P Neelamegam wrote:
> Hi All,
> 
> This is not a SNMP4J question per se, but thought that is still a good 
> place to post to get some advice.
> 
> I am in the process of designing a MIB. Our agent will need to expose 
> information from two modules (say Module_A and Module_B). I have a table 
> for Module_A with the following columns
> Indx
> Data1
> Data2
> 
> I was planning to add an augmented table for Moudle_B with the following 
> columns
> Data3
> Data4
> 
> with indx being the index of this table as well.
> 
> The issue is that Module_B is an optional module in our product and 
> might or might not exist. In other words, the agent might have Data3 and 
> Data4 or might not have it. What is a good way to architect this?
> 
> If I use the augmented table approach above, will the agent need to 
> return empty values (or some values indicating _not_available_) for 
> Data3 and Data4 for the case where Module_B is not present? I could have 
> a scalar to indicate whether Module_B is present or not and then let the 
> NMS interpret the values of Data3 and Data4 based on this value. Is this 
> a good idea?
> 
> Any suggestions/advice would be helpful.
> 
> Thanks in advance.
> Jothi
> 
> -- 
> 
> The information contained in this communication may be confidential and is
> intended only for the use of the recipient(s) named above.  If the reader
> of this communication is not the intended recipient(s), you are hereby
> notified that any dissemination, distribution, or copying of this
> communication, or any of its contents, is strictly prohibited.  If you are
> not a named recipient or received this communication by mistake, please
> notify the sender and delete the communication and all copies of it.
> 
> 
> _______________________________________________
> SNMP4J mailing list
> SNMP4J at agentpp.org
> http://lists.agentpp.org/mailman/listinfo/snmp4j

-- 
AGENT++
http://www.agentpp.com
http://www.mibexplorer.com
http://www.mibdesigner.com