MIB-design for beginners

[Vasay, Al]

Hi Dirk,
 
We had a similar issue in our company. Our company manufactures ATM machines and the network devices that we try to manage via SNMP include Printer, Depositor, Dispenser, Card Reader, etc. For versioning, we decided to add a node that says "Release" and under that would be the releases, say "Release1", "Release2", and so on. Thus,
 
fooMIBRoot.fooPhysicalDevice.fooPrinter.fooPrinterMIBClassRelease.fooPrinterMIBClassRelease1
 
would correspond to version 1, and so on and so forth. Hope this helps.
 
Al Vasay
Software Engineer
Diebold, Incorporated
 

-----Original Message-----
From: Dirk Moermans [mailto:dmoermans____argogroup.com]
Sent: Tuesday, March 27, 2001 5:10 AM
To: agentpp-dl____fock.de
Subject: MIB-design for beginners


Hi,
 
We have managed to create an agent for a very simple MIB which was a trial in itself.
We now wish to create a proper mib for our product and want to make it future proof i.e. we can expand the MIB to support future versions and other products by our organisation. Are there general guidelines for doing this or is it entirely on a per company basis?
 
Should we subdivide our OID in version-specific subtrees (like mib-ii), product-specific subtrees or simply extend the MIB as the functionality grows?
 
cheers
Dirk Moermans
 
 
 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.agentpp.org/pipermail/agentpp/attachments/20010327/482329ae/attachment.htm