Entity Sensor Management Information Base
RFC 3433
Document | Type | RFC - Proposed Standard (December 2002; Errata) | |
---|---|---|---|
Authors | Kenyon Norseth , Dan Romascanu , Andy Bierman | ||
Last updated | 2020-01-21 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized with errata bibtex | ||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 3433 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Bert Wijnen | ||
IESG note |
Requeted to be on IESG agenda for 19 Sept 2002 Responsible: RFC Editor |
||
Send notices to | (None) |
Network Working Group A. Bierman Request for Comments: 3433 Cisco Systems, Inc. Category: Standards Track D. Romascanu Avaya Inc. K.C. Norseth L-3 Communications December 2002 Entity Sensor Management Information Base 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 (2002). All Rights Reserved. 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 for extending the Entity MIB (RFC 2737) to provide generalized access to information related to physical sensors, which are often found in networking equipment (such as chassis temperature, fan RPM, power supply voltage). Table of Contents 1 The Internet-Standard Management Framework .................. 2 2 Overview .................................................... 2 2.1 Terms ................................................... 2 2.2 Relationship to the Entity MIB .......................... 2 2.3 Relationship to General Thresholding Mechanisms ......... 3 3 MIB Structure ............................................... 3 4 Definitions ................................................. 4 5 Intellectual Property ....................................... 13 6 Acknowledgements ............................................ 14 7 Normative References ........................................ 14 8 Informative References ...................................... 14 9 Security Considerations ..................................... 15 10 Authors' Addresses .......................................... 16 11 Full Copyright Statement .................................... 17 Bierman, et. al. Standards Track [Page 1] RFC 3433 Entity Sensor MIB December 2002 1. The Internet-Standard 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 Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 2. Overview There is a need for a standardized way of obtaining information related to the physical sensors which are commonly found in networking equipment. Information such as the current value of the sensor, the current operational status, and the data units precision associated with the sensor, should be represented in a consistent manner for any type of sensor. Physical sensors are represented in the Entity MIB with entPhysicalEntry and an entPhysicalClass value of 'sensor(8)'. The information provided in the ENTITY-SENSOR-MIB module (defined in this document) defines a sparse augmentation of the entPhysicalTable, for entries which represent physical sensors. 2.1. Terms The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, RFC 2119. [RFC2119] 2.2. Relationship to the Entity MIB The MIB objects defined in this document provide a sparse augmentation to the entPhysicalTable in the Entity MIB, for entries in which the associated entPhysicalClass object is equal to 'sensor(8)'. An agent is expected to maintain an entPhySensorEntry with the same entPhysicalIndex value for each entPhysicalEntry representing a physical sensor. Therefore, implementation of the entityPhysicalGroup is required for agents that implement the Entity Sensor MIB. Bierman, et. al. Standards Track [Page 2] RFC 3433 Entity Sensor MIB December 2002 2.3. Relationship to General Thresholding MechanismsShow full document text