Entity MIB using SMIv2
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 35
- Abstract
- This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing multiple logical and physical entities managed by a single SNMP agent. [STANDARDS-TRACK]
- Publication Date
- 1996-10-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC2037- Link
- https://doi.org/10.17487/RFC2037
- Author(s)
- Keith McCloghrieAndy Bierman
- Keyword(s)
- ENTITY-MIB, MIB, SNMP
Latest version of IETF RFC 2037
Document Versions — IETF RFC 2037
-
▶ IETF RFC 2037 (1996-10-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Bibliographic Reference(s)
- IETF RFC 1157 [Active*]
- IETF RFC 1213 [Active*]
- IETF RFC 1573 [Superseded*]
- IETF RFC 1901 [Active*]
- IETF RFC 1902 [Superseded*]
- IETF RFC 1903 [Superseded*]
- IETF RFC 1904 [Superseded*]
- IETF RFC 1905 [Superseded*]
- IETF RFC 1906 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC2037.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 2037, Entity MIB using SMIv2. Available at https://doi.org/10.17487/RFC2037
Snippet:
IETF RFC 2037, Entity MIB using SMIv2. Available at https://doi.org/10.17487/RFC2037
HTML (ISO 690 compliant)
Preview:
IETF RFC 2037, Entity MIB using SMIv2. Available at https://doi.org/10.17487/RFC2037
Snippet:
<span class="citation"><cite>IETF RFC 2037</cite>, Entity MIB using SMIv2. Available at <a href="https://doi.org/10.17487/RFC2037" target="_blank" rel="noopener">https://doi.org/10.17487/RFC2037</a></span>
SMPTE's HTML Pub
Preview:
Snippet:
<li> <cite id="bib-rfc2037">IETF RFC 2037</cite>, Entity MIB using SMIv2 <span class="doi">10.17487/RFC2037</span> </li>
Referenced By
- IETF RFC 2564 [Active*]
- IETF RFC 2613 [Active*]
- IETF RFC 2737 [Superseded*]
- IETF RFC 4133 [Superseded*]
- IETF RFC 6933 [Active*]