Difference between revisions of "SMIv2 Conformance Statement"
From Net-SNMP Wiki
(change category to MIBs) |
|||
| Line 24: | Line 24: | ||
a feeling for it look at some MIB modules and read RFC 2580. | a feeling for it look at some MIB modules and read RFC 2580. | ||
| − | [[Category: | + | [[Category:MIBs]] |
Latest revision as of 17:48, 15 October 2007
Good Answer
This is a Good Answer article. It was likely created as a response to a question on a Net-SNMP Mailing List and written up here for others to see. It likely covers material not yet in the FAQ or in the Tutorial but may someday be moved there
Questions
- What are the SNMP Conformance Statements .
- What it is the need of Conformance Statements .
- How can i used this to write my MIB Module.
Answer
Conformance Statements
See RFC 2580 for details, but in simple terms the SNMP conformance statements are the boundaries of being compliant with a MIB module (or the standard, so to say).
For instance, is a MIB has readable and writable managed objects you could define a read-only compliance and full (read/write) compliance.
Purpose
To express implementation conformance with a standard.
How/Where
These are mostly added in the last part of a MIB module. To get a feeling for it look at some MIB modules and read RFC 2580.
