On 5 January 2011 06:10, Ravi Kumar <[email protected]> wrote:
> Could any one plz give an reason with example that why do we need
> Groups/Conformance info while writhing a mib file.
Groups are used in two places:
- compliance definitions
- agent capability definitions
So let's take these two in turn.
The idea of compliance definitions is to answer the question
"what does it mean to implement a given MIB?"
The MODULE-COMPLIANCE definition species which elements
are required, and which are optional.
For example, the compliance definitions within SNMPv2-MIB
essentially state that a vendor has to implement everything
(relevant), or else it cannot claim to support the SNMPv2-MIB
As another example, the compliance definition within TCP-MIB
says that a vendor may omit the two high-capacity counters
(assuming the system is relatively slow) and still claim to
implement the MIB
A third example, the compliance definition within
SNMP-USER-BASED-SM-MIB says that a vendor must
implement all the objects, but need not support SET
requests on the two UserXxxxProtocol objects.
The idea of agent capabilities was to allow the agent to describe what
it *actually* implements (as opposed to what it ought to support!)
This is what should be reported via the sysORTable.
It's difficult to give an example of this, as it never really took off.
The Net-SNMP agent has a broken (but arguably more useful) approach,
since it returns the OID of each implemented module for sysORID,
rather than a (private) definition of which bits it does/doesn't handle.
The simplest way to handle the conformance block is probably to
define a single group (containing everything), and define this as
mandatory. But if there are aspects that are optional, or not
relevant in certain circumstances, then use a more fine-grained
group structure, and define the status accordingly.
Hope this helps
Dave
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
