On Fri, 11 Jun 2004 11:17:08 -0400 [EMAIL PROTECTED] wrote:
CRC> Is there a common, typical, or expected organization of the objects in an
CRC> enterprise MIB? I imagine most vendors have multiple, device-specific
CRC> MIBs. Would I expect to find those organized like:
CRC>
CRC> RFC1155-SMI::enterprises.myent.device1.something
CRC> RFC1155-SMI::enterprises.myent.device2.something
CRC> ...
CRC>
CRC> or
CRC>
CRC> RFC1155-SMI::enterprises.myent.devices.d1.something
CRC> RFC1155-SMI::enterprises.myent.devices.d2.something
CRC> ...
CRC>
CRC> or something else? Thanks.
It varies a lot. If you are writing MIBs, "Understanding SNMP MIBs" is highly
recommended.
One thing I usually do is partition the enterprise space at the top, so the
very top level doesn't get cluttered with device specific nodes.
egtReg OBJECT-IDENTITY
"Sub-tree for registrations"
egtGeneric OBJECT-IDENTITY
"Sub-tree for common object and event definitions"
egtProducts OBJECT-IDENTITY
"Sub-tree for specific object and event definitions"
egtCaps OBJECT-IDENTITY
"Sub-tree for agent profiles"
::= { egtRoot 40 }
egtReqs OBJECT-IDENTITY
"Sub-tree for management application requirements"
egtExpr OBJECT-IDENTITY
"Sub-tree for experimental definitions"
--
Robert Story; NET-SNMP Junkie <http://www.net-snmp.org/>
<irc://irc.freenode.net/#net-snmp>
Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-users>
You are lost in a twisty maze of little standards, all different.
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the
one installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
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
