Entity MIB (Version 3)
RFC 4133
| Document | Type |
RFC - Proposed Standard
(August 2005; Errata)
Obsoleted by RFC 6933
Obsoletes RFC 2737
|
|
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Stream | WG state | (None) | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 4133 (Proposed Standard) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Bert Wijnen | ||
| Send notices to | (None) | ||
Network Working Group A. Bierman
Request for Comments: 4133 K. McCloghrie
Obsoletes: 2737 Cisco Systems, Inc.
Category: Standards Track August 2005
Entity MIB (Version 3)
Status of This Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2005).
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. This document specifies version 3 of the Entity MIB, which
obsoletes version 2 (RFC 2737).
Bierman & McCloghrie Standards Track [Page 1]
RFC 4133 Entity MIB (Version 3) August 2005
Table of Contents
1. The SNMP Management Framework ...................................3
2. Overview ........................................................3
2.1. Terms ......................................................4
2.2. Relationship to Community Strings ..........................5
2.3. Relationship to SNMP Contexts ..............................5
2.4. Relationship to Proxy Mechanisms ...........................6
2.5. Relationship to a Chassis MIB ..............................6
2.6. Relationship to the Interfaces MIB .........................6
2.7. Relationship to the Other MIBs .............................7
2.8. Relationship to Naming Scopes ..............................7
2.9. Multiple Instances of the Entity MIB .......................7
2.10. Re-Configuration of Entities ..............................8
2.11. Textual Convention Change .................................8
2.12. MIB Structure .............................................8
2.12.1. entityPhysical Group ..............................9
2.12.2. entityLogical Group ..............................11
2.12.3. entityMapping Group ..............................11
2.12.4. entityGeneral Group ..............................12
2.12.5. entityNotifications Group ........................12
2.13. Multiple Agents ..........................................12
2.14. Changes Since RFC 2037 ...................................12
2.14.1. Textual Conventions ..............................12
2.14.2. New entPhysicalTable Objects .....................13
2.14.3. New entLogicalTable Objects ......................13
2.14.4. Bug Fixes ........................................13
2.15. Changes Since RFC 2737 ...................................13
2.15.1. Textual Conventions ..............................13
2.15.2. New Objects ......................................14
2.15.3. Bug Fixes ........................................14
3. Definitions ....................................................14
4. Usage Examples .................................................44
4.1. Router/Bridge .............................................44
4.2. Repeaters .................................................50
5. Security Considerations ........................................57
6. IANA Considerations ............................................58
7. Acknowledgements ...............................................59
8. References .....................................................59
8.1. Normative References ......................................59
8.2. Informative References ....................................59
Bierman & McCloghrie Standards Track [Page 2]
RFC 4133 Entity MIB (Version 3) August 2005
1. The SNMP Management Framework
For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Show full document text