Connected: An Internet Encyclopedia
5.4.1. Mapping of the MANDATORY-GROUPS clause

Up: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1904
Up: 5. Mapping of the MODULE-COMPLIANCE macro
Up: 5.4. Mapping of the MODULE clause
Prev: 5.4. Mapping of the MODULE clause
Next: 5.4.2. Mapping of the GROUP clause

5.4.1. Mapping of the MANDATORY-GROUPS clause

5.4.1. Mapping of the MANDATORY-GROUPS clause

The MANDATORY-GROUPS clause, which need not be present, names the one or more object or notification groups within the correspondent MIB module which are unconditionally mandatory for implementation. If a SNMPv2 entity acting in an agent role claims compliance to the MIB module, then it must implement each and every object and notification within each conformance group listed. That is, if a SNMPv2 entity returns a noSuchObject exception in response to a management protocol get operation [4] for any object within any mandatory conformance group for every MIB view, or if the SNMPv2 entity cannot generate each notification listed in any conformance group under the appropriate circumstances, then that SNMPv2 entity is not a conformant implementation of the MIB module.


Next: 5.4.2. Mapping of the GROUP clause

Connected: An Internet Encyclopedia
5.4.1. Mapping of the MANDATORY-GROUPS clause