Entity MIB (entmib)Last Modified: 2005-06-10
Operations and Management Area Director(s):
Operations and Management Area Advisor:
General Discussion: firstname.lastname@example.org
Description of Working Group:This working group is chartered to standardize a set of managed
objects representing logical and physical entities and the
relationships between them. Logical entities can occur when a
single agent supports multiple instances of one MIB, such as
RFCs 1493, 1525, or 1850 where each instance represents a
single (logical) device/entity. Physical entities are the actual
physical components on which the logical entities operate;
typically, the physical components exist in a hierarchy.
The set of objects will be consistent with the SNMP framework and
existing SNMP standards.
The scope of the defined managed objects should allow an NMS to
interrogate a standard SNMP context and thereby discover what
logical and physical entities exist, how to access the MIB
information of each logical entity, and the relationships between
the various entities. The MIB should support both a single agent
or multiple agents in one physical entity.
The WG will also standardize a set of managed objects representing
sensor entities. Sensor entities are physical entities that report
a value based on external conditions, such as temperature sensors,
power monitors, etc. The Sensor Entity MIB will augment the basic
Entity MIB to allow an NMS to obtain the value reported by a sensor.
This MIB will not contain internal support for alarms or
thresholds, but should work with standard alarm and threshold MIBs,
such as RMON-2.
Goals and Milestones:
No Current Internet-Drafts
Request For Comments:Entity MIB (RFC 2037) (74362 bytes) obsoleted by RFC 2737
Entity MIB (Version 2) (RFC 2737) (125141 bytes) obsoletes RFC 2037/ obsoleted by RFC 4133
Entity Sensor Management Information Base (RFC 3433) (31857 bytes)
Entity MIB (Version 3) (RFC 4133) (136711 bytes) obsoletes RFC 2737
Entity State MIB (RFC 4268) (40348 bytes)