Connected: An Internet Encyclopedia
RFC 1904 - 3. Mapping of the OBJECT-GROUP macro

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1904
Prev: 2. Definitions
Next: 3.1. Mapping of the OBJECTS clause

### 3. Mapping of the OBJECT-GROUP macro

For conformance purposes, it is useful to define a collection of related managed objects. The OBJECT-GROUP macro is used to define each such collection of related objects. It should be noted that the expansion of the OBJECT-GROUP macro is something which conceptually happens during implementation and not during run-time.

To "implement" an object, a SNMPv2 entity acting in an agent role must return a reasonably accurate value for management protocol retrieval operations; similarly, if the object is writable, then in response to a management protocol set operation, a SNMPv2 entity must accordingly be able to reasonably influence the underlying managed entity. If a SNMPv2 entity acting in an agent role can not implement an object, the management protocol provides for the SNMPv2 entity to return an exception or error, e.g, noSuchObject [4]. Under no circumstances shall a SNMPv2 entity return a value for objects which it does not implement -- it must always return the appropriate exception or error, as described in the protocol specification [4].

3.1. Mapping of the OBJECTS clause
3.2. Mapping of the STATUS clause
3.3. Mapping of the DESCRIPTION clause
3.4. Mapping of the REFERENCE clause
3.5. Mapping of the OBJECT-GROUP value
3.6. Usage Example

Next: 3.1. Mapping of the OBJECTS clause

Connected: An Internet Encyclopedia
RFC 1904 - 3. Mapping of the OBJECT-GROUP macro