[SNMP4J] Extending MIBs

[Frank Fock]

Hi Ron,

Class extension can be best modeled in SNMP by augmenting
tables. The augmenting table z the extends the base table y,
for example.

The different tables can be placed in different MIB modules,
but that is not necessary. It might be useful, if there is
one base table (like an abstract class) that is commonly used
at several extensions of the table in different MIB modules
each representing a variation of the base system.

Hope this helps.

Best regards,
Frank


Ron Fulkerson wrote:
> Hi All,
> 
> I am in the midst of writing several MIBs and the accompanying SNMP code 
> for an existing product.  While I have been working on this I have 
> wondered what experience people have had setting up an hierarchy of MIBs 
> for a single software product.
> 
> I am thinking of an hierarchy along the lines of something similar to 
> how java objects extend one another.  For example, if I have a three 
> classes z which extends y which extends x; is it best to make three 
> separate MIBs which describe the SNMP components of each class (i.e. 
> xMIB, yMIB, and zMIB -- using proper MIB extension).  Or, is it better 
> to implement a single MIB which describes a single view of the product 
> (i.e. xyzMIB).
> 
> Please let me know about your experiences and opinions!
> 
> Thanks,
> Ron
> 
> _______________________________________________
> 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