As per Relevance of the word conformance, we have this rfc below:
Network Working Group SNMPv2 Working
Request for Comments: 1904 J.
Obsoletes: 1444 SNMP Research, Inc
Category: Standards Track K.
Cisco Systems, Inc
M.
Dover Beach Consulting, Inc
S.
International Network
January 1996
Conformance Statements for Version 2 of
Simple Network Management Protocol (SNMPv2)
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
Table of
1. Introduction ................................................ 2
1.1 A Note on Terminology ...................................... 3
2. Definitions ................................................. 3
2.1 The OBJECT-GROUP macro ..................................... 3
2.2 The NOTIFICATION-GROUP macro ............................... 4
2.3 The MODULE-COMPLIANCE macro ................................ 5
2.4 The AGENT-CAPABILITIES macro ............................... 7
3. Mapping of the OBJECT-GROUP macro ........................... 9
3.1 Mapping of the OBJECTS clause .............................. 10
3.2 Mapping of the STATUS clause ............................... 10
3.3 Mapping of the DESCRIPTION clause .......................... 10
3.4 Mapping of the REFERENCE clause ............................ 10
3.5 Mapping of the OBJECT-GROUP value .......................... 10
3.6 Usage Example .............................................. 11
4. Mapping of the NOTIFICATION-GROUP macro ..................... 11
4.1 Mapping of the NOTIFICATIONS clause ........................ 11
4.2 Mapping of the STATUS clause ............................... 11
4.3 Mapping of the DESCRIPTION clause .......................... 12
4.4 Mapping of the REFERENCE clause ............................ 12
4.5 Mapping of the NOTIFICATION-GROUP value .................... 12
4.6 Usage Example .............................................. 12
5. Mapping of the MODULE-COMPLIANCE macro ...................... 12
5.1 Mapping of the STATUS clause ............................... 13
SNMPv2 Working Group Standards Track [Page 1]
RFC 1904 Conformance Statements for SNMPv2 January 1996
5.2 Mapping of the DESCRIPTION clause .......................... 13
5.3 Mapping of the REFERENCE clause ............................ 13
5.4 Mapping of the MODULE clause ............................... 13
5.4.1 Mapping of the MANDATORY-GROUPS clause ................... 13
5.4.2 Mapping of the GROUP clause .............................. 14
5.4.3 Mapping of the OBJECT clause ............................. 14
5.4.3.1 Mapping of the SYNTAX clause ........................... 14
5.4.3.2 Mapping of the WRITE-SYNTAX clause ..................... 15
5.4.3.3 Mapping of the MIN-ACCESS clause ....................... 15
5.4.4 Mapping of the DESCRIPTION clause ........................ 15
5.5 Mapping of the MODULE-COMPLIANCE value ..................... 15
5.6 Usage Example .............................................. 16
6. Mapping of the AGENT-CAPABILITIES macro ..................... 16
6.1 Mapping of the PRODUCT-RELEASE clause ...................... 17
6.2 Mapping of the STATUS clause ............................... 17
6.3 Mapping of the DESCRIPTION clause .......................... 17
6.4 Mapping of the REFERENCE clause ............................ 17
6.5 Mapping of the SUPPORTS clause ............................. 18
6.5.1 Mapping of the INCLUDES clause ........................... 18
6.5.2 Mapping of the VARIATION clause .......................... 18
6.5.2.1 Mapping of the SYNTAX clause ........................... 18
6.5.2.2 Mapping of the WRITE-SYNTAX clause ..................... 18
6.5.2.3 Mapping of the ACCESS clause ........................... 19
6.5.2.4 Mapping of the CREATION-REQUIRES clause ................ 19
6.5.2.5 Mapping of the DEFVAL clause ........................... 20
6.5.2.6 Mapping of the DESCRIPTION clause ...................... 20
6.6 Mapping of the AGENT-CAPABILITIES value .................... 20
6.7 Usage Example .............................................. 20
7. Extending an Information Module ............................. 22
7.1 Conformance Groups ......................................... 22
7.2 Compliance Definitions ..................................... 22
7.3 Capabilities Definitions ................................... 22
8. Security Considerations ..................................... 23
9. Editor's Address ............................................ 23
10. Acknowledgements ........................................... 23
11. References ................................................. 24
1.
A management system contains: several (potentially many) nodes,
with a processing entity, termed an agent, which has access
management instrumentation; at least one management station; and,
management protocol, used to convey management information
the agents and management stations. Operations of the protocol
carried out under an administrative framework which
authentication, authorization, access control, and privacy policies
SNMPv2 Working Group Standards Track [Page 2]
RFC 1904 Conformance Statements for SNMPv2 January 1996
Management stations execute management applications which monitor
control managed elements. Managed elements are devices such
hosts, routers, terminal servers, etc., which are monitored
controlled via access to their management information
Management information is viewed as a collection of managed objects
residing in a virtual information store, termed the
Information Base (MIB). Collections of related objects are
in MIB modules. These modules are written using a subset of OSI'
Abstract Syntax Notation One (ASN.1) [1], termed the Structure
Management Information (SMI) [2].
It may be useful to define the acceptable lower-bounds
implementation, along with the actual level of
achieved. It is the purpose of this document to define the
used for these purposes
1.1. A Note on
For the purpose of exposition, the original Internet-standard
Management Framework, as described in RFCs 1155 (STD 16), 1157 (
15), and 1212 (STD 16), is termed the SNMP version 1
(SNMPv1). The current framework is termed the SNMP version 2
framework (SNMPv2).
2.
SNMPv2-CONF DEFINITIONS ::=
-- definitions for conformance
OBJECT-GROUP MACRO ::=
TYPE NOTATION ::=
"STATUS"
"DESCRIPTION"
VALUE NOTATION ::=
value(VALUE OBJECT IDENTIFIER
ObjectsPart ::=
"OBJECTS" "{" Objects "}"
Objects ::=
| Objects ","
Object ::=
SNMPv2 Working Group Standards Track [Page 3]
RFC 1904 Conformance Statements for SNMPv2 January 1996
value(Name ObjectName
Status ::=
"current
| "deprecated
| "obsolete
ReferPart ::=
"REFERENCE"
|
-- uses the NVT ASCII character
Text ::= """" string """"
-- more definitions for conformance
NOTIFICATION-GROUP MACRO ::=
TYPE NOTATION ::=
"STATUS"
"DESCRIPTION"
VALUE NOTATION ::=
value(VALUE OBJECT IDENTIFIER
NotificationsPart ::=
"NOTIFICATIONS" "{" Notifications "}"
Notifications ::=
| Notifications ","
Notification ::=
value(Name NotificationName
Status ::=
"current
| "deprecated
| "obsolete
ReferPart ::=
"REFERENCE"
|
-- uses the NVT ASCII character
Text ::= """" string """"
SNMPv2 Working Group Standards Track [Page 4]
RFC 1904 Conformance Statements for SNMPv2 January 1996
-- definitions for compliance
MODULE-COMPLIANCE MACRO ::=
TYPE NOTATION ::=
"STATUS"
"DESCRIPTION"
VALUE NOTATION ::=
value(VALUE OBJECT IDENTIFIER
Status ::=
"current
| "deprecated
| "obsolete
ReferPart ::=
"REFERENCE"
|
ModulePart ::=
|
Modules ::=
| Modules
Module ::=
-- name of module --
"MODULE"
ModuleName ::=
modulereference
-- must not be empty unless
-- in MIB
|
ModuleIdentifier ::=
value(ModuleID OBJECT IDENTIFIER
|
MandatoryPart ::=
"MANDATORY-GROUPS" "{" Groups "}"
SNMPv2 Working Group Standards Track [Page 5]
RFC 1904 Conformance Statements for SNMPv2 January 1996
|
Groups ::=
| Groups ","
Group ::=
value(Group OBJECT IDENTIFIER
CompliancePart ::=
|
Compliances ::=
| Compliances
Compliance ::=
|
ComplianceGroup ::=
"GROUP" value(Name OBJECT IDENTIFIER
"DESCRIPTION"
Object ::=
"OBJECT" value(Name ObjectName
"DESCRIPTION"
-- must be a refinement for object's SYNTAX
SyntaxPart ::=
"SYNTAX" type(SYNTAX
|
-- must be a refinement for object's SYNTAX
WriteSyntaxPart ::=
"WRITE-SYNTAX" type(WriteSYNTAX
|
AccessPart ::=
"MIN-ACCESS"
|
Access ::=
"not-accessible
| "accessible-for-notify
| "read-only
| "read-write
SNMPv2 Working Group Standards Track [Page 6]
RFC 1904 Conformance Statements for SNMPv2 January 1996
| "read-create
-- uses the NVT ASCII character
Text ::= """" string """"
-- definitions for capabilities
AGENT-CAPABILITIES MACRO ::=
TYPE NOTATION ::=
"PRODUCT-RELEASE"
"STATUS"
"DESCRIPTION"
VALUE NOTATION ::=
value(VALUE OBJECT IDENTIFIER
Status ::=
"current
| "obsolete
ReferPart ::=
"REFERENCE"
|
ModulePart ::=
|
Modules ::=
| Modules
Module ::=
-- name of module --
"SUPPORTS"
"INCLUDES" "{" Groups "}"
ModuleName ::=
identifier
ModuleIdentifier ::=
value(ModuleID OBJECT IDENTIFIER
|
Groups ::=
SNMPv2 Working Group Standards Track [Page 7]
RFC 1904 Conformance Statements for SNMPv2 January 1996
| Groups ","
Group ::=
value(Name OBJECT IDENTIFIER
VariationPart ::=
|
Variations ::=
| Variations
Variation ::=
|
NotificationVariation ::=
"VARIATION" value(Name NotificationName
"DESCRIPTION"
ObjectVariation ::=
"VARIATION" value(Name ObjectName
"DESCRIPTION"
-- must be a refinement for object's SYNTAX
SyntaxPart ::=
"SYNTAX" type(SYNTAX
|
-- must be a refinement for object's SYNTAX
WriteSyntaxPart ::=
"WRITE-SYNTAX" type(WriteSYNTAX
|
AccessPart ::=
"ACCESS"
|
Access ::=
"not-implemented
-- only "not-implemented" for
| "accessible-for-notify
SNMPv2 Working Group Standards Track [Page 8]
RFC 1904 Conformance Statements for SNMPv2 January 1996
| "read-only
| "read-write
| "read-create
-- following is for backward-compatibility
| "write-only
CreationPart ::=
"CREATION-REQUIRES" "{" Cells "}"
|
Cells ::=
| Cells ","
Cell ::=
value(Cell ObjectName
DefValPart ::=
"DEFVAL" "{" value(Defval ObjectSyntax) "}"
|
-- uses the NVT ASCII character
Text ::= """" string """"
3. Mapping of the OBJECT-GROUP
For conformance purposes, it is useful to define a collection
related managed objects. The OBJECT-GROUP macro is used to
each such collection of related objects. It should be noted that
expansion of the OBJECT-GROUP macro is something which
happens during implementation and not during run-time
To "implement" an object, a SNMPv2 entity acting in an agent
must return a reasonably accurate value for management
retrieval operations; similarly, if the object is writable, then
response to a management protocol set operation, a SNMPv2 entity
accordingly be able to reasonably influence the underlying
entity. If a SNMPv2 entity acting in an agent role can not
an object, the management protocol provides for the SNMPv2 entity
return an exception or error, e.g, noSuchObject [4]. Under
circumstances shall a SNMPv2 entity return a value for objects
it does not implement -- it must always return the
exception or error, as described in the protocol specification [4].
SNMPv2 Working Group Standards Track [Page 9]
RFC 1904 Conformance Statements for SNMPv2 January 1996
3.1. Mapping of the OBJECTS
The OBJECTS clause, which must be present, is used to name
object contained in the conformance group. Each of the named
must be defined in the same information module as the OBJECT-
macro appears, and must have a MAX-ACCESS clause value
"accessible-for-notify", "read-only", "read-write", or "read-create".
It is required that every object defined in an information
with a MAX-ACCESS clause other than "not-accessible" be contained
at least one object group. This avoids the common error of adding
new object to an information module and forgetting to add the
object to a group
3.2. Mapping of the STATUS
The STATUS clause, which must be present, indicates whether
definition is current or historic
The values "current", and "obsolete" are self-explanatory.
"deprecated" value indicates that the definition is obsolete,
that an implementor may wish to support the group to
interoperability with older implementations
3.3. Mapping of the DESCRIPTION
The DESCRIPTION clause, which must be present, contains a
definition of that group, along with a description of any
to other groups. Note that generic compliance requirements
not be stated in this clause. However, implementation
between this group and other groups may be defined in this clause
3.4. Mapping of the REFERENCE
The REFERENCE clause, which need not be present, contains a
cross-reference to a group defined in some other information module
This is useful when de-osifying a MIB module produced by some
organization
3.5. Mapping of the OBJECT-GROUP
The value of an invocation of the OBJECT-GROUP macro is the name
the group, which is an OBJECT IDENTIFIER, an
assigned name
SNMPv2 Working Group Standards Track [Page 10]
RFC 1904 Conformance Statements for SNMPv2 January 1996
3.6. Usage
The SNMP Group [3] is described
snmpGroup OBJECT-
OBJECTS { snmpInPkts
snmpInBadVersions
snmpInASNParseErrs
snmpBadOperations
snmpSilentDrops
snmpProxyDrops
snmpEnableAuthenTraps }
STATUS
"A collection of objects providing basic instrumentation
control of an SNMPv2 entity."
::= { snmpMIBGroups 8 }
According to this invocation, the conformance group
{ snmpMIBGroups 8 }
contains 7 objects
4. Mapping of the NOTIFICATION-GROUP
For conformance purposes, it is useful to define a collection
notifications. The NOTIFICATION-GROUP macro serves this purpose.
should be noted that the expansion of the NOTIFICATION-GROUP macro
something which conceptually happens during implementation and
during run-time
4.1. Mapping of the NOTIFICATIONS
The NOTIFICATIONS clause, which must be present, is used to name
notification contained in the conformance group. Each of the
notifications must be defined in the same information module as
NOTIFICATION-GROUP macro appears
4.2. Mapping of the STATUS
The STATUS clause, which must be present, indicates whether
definition is current or historic
The values "current", and "obsolete" are self-explanatory.
"deprecated" value indicates that the definition is obsolete,
that an implementor may wish to support the group to
SNMPv2 Working Group Standards Track [Page 11]
RFC 1904 Conformance Statements for SNMPv2 January 1996
interoperability with older implementations
4.3. Mapping of the DESCRIPTION
The DESCRIPTION clause, which must be present, contains a
definition of the group, along with a description of any relations
other groups. Note that generic compliance requirements should
be stated in this clause. However, implementation
between this group and other groups may be defined in this clause
4.4. Mapping of the REFERENCE
The REFERENCE clause, which need not be present, contains a
cross-reference to a group defined in some other information module
This is useful when de-osifying a MIB module produced by some
organization
4.5. Mapping of the NOTIFICATION-GROUP
The value of an invocation of the NOTIFICATION-GROUP macro is
name of the group, which is an OBJECT IDENTIFIER, an
assigned name
4.6. Usage
The SNMP Basic Notifications Group [3] is described
snmpBasicNotificationsGroup NOTIFICATION-
NOTIFICATIONS { coldStart, authenticationFailure }
STATUS
"The two notifications which an SNMPv2 entity is required
implement."
::= { snmpMIBGroups 7 }
According to this invocation, the conformance group
{ snmpMIBGroups 1 }
contains 2 notifications
5. Mapping of the MODULE-COMPLIANCE
The MODULE-COMPLIANCE macro is used to convey a minimum set
requirements with respect to implementation of one or more
modules. It should be noted that the expansion of the MODULE
COMPLIANCE macro is something which conceptually happens
implementation and not during run-time
SNMPv2 Working Group Standards Track [Page 12]
RFC 1904 Conformance Statements for SNMPv2 January 1996
A requirement on all "standard" MIB modules is that a
MODULE-COMPLIANCE specification is also defined, either in the
information module or in a companion information module
5.1. Mapping of the STATUS
The STATUS clause, which must be present, indicates whether
definition is current or historic
The values "current", and "obsolete" are self-explanatory.
"deprecated" value indicates that the specification is obsolete,
that an implementor may wish to support that object to
interoperability with older implementations
5.2. Mapping of the DESCRIPTION
The DESCRIPTION clause, which must be present, contains a
definition of this compliance statement and should embody
information which would otherwise be communicated in any ASN.1
commentary annotations associated with the statement
5.3. Mapping of the REFERENCE
The REFERENCE clause, which need not be present, contains a
cross-reference to a compliance statement defined in some
information module
5.4. Mapping of the MODULE
The MODULE clause, which must be present, is repeatedly used to
each MIB module for which compliance requirements are
specified. Each MIB module is named by its module name,
optionally, by its associated OBJECT IDENTIFIER as well. The
name can be omitted when the MODULE-COMPLIANCE invocation
inside a MIB module, to refer to the encompassing MIB module
5.4.1. Mapping of the MANDATORY-GROUPS
The MANDATORY-GROUPS clause, which need not be present, names the
or more object or notification groups within the correspondent
module which are unconditionally mandatory for implementation. If
SNMPv2 entity acting in an agent role claims compliance to the
module, then it must implement each and every object and
within each conformance group listed. That is, if a SNMPv2
returns a noSuchObject exception in response to a management
get operation [4] for any object within any mandatory
group for every MIB view, or if the SNMPv2 entity cannot
each notification listed in any conformance group under
SNMPv2 Working Group Standards Track [Page 13]
RFC 1904 Conformance Statements for SNMPv2 January 1996
appropriate circumstances, then that SNMPv2 entity is not
conformant implementation of the MIB module
5.4.2. Mapping of the GROUP
The GROUP clause, which need not be present, is repeatedly used
name each object and notification group which is
mandatory or unconditionally optional for compliance to the
module. A group named in a GROUP clause must be absent from
correspondent MANDATORY-GROUPS clause
Conditionally mandatory groups include those which are mandatory
if a particular protocol is implemented, or only if another group
implemented. A GROUP clause's DESCRIPTION specifies the
under which the group is conditionally mandatory
A group which is named in neither a MANDATORY-GROUPS clause nor
GROUP clause, is unconditionally optional for compliance to the
module
5.4.3. Mapping of the OBJECT
The OBJECT clause, which need not be present, is repeatedly used
name each MIB object for which compliance has a refined
with respect to the MIB module definition. The MIB object must
present in one of the conformance groups named in the
MANDATORY-GROUPS clause or GROUP clauses
By definition, each object specified in an OBJECT clause follows
MODULE clause which names the information module in which that
is defined. Therefore, the use of an IMPORTS statement, to
from where such objects are imported, is redundant and is
required in an information module
5.4.3.1. Mapping of the SYNTAX
The SYNTAX clause, which need not be present, is used to provide
refined SYNTAX for the object named in the correspondent
clause. Note that if this clause and a WRITE-SYNTAX clause are
present, then this clause only applies when instances of the
named in the correspondent OBJECT clause are read
Consult Section 9 of [2] for more information on refined syntax
SNMPv2 Working Group Standards Track [Page 14]
RFC 1904 Conformance Statements for SNMPv2 January 1996
5.4.3.2. Mapping of the WRITE-SYNTAX
The WRITE-SYNTAX clause, which need not be present, is used
provide a refined SYNTAX for the object named in the
OBJECT clause when instances of that object are written
Consult Section 9 of [2] for more information on refined syntax
5.4.3.3. Mapping of the MIN-ACCESS
The MIN-ACCESS clause, which need not be present, is used to
the minimal level of access for the object named in the
OBJECT clause. If this clause is absent, the minimal level of
is the same as the maximal level specified in the
invocation of the OBJECT-TYPE macro. If present, this clause
not specify a greater level of access than is specified in
correspondent invocation of the OBJECT-TYPE macro
The level of access for certain types of objects is fixed
to their syntax definition. These types include: conceptual
and rows, auxiliary objects, and objects with the syntax
Counter32, Counter64 (and possibly, certain types of
conventions). A MIN-ACCESS clause should not be present for
objects
An implementation is compliant if the level of access it provides
greater or equal to the minimal level in the MODULE-COMPLIANCE
and less or equal to the maximal level in the OBJECT-TYPE macro
5.4.4. Mapping of the DESCRIPTION
The DESCRIPTION clause must be present for each use of the GROUP
OBJECT clause. For an OBJECT clause, it contains a
description of the refined compliance requirement. For a
clause, it contains a textual description of the conditions
which the group is conditionally mandatory or
optional
5.5. Mapping of the MODULE-COMPLIANCE
The value of an invocation of the MODULE-COMPLIANCE macro is
OBJECT IDENTIFIER. As such, this value may be authoritatively
when referring to the compliance statement embodied by
invocation of the macro
SNMPv2 Working Group Standards Track [Page 15]
RFC 1904 Conformance Statements for SNMPv2 January 1996
5.6. Usage
The compliance statement contained in the (hypothetical) XYZv2-
might be
xyzMIBCompliance MODULE-
STATUS
"The compliance statement for XYZv2 entities which
the XYZv2 MIB."
MODULE -- compliance to the containing MIB
MANDATORY-GROUPS { xyzSystemGroup
xyzStatsGroup, xyzTrapGroup
xyzSetGroup
xyzBasicNotificationsGroup }
GROUP xyzV1
"The xyzV1 group is mandatory only for
XYZv2 entities which also implement XYZv1."
::= { xyzMIBCompliances 1 }
According to this invocation, to claim alignment with the
statement
{ xyzMIBCompliances 1 }
a system must implement the XYZv2-MIB's xyzSystemGroup
xyzStatsGroup, xyzTrapGroup, and xyzSetGroup object
groups, as well as the xyzBasicNotificationsGroup
group. Furthermore, if the XYZv2 entity also implements XYZv1,
it must also support the XYZv1Group group, if compliance is to
claimed
6. Mapping of the AGENT-CAPABILITIES
The AGENT-CAPABILITIES macro is used to convey a set of
present in a SNMPv2 entity acting in an agent role. It should
noted that the expansion of the AGENT-CAPABILITIES macro is
which conceptually happens during implementation and not during run
time
When a MIB module is written, it is divided into units of
termed groups. If a SNMPv2 entity acting in an agent role claims
implement a group, then it must implement each and every
within that group. Of course, for whatever reason, a SNMPv2
might implement only a subset of the groups within a MIB module.
addition, the definition of some MIB objects leave some aspects
SNMPv2 Working Group Standards Track [Page 16]
RFC 1904 Conformance Statements for SNMPv2 January 1996
the definition to the discretion of an implementor
Practical experience has demonstrated a need for concisely
the capabilities of an agent with respect to one or more MIB modules
The AGENT-CAPABILITIES macro allows an agent implementor to
the precise level of support which an agent claims in regards to
MIB group, and to bind that description to the value of an
of sysORID [3]. In particular, some objects may have restricted
augmented syntax or access-levels
If the AGENT-CAPABILITIES invocation is given to a management-
implementor, then that implementor can build management
which optimize themselves when communicating with a particular agent
For example, the management-station can maintain a database of
invocations. When a management-station interacts with an agent,
retrieves from the agent the values of all instances of sysORID [3].
Based on this, it consults the database to locate each entry
one of the retrieved values of sysORID. Using the located entries
the management application can now optimize its behavior accordingly
Note that the AGENT-CAPABILITIES macro specifies refinements
variations with respect to OBJECT-TYPE and NOTIFICATION-TYPE
in MIB modules, NOT with respect to MODULE-COMPLIANCE macros
compliance statements
6.1. Mapping of the PRODUCT-RELEASE
The PRODUCT-RELEASE clause, which must be present, contains a
description of the product release which includes this set
capabilities
6.2. Mapping of the STATUS
The STATUS clause, which must be present, indicates whether
definition is current ("current") or historic ("obsolete").
6.3. Mapping of the DESCRIPTION
The DESCRIPTION clause, which must be present, contains a
description of this set of capabilities
6.4. Mapping of the REFERENCE
The REFERENCE clause, which need not be present, contains a
cross-reference to a capability statement defined in some
information module
SNMPv2 Working Group Standards Track [Page 17]
RFC 1904 Conformance Statements for SNMPv2 January 1996
6.5. Mapping of the SUPPORTS
The SUPPORTS clause, which need not be present, is repeatedly used
name each MIB module for which the agent claims a complete or
implementation. Each MIB module is named by its module name,
optionally, by its associated OBJECT IDENTIFIER as well
6.5.1. Mapping of the INCLUDES
The INCLUDES clause, which must be present for each use of
SUPPORTS clause, is used to name each MIB group associated with
SUPPORTS clause, which the agent claims to implement
6.5.2. Mapping of the VARIATION
The VARIATION clause, which need not be present, is repeatedly
to name each object or notification which the agent implements
some variant or refined fashion with respect to the
invocation of the OBJECT-TYPE or NOTIFICATION-TYPE macro
Note that the variation concept is meant for generic
restrictions, e.g., if the variation for an object depends on
values of other objects, then this should be noted in the
DESCRIPTION clause
By definition, each object specified in a VARIATION clause follows
SUPPORTS clause which names the information module in which
object is defined. Therefore, the use of an IMPORTS statement,
specify from where such objects are imported, is redundant and is
required in an information module
6.5.2.1. Mapping of the SYNTAX
The SYNTAX clause, which need not be present, is used to provide
refined SYNTAX for the object named in the correspondent
clause. Note that if this clause and a WRITE-SYNTAX clause are
present, then this clause only applies when instances of the
named in the correspondent VARIATION clause are read
Consult Section 9 of [2] for more information on refined syntax
6.5.2.2. Mapping of the WRITE-SYNTAX
The WRITE-SYNTAX clause, which need not be present, is used
provide a refined SYNTAX for the object named in the
VARIATION clause when instances of that object are written
Consult Section 9 of [2] for more information on refined syntax
SNMPv2 Working Group Standards Track [Page 18]
RFC 1904 Conformance Statements for SNMPv2 January 1996
6.5.2.3. Mapping of the ACCESS
The ACCESS clause, which need not be present, is used to indicate
agent provides less than the maximal level of access to the object
notification named in the correspondent VARIATION clause
The only value applicable to notifications is "not-implemented".
The value "not-implemented" indicates the agent does not
the object or notification, and in the ordering of possible values
equivalent to "not-accessible".
The value "write-only" is provided solely for backward compatibility
and shall not be used for newly-defined object types. In
ordering of possible values, "write-only" is less than "not
accessible".
6.5.2.4. Mapping of the CREATION-REQUIRES
The CREATION-REQUIRES clause, which need not be present, is used
name the columnar objects of a conceptual row to which values must
explicitly assigned, by a management protocol set operation,
the agent will allow the instance of the status column of that row
be set to `active'. (Consult the definition of RowStatus [5].)
If the conceptual row does not have a status column (i.e.,
objects corresponding to the conceptual table were defined using
mechanisms in [6,7]), then the CREATION-REQUIRES clause, which
not be present, is used to name the columnar objects of a
row to which values must be explicitly assigned, by a
protocol set operation, before the agent will create new instances
objects in that row
This clause must not present unless the object named in
correspondent VARIATION clause is a conceptual row, i.e., has
syntax which resolves to a SEQUENCE containing columnar objects.
objects named in the value of this clause usually will refer
columnar objects in that row. However, objects unrelated to
conceptual row may also be specified
All objects which are named in the CREATION-REQUIRES clause for
conceptual row, and which are columnar objects of that row, must
an access level of "read-create".
SNMPv2 Working Group Standards Track [Page 19]
RFC 1904 Conformance Statements for SNMPv2 January 1996
6.5.2.5. Mapping of the DEFVAL
The DEFVAL clause, which need not be present, is used to provide
refined DEFVAL value for the object named in the
VARIATION clause. The semantics of this value are identical to
of the OBJECT-TYPE macro's DEFVAL clause
6.5.2.6. Mapping of the DESCRIPTION
The DESCRIPTION clause, which must be present for each use of
VARIATION clause, contains a textual description of the variant
refined implementation of the object or notification
6.6. Mapping of the AGENT-CAPABILITIES
The value of an invocation of the AGENT-CAPABILITIES macro is
OBJECT IDENTIFIER, which names the value of sysORID [3] for
this capabilities statement is valid
6.7. Usage
Consider how a capabilities statement for an agent might
described
exampleAgent AGENT-
PRODUCT-RELEASE "ACME Agent release 1.1 for 4BSD
STATUS
DESCRIPTION "ACME agent for 4BSD
SUPPORTS SNMPv2-
INCLUDES { systemGroup, snmpGroup, snmpSetGroup
snmpBasicNotificationsGroup }
VARIATION
DESCRIPTION "A coldStart trap is generated on
reboots."
SUPPORTS IF-
INCLUDES { ifGeneralGroup, ifPacketGroup }
VARIATION
SYNTAX INTEGER { up(1), down(2) }
DESCRIPTION "Unable to set test mode on 4BSD
VARIATION
SYNTAX INTEGER { up(1), down(2) }
DESCRIPTION "Information limited on 4BSD
SNMPv2 Working Group Standards Track [Page 20]
RFC 1904 Conformance Statements for SNMPv2 January 1996
SUPPORTS IP-
INCLUDES { ipGroup, icmpGroup }
VARIATION
SYNTAX INTEGER (255..255)
DESCRIPTION "Hard-wired on 4BSD
VARIATION
ACCESS not-
DESCRIPTION "Information not available on 4BSD
VARIATION
CREATION-REQUIRES { ipNetToMediaPhysAddress }
DESCRIPTION "Address mappings on 4BSD
both protocol and media addresses
SUPPORTS TCP-
INCLUDES { tcpGroup }
VARIATION
ACCESS read-
DESCRIPTION "Unable to set this on 4BSD
SUPPORTS UDP-
INCLUDES { udpGroup }
SUPPORTS EVAL-
INCLUDES { functionsGroup, expressionsGroup }
VARIATION
CREATION-REQUIRES { evalString }
DESCRIPTION "Conceptual row creation supported
::= { acmeAgents 1 }
According to this invocation, an agent with a sysORID value
{ acmeAgents 1 }
supports six MIB modules
From SNMPv2-MIB, five conformance groups are supported
From IF-MIB, the ifGeneralGroup and ifPacketGroup groups
supported. However, the objects ifAdminStatus and ifOperStatus
a restricted syntax
SNMPv2 Working Group Standards Track [Page 21]
RFC 1904 Conformance Statements for SNMPv2 January 1996
From IP-MIB, all objects in the ipGroup and icmpGroup are
except ipInAddrErrors, while ipDefaultTTL has a restricted range,
when creating a new instance in the ipNetToMediaTable, the set
request must create an instance of atPhysAddress
From TCP-MIB, the tcpGroup is supported except that tcpConnState
available only for reading
From UDP-MIB, the udpGroup is fully supported
From the EVAL-MIB, all the objects contained in the
and expressionsGroup conformance groups are supported,
variation. In addition, creation of new instances in the expr
is supported
7. Extending an Information
As experience is gained with a published information module, it
be desirable to revise that information module
Section 10 of [2] defines the rules for extending an
module. The remainder of this section defines how
groups, compliance statements, and capabilities statements may
extended
7.1. Conformance
If any non-editorial change is made to any clause of an object
then the OBJECT IDENTIFIER value associated with that object
must also be changed, along with its associated descriptor
7.2. Compliance
If any non-editorial change is made to any clause of a
definition, then the OBJECT IDENTIFIER value associated with
compliance definition must also be changed, along with its
descriptor
7.3. Capabilities
If any non-editorial change is made to any clause of a
definition, then the OBJECT IDENTIFIER value associated with
capabilities definition must also be changed, along with
associated descriptor
SNMPv2 Working Group Standards Track [Page 22]
RFC 1904 Conformance Statements for SNMPv2 January 1996
8. Security
Security issues are not discussed in this memo
9. Editor's
Keith
Cisco Systems, Inc
170 West Tasman
San Jose, CA 95134-1706
Phone: +1 408 526 5260
EMail: kzm@cisco.
10.
This document is the result of significant work by the four
contributors
Jeffrey D. Case (SNMP Research, case@snmp.com
Keith McCloghrie (Cisco Systems, kzm@cisco.com
Marshall T. Rose (Dover Beach Consulting, mrose@dbc.mtview.ca.us
Steven Waldbusser (International Network Services, stevew@uni.ins.com
In addition, the contributions of the SNMPv2 Working Group
acknowledged. In particular, a special thanks is extended for
contributions of
Alexander I. Alten (Novell
Dave Arneson (Cabletron
Uri Blumenthal (IBM
Doug Book (Chipcom
Kim Curran (Bell-Northern Research
Jim Galvin (Trusted Information Systems
Maria Greene (Ascom Timeplex
Iain Hanson (Digital
Dave Harrington (Cabletron
Nguyen Hien (IBM
Jeff Johnson (Cisco Systems
Michael Kornegay (Object Quest
Deirdre Kostick (AT&T Bell Labs
David Levi (SNMP Research
Daniel Mahoney (Cabletron
Bob Natale (ACE*COMM
Brian O'Keefe (Hewlett Packard
Andrew Pearson (SNMP Research
Dave Perkins (Peer Networks
SNMPv2 Working Group Standards Track [Page 23]
RFC 1904 Conformance Statements for SNMPv2 January 1996
Randy Presuhn (Peer Networks
Aleksey Romanov (Quality Quorum
Shawn Routhier (Epilogue
Jon Saperia (BGS Systems
Bob Stewart (Cisco Systems, bstewart@cisco.com),
Kaj Tesink (Bellcore
Glenn Waters (Bell-Northern Research
Bert Wijnen (IBM
11.
[1] Information processing systems - Open Systems Interconnection -
Specification of Abstract Syntax Notation One (ASN.1),
International Organization for Standardization.
Standard 8824, (December, 1987).
[2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M.,
S. Waldbusser, "Structure of Management Information for Version 2
of the Simple Network Management Protocol (SNMPv2)", RFC 1902,
January 1996.
[3] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M.,
S. Waldbusser, "Management Information Base for Version 2 of
Simple Network Management Protocol (SNMPv2)", RFC 1907,
January 1996.
[4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M.,
S. Waldbusser, "Protocol Operations for Version 2 of the
Network Management Protocol (SNMPv2)", RFC 1905, January 1996.
[5] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M.,
S. Waldbusser, "Textual Conventions for Version 2 of the
Network Management Protocol (SNMPv2)", RFC 1903, January 1996.
[6] Rose, M., and K. McCloghrie, "Structure and Identification
Management Information for TCP/IP-based internets", STD 16,
1155, May 1990.
[7] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16,
RFC 1212, March 1991.
SNMPv2 Working Group Standards Track [Page 24]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
