draft-ietf-entmib-v3-07.txt   rfc4133.txt 
Entity MIB Working Group Andy Bierman Network Working Group A. Bierman
Internet Draft Keith McCloghrie Request for Comments: 4133 K. McCloghrie
Cisco Systems, Inc. Obsoletes: 2737 Cisco Systems, Inc.
19 January 2005 Category: Standards Track August 2005
Entity MIB (Version 3) Entity MIB (Version 3)
<draft-ietf-entmib-v3-07.txt> Status of This Memo
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of RFC 3668.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as
Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet-Drafts
as reference material or to cite them other than as "work in
progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at This document specifies an Internet standards track protocol for the
http://www.ietf.org/shadow.html 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 Notice
Copyright (C) The Internet Society (2005). All Rights Reserved. Copyright (C) The Internet Society (2005).
Abstract Abstract
This memo defines a portion of the Management Information Base This memo defines a portion of the Management Information Base (MIB)
(MIB) for use with network management protocols in the Internet for use with network management protocols in the Internet community.
community. In particular, it describes managed objects used for In particular, it describes managed objects used for managing
managing multiple logical and physical entities managed by a single multiple logical and physical entities managed by a single SNMP
SNMP agent. This document specifies version 3 of the Entity MIB, agent. This document specifies version 3 of the Entity MIB, which
which obsoletes version 2 (RFC 2737). obsoletes version 2 (RFC 2737).
Table of Contents Table of Contents
1 The SNMP Management Framework .............................. 3 1. The SNMP Management Framework ...................................3
2 Overview ................................................... 3 2. Overview ........................................................3
2.1 Terms .................................................... 4 2.1. Terms ......................................................4
2.2 Relationship to Community Strings ........................ 6 2.2. Relationship to Community Strings ..........................5
2.3 Relationship to SNMP Contexts ............................ 6 2.3. Relationship to SNMP Contexts ..............................5
2.4 Relationship to Proxy Mechanisms ......................... 6 2.4. Relationship to Proxy Mechanisms ...........................6
2.5 Relationship to a Chassis MIB ............................ 7 2.5. Relationship to a Chassis MIB ..............................6
2.6 Relationship to the Interfaces MIB ....................... 7 2.6. Relationship to the Interfaces MIB .........................6
2.7 Relationship to the Other MIBs ........................... 7 2.7. Relationship to the Other MIBs .............................7
2.8 Relationship to Naming Scopes ............................ 8 2.8. Relationship to Naming Scopes ..............................7
2.9 Multiple Instances of the Entity MIB ..................... 8 2.9. Multiple Instances of the Entity MIB .......................7
2.10 Re-Configuration of Entities ............................ 9 2.10. Re-Configuration of Entities ..............................8
2.11 Textual Convention Change ............................... 9 2.11. Textual Convention Change .................................8
2.12 MIB Structure ........................................... 9 2.12. MIB Structure .............................................8
2.12.1 entityPhysical Group .................................. 10 2.12.1. entityPhysical Group ..............................9
2.12.2 entityLogical Group ................................... 12 2.12.2. entityLogical Group ..............................11
2.12.3 entityMapping Group ................................... 12 2.12.3. entityMapping Group ..............................11
2.12.4 entityGeneral Group ................................... 13 2.12.4. entityGeneral Group ..............................12
2.12.5 entityNotifications Group ............................. 13 2.12.5. entityNotifications Group ........................12
2.13 Multiple Agents ......................................... 13 2.13. Multiple Agents ..........................................12
2.14 Changes Since RFC 2037 .................................. 14 2.14. Changes Since RFC 2037 ...................................12
2.14.1 Textual Conventions ................................... 14 2.14.1. Textual Conventions ..............................12
2.14.2 New entPhysicalTable Objects .......................... 14 2.14.2. New entPhysicalTable Objects .....................13
2.14.3 New entLogicalTable Objects ........................... 14 2.14.3. New entLogicalTable Objects ......................13
2.14.4 Bugfixes .............................................. 15 2.14.4. Bug Fixes ........................................13
2.15 Changes Since RFC 2737 .................................. 15 2.15. Changes Since RFC 2737 ...................................13
2.15.1 Textual Conventions ................................... 15 2.15.1. Textual Conventions ..............................13
2.15.2 New Objects ........................................... 15 2.15.2. New Objects ......................................14
2.15.3 Bugfixes .............................................. 15 2.15.3. Bug Fixes ........................................14
3 Definitions ................................................ 16 3. Definitions ....................................................14
4 Usage Examples ............................................. 48 4. Usage Examples .................................................44
4.1 Router/Bridge ............................................ 48 4.1. Router/Bridge .............................................44
4.2 Repeaters ................................................ 55 4.2. Repeaters .................................................50
5 Security Considerations .................................... 62 5. Security Considerations ........................................57
6 IANA Considerations ........................................ 64 6. IANA Considerations ............................................58
7 Acknowledgements ........................................... 64 7. Acknowledgements ...............................................59
8 References ................................................. 64 8. References .....................................................59
8.1 Normative References ..................................... 64 8.1. Normative References ......................................59
8.2 Informative References ................................... 65 8.2. Informative References ....................................59
1. The SNMP Management Framework 1. The SNMP Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 Internet-Standard Management Framework, please refer to section 7 of
of RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, Managed objects are accessed via a virtual information store, termed
termed the Management Information Base or MIB. MIB objects are the Management Information Base or MIB. MIB objects are generally
generally accessed through the Simple Network Management Protocol accessed through the Simple Network Management Protocol (SNMP).
(SNMP). Objects in the MIB are defined using the mechanisms Objects in the MIB are defined using the mechanisms defined in the
defined in the Structure of Management Information (SMI). This Structure of Management Information (SMI). This memo specifies a MIB
memo specifies a MIB module that is compliant to the SMIv2, which module that is compliant to the SMIv2, which is described in STD 58,
is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2579] and STD 58, RFC 2580 [RFC2580]. [RFC2580].
2. Overview 2. Overview
There is a need for a standardized way of representing a single There is a need for a standardized way of representing a single
agent which supports multiple instances of one MIB. This is agent, which supports multiple instances of one MIB. This is
presently true for at least 3 standard MIBs, and is likely to presently true for at least 3 standard MIBs, and is likely to become
become true for more and more MIBs as time passes. For example: true for more and more MIBs as time passes. For example:
- multiple instances of a bridge supported within a single device - multiple instances of a bridge supported within a single device
having a single agent; that has a single agent;
- multiple repeaters supported by a single agent; - multiple repeaters supported by a single agent;
- multiple OSPF backbone areas, each one operating as part of its own - multiple OSPF backbone areas, each operating as part of its own
Autonomous System, and each identified by the same area-id (e.g., Autonomous System, and each identified by the same area-id (e.g.,
0.0.0.0), supported inside a single router with one agent. 0.0.0.0), supported inside a single router with one agent.
The fact that it is a single agent in each of these cases implies The single agent present in each of these cases implies a
there is some relationship which binds all of these entities relationship binds these entities. Effectively, there is some
together. Effectively, there is some "overall" physical entity "overall" physical entity which houses the sum of the things managed
which houses the sum of the things managed by that one agent, i.e., by that one agent, i.e., there are multiple "logical" entities within
there are multiple "logical" entities within a single physical a single physical entity. Sometimes, the overall physical entity
entity. Sometimes, the overall physical entity contains multiple contains multiple (smaller) physical entities, and each logical
(smaller) physical entities and each logical entity is associated entity is associated with a particular physical entity. Sometimes,
with a particular physical entity. Sometimes, the overall physical the overall physical entity is a "compound" of multiple physical
entity is a "compound" of multiple physical entities (e.g., a stack entities (e.g., a stack of stackable hubs).
of stackable hubs).
What is needed is a way to determine exactly what logical entities What is needed is a way to determine exactly which logical entities
are managed by the agent (with some version of SNMP), and thereby are managed by the agent (with some version of SNMP) in order to
to be able to communicate with the agent about a particular logical communicate with the agent about a particular logical entity. When
entity. When different logical entities are associated with different logical entities are associated with different physical
different physical entities within the overall physical entity, it entities within the overall physical entity, it is also useful to be
is also useful to be able to use this information to distinguish able to use this information to distinguish between logical entities.
between logical entities.
In these situations, there is no need for varbinds for multiple In these situations, there is no need for varbinds for multiple
logical entities to be referenced in the same SNMP message logical entities to be referenced in the same SNMP message (although
(although that might be useful in the future). Rather, it is that might be useful in the future). Rather, it is sufficient, and
sufficient, and in some situations preferable, to have the in some situations preferable, to have the context/community in the
context/community in the message identify the logical entity to message identify the logical entity to which the varbinds apply.
which the varbinds apply.
Version 2 of this MIB addresses new requirements that have emerged Version 2 of this MIB addresses new requirements, which have emerged
since the publication of the first Entity MIB (RFC 2037 [RFC2037]). since the publication of the first Entity MIB (RFC 2037 [RFC2037]).
There is a need for a standardized way of providing non-volatile, There is a need for a standardized way of providing non-volatile,
administratively assigned identifiers for physical components administratively-assigned identifiers for physical components
represented with the Entity MIB. There is also a need to align the represented with the Entity MIB. There is also a need to align the
Entity MIB with the SNMPv3 administrative framework (STD 62, RFC Entity MIB with the SNMPv3 administrative framework (STD 62, RFC 3411
3411 [RFC3411]). Implementation experience has shown that [RFC3411]). Implementation experience has shown that additional
additional physical component attributes are also desirable. physical component attributes are also desirable.
Version 3 of this MIB addresses new requirements that have emerged Version 3 of this MIB addresses new requirements, which have emerged
since the publication of the second Entity MIB (RFC 2737 since the publication of the second Entity MIB (RFC 2737 [RFC2737]).
[RFC2737]). There is a need for identifying physical entities There is a need to identify physical entities that are central
which are central processing units (CPUs) and a need to provide a processing units (CPUs) and a need to provide a textual convention
textual convention which identifies an entPhysicalIndex value or that identifies an entPhysicalIndex value or zero, where the value
zero, where the value zero has application-specific semantics. Two zero has application-specific semantics. Two new objects have been
new objects have been added to the entPhysicalTable to identify the added to the entPhysicalTable to identify the manufacturing date and
manufacturing date and provide additional URIs for a particular provide additional URIs for a particular physical entity.
physical entity.
2.1. Terms 2.1. Terms
Some new terms are used throughout this document: Some new terms are used throughout this document:
- Naming Scope - Naming Scope
A "naming scope" represents the set of information that may be A "naming scope" represents the set of information that may be
potentially accessed through a single SNMP operation. All instances potentially accessed through a single SNMP operation. All
within the naming scope share the same unique identifier space. instances within the naming scope share the same unique identifier
For SNMPv1, a naming scope is identified by the value of the space. For SNMPv1, a naming scope is identified by the value of
associated 'entLogicalCommunity' instance. For SNMPv3, the term the associated 'entLogicalCommunity' instance. For SNMPv3, the
'context' is used instead of 'naming scope'. The complete term 'context' is used instead of 'naming scope'. The complete
definition of an SNMP context can be found in section 3.3.1 of RFC definition of an SNMP context can be found in section 3.3.1 of RFC
3411 [RFC3411]. 3411 [RFC3411].
- Multi-Scoped Object - Multi-Scoped Object
A MIB object, for which identical instance values identify A MIB object, for which identical instance values identify
different managed information in different naming scopes, is called different managed information in different naming scopes, is called
a "multi-scoped" MIB object. a "multi-scoped" MIB object.
- Single-Scoped Object - Single-Scoped Object
A MIB object, for which identical instance values identify the same A MIB object, for which identical instance values identify the same
skipping to change at page 5, line 33 skipping to change at page 5, line 16
A managed system contains one or more logical entities, each A managed system contains one or more logical entities, each
represented by at most one instantiation of each of a particular represented by at most one instantiation of each of a particular
set of MIB objects. A set of management functions is associated set of MIB objects. A set of management functions is associated
with each logical entity. Examples of logical entities include with each logical entity. Examples of logical entities include
routers, bridges, print-servers, etc. routers, bridges, print-servers, etc.
- Physical Entity - Physical Entity
A "physical entity" or "physical component" represents an A "physical entity" or "physical component" represents an
identifiable physical resource within a managed system. Zero or identifiable physical resource within a managed system. Zero or
more logical entities may utilize a physical resource at any given more logical entities may utilize a physical resource at any given
time. It is an implementation-specific manner as to which physical time. Determining which physical components are represented by an
components are represented by an agent in the EntPhysicalTable. agent in the EntPhysicalTable is an implementation-specific matter.
Typically, physical resources (e.g., communications ports, Typically, physical resources (e.g., communications ports,
backplanes, sensors, daughter-cards, power supplies, the overall backplanes, sensors, daughter-cards, power supplies, the overall
chassis) which can be managed via functions associated with one or chassis), which can be managed via functions associated with one or
more logical entities are included in the MIB. more logical entities, are included in the MIB.
- Containment Tree - Containment Tree
Each physical component may be modeled as 'contained' within Each physical component may be modeled as 'contained' within
another physical component. A "containment-tree" is the conceptual another physical component. A "containment-tree" is the conceptual
sequence of entPhysicalIndex values which uniquely specifies the sequence of entPhysicalIndex values that uniquely specifies the
exact physical location of a physical component within the managed exact physical location of a physical component within the managed
system. It is generated by 'following and recording' each system. It is generated by 'following and recording' each
'entPhysicalContainedIn' instance 'up the tree towards the root', 'entPhysicalContainedIn' instance 'up the tree towards the root',
until a value of zero indicating no further containment is found. until a value of zero indicating no further containment is found.
2.2. Relationship to Community Strings 2.2. Relationship to Community Strings
For community-based SNMP, distinguishing between different logical For community-based SNMP, differentiating logical entities is one
entities is one (but not the only) purpose of the community string (but not the only) purpose of the community string (RFC 1157
(RFC 1157 [RFC1157]). This is accommodated by representing each [RFC1157]). This is accommodated by representing each community
community string as a logical entity. string as a logical entity.
Note that different logical entities may share the same naming Note that different logical entities may share the same naming scope
scope (and therefore the same values of entLogicalCommunity). This and, therefore, the same values of entLogicalCommunity. This is
is possible, providing they have no need for the same instance of a possible, providing they have no need for the same instance of a MIB
MIB object to represent different managed information. object to represent different managed information.
2.3. Relationship to SNMP Contexts 2.3. Relationship to SNMP Contexts
Version 2 of the Entity MIB contains support for associating SNMPv3 Version 2 of the Entity MIB contains support for associating SNMPv3
contexts with logical entities. Two new MIB objects, defining an contexts with logical entities. Two new MIB objects, defining an
SnmpEngineID and ContextName pair, are used together to identify an SnmpEngineID and ContextName pair, are used together to identify an
SNMP context associated with a logical entity. This context can be SNMP context associated with a logical entity. This context can be
used (in conjunction with the entLogicalTAddress and used (in conjunction with the entLogicalTAddress and
entLogicalTDomain MIB objects) to send SNMPv3 messages on behalf of entLogicalTDomain MIB objects) to send SNMPv3 messages on behalf of a
a particular logical entity. particular logical entity.
2.4. Relationship to Proxy Mechanisms 2.4. Relationship to Proxy Mechanisms
The Entity MIB is designed to allow functional component discovery. The Entity MIB is designed to allow functional component discovery.
The administrative relationships between different logical entities The administrative relationships between different logical entities
are not visible in any Entity MIB tables. An NMS cannot determine are not visible in any Entity MIB tables. A Network Management
whether MIB instances in different naming scopes are realized System (NMS) cannot determine whether MIB instances in different
locally or remotely (e.g., via some proxy mechanism) by examining naming scopes are realized locally or remotely (e.g., via some proxy
any particular Entity MIB objects. mechanism) by examining any particular Entity MIB objects.
The management of administrative framework functions is not an The management of administrative framework functions is not an
explicit goal of the Entity MIB WG at this time. This new area of explicit goal of the Entity MIB WG at this time. This new area of
functionality may be revisited after some operational experience functionality may be revisited after some operational experience with
with the Entity MIB is gained. the Entity MIB is gained.
Note that for community-based versions of SNMP, a network Note that for community-based versions of SNMP, a network
administrator will likely be able to associate community strings administrator will likely be able to associate community strings with
with naming scopes with proprietary mechanisms, as a matter of naming scopes that have proprietary mechanisms, as a matter of
configuration. There are no mechanisms for managing naming scopes configuration. There are no mechanisms for managing naming scopes
defined in this MIB. defined in this MIB.
2.5. Relationship to a Chassis MIB 2.5. Relationship to a Chassis MIB
Some readers may recall that a previous IETF working group Some readers may recall that a previous IETF working group attempted
attempted to define a Chassis MIB. No consensus was reached by to define a Chassis MIB. No consensus was reached by that working
that working group, possibly because its scope was too broad. As group, possibly because its scope was too broad. As such, it is not
such, it is not the purpose of this MIB to be a "Chassis MIB the purpose of this MIB to be a "Chassis MIB replacement", nor is it
replacement", nor is it within the scope of this MIB to contain all within the scope of this MIB to contain all the information which
the information which might be necessary to manage a "chassis". On might be necessary to manage a "chassis". On the other hand, the
the other hand, the entities represented by an implementation of entities represented by an implementation of this MIB might well be
this MIB might well be contained in a chassis. contained in a chassis.
2.6. Relationship to the Interfaces MIB 2.6. Relationship to the Interfaces MIB
The Entity MIB contains a mapping table identifying physical The Entity MIB contains a mapping table identifying physical
components that have 'external values' (e.g., ifIndex) associated components that have 'external values' (e.g., ifIndex) associated
with them within a given naming scope. This table can be used to with them within a given naming scope. This table can be used to
identify the physical location of each interface in the ifTable identify the physical location of each interface in the ifTable (RFC
(RFC 2863 [RFC2863]). Since ifIndex values in different contexts 2863 [RFC2863]). Because ifIndex values in different contexts are
are not related to one another, the interface to physical component not related to one another, the interface to physical component
associations are relative to the same logical entity within the associations are relative to the same logical entity within the
agent. agent.
The Entity MIB also contains 'entPhysicalName' and The Entity MIB also contains 'entPhysicalName' and 'entPhysicalAlias'
'entPhysicalAlias' objects, which approximate the semantics of the objects, which approximate the semantics of the 'ifName' and
'ifName' and 'ifAlias' objects (respectively) from the Interfaces 'ifAlias' objects (respectively) from the Interfaces MIB [RFC2863],
MIB [RFC2863], for all types of physical components. for all types of physical components.
2.7. Relationship to the Other MIBs 2.7. Relationship to the Other MIBs
The Entity MIB contains a mapping table identifying physical The Entity MIB contains a mapping table identifying physical
components that have identifiers from other standard MIBs components that have identifiers from other standard MIBs associated
associated with them. For example, this table can be used along with them. For example, this table can be used along with the
with the physical mapping table to identify the physical location physical mapping table to identify the physical location of each
of each repeater port in the rptrPortTable, or each interface in repeater port in the rptrPortTable, or each interface in the ifTable.
the ifTable.
2.8. Relationship to Naming Scopes 2.8. Relationship to Naming Scopes
There is some question as to which MIB objects may be returned There is some question as to which MIB objects may be returned within
within a given naming scope. MIB objects which are not multi-scoped a given naming scope. MIB objects which are not multi-scoped within
within a managed system are likely to ignore context information in a managed system are likely to ignore context information in
implementation. In such a case, it is likely such objects will be implementation. In such a case, it is likely such objects will be
returned in all naming scopes (e.g., not just the 'default' naming returned in all naming scopes (e.g., not just the 'default' naming
scope or the SNMPv3 default context). scope or the SNMPv3 default context).
For example, a community string used to access the management For example, a community string used to access the management
information for logical device 'bridge2' may allow access to all information for logical device 'bridge2' may allow access to all the
the non-bridge related objects in the 'default' naming scope, as non-bridge related objects in the 'default' naming scope, as well as
well as a second instance of the Bridge MIB (RFC 1493 [RFC1493]). a second instance of the Bridge MIB (RFC 1493 [RFC1493]).
It is an implementation-specific matter as to the isolation of The isolation of single-scoped MIB objects by the agent is an
single-scoped MIB objects by the agent. An agent may wish to limit implementation-specific matter. An agent may wish to limit the
the objects returned in a particular naming scope to just the objects returned in a particular naming scope to only the multi-
multi-scoped objects in that naming scope (e.g., system group and scoped objects in that naming scope (e.g., system group and the
the Bridge MIB). In this case, all single-scoped management Bridge MIB). In this case, all single-scoped management information
information would belong to a common naming scope (e.g., would belong to a common naming scope (e.g., 'default'), which itself
'default'), which itself may contain some multi-scoped objects may contain some multi-scoped objects (e.g., system group).
(e.g., system group).
2.9. Multiple Instances of the Entity MIB 2.9. Multiple Instances of the Entity MIB
It is possible that more than one agent exists in a managed system, It is possible that more than one agent may exist in a managed
and in such cases, multiple instances of the Entity MIB system. In such cases, multiple instances of the Entity MIB
(representing the same managed objects) may be available to an NMS. (representing the same managed objects) may be available to an NMS.
In order to reduce complexity for agent implementation, multiple In order to reduce complexity for agent implementation, multiple
instances of the Entity MIB are not required to be equivalent or instances of the Entity MIB are not required to be equivalent or even
even consistent. An NMS may be able to 'align' instances returned consistent. An NMS may be able to 'align' instances returned by
by different agents by examining the columns of each table, but different agents by examining the columns of each table, but vendor-
vendor-specific identifiers and (especially) index values are specific identifiers and (especially) index values are likely to be
likely to be different. Each agent may be managing different different. Each agent may be managing different subsets of the
subsets of the entire chassis as well. entire chassis as well.
When all of a physically-modular device is represented by a single When all of a physically-modular device is represented by a single
agent, the entry for which entPhysicalContainedIn has the value agent, the entry (for which entPhysicalContainedIn has the value
zero would likely have 'chassis' as the value of its zero) would likely have 'chassis' as the value of its
entPhysicalClass; alternatively, for an agent on a module where the entPhysicalClass. Alternatively, for an agent on a module where the
agent represents only the physical entities on that module (not agent represents only the physical entities on that module (not those
those on other modules), the entry for which entPhysicalContainedIn on other modules), the entry (for which entPhysicalContainedIn has
has the value zero would likely have 'module' as the value of its the value zero) would likely have 'module' as the value of its
entPhysicalClass. entPhysicalClass.
An agent implementation of the entLogicalTable is not required to An agent implementation of the entLogicalTable is not required to
contain information about logical entities managed primarily by contain information about logical entities managed primarily by other
other agents. That is, the entLogicalTAddress and entLogicalTDomain agents. That is, the entLogicalTAddress and entLogicalTDomain
objects in the entLogicalTable are provided to support an objects in the entLogicalTable are provided to support an historical
historical multiplexing mechanism, not to identify other SNMP multiplexing mechanism, not to identify other SNMP agents.
agents.
Note that the Entity MIB is a single-scoped MIB, in the event an Note that the Entity MIB is a single-scoped MIB, in the event an
agent represents the MIB in different naming scopes. agent represents the MIB in different naming scopes.
2.10. Re-Configuration of Entities 2.10. Re-Configuration of Entities
Most of the MIB objects defined in this MIB have at most a Most of the MIB objects defined in this MIB have, at most, a read-
read-only MAX-ACCESS clause. This is a conscious decision by the only MAX-ACCESS clause. This is a conscious decision by the working
working group to limit this MIB's scope. The second version of the group to limit this MIB's scope. The second version of the Entity
Entity MIB allows a network administrator to configure some common MIB allows a network administrator to configure some common
attributes of physical components. attributes of physical components.
2.11. Textual Convention Change 2.11. Textual Convention Change
Version 1 of the Entity MIB contains three MIB objects defined with Version 1 of the Entity MIB contains three MIB objects defined with
the (now obsolete) DisplayString textual convention. In version 2 the (now obsolete) DisplayString textual convention. In version 2 of
of the Entity MIB, the syntax for these objects has been updated to the Entity MIB, the syntax for these objects has been updated to use
use the (now preferred) SnmpAdminString textual convention. the (now preferred) SnmpAdminString textual convention.
The working group realizes that this change is not strictly The working group realizes that this change is not strictly supported
supported by SMIv2. In our judgment, the alternative of by SMIv2. In our judgment, the alternative of deprecating the old
deprecating the old objects and defining new objects would have a objects and defining new objects would have a more adverse impact on
more adverse impact on backward compatibility and interoperability, backward compatibility and interoperability, given the particular
given the particular semantics of these objects. semantics of these objects.
2.12. MIB Structure 2.12. MIB Structure
The Entity MIB contains five groups of MIB objects: The Entity MIB contains five groups of MIB objects:
- entityPhysical group - entityPhysical group
Describes the physical entities managed by a single agent. Describes the physical entities managed by a single agent.
- entityLogical group - entityLogical group
Describes the logical entities managed by a single agent. Describes the logical entities managed by a single agent.
skipping to change at page 10, line 32 skipping to change at page 9, line 29
This group contains a single table to identify physical system This group contains a single table to identify physical system
components, called the entPhysicalTable. components, called the entPhysicalTable.
The entPhysicalTable contains one row per physical entity, and must The entPhysicalTable contains one row per physical entity, and must
always contain at least one row for an "overall" physical entity, always contain at least one row for an "overall" physical entity,
which should have an entPhysicalClass value of 'stack(11)', which should have an entPhysicalClass value of 'stack(11)',
'chassis(3)' or 'module(9)'. 'chassis(3)' or 'module(9)'.
Each row is indexed by an arbitrary, small integer, and contains a Each row is indexed by an arbitrary, small integer, and contains a
description and type of the physical entity. It also optionally description and type of the physical entity. It also optionally
contains the index number of another entPhysicalEntry indicating a contains the index number of another entPhysicalEntry, indicating a
containment relationship between the two. containment relationship between the two.
Version 2 of the Entity MIB provides additional MIB objects for Version 2 of the Entity MIB provides additional MIB objects for each
each physical entity. Some common read-only attributes have been physical entity. Some common read-only attributes have been added,
added, as well as three writable string objects. as well as three writable string objects.
- entPhysicalAlias - entPhysicalAlias
This string can be used by an NMS as a non-volatile identifier for This string can be used by an NMS as a non-volatile identifier for
the physical component. Maintaining a non-volatile string for every the physical component. Maintaining a non-volatile string for
physical component represented in the entPhysicalTable can be every physical component represented in the entPhysicalTable can be
costly and unnecessary. An agent may algorithmically generate costly and unnecessary. An agent may algorithmically generate
'entPhysicalAlias' strings for particular entries (e.g., based on 'entPhysicalAlias' strings for particular entries (e.g., based on
the entPhysicalClass value). the entPhysicalClass value).
- entPhysicalAssetID - entPhysicalAssetID
This string is provided to store a user-specific asset identifier This string is provided to store a user-specific asset identifier
for removable physical components. In order to reduce the for removable physical components. In order to reduce the non-
non-volatile storage needed by a particular agent, a network volatile storage needed by a particular agent, a network
administrator should only assign asset identifiers to physical administrator should only assign asset identifiers to physical
entities which are field-replaceable (i.e., not permanently entities that are field-replaceable (i.e., not permanently
contained within another physical entity). contained within another physical entity).
- entPhysicalSerialNum - entPhysicalSerialNum
This string is provided to store a vendor-specific serial number This string is provided to store a vendor-specific serial number
string for physical components. This is a writable object in case string for physical components. This writable object is used when
an agent cannot identify the serial numbers of all installed an agent cannot identify the serial numbers of all installed
physical entities, and a network administrator wishes to configure physical entities, and a network administrator wishes to configure
the non-volatile serial number strings manually (via an NMS the non-volatile serial number strings manually (via an NMS
application). application).
Version 3 of the Entity MIB provides two additional MIB objects for Version 3 of the Entity MIB provides two additional MIB objects for
each physical entity: each physical entity:
- entPhysicalMfgDate - entPhysicalMfgDate
This object contains the date of manufacturing of the managed This object contains the date of manufacturing of the managed
entity. If the manufacturing date is unknown or not supported the entity. If the manufacturing date is unknown or not supported the
object is not instantiated. The special value '0000000000000000'H object is not instantiated. The special value '0000000000000000'H
may also be returned in this case. may also be returned in this case.
- entPhysicalUris - entPhysicalUris
This object provides additional identification information about This object provides additional identification information about
the physical entity. the physical entity.
The object contains one or more Uniform Resource Identifiers (URIs) This object contains one or more Uniform Resource Identifiers
and therefore the syntax of this object must conform to RFC 2396 (URIs) and, therefore, the syntax of this object must conform to
[RFC2396] section 2. Uniform Resource Names (URNs), RFC 3406 RFC 3986 [RFC3986] section 2. Uniform Resource Names (URNs), RFC
[RFC3406], are resource identifiers with the specific requirements 3406 [RFC3406], are resource identifiers with the specific
for enabling location independent identification of a resource, as requirements for enabling location independent identification of a
well as longevity of reference. URNs are part of the larger URI resource, as well as longevity of reference. URNs are part of the
family with the specific goal of providing persistent naming of larger URI family with the specific goal of providing persistent
resources. URI schemes and URN name spaces are registered by IANA naming of resources. URI schemes and URN name spaces are
(see http://www.iana.org/assignments/uri-schemes and registered by IANA (see http://www.iana.org/assignments/uri-schemes
http://www.iana.org/assignments/urn-namespaces). and http://www.iana.org/assignments/urn-namespaces).
The entPhysicalUris object may be used to encode for example a URI For example, the entPhysicalUris object may be used to encode a URI
containing a Common Language Equipment Identifier (CLEI) URI for containing a Common Language Equipment Identifier (CLEI) URN for
the managed physical entity. The URN name space for CLEIs is the managed physical entity. The URN name space for CLEIs is
defined in [RFC CLEIURN], and the CLEI format is defined in defined in [RFCYYYY], and the CLEI format is defined in
[T1.213][T1.213a]. For example, an entPhysicalUris instance may [T1.213][T1.213a]. For example, an entPhysicalUris instance may
have the value of have the value of
URN:CLEI:D4CE18B7AA URN:CLEI:D4CE18B7AA
[RFC2396] and [RFCCLEIURN] identify this as a URI in the CLEI URN [RFC3986] and [RFCYYYY] identify this as a URI in the CLEI URN name
name space, and the specific CLEI code, D4CE18B7AA is based on the space. The specific CLEI code, D4CE18B7AA, is based on the example
example provided in [T1.213a]. provided in [T1.213a].
Multiple URIs may be present and are separated by white space Multiple URIs may be present and are separated by white space
characters. Leading and trailing white space characters are characters. Leading and trailing white space characters are
ignored. ignored.
If no additional identification information is known or supported If no additional identification information is known about the
about the physical entity the object is not instantiated. physical entity or supported, the object is not instantiated.
2.12.2. entityLogical Group 2.12.2. entityLogical Group
This group contains a single table to identify logical entities, This group contains a single table to identify logical entities,
called the entLogicalTable. called the entLogicalTable.
The entLogicalTable contains one row per logical entity. Each row The entLogicalTable contains one row per logical entity. Each row is
is indexed by an arbitrary, small integer and contains a name, indexed by an arbitrary, small integer and contains a name,
description, and type of the logical entity. It also contains description, and type of the logical entity. It also contains
information to allow access to the MIB information for the logical information to allow access to the MIB information for the logical
entity. This includes SNMP versions that use a community name (with entity. This includes SNMP versions that use a community name (with
some form of implied context representation) and SNMP versions that some form of implied context representation) and SNMP versions that
use the SNMP ARCH [RFC3411] method of context identification. use the SNMP ARCH [RFC3411] method of context identification.
If a agent represents multiple logical entities with this MIB, then If an agent represents multiple logical entities with this MIB, then
this group must be implemented for all logical entities known to this group must be implemented for all logical entities known to the
the agent. agent.
If an agent represents a single logical entity, or multiple logical If an agent represents a single logical entity, or multiple logical
entities within a single naming scope, then implementation of this entities within a single naming scope, then implementation of this
group may be omitted by the agent. group may be omitted by the agent.
2.12.3. entityMapping Group 2.12.3. entityMapping Group
This group contains three tables to identify associations between This group contains three tables to identify associations between
different system components. different system components.
The entLPMappingTable contains mappings between entLogicalIndex - entLPMappingTable
values (logical entities) and entPhysicalIndex values (the physical This table contains mappings between entLogicalIndex values
(logical entities) and entPhysicalIndex values (the physical
components supporting that entity). A logical entity can map to components supporting that entity). A logical entity can map to
more than one physical component, and more than one logical entity more than one physical component, and more than one logical entity
can map to (share) the same physical component. If an agent can map to (share) the same physical component. If an agent
represents a single logical entity, or multiple logical entities represents a single logical entity, or multiple logical entities
within a single naming scope, then implementation of this table may within a single naming scope, then implementation of this table may
be omitted by the agent. Note that this table is deprecated in be omitted by the agent.
version 3 of the Entity MIB.
The entAliasMappingTable contains mappings between entLogicalIndex, - entAliasMappingTable
entPhysicalIndex pairs and 'alias' object identifier values. This This table contains mappings between entLogicalIndex,
entPhysicalIndex pairs, and 'alias' object identifier values. This
allows resources managed with other MIBs (e.g., repeater ports, allows resources managed with other MIBs (e.g., repeater ports,
bridge ports, physical and logical interfaces) to be identified in bridge ports, physical and logical interfaces) to be identified in
the physical entity hierarchy. Note that each alias identifier is the physical entity hierarchy. Note that each alias identifier is
only relevant in a particular naming scope. If an agent represents only relevant in a particular naming scope. If an agent represents
a single logical entity, or multiple logical entities within a a single logical entity, or multiple logical entities within a
single naming scope, then implementation of this table may be single naming scope, then implementation of this table may be
omitted by the agent. omitted by the agent.
The entPhysicalContainsTable contains simple mappings between - entPhysicalContainsTable
This table contains simple mappings between
'entPhysicalContainedIn' values for each container/'containee' 'entPhysicalContainedIn' values for each container/'containee'
relationship in the managed system. The indexing of this table relationship in the managed system. The indexing of this table
allows an NMS to quickly discover the 'entPhysicalIndex' values for allows an NMS to quickly discover the 'entPhysicalIndex' values for
all children of a given physical entity. all children of a given physical entity.
2.12.4. entityGeneral Group 2.12.4. entityGeneral Group
This group contains general information relating to the other This group contains general information relating to the other object
object groups. groups.
At this time, the entGeneral group contains a single scalar object At this time, the entGeneral group contains a single scalar object
(entLastChangeTime), which represents the value of sysUptime when (entLastChangeTime), which represents the value of sysUptime when any
any part of the Entity MIB configuration last changed. part of the Entity MIB configuration last changed.
2.12.5. entityNotifications Group 2.12.5. entityNotifications Group
This group contains notification definitions relating to the This group contains notification definitions relating to the overall
overall status of the Entity MIB instantiation. status of the Entity MIB instantiation.
2.13. Multiple Agents 2.13. Multiple Agents
Even though a primary motivation for this MIB is to represent the Even though a primary motivation for this MIB is to represent the
multiple logical entities supported by a single agent, it is also multiple logical entities supported by a single agent, another
possible to use it to represent multiple logical entities supported motivation is to represent multiple logical entities supported by
by multiple agents (in the same "overall" physical entity). multiple agents (in the same "overall" physical entity). Indeed, it
Indeed, it is implicit in the SNMP architecture, that the number of is implicit in the SNMP architecture that the number of agents is
agents is transparent to a network management station. transparent to a network management station.
However, there is no agreement at this time as to the degree of However, there is no agreement at this time as to the degree of
cooperation which should be expected for agent implementations. cooperation that should be expected for agent implementations.
Therefore, multiple agents within the same managed system are free Therefore, multiple agents within the same managed system are free to
to implement the Entity MIB independently. (Refer the section on implement the Entity MIB independently. (For more information, refer
"Multiple Instances of the Entity MIB" for more details). to Section 2.9, "Multiple Instances of the Entity MIB".)
2.14. Changes Since RFC 2037 2.14. Changes Since RFC 2037
2.14.1. Textual Conventions 2.14.1. Textual Conventions
The PhysicalClass TC text has been clarified, and a new enumeration The PhysicalClass TC text has been clarified, and a new enumeration
to support 'stackable' components has been added. The to support 'stackable' components has been added. The
SnmpEngineIdOrNone TC has been added to support SNMPv3. SnmpEngineIdOrNone TC has been added to support SNMPv3.
2.14.2. New entPhysicalTable Objects 2.14.2. New entPhysicalTable Objects
The entPhysicalHardwareRev, entPhysicalFirmwareRev, and The entPhysicalHardwareRev, entPhysicalFirmwareRev, and
entPhysicalSoftwareRev objects have been added for revision entPhysicalSoftwareRev objects have been added for revision
identification. identification.
The entPhysicalSerialNum, entPhysicalMfgName, entPhysicalModelName, The entPhysicalSerialNum, entPhysicalMfgName, entPhysicalModelName,
and entPhysicalIsFru objects have been added for better vendor and entPhysicalIsFru objects have been added for better vendor
identification for physical components. The entPhysicalSerialNum identification for physical components. In the event the agent
object can be set by a management station in the event the agent cannot identify this information, the entPhysicalSerialNum object can
cannot identify this information. be set by a management station.
The entPhysicalAlias and entPhysicalAssetID objects have been added The entPhysicalAlias and entPhysicalAssetID objects have been added
for better user component identification. These objects are for better user component identification. These objects are intended
intended to be set by a management station and preserved by the to be set by a management station and preserved by the agent across
agent across restarts. restarts.
2.14.3. New entLogicalTable Objects 2.14.3. New entLogicalTable Objects
The entLogicalContextEngineID and entLogicalContextName objects The entLogicalContextEngineID and entLogicalContextName objects have
have been added to provide an SNMP context for SNMPv3 access on been added to provide an SNMP context for SNMPv3 access on behalf of
behalf of a logical entity. a logical entity.
2.14.4. Bugfixes 2.14.4. Bug Fixes
A bug was fixed in the entLogicalCommunity object. The subrange was A bug was fixed in the entLogicalCommunity object. The subrange was
incorrect (1..255) and is now (0..255). The description clause has incorrect (1..255) and is now (0..255). The description clause has
also been clarified. This object is now deprecated. also been clarified. This object is now deprecated.
The entLastChangeTime object description has been changed to The entLastChangeTime object description has been changed to
generalize the events which cause an update to the last change generalize the events that cause an update to the last change
timestamp. timestamp.
The syntax was changed from DisplayString to SnmpAdminString for The syntax was changed from DisplayString to SnmpAdminString for the
the entPhysicalDescr, entPhysicalName, and entLogicalDescr objects. entPhysicalDescr, entPhysicalName, and entLogicalDescr objects.
2.15. Changes Since RFC 2737 2.15. Changes Since RFC 2737
2.15.1. Textual Conventions 2.15.1. Textual Conventions
The PhysicalIndexOrZero TC has been added to allow objects to The PhysicalIndexOrZero TC has been added to allow objects to
reference an entPhysicalIndex value or zero. The PhysicalClass TC reference an entPhysicalIndex value or zero. The PhysicalClass TC
has been extended to support a new enumeration for central has been extended to support a new enumeration for central processing
processing units. units.
2.15.2. New Objects 2.15.2. New Objects
The entPhysicalMfgDate object has been added to the The entPhysicalMfgDate object has been added to the entPhysicalTable
entPhysicalTable to provide the date of manufacturing of the to provide the date of manufacturing of the managed entity.
managed entity.
The entPhysicalUris object has been added to the entPhysicalTable The entPhysicalUris object has been added to the entPhysicalTable to
to provide additional identification information about the physical provide additional identification information about the physical
entity, such as a Common Language Equipment Identifier (CLEI) URI. entity, such as a Common Language Equipment Identifier (CLEI) URN.
2.15.3. Bugfixes 2.15.3. Bug Fixes
The syntax was changed from INTEGER to Integer32 for the The syntax was changed from INTEGER to Integer32 for the
entPhysicalParentRelPos, entLogicalIndex, and entPhysicalParentRelPos, entLogicalIndex, and
entAliasLogicalIndexOrZero objects, and from INTEGER to entAliasLogicalIndexOrZero objects, and from INTEGER to
PhysicalIndexOrZero for the entPhysicalContainedIn object. PhysicalIndexOrZero for the entPhysicalContainedIn object.
3. Definitions 3. Definitions
ENTITY-MIB DEFINITIONS ::= BEGIN ENTITY-MIB DEFINITIONS ::= BEGIN
skipping to change at page 16, line 23 skipping to change at page 14, line 39
TDomain, TAddress, TEXTUAL-CONVENTION, TDomain, TAddress, TEXTUAL-CONVENTION,
AutonomousType, RowPointer, TimeStamp, TruthValue, AutonomousType, RowPointer, TimeStamp, TruthValue,
DateAndTime DateAndTime
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB; FROM SNMP-FRAMEWORK-MIB;
entityMIB MODULE-IDENTITY entityMIB MODULE-IDENTITY
LAST-UPDATED "200501190000Z" LAST-UPDATED "200508100000Z"
ORGANIZATION "IETF ENTMIB Working Group" ORGANIZATION "IETF ENTMIB Working Group"
CONTACT-INFO CONTACT-INFO
" WG E-mail: entmib@ietf.org " WG E-mail: entmib@ietf.org
Mailing list subscription info: Mailing list subscription info:
http://www.ietf.org/mailman/listinfo/entmib http://www.ietf.org/mailman/listinfo/entmib
Andy Bierman Andy Bierman
Cisco Systems Inc. ietf@andybierman.com
170 West Tasman Drive
San Jose, CA 95134
+1 408-527-3711
abierman@cisco.com
Keith McCloghrie Keith McCloghrie
Cisco Systems Inc. Cisco Systems Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
+1 408-526-5260 +1 408-526-5260
kzm@cisco.com" kzm@cisco.com"
DESCRIPTION DESCRIPTION
"The MIB module for representing multiple logical "The MIB module for representing multiple logical
entities supported by a single SNMP agent. entities supported by a single SNMP agent.
Copyright (C) The Internet Society (2005). This Copyright (C) The Internet Society (2005). This
version of this MIB module is part of RFC xxxx; see version of this MIB module is part of RFC 4133; see
the RFC itself for full legal notices." the RFC itself for full legal notices."
REVISION "200501190000Z" REVISION "200508100000Z"
DESCRIPTION DESCRIPTION
"Initial Version of Entity MIB (Version 3). "Initial Version of Entity MIB (Version 3).
This revision obsoletes RFC 2737. This revision obsoletes RFC 2737.
Additions: Additions:
- cpu(12) enumeration added to PhysicalClass TC - cpu(12) enumeration added to PhysicalClass TC
- DISPLAY-HINT clause to PhysicalIndex TC - DISPLAY-HINT clause to PhysicalIndex TC
- PhysicalIndexOrZero TC - PhysicalIndexOrZero TC
- entPhysicalMfgDate object - entPhysicalMfgDate object
- entPhysicalUris object - entPhysicalUris object
Changes: Changes:
- entPhysicalContainedIn SYNTAX changed from - entPhysicalContainedIn SYNTAX changed from
INTEGER to PhysicalIndexOrZero INTEGER to PhysicalIndexOrZero
This version published as RFC xxxx." This version published as RFC 4133."
REVISION "199912070000Z" REVISION "199912070000Z"
DESCRIPTION DESCRIPTION
"Initial Version of Entity MIB (Version 2). "Initial Version of Entity MIB (Version 2).
This revision obsoletes RFC 2037. This revision obsoletes RFC 2037.
This version published as RFC 2737." This version published as RFC 2737."
REVISION "199610310000Z" REVISION "199610310000Z"
DESCRIPTION DESCRIPTION
"Initial version (version 1), published as "Initial version (version 1), published as
skipping to change at page 18, line 5 skipping to change at page 16, line 10
entityPhysical OBJECT IDENTIFIER ::= { entityMIBObjects 1 } entityPhysical OBJECT IDENTIFIER ::= { entityMIBObjects 1 }
entityLogical OBJECT IDENTIFIER ::= { entityMIBObjects 2 } entityLogical OBJECT IDENTIFIER ::= { entityMIBObjects 2 }
entityMapping OBJECT IDENTIFIER ::= { entityMIBObjects 3 } entityMapping OBJECT IDENTIFIER ::= { entityMIBObjects 3 }
entityGeneral OBJECT IDENTIFIER ::= { entityMIBObjects 4 } entityGeneral OBJECT IDENTIFIER ::= { entityMIBObjects 4 }
-- Textual Conventions -- Textual Conventions
PhysicalIndex ::= TEXTUAL-CONVENTION PhysicalIndex ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary value which uniquely identifies the physical "An arbitrary value that uniquely identifies the physical
entity. The value should be a small positive integer; index entity. The value should be a small, positive integer.
values for different physical entities are not necessarily Index values for different physical entities are not
contiguous." necessarily contiguous."
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
PhysicalIndexOrZero ::= TEXTUAL-CONVENTION PhysicalIndexOrZero ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual convention is an extension of the "This textual convention is an extension of the
PhysicalIndex convention which defines a greater than zero PhysicalIndex convention, which defines a greater than zero
value used to identify a physical entity. This extension value used to identify a physical entity. This extension
permits the additional value of zero. The semantics of the permits the additional value of zero. The semantics of the
value zero are object-specific and must therefore be defined value zero are object-specific and must, therefore, be
as part of the description of any object which uses this defined as part of the description of any object that uses
syntax. Examples of the usage of this extension are this syntax. Examples of the usage of this extension are
situations where none or all physical entities need to be situations where none or all physical entities need to be
referenced." referenced."
SYNTAX Integer32 (0..2147483647) SYNTAX Integer32 (0..2147483647)
PhysicalClass ::= TEXTUAL-CONVENTION PhysicalClass ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An enumerated value which provides an indication of the "An enumerated value which provides an indication of the
general hardware type of a particular physical entity. general hardware type of a particular physical entity.
There are no restrictions as to the number of There are no restrictions as to the number of
skipping to change at page 18, line 44 skipping to change at page 16, line 49
The enumeration 'other' is applicable if the physical entity The enumeration 'other' is applicable if the physical entity
class is known, but does not match any of the supported class is known, but does not match any of the supported
values. values.
The enumeration 'unknown' is applicable if the physical The enumeration 'unknown' is applicable if the physical
entity class is unknown to the agent. entity class is unknown to the agent.
The enumeration 'chassis' is applicable if the physical The enumeration 'chassis' is applicable if the physical
entity class is an overall container for networking entity class is an overall container for networking
equipment. Any class of physical entity except a stack may equipment. Any class of physical entity, except a stack,
be contained within a chassis, and a chassis may only be may be contained within a chassis; and a chassis may only
contained within a stack. be contained within a stack.
The enumeration 'backplane' is applicable if the physical The enumeration 'backplane' is applicable if the physical
entity class is some sort of device for aggregating and entity class is some sort of device for aggregating and
forwarding networking traffic, such as a shared backplane in forwarding networking traffic, such as a shared backplane in
a modular ethernet switch. Note that an agent may model a a modular ethernet switch. Note that an agent may model a
backplane as a single physical entity, which is actually backplane as a single physical entity, which is actually
implemented as multiple discrete physical components (within implemented as multiple discrete physical components (within
a chassis or stack). a chassis or stack).
The enumeration 'container' is applicable if the physical The enumeration 'container' is applicable if the physical
entity class is capable of containing one or more removable entity class is capable of containing one or more removable
physical entities, possibly of different types. For example, physical entities, possibly of different types. For
each (empty or full) slot in a chassis will be modeled as a example, each (empty or full) slot in a chassis will be
container. Note that all removable physical entities should modeled as a container. Note that all removable physical
be modeled within a container entity, such as entities should be modeled within a container entity, such
field-replaceable modules, fans, or power supplies. Note as field-replaceable modules, fans, or power supplies. Note
that all known containers should be modeled by the agent, that all known containers should be modeled by the agent,
including empty containers. including empty containers.
The enumeration 'powerSupply' is applicable if the physical The enumeration 'powerSupply' is applicable if the physical
entity class is a power-supplying component. entity class is a power-supplying component.
The enumeration 'fan' is applicable if the physical entity The enumeration 'fan' is applicable if the physical entity
class is a fan or other heat-reduction component. class is a fan or other heat-reduction component.
The enumeration 'sensor' is applicable if the physical The enumeration 'sensor' is applicable if the physical
entity class is some sort of sensor, such as a temperature entity class is some sort of sensor, such as a temperature
sensor within a router chassis. sensor within a router chassis.
The enumeration 'module' is applicable if the physical The enumeration 'module' is applicable if the physical
entity class is some sort of self-contained sub-system. If entity class is some sort of self-contained sub-system. If
it is removable, then it should be modeled within a the enumeration 'module' is removable, then it should be
container entity, otherwise it should be modeled directly modeled within a container entity, otherwise it should be
within another physical entity (e.g., a chassis or another modeled directly within another physical entity (e.g., a
module). chassis or another module).
The enumeration 'port' is applicable if the physical entity The enumeration 'port' is applicable if the physical entity
class is some sort of networking port, capable of receiving class is some sort of networking port, capable of receiving
and/or transmitting networking traffic. and/or transmitting networking traffic.
The enumeration 'stack' is applicable if the physical entity The enumeration 'stack' is applicable if the physical entity
class is some sort of super-container (possibly virtual), class is some sort of super-container (possibly virtual),
intended to group together multiple chassis entities. A intended to group together multiple chassis entities. A
stack may be realized by a 'virtual' cable, a real stack may be realized by a 'virtual' cable, a real
interconnect cable, attached to multiple chassis, or may in interconnect cable, attached to multiple chassis, or may in
skipping to change at page 20, line 38 skipping to change at page 18, line 36
Entity MIB. Entity MIB.
If an instance of an object of SYNTAX SnmpEngineIdOrNone has If an instance of an object of SYNTAX SnmpEngineIdOrNone has
a non-zero length, then the object encoding and semantics a non-zero length, then the object encoding and semantics
are defined by the SnmpEngineID textual convention (see STD are defined by the SnmpEngineID textual convention (see STD
62, RFC 3411 [RFC3411]). 62, RFC 3411 [RFC3411]).
If an instance of an object of SYNTAX SnmpEngineIdOrNone If an instance of an object of SYNTAX SnmpEngineIdOrNone
contains a zero-length string, then no appropriate contains a zero-length string, then no appropriate
SnmpEngineID is associated with the logical entity (i.e., SnmpEngineID is associated with the logical entity (i.e.,
SNMPv3 not supported)." SNMPv3 is not supported)."
SYNTAX OCTET STRING (SIZE(0..32)) -- empty string or SnmpEngineID SYNTAX OCTET STRING (SIZE(0..32)) -- empty string or SnmpEngineID
-- The Physical Entity Table -- The Physical Entity Table
entPhysicalTable OBJECT-TYPE entPhysicalTable OBJECT-TYPE
SYNTAX SEQUENCE OF EntPhysicalEntry SYNTAX SEQUENCE OF EntPhysicalEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains one row per physical entity. There is "This table contains one row per physical entity. There is
always at least one row for an 'overall' physical entity." always at least one row for an 'overall' physical entity."
skipping to change at page 22, line 14 skipping to change at page 20, line 5
DESCRIPTION DESCRIPTION
"The index for this entry." "The index for this entry."
::= { entPhysicalEntry 1 } ::= { entPhysicalEntry 1 }
entPhysicalDescr OBJECT-TYPE entPhysicalDescr OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A textual description of physical entity. This object "A textual description of physical entity. This object
should contain a string which identifies the manufacturer's should contain a string that identifies the manufacturer's
name for the physical entity, and should be set to a name for the physical entity, and should be set to a
distinct value for each version or model of the physical distinct value for each version or model of the physical
entity. " entity. "
::= { entPhysicalEntry 2 } ::= { entPhysicalEntry 2 }
entPhysicalVendorType OBJECT-TYPE entPhysicalVendorType OBJECT-TYPE
SYNTAX AutonomousType SYNTAX AutonomousType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An indication of the vendor-specific hardware type of the "An indication of the vendor-specific hardware type of the
physical entity. Note that this is different from the physical entity. Note that this is different from the
definition of MIB-II's sysObjectID. definition of MIB-II's sysObjectID.
An agent should set this object to a enterprise-specific An agent should set this object to an enterprise-specific
registration identifier value indicating the specific registration identifier value indicating the specific
equipment type in detail. The associated instance of equipment type in detail. The associated instance of
entPhysicalClass is used to indicate the general type of entPhysicalClass is used to indicate the general type of
hardware device. hardware device.
If no vendor-specific registration identifier exists for If no vendor-specific registration identifier exists for
this physical entity, or the value is unknown by this agent, this physical entity, or the value is unknown by this agent,
then the value { 0 0 } is returned." then the value { 0 0 } is returned."
::= { entPhysicalEntry 3 } ::= { entPhysicalEntry 3 }
skipping to change at page 23, line 7 skipping to change at page 20, line 43
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of entPhysicalIndex for the physical entity which "The value of entPhysicalIndex for the physical entity which
'contains' this physical entity. A value of zero indicates 'contains' this physical entity. A value of zero indicates
this physical entity is not contained in any other physical this physical entity is not contained in any other physical
entity. Note that the set of 'containment' relationships entity. Note that the set of 'containment' relationships
define a strict hierarchy; that is, recursion is not define a strict hierarchy; that is, recursion is not
allowed. allowed.
In the event a physical entity is contained by more than one In the event that a physical entity is contained by more
physical entity (e.g., double-wide modules), this object than one physical entity (e.g., double-wide modules), this
should identify the containing entity with the lowest value object should identify the containing entity with the lowest
of entPhysicalIndex." value of entPhysicalIndex."
::= { entPhysicalEntry 4 } ::= { entPhysicalEntry 4 }
entPhysicalClass OBJECT-TYPE entPhysicalClass OBJECT-TYPE
SYNTAX PhysicalClass SYNTAX PhysicalClass
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An indication of the general hardware type of the physical "An indication of the general hardware type of the physical
entity. entity.
An agent should set this object to the standard enumeration An agent should set this object to the standard enumeration
value which most accurately indicates the general class of value that most accurately indicates the general class of
the physical entity, or the primary class if there is more the physical entity, or the primary class if there is more
than one. than one entity.
If no appropriate standard registration identifier exists If no appropriate standard registration identifier exists
for this physical entity, then the value 'other(1)' is for this physical entity, then the value 'other(1)' is
returned. If the value is unknown by this agent, then the returned. If the value is unknown by this agent, then the
value 'unknown(2)' is returned." value 'unknown(2)' is returned."
::= { entPhysicalEntry 5 } ::= { entPhysicalEntry 5 }
entPhysicalParentRelPos OBJECT-TYPE entPhysicalParentRelPos OBJECT-TYPE
SYNTAX Integer32 (-1..2147483647) SYNTAX Integer32 (-1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An indication of the relative position of this 'child' "An indication of the relative position of this 'child'
component among all its 'sibling' components. Sibling component among all its 'sibling' components. Sibling
components are defined as entPhysicalEntries which share the components are defined as entPhysicalEntries that share the
same instance values of each of the entPhysicalContainedIn same instance values of each of the entPhysicalContainedIn
and entPhysicalClass objects. and entPhysicalClass objects.
An NMS can use this object to identify the relative ordering An NMS can use this object to identify the relative ordering
for all sibling components of a particular parent for all sibling components of a particular parent
(identified by the entPhysicalContainedIn instance in each (identified by the entPhysicalContainedIn instance in each
sibling entry). sibling entry).
This value should match any external labeling of the If possible, this value should match any external labeling
physical component if possible. For example, for a container of the physical component. For example, for a container
(e.g., card slot) labeled as 'slot #3', (e.g., card slot) labeled as 'slot #3',
entPhysicalParentRelPos should have the value '3'. Note entPhysicalParentRelPos should have the value '3'. Note
that the entPhysicalEntry for the module plugged in slot 3 that the entPhysicalEntry for the module plugged in slot 3
should have an entPhysicalParentRelPos value of '1'. should have an entPhysicalParentRelPos value of '1'.
If the physical position of this component does not match If the physical position of this component does not match
any external numbering or clearly visible ordering, then any external numbering or clearly visible ordering, then
user documentation or other external reference material user documentation or other external reference material
should be used to determine the parent-relative position. If should be used to determine the parent-relative position.
this is not possible, then the the agent should assign a If this is not possible, then the agent should assign a
consistent (but possibly arbitrary) ordering to a given set consistent (but possibly arbitrary) ordering to a given set
of 'sibling' components, perhaps based on internal of 'sibling' components, perhaps based on internal
representation of the components. representation of the components.
If the agent cannot determine the parent-relative position If the agent cannot determine the parent-relative position
for some reason, or if the associated value of for some reason, or if the associated value of
entPhysicalContainedIn is '0', then the value '-1' is entPhysicalContainedIn is '0', then the value '-1' is
returned. Otherwise a non-negative integer is returned, returned. Otherwise, a non-negative integer is returned,
indicating the parent-relative position of this physical indicating the parent-relative position of this physical
entity. entity.
Parent-relative ordering normally starts from '1' and Parent-relative ordering normally starts from '1' and
continues to 'N', where 'N' represents the highest continues to 'N', where 'N' represents the highest
positioned child entity. However, if the physical entities positioned child entity. However, if the physical entities
(e.g., slots) are labeled from a starting position of zero, (e.g., slots) are labeled from a starting position of zero,
then the first sibling should be associated with a then the first sibling should be associated with an
entPhysicalParentRelPos value of '0'. Note that this entPhysicalParentRelPos value of '0'. Note that this
ordering may be sparse or dense, depending on agent ordering may be sparse or dense, depending on agent
implementation. implementation.
The actual values returned are not globally meaningful, as The actual values returned are not globally meaningful, as
each 'parent' component may use different numbering each 'parent' component may use different numbering
algorithms. The ordering is only meaningful among siblings algorithms. The ordering is only meaningful among siblings
of the same parent component. of the same parent component.
The agent should retain parent-relative position values The agent should retain parent-relative position values
skipping to change at page 25, line 9 skipping to change at page 22, line 40
entPhysicalName OBJECT-TYPE entPhysicalName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The textual name of the physical entity. The value of this "The textual name of the physical entity. The value of this
object should be the name of the component as assigned by object should be the name of the component as assigned by
the local device and should be suitable for use in commands the local device and should be suitable for use in commands
entered at the device's `console'. This might be a text entered at the device's `console'. This might be a text
name, such as `console' or a simple component number (e.g., name (e.g., `console') or a simple component number (e.g.,
port or module number), such as `1', depending on the port or module number, such as `1'), depending on the
physical component naming syntax of the device. physical component naming syntax of the device.
If there is no local name, or this object is otherwise not If there is no local name, or if this object is otherwise
applicable, then this object contains a zero-length string. not applicable, then this object contains a zero-length
string.
Note that the value of entPhysicalName for two physical Note that the value of entPhysicalName for two physical
entities will be the same in the event that the console entities will be the same in the event that the console
interface does not distinguish between them, e.g., slot-1 interface does not distinguish between them, e.g., slot-1
and the card in slot-1." and the card in slot-1."
::= { entPhysicalEntry 7 } ::= { entPhysicalEntry 7 }
entPhysicalHardwareRev OBJECT-TYPE entPhysicalHardwareRev OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 25, line 38 skipping to change at page 23, line 21
physical entity. The preferred value is the hardware physical entity. The preferred value is the hardware
revision identifier actually printed on the component itself revision identifier actually printed on the component itself
(if present). (if present).
Note that if revision information is stored internally in a Note that if revision information is stored internally in a
non-printable (e.g., binary) format, then the agent must non-printable (e.g., binary) format, then the agent must
convert such information to a printable format, in an convert such information to a printable format, in an
implementation-specific manner. implementation-specific manner.
If no specific hardware revision string is associated with If no specific hardware revision string is associated with
the physical component, or this information is unknown to the physical component, or if this information is unknown to
the agent, then this object will contain a zero-length the agent, then this object will contain a zero-length
string." string."
::= { entPhysicalEntry 8 } ::= { entPhysicalEntry 8 }
entPhysicalFirmwareRev OBJECT-TYPE entPhysicalFirmwareRev OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The vendor-specific firmware revision string for the "The vendor-specific firmware revision string for the
physical entity. physical entity.
Note that if revision information is stored internally in a Note that if revision information is stored internally in a
non-printable (e.g., binary) format, then the agent must non-printable (e.g., binary) format, then the agent must
convert such information to a printable format, in an convert such information to a printable format, in an
implementation-specific manner. implementation-specific manner.
If no specific firmware programs are associated with the If no specific firmware programs are associated with the
physical component, or this information is unknown to the physical component, or if this information is unknown to the
agent, then this object will contain a zero-length string." agent, then this object will contain a zero-length string."
::= { entPhysicalEntry 9 } ::= { entPhysicalEntry 9 }
entPhysicalSoftwareRev OBJECT-TYPE entPhysicalSoftwareRev OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The vendor-specific software revision string for the "The vendor-specific software revision string for the
physical entity. physical entity.
Note that if revision information is stored internally in a Note that if revision information is stored internally in a
non-printable (e.g., binary) format, then the agent must non-printable (e.g., binary) format, then the agent must
convert such information to a printable format, in an convert such information to a printable format, in an
implementation-specific manner. implementation-specific manner.
If no specific software programs are associated with the If no specific software programs are associated with the
physical component, or this information is unknown to the physical component, or if this information is unknown to the
agent, then this object will contain a zero-length string." agent, then this object will contain a zero-length string."
::= { entPhysicalEntry 10 } ::= { entPhysicalEntry 10 }
entPhysicalSerialNum OBJECT-TYPE entPhysicalSerialNum OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32)) SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The vendor-specific serial number string for the physical "The vendor-specific serial number string for the physical
entity. The preferred value is the serial number string entity. The preferred value is the serial number string
actually printed on the component itself (if present). actually printed on the component itself (if present).
On the first instantiation of an physical entity, the value On the first instantiation of an physical entity, the value
of entPhysicalSerialNum associated with that entity is set of entPhysicalSerialNum associated with that entity is set
to the correct vendor-assigned serial number, if this to the correct vendor-assigned serial number, if this
information is available to the agent. If a serial number information is available to the agent. If a serial number
is unknown or non-existent, the entPhysicalSerialNum will be is unknown or non-existent, the entPhysicalSerialNum will be
set to a zero-length string instead. set to a zero-length string instead.
Note that implementations which can correctly identify the Note that implementations that can correctly identify the
serial numbers of all installed physical entities do not serial numbers of all installed physical entities do not
need to provide write access to the entPhysicalSerialNum need to provide write access to the entPhysicalSerialNum
object. Agents which cannot provide non-volatile storage for object. Agents which cannot provide non-volatile storage
the entPhysicalSerialNum strings are not required to for the entPhysicalSerialNum strings are not required to
implement write access for this object. implement write access for this object.
Not every physical component will have a serial number, or Not every physical component will have a serial number, or
even need one. Physical entities for which the associated even need one. Physical entities for which the associated
value of the entPhysicalIsFRU object is equal to 'false(2)' value of the entPhysicalIsFRU object is equal to 'false(2)'
(e.g., the repeater ports within a repeater module), do not (e.g., the repeater ports within a repeater module), do not
need their own unique serial number. An agent does not have need their own unique serial number. An agent does not have
to provide write access for such entities, and may return a to provide write access for such entities, and may return a
zero-length string. zero-length string.
If write access is implemented for an instance of If write access is implemented for an instance of
entPhysicalSerialNum, and a value is written into the entPhysicalSerialNum, and a value is written into the
instance, the agent must retain the supplied value in the instance, the agent must retain the supplied value in the
entPhysicalSerialNum instance associated with the same entPhysicalSerialNum instance (associated with the same
physical entity for as long as that entity remains physical entity) for as long as that entity remains
instantiated. This includes instantiations across all instantiated. This includes instantiations across all
re-initializations/reboots of the network management system, re-initializations/reboots of the network management system,
including those which result in a change of the physical including those resulting in a change of the physical
entity's entPhysicalIndex value." entity's entPhysicalIndex value."
::= { entPhysicalEntry 11 } ::= { entPhysicalEntry 11 }
entPhysicalMfgName OBJECT-TYPE entPhysicalMfgName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The name of the manufacturer of this physical component. "The name of the manufacturer of this physical component.
The preferred value is the manufacturer name string actually The preferred value is the manufacturer name string actually
skipping to change at page 28, line 25 skipping to change at page 25, line 47
If the model name string associated with the physical If the model name string associated with the physical
component is unknown to the agent, then this object will component is unknown to the agent, then this object will
contain a zero-length string." contain a zero-length string."
::= { entPhysicalEntry 13 } ::= { entPhysicalEntry 13 }
entPhysicalAlias OBJECT-TYPE entPhysicalAlias OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32)) SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is an 'alias' name for the physical entity as "This object is an 'alias' name for the physical entity, as
specified by a network manager, and provides a non-volatile specified by a network manager, and provides a non-volatile
'handle' for the physical entity. 'handle' for the physical entity.
On the first instantiation of an physical entity, the value On the first instantiation of a physical entity, the value
of entPhysicalAlias associated with that entity is set to of entPhysicalAlias associated with that entity is set to
the zero-length string. However, agent may set the value to the zero-length string. However, the agent may set the
a locally unique default value, instead of a zero-length value to a locally unique default value, instead of a
string. zero-length string.
If write access is implemented for an instance of If write access is implemented for an instance of
entPhysicalAlias, and a value is written into the instance, entPhysicalAlias, and a value is written into the instance,
the agent must retain the supplied value in the the agent must retain the supplied value in the
entPhysicalAlias instance associated with the same physical entPhysicalAlias instance (associated with the same physical
entity for as long as that entity remains instantiated. entity) for as long as that entity remains instantiated.
This includes instantiations across all This includes instantiations across all
re-initializations/reboots of the network management system, re-initializations/reboots of the network management system,
including those which result in a change of the physical including those resulting in a change of the physical
entity's entPhysicalIndex value." entity's entPhysicalIndex value."
::= { entPhysicalEntry 14 } ::= { entPhysicalEntry 14 }
entPhysicalAssetID OBJECT-TYPE entPhysicalAssetID OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32)) SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is a user-assigned asset tracking identifier "This object is a user-assigned asset tracking identifier
for the physical entity as specified by a network manager, (as specified by a network manager) for the physical entity,
and provides non-volatile storage of this information. and provides non-volatile storage of this information.
On the first instantiation of an physical entity, the value On the first instantiation of a physical entity, the value
of entPhysicalAssetID associated with that entity is set to of entPhysicalAssetID associated with that entity is set to
the zero-length string. the zero-length string.
Not every physical component will have a asset tracking Not every physical component will have an asset tracking
identifier, or even need one. Physical entities for which identifier, or even need one. Physical entities for which
the associated value of the entPhysicalIsFRU object is equal the associated value of the entPhysicalIsFRU object is equal
to 'false(2)' (e.g., the repeater ports within a repeater to 'false(2)' (e.g., the repeater ports within a repeater
module), do not need their own unique asset tracking module), do not need their own unique asset tracking
identifier. An agent does not have to provide write access identifier. An agent does not have to provide write access
for such entities, and may instead return a zero-length for such entities, and may instead return a zero-length
string. string.
If write access is implemented for an instance of If write access is implemented for an instance of
entPhysicalAssetID, and a value is written into the entPhysicalAssetID, and a value is written into the
instance, the agent must retain the supplied value in the instance, the agent must retain the supplied value in the
entPhysicalAssetID instance associated with the same entPhysicalAssetID instance (associated with the same
physical entity for as long as that entity remains physical entity) for as long as that entity remains
instantiated. This includes instantiations across all instantiated. This includes instantiations across all
re-initializations/reboots of the network management system, re-initializations/reboots of the network management system,
including those which result in a change of the physical including those resulting in a change of the physical
entity's entPhysicalIndex value. entity's entPhysicalIndex value.
If no asset tracking information is associated with the If no asset tracking information is associated with the
physical component, then this object will contain a physical component, then this object will contain a
zero-length string." zero-length string."
::= { entPhysicalEntry 15 } ::= { entPhysicalEntry 15 }
entPhysicalIsFRU OBJECT-TYPE entPhysicalIsFRU OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates whether or not this physical entity "This object indicates whether or not this physical entity
is considered a 'field replaceable unit' by the vendor. If is considered a 'field replaceable unit' by the vendor. If
this object contains the value 'true(1)' then this this object contains the value 'true(1)' then this
entPhysicalEntry identifies a field replaceable unit. For entPhysicalEntry identifies a field replaceable unit. For
all entPhysicalEntries which represent components that are all entPhysicalEntries that represent components
permanently contained within a field replaceable unit, the permanently contained within a field replaceable unit, the
value 'false(2)' should be returned for this object." value 'false(2)' should be returned for this object."
::= { entPhysicalEntry 16 } ::= { entPhysicalEntry 16 }
entPhysicalMfgDate OBJECT-TYPE entPhysicalMfgDate OBJECT-TYPE
SYNTAX DateAndTime SYNTAX DateAndTime
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the date of manufacturing of the "This object contains the date of manufacturing of the
managed entity. If the manufacturing date is unknown or not managed entity. If the manufacturing date is unknown or not
supported the object is not instantiated. The special value supported, the object is not instantiated. The special
'0000000000000000'H may also be returned in this case." value '0000000000000000'H may also be returned in this
case."
::= { entPhysicalEntry 17 } ::= { entPhysicalEntry 17 }
entPhysicalUris OBJECT-TYPE entPhysicalUris OBJECT-TYPE
SYNTAX OCTET STRING SYNTAX OCTET STRING
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains additional identification information "This object contains additional identification information
about the physical entity. The object contains URIs and about the physical entity. The object contains URIs and,
therefore the syntax of this object must conform to RFC therefore, the syntax of this object must conform to RFC
2396, section 2. 3986, section 2.
Multiple URIs may be present and are separated by white Multiple URIs may be present and are separated by white
space characters. Leading and trailing white space space characters. Leading and trailing white space
characters are ignored. characters are ignored.
If no additional identification information is known or If no additional identification information is known
supported about the physical entity the object is not about the physical entity or supported, the object is not
instantiated. A zero length octet string may also be instantiated. A zero length octet string may also be
returned in this case." returned in this case."
REFERENCE REFERENCE
"RFC 2396, Uniform Resource Identifiers (URI): Generic "RFC 3986, Uniform Resource Identifiers (URI): Generic
Syntax, section 2, August 1998." Syntax, section 2, August 1998."
::= { entPhysicalEntry 18 } ::= { entPhysicalEntry 18 }
-- The Logical Entity Table -- The Logical Entity Table
entLogicalTable OBJECT-TYPE entLogicalTable OBJECT-TYPE
SYNTAX SEQUENCE OF EntLogicalEntry SYNTAX SEQUENCE OF EntLogicalEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains one row per logical entity. For agents "This table contains one row per logical entity. For agents
which implement more than one naming scope, at least one that implement more than one naming scope, at least one
entry must exist. Agents which instantiate all MIB objects entry must exist. Agents which instantiate all MIB objects
within a single naming scope are not required to implement within a single naming scope are not required to implement
this table." this table."
::= { entityLogical 1 } ::= { entityLogical 1 }
entLogicalEntry OBJECT-TYPE entLogicalEntry OBJECT-TYPE
SYNTAX EntLogicalEntry SYNTAX EntLogicalEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 31, line 39 skipping to change at page 29, line 6
entLogicalContextName SnmpAdminString entLogicalContextName SnmpAdminString
} }
entLogicalIndex OBJECT-TYPE entLogicalIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object uniquely identifies the logical "The value of this object uniquely identifies the logical
entity. The value should be a small positive integer; index entity. The value should be a small positive integer; index
values for different logical entities are are not values for different logical entities are not necessarily
necessarily contiguous." contiguous."
::= { entLogicalEntry 1 } ::= { entLogicalEntry 1 }
entLogicalDescr OBJECT-TYPE entLogicalDescr OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A textual description of the logical entity. This object "A textual description of the logical entity. This object
should contain a string which identifies the manufacturer's should contain a string that identifies the manufacturer's
name for the logical entity, and should be set to a distinct name for the logical entity, and should be set to a distinct
value for each version of the logical entity. " value for each version of the logical entity. "
::= { entLogicalEntry 2 } ::= { entLogicalEntry 2 }
entLogicalType OBJECT-TYPE entLogicalType OBJECT-TYPE
SYNTAX AutonomousType SYNTAX AutonomousType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An indication of the type of logical entity. This will "An indication of the type of logical entity. This will
skipping to change at page 32, line 31 skipping to change at page 29, line 43
a logical entity of a 802.3 repeater -> snmpDot3RptrMgmt a logical entity of a 802.3 repeater -> snmpDot3RptrMgmt
If an appropriate node in the SMI's naming hierarchy cannot If an appropriate node in the SMI's naming hierarchy cannot
be identified, the value 'mib-2' should be used." be identified, the value 'mib-2' should be used."
::= { entLogicalEntry 3 } ::= { entLogicalEntry 3 }
entLogicalCommunity OBJECT-TYPE entLogicalCommunity OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..255)) SYNTAX OCTET STRING (SIZE (0..255))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"An SNMPv1 or SNMPv2C community-string which can be used to "An SNMPv1 or SNMPv2C community-string, which can be used to
access detailed management information for this logical access detailed management information for this logical
entity. The agent should allow read access with this entity. The agent should allow read access with this
community string (to an appropriate subset of all managed community string (to an appropriate subset of all managed
objects) and may also return a community string based on the objects) and may also return a community string based on the
privileges of the request used to read this object. Note privileges of the request used to read this object. Note
that an agent may return a community string with read-only that an agent may return a community string with read-only
privileges, even if this object is accessed with a privileges, even if this object is accessed with a
read-write community string. However, the agent must take read-write community string. However, the agent must take
care not to return a community string which allows more care not to return a community string that allows more
privileges than the community string used to access this privileges than the community string used to access this
object. object.
A compliant SNMP agent may wish to conserve naming scopes by A compliant SNMP agent may wish to conserve naming scopes by
representing multiple logical entities in a single 'default' representing multiple logical entities in a single 'default'
naming scope. This is possible when the logical entities naming scope. This is possible when the logical entities,
represented by the same value of entLogicalCommunity have no represented by the same value of entLogicalCommunity, have
object instances in common. For example, 'bridge1' and no object instances in common. For example, 'bridge1' and
'repeater1' may be part of the main naming scope, but at 'repeater1' may be part of the main naming scope, but at
least one additional community string is needed to represent least one additional community string is needed to represent
'bridge2' and 'repeater2'. 'bridge2' and 'repeater2'.
Logical entities 'bridge1' and 'repeater1' would be Logical entities 'bridge1' and 'repeater1' would be
represented by sysOREntries associated with the 'default' represented by sysOREntries associated with the 'default'
naming scope. naming scope.
For agents not accessible via SNMPv1 or SNMPv2C, the value For agents not accessible via SNMPv1 or SNMPv2C, the value
of this object is the empty string. This object may also of this object is the empty string. This object may also
contain an empty string if a community string has not yet contain an empty string if a community string has not yet
been assigned by the agent, or no community string with been assigned by the agent, or if no community string with
suitable access rights can be returned for a particular SNMP suitable access rights can be returned for a particular SNMP
request. request.
Note that this object is deprecated. Agents which implement Note that this object is deprecated. Agents which implement
SNMPv3 access should use the entLogicalContextEngineID and SNMPv3 access should use the entLogicalContextEngineID and
entLogicalContextName objects to identify the context entLogicalContextName objects to identify the context
associated with each logical entity. SNMPv3 agents may associated with each logical entity. SNMPv3 agents may
return a zero-length string for this object, or may continue return a zero-length string for this object, or may continue
to return a community string (e.g., tri-lingual agent to return a community string (e.g., tri-lingual agent
support)." support)."
skipping to change at page 33, line 37 skipping to change at page 30, line 46
entLogicalTAddress OBJECT-TYPE entLogicalTAddress OBJECT-TYPE
SYNTAX TAddress SYNTAX TAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The transport service address by which the logical entity "The transport service address by which the logical entity
receives network management traffic, formatted according to receives network management traffic, formatted according to
the corresponding value of entLogicalTDomain. the corresponding value of entLogicalTDomain.
For snmpUDPDomain, a TAddress is 6 octets long, the initial For snmpUDPDomain, a TAddress is 6 octets long: the initial
4 octets containing the IP-address in network-byte order and 4 octets contain the IP-address in network-byte order and
the last 2 containing the UDP port in network-byte order. the last 2 contain the UDP port in network-byte order.
Consult 'Transport Mappings for the Simple Network Consult 'Transport Mappings for the Simple Network
Management Protocol' (STD 62, RFC 3417 [RFC3417]) for Management Protocol' (STD 62, RFC 3417 [RFC3417]) for
further information on snmpUDPDomain." further information on snmpUDPDomain."
::= { entLogicalEntry 5 } ::= { entLogicalEntry 5 }
entLogicalTDomain OBJECT-TYPE entLogicalTDomain OBJECT-TYPE
SYNTAX TDomain SYNTAX TDomain
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 35, line 18 skipping to change at page 32, line 20
::= { entLogicalEntry 8 } ::= { entLogicalEntry 8 }
entLPMappingTable OBJECT-TYPE entLPMappingTable OBJECT-TYPE
SYNTAX SEQUENCE OF EntLPMappingEntry SYNTAX SEQUENCE OF EntLPMappingEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains zero or more rows of logical entity to "This table contains zero or more rows of logical entity to
physical equipment associations. For each logical entity physical equipment associations. For each logical entity
known by this agent, there are zero or more mappings to the known by this agent, there are zero or more mappings to the
physical resources which are used to realize that logical physical resources, which are used to realize that logical
entity. entity.
An agent should limit the number and nature of entries in An agent should limit the number and nature of entries in
this table such that only meaningful and non-redundant this table such that only meaningful and non-redundant
information is returned. For example, in a system which information is returned. For example, in a system that
contains a single power supply, mappings between logical contains a single power supply, mappings between logical
entities and the power supply are not useful and should not entities and the power supply are not useful and should not
be included. be included.
Also, only the most appropriate physical component which is Also, only the most appropriate physical component, which is
closest to the root of a particular containment tree should closest to the root of a particular containment tree, should
be identified in an entLPMapping entry. be identified in an entLPMapping entry.
For example, suppose a bridge is realized on a particular For example, suppose a bridge is realized on a particular
module, and all ports on that module are ports on this module, and all ports on that module are ports on this
bridge. A mapping between the bridge and the module would be bridge. A mapping between the bridge and the module would
useful, but additional mappings between the bridge and each be useful, but additional mappings between the bridge and
of the ports on that module would be redundant (since the each of the ports on that module would be redundant (because
entPhysicalContainedIn hierarchy can provide the same the entPhysicalContainedIn hierarchy can provide the same
information). If, on the other hand, more than one bridge information). On the other hand, if more than one bridge
was utilizing ports on this module, then mappings between were utilizing ports on this module, then mappings between
each bridge and the ports it used would be appropriate. each bridge and the ports it used would be appropriate.
Also, in the case of a single backplane repeater, a mapping Also, in the case of a single backplane repeater, a mapping
for the backplane to the single repeater entity is not for the backplane to the single repeater entity is not
necessary." necessary."
::= { entityMapping 1 } ::= { entityMapping 1 }
entLPMappingEntry OBJECT-TYPE entLPMappingEntry OBJECT-TYPE
SYNTAX EntLPMappingEntry SYNTAX EntLPMappingEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 37, line 13 skipping to change at page 34, line 10
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about a particular physical equipment, logical "Information about a particular physical equipment, logical
entity to external identifier binding. Each logical entity to external identifier binding. Each logical
entity/physical component pair may be associated with one entity/physical component pair may be associated with one
alias mapping. The logical entity index may also be used as alias mapping. The logical entity index may also be used as
a 'wildcard' (refer to the entAliasLogicalIndexOrZero object a 'wildcard' (refer to the entAliasLogicalIndexOrZero object
DESCRIPTION clause for details.) DESCRIPTION clause for details.)
Note that only entPhysicalIndex values which represent Note that only entPhysicalIndex values that represent
physical ports (i.e. associated entPhysicalClass value is physical ports (i.e., associated entPhysicalClass value is
'port(10)') are permitted to exist in this table." 'port(10)') are permitted to exist in this table."
INDEX { entPhysicalIndex, entAliasLogicalIndexOrZero } INDEX { entPhysicalIndex, entAliasLogicalIndexOrZero }
::= { entAliasMappingTable 1 } ::= { entAliasMappingTable 1 }
EntAliasMappingEntry ::= SEQUENCE { EntAliasMappingEntry ::= SEQUENCE {
entAliasLogicalIndexOrZero Integer32, entAliasLogicalIndexOrZero Integer32,
entAliasMappingIdentifier RowPointer entAliasMappingIdentifier RowPointer
} }
entAliasLogicalIndexOrZero OBJECT-TYPE entAliasLogicalIndexOrZero OBJECT-TYPE
SYNTAX Integer32 (0..2147483647) SYNTAX Integer32 (0..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object identifies the logical entity "The value of this object identifies the logical entity
which defines the naming scope for the associated instance that defines the naming scope for the associated instance
of the 'entAliasMappingIdentifier' object. of the 'entAliasMappingIdentifier' object.
If this object has a non-zero value, then it identifies the If this object has a non-zero value, then it identifies the
logical entity named by the same value of entLogicalIndex. logical entity named by the same value of entLogicalIndex.
If this object has a value of zero, then the mapping between If this object has a value of zero, then the mapping between
the physical component and the alias identifier for this the physical component and the alias identifier for this
entAliasMapping entry is associated with all unspecified entAliasMapping entry is associated with all unspecified
logical entities. That is, a value of zero (the default logical entities. That is, a value of zero (the default
mapping) identifies any logical entity which does not have mapping) identifies any logical entity that does not have
an explicit entry in this table for a particular an explicit entry in this table for a particular
entPhysicalIndex/entAliasMappingIdentifier pair. entPhysicalIndex/entAliasMappingIdentifier pair.
For example, to indicate that a particular interface (e.g., For example, to indicate that a particular interface (e.g.,
physical component 33) is identified by the same value of physical component 33) is identified by the same value of
ifIndex for all logical entities, the following instance ifIndex for all logical entities, the following instance
might exist: might exist:
entAliasMappingIdentifier.33.0 = ifIndex.5 entAliasMappingIdentifier.33.0 = ifIndex.5
In the event an entPhysicalEntry is associated differently In the event an entPhysicalEntry is associated differently
for some logical entities, additional entAliasMapping for some logical entities, additional entAliasMapping
entries may exist, e.g.: entries may exist, e.g.:
entAliasMappingIdentifier.33.0 = ifIndex.6 entAliasMappingIdentifier.33.0 = ifIndex.6
entAliasMappingIdentifier.33.4 = ifIndex.1 entAliasMappingIdentifier.33.4 = ifIndex.1
entAliasMappingIdentifier.33.5 = ifIndex.1 entAliasMappingIdentifier.33.5 = ifIndex.1
entAliasMappingIdentifier.33.10 = ifIndex.12 entAliasMappingIdentifier.33.10 = ifIndex.12
Note that entries with non-zero entAliasLogicalIndexOrZero Note that entries with non-zero entAliasLogicalIndexOrZero
index values have precedence over any zero-indexed entry. In index values have precedence over zero-indexed entries. In
this example, all logical entities except 4, 5, and 10, this example, all logical entities except 4, 5, and 10,
associate physical entity 33 with ifIndex.6." associate physical entity 33 with ifIndex.6."
::= { entAliasMappingEntry 1 } ::= { entAliasMappingEntry 1 }
entAliasMappingIdentifier OBJECT-TYPE entAliasMappingIdentifier OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object identifies a particular conceptual "The value of this object identifies a particular conceptual
row associated with the indicated entPhysicalIndex and row associated with the indicated entPhysicalIndex and
entLogicalIndex pair. entLogicalIndex pair.
Since only physical ports are modeled in this table, only Because only physical ports are modeled in this table, only
entries which represent interfaces or ports are allowed. If entries that represent interfaces or ports are allowed. If
an ifEntry exists on behalf of a particular physical port, an ifEntry exists on behalf of a particular physical port,
then this object should identify the associated 'ifEntry'. then this object should identify the associated 'ifEntry'.
For repeater ports, the appropriate row in the For repeater ports, the appropriate row in the
'rptrPortGroupTable' should be identified instead. 'rptrPortGroupTable' should be identified instead.
For example, suppose a physical port was represented by For example, suppose a physical port was represented by
entPhysicalEntry.3, entLogicalEntry.15 existed for a entPhysicalEntry.3, entLogicalEntry.15 existed for a
repeater, and entLogicalEntry.22 existed for a bridge. Then repeater, and entLogicalEntry.22 existed for a bridge. Then
there might be two related instances of there might be two related instances of
entAliasMappingIdentifier: entAliasMappingIdentifier:
skipping to change at page 39, line 13 skipping to change at page 36, line 5
appropriate ifEntries associated with each 'dot1dBasePort', appropriate ifEntries associated with each 'dot1dBasePort',
and are thus not represented in this table." and are thus not represented in this table."
::= { entAliasMappingEntry 2 } ::= { entAliasMappingEntry 2 }
-- physical mapping table -- physical mapping table
entPhysicalContainsTable OBJECT-TYPE entPhysicalContainsTable OBJECT-TYPE
SYNTAX SEQUENCE OF EntPhysicalContainsEntry SYNTAX SEQUENCE OF EntPhysicalContainsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table which exposes the container/'containee' "A table that exposes the container/'containee'
relationships between physical entities. This table provides relationships between physical entities. This table
all the information found by constructing the virtual provides all the information found by constructing the
containment tree for a given entPhysicalTable, but in a more virtual containment tree for a given entPhysicalTable, but
direct format. in a more direct format.
In the event a physical entity is contained by more than one In the event a physical entity is contained by more than one
other physical entity (e.g., double-wide modules), this other physical entity (e.g., double-wide modules), this
table should include these additional mappings, which cannot table should include these additional mappings, which cannot
be represented in the entPhysicalTable virtual containment be represented in the entPhysicalTable virtual containment
tree." tree."
::= { entityMapping 3 } ::= { entityMapping 3 }
entPhysicalContainsEntry OBJECT-TYPE entPhysicalContainsEntry OBJECT-TYPE
SYNTAX EntPhysicalContainsEntry SYNTAX EntPhysicalContainsEntry
skipping to change at page 40, line 44 skipping to change at page 37, line 31
is the suggested default). A 'notification-event' is the is the suggested default). A 'notification-event' is the
transmission of a single trap or inform PDU to a list of transmission of a single trap or inform PDU to a list of
notification destinations. notification destinations.
If additional configuration changes occur within the If additional configuration changes occur within the
throttling period, then notification-events for these throttling period, then notification-events for these
changes should be suppressed by the agent until the current changes should be suppressed by the agent until the current
throttling period expires. At the end of a throttling throttling period expires. At the end of a throttling
period, one notification-event should be generated if any period, one notification-event should be generated if any
configuration changes occurred since the start of the configuration changes occurred since the start of the
throttling period. In such a case, another throttling period throttling period. In such a case, another throttling
is started right away. period is started right away.
An NMS should periodically check the value of An NMS should periodically check the value of
entLastChangeTime to detect any missed entConfigChange entLastChangeTime to detect any missed entConfigChange
notification-events, e.g., due to throttling or transmission notification-events, e.g., due to throttling or transmission
loss." loss."
::= { entityMIBTrapPrefix 1 } ::= { entityMIBTrapPrefix 1 }
-- conformance information -- conformance information
entityConformance OBJECT IDENTIFIER ::= { entityMIB 3 } entityConformance OBJECT IDENTIFIER ::= { entityMIB 3 }
entityCompliances OBJECT IDENTIFIER ::= { entityConformance 1 } entityCompliances OBJECT IDENTIFIER ::= { entityConformance 1 }
entityGroups OBJECT IDENTIFIER ::= { entityConformance 2 } entityGroups OBJECT IDENTIFIER ::= { entityConformance 2 }
-- compliance statements -- compliance statements
entityCompliance MODULE-COMPLIANCE entityCompliance MODULE-COMPLIANCE
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The compliance statement for SNMP entities which implement "The compliance statement for SNMP entities that implement
version 1 of the Entity MIB." version 1 of the Entity MIB."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
entityPhysicalGroup, entityPhysicalGroup,
entityLogicalGroup, entityLogicalGroup,
entityMappingGroup, entityMappingGroup,
entityGeneralGroup, entityGeneralGroup,
entityNotificationsGroup entityNotificationsGroup
} }
::= { entityCompliances 1 } ::= { entityCompliances 1 }
entity2Compliance MODULE-COMPLIANCE entity2Compliance MODULE-COMPLIANCE
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The compliance statement for SNMP entities which implement "The compliance statement for SNMP entities that implement
version 2 of the Entity MIB." version 2 of the Entity MIB."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
entityPhysicalGroup, entityPhysicalGroup,
entityPhysical2Group, entityPhysical2Group,
entityGeneralGroup, entityGeneralGroup,
entityNotificationsGroup entityNotificationsGroup
} }
GROUP entityLogical2Group GROUP entityLogical2Group
DESCRIPTION DESCRIPTION
"Implementation of this group is not mandatory for agents "Implementation of this group is not mandatory for agents
which model all MIB object instances within a single naming that model all MIB object instances within a single naming
scope." scope."
GROUP entityMappingGroup GROUP entityMappingGroup
DESCRIPTION DESCRIPTION
"Implementation of the entPhysicalContainsTable is mandatory "Implementation of the entPhysicalContainsTable is mandatory
for all agents. Implementation of the entLPMappingTable and for all agents. Implementation of the entLPMappingTable and
entAliasMappingTables are not mandatory for agents which entAliasMappingTables are not mandatory for agents that
model all MIB object instances within a single naming scope. model all MIB object instances within a single naming scope.
Note that the entAliasMappingTable may be useful for all Note that the entAliasMappingTable may be useful for all
agents, however implementation of the entityLogicalGroup or agents; however, implementation of the entityLogicalGroup or
entityLogical2Group is required to support this table." entityLogical2Group is required to support this table."
OBJECT entPhysicalSerialNum OBJECT entPhysicalSerialNum
MIN-ACCESS not-accessible MIN-ACCESS not-accessible
DESCRIPTION DESCRIPTION
"Read and write access is not required for agents which "Read and write access is not required for agents that
cannot identify serial number information for physical cannot identify serial number information for physical
entities, and/or cannot provide non-volatile storage for entities, and/or cannot provide non-volatile storage for
NMS-assigned serial numbers. NMS-assigned serial numbers.
Write access is not required for agents which can identify Write access is not required for agents that can identify
serial number information for physical entities, but cannot serial number information for physical entities, but cannot
provide non-volatile storage for NMS-assigned serial provide non-volatile storage for NMS-assigned serial
numbers. numbers.
Write access is not required for physical entities for Write access is not required for physical entities for which
physical entities for which the associated value of the the associated value of the entPhysicalIsFRU object is equal
entPhysicalIsFRU object is equal to 'false(2)'." to 'false(2)'."
OBJECT entPhysicalAlias OBJECT entPhysicalAlias
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is required only if the associated "Write access is required only if the associated
entPhysicalClass value is equal to 'chassis(3)'." entPhysicalClass value is equal to 'chassis(3)'."
OBJECT entPhysicalAssetID OBJECT entPhysicalAssetID
MIN-ACCESS not-accessible MIN-ACCESS not-accessible
DESCRIPTION DESCRIPTION
"Read and write access is not required for agents which "Read and write access is not required for agents that
cannot provide non-volatile storage for NMS-assigned asset cannot provide non-volatile storage for NMS-assigned asset
identifiers. identifiers.
Write access is not required for physical entities for which Write access is not required for physical entities for which
the associated value of entPhysicalIsFRU is equal to the associated value of the entPhysicalIsFRU object is equal
'false(2)'." to 'false(2)'."
OBJECT entPhysicalClass OBJECT entPhysicalClass
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
unknown(2), unknown(2),
chassis(3), chassis(3),
backplane(4), backplane(4),
container(5), container(5),
powerSupply(6), powerSupply(6),
fan(7), fan(7),
sensor(8), sensor(8),
skipping to change at page 43, line 27 skipping to change at page 40, line 8
} }
DESCRIPTION DESCRIPTION
"Implementation of the 'cpu(12)' enumeration is not "Implementation of the 'cpu(12)' enumeration is not
required." required."
::= { entityCompliances 2 } ::= { entityCompliances 2 }
entity3Compliance MODULE-COMPLIANCE entity3Compliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SNMP entities which implement "The compliance statement for SNMP entities that implement
version 3 of the Entity MIB." version 3 of the Entity MIB."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
entityPhysicalGroup, entityPhysicalGroup,
entityPhysical2Group, entityPhysical2Group,
entityPhysical3Group, entityPhysical3Group,
entityGeneralGroup, entityGeneralGroup,
entityNotificationsGroup entityNotificationsGroup
} }
GROUP entityLogical2Group GROUP entityLogical2Group
DESCRIPTION DESCRIPTION
"Implementation of this group is not mandatory for agents "Implementation of this group is not mandatory for agents
which model all MIB object instances within a single naming that model all MIB object instances within a single naming
scope." scope."
GROUP entityMappingGroup GROUP entityMappingGroup
DESCRIPTION DESCRIPTION
"Implementation of the entPhysicalContainsTable is mandatory "Implementation of the entPhysicalContainsTable is mandatory
for all agents. Implementation of the entLPMappingTable and for all agents. Implementation of the entLPMappingTable and
entAliasMappingTables are not mandatory for agents which entAliasMappingTables are not mandatory for agents that
model all MIB object instances within a single naming scope. model all MIB object instances within a single naming scope.
Note that the entAliasMappingTable may be useful for all Note that the entAliasMappingTable may be useful for all
agents, however implementation of the entityLogicalGroup or agents; however, implementation of the entityLogicalGroup or
entityLogical2Group is required to support this table." entityLogical2Group is required to support this table."
OBJECT entPhysicalSerialNum OBJECT entPhysicalSerialNum
MIN-ACCESS not-accessible MIN-ACCESS not-accessible
DESCRIPTION DESCRIPTION
"Read and write access is not required for agents which "Read and write access is not required for agents that
cannot identify serial number information for physical cannot identify serial number information for physical
entities, and/or cannot provide non-volatile storage for entities, and/or cannot provide non-volatile storage for
NMS-assigned serial numbers. NMS-assigned serial numbers.
Write access is not required for agents which can identify Write access is not required for agents that can identify
serial number information for physical entities, but cannot serial number information for physical entities, but cannot
provide non-volatile storage for NMS-assigned serial provide non-volatile storage for NMS-assigned serial
numbers. numbers.
Write access is not required for physical entities for Write access is not required for physical entities for
physical entities for which the associated value of the which the associated value of the entPhysicalIsFRU object
entPhysicalIsFRU object is equal to 'false(2)'." is equal to 'false(2)'."
OBJECT entPhysicalAlias OBJECT entPhysicalAlias
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is required only if the associated "Write access is required only if the associated
entPhysicalClass value is equal to 'chassis(3)'." entPhysicalClass value is equal to 'chassis(3)'."
OBJECT entPhysicalAssetID OBJECT entPhysicalAssetID
MIN-ACCESS not-accessible MIN-ACCESS not-accessible
DESCRIPTION DESCRIPTION
"Read and write access is not required for agents which "Read and write access is not required for agents that
cannot provide non-volatile storage for NMS-assigned asset cannot provide non-volatile storage for NMS-assigned asset
identifiers. identifiers.
Write access is not required for physical entities for which Write access is not required for physical entities for which
the associated value of entPhysicalIsFRU is equal to the associated value of entPhysicalIsFRU is equal to
'false(2)'." 'false(2)'."
::= { entityCompliances 3 } ::= { entityCompliances 3 }
-- MIB groupings -- MIB groupings
entityPhysicalGroup OBJECT-GROUP entityPhysicalGroup OBJECT-GROUP
OBJECTS { OBJECTS {
entPhysicalDescr, entPhysicalDescr,
entPhysicalVendorType, entPhysicalVendorType,
entPhysicalContainedIn, entPhysicalContainedIn,
entPhysicalClass, entPhysicalClass,
entPhysicalParentRelPos, entPhysicalParentRelPos,
entPhysicalName entPhysicalName
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent "The collection of objects used to represent physical
physical system components, for which a single agent system components, for which a single agent provides
provides management information." management information."
::= { entityGroups 1 } ::= { entityGroups 1 }
entityLogicalGroup OBJECT-GROUP entityLogicalGroup OBJECT-GROUP
OBJECTS { OBJECTS {
entLogicalDescr, entLogicalDescr,
entLogicalType, entLogicalType,
entLogicalCommunity, entLogicalCommunity,
entLogicalTAddress, entLogicalTAddress,
entLogicalTDomain entLogicalTDomain
} }
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent the "The collection of objects used to represent the list of
list of logical entities for which a single agent provides logical entities, for which a single agent provides
management information." management information."
::= { entityGroups 2 } ::= { entityGroups 2 }
entityMappingGroup OBJECT-GROUP entityMappingGroup OBJECT-GROUP
OBJECTS { OBJECTS {
entLPPhysicalIndex, entLPPhysicalIndex,
entAliasMappingIdentifier, entAliasMappingIdentifier,
entPhysicalChildIndex entPhysicalChildIndex
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent the "The collection of objects used to represent the
associations between multiple logical entities, physical associations between multiple logical entities, physical
components, interfaces, and port identifiers for which a components, interfaces, and port identifiers, for which a
single agent provides management information." single agent provides management information."
::= { entityGroups 3 } ::= { entityGroups 3 }
entityGeneralGroup OBJECT-GROUP entityGeneralGroup OBJECT-GROUP
OBJECTS { OBJECTS {
entLastChangeTime entLastChangeTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent "The collection of objects used to represent general entity
general entity information for which a single agent provides information, for which a single agent provides management
management information." information."
::= { entityGroups 4 } ::= { entityGroups 4 }
entityNotificationsGroup NOTIFICATION-GROUP entityNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS { entConfigChange } NOTIFICATIONS { entConfigChange }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of notifications used to indicate Entity MIB "The collection of notifications used to indicate Entity MIB
data consistency and general status information." data consistency and general status information."
::= { entityGroups 5 } ::= { entityGroups 5 }
skipping to change at page 46, line 35 skipping to change at page 43, line 5
entPhysicalSoftwareRev, entPhysicalSoftwareRev,
entPhysicalSerialNum, entPhysicalSerialNum,
entPhysicalMfgName, entPhysicalMfgName,
entPhysicalModelName, entPhysicalModelName,
entPhysicalAlias, entPhysicalAlias,
entPhysicalAssetID, entPhysicalAssetID,
entPhysicalIsFRU entPhysicalIsFRU
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent "The collection of objects used to represent physical
physical system components, for which a single agent system components, for which a single agent provides
provides management information. This group augments the management information. This group augments the objects
objects contained in the entityPhysicalGroup." contained in the entityPhysicalGroup."
::= { entityGroups 6 } ::= { entityGroups 6 }
entityLogical2Group OBJECT-GROUP entityLogical2Group OBJECT-GROUP
OBJECTS { OBJECTS {
entLogicalDescr, entLogicalDescr,
entLogicalType, entLogicalType,
entLogicalTAddress, entLogicalTAddress,
entLogicalTDomain, entLogicalTDomain,
entLogicalContextEngineID, entLogicalContextEngineID,
entLogicalContextName entLogicalContextName
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent the "The collection of objects used to represent the
list of logical entities for which a single SNMP entity list of logical entities, for which a single SNMP entity
provides management information." provides management information."
::= { entityGroups 7 } ::= { entityGroups 7 }
entityPhysical3Group OBJECT-GROUP entityPhysical3Group OBJECT-GROUP
OBJECTS { OBJECTS {
entPhysicalMfgDate, entPhysicalMfgDate,
entPhysicalUris entPhysicalUris
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent "The collection of objects used to represent physical
physical system components, for which a single agent system components, for which a single agent provides
provides management information. This group augments the management information. This group augments the objects
objects contained in the entityPhysicalGroup." contained in the entityPhysicalGroup."
::= { entityGroups 8 } ::= { entityGroups 8 }
END END
4. Usage Examples 4. Usage Examples
The following sections iterate the instance values for two example The following sections iterate the instance values for two example
networking devices. These examples are kept simple to make them networking devices. These examples are kept simple to make them more
more understandable. Auxiliary components, such as fans, sensors, understandable. Auxiliary components such as fans, sensors, empty
empty slots, and sub-modules are not shown, but might be modeled in slots, and sub-modules are not shown, but might be modeled in real
real implementations. implementations.
4.1. Router/Bridge 4.1. Router/Bridge
A router containing two slots. Each slot contains a 3 port The first example is a router containing two slots. Each slot
router/bridge module. Each port is represented in the ifTable. contains a 3 port router/bridge module. Each port is represented in
There are two logical instances of OSPF running and two logical the ifTable. There are two logical instances of OSPF running and two
bridges: logical bridges:
Physical entities -- entPhysicalTable: Physical entities -- entPhysicalTable:
1 Field-replaceable physical chassis: 1 Field-replaceable physical chassis:
entPhysicalDescr.1 == 'Acme Chassis Model 100' entPhysicalDescr.1 == 'Acme Chassis Model 100'
entPhysicalVendorType.1 == acmeProducts.chassisTypes.1 entPhysicalVendorType.1 == acmeProducts.chassisTypes.1
entPhysicalContainedIn.1 == 0 entPhysicalContainedIn.1 == 0
entPhysicalClass.1 == chassis(3) entPhysicalClass.1 == chassis(3)
entPhysicalParentRelPos.1 == 0 entPhysicalParentRelPos.1 == 0
entPhysicalName.1 == '100-A' entPhysicalName.1 == '100-A'
entPhysicalHardwareRev.1 == 'A(1.00.02)' entPhysicalHardwareRev.1 == 'A(1.00.02)'
skipping to change at page 52, line 42 skipping to change at page 48, line 32
entPhysicalAssetID.11 == '' entPhysicalAssetID.11 == ''
entPhysicalIsFRU.11 == false(2) entPhysicalIsFRU.11 == false(2)
entPhysicalMfgDate.11 == '2002-8-16,15:35:15.0,-4:0' entPhysicalMfgDate.11 == '2002-8-16,15:35:15.0,-4:0'
entPhysicalUris.11 == 'URN:CLEI:CNMES23ARA' entPhysicalUris.11 == 'URN:CLEI:CNMES23ARA'
Logical entities -- entLogicalTable; no SNMPv3 support Logical entities -- entLogicalTable; no SNMPv3 support
2 OSPF instances: 2 OSPF instances:
entLogicalDescr.1 == 'Acme OSPF v1.1' entLogicalDescr.1 == 'Acme OSPF v1.1'
entLogicalType.1 == ospf entLogicalType.1 == ospf
entLogicalCommunity.1 == 'public-ospf1' entLogicalCommunity.1 == 'public-ospf1'
entLogicalTAddress.1 == 124.125.126.127:161 entLogicalTAddress.1 == 192.0.2.1:161
entLogicalTDomain.1 == snmpUDPDomain entLogicalTDomain.1 == snmpUDPDomain
entLogicalContextEngineID.1 == '' entLogicalContextEngineID.1 == ''
entLogicalContextName.1 == '' entLogicalContextName.1 == ''
entLogicalDescr.2 == 'Acme OSPF v1.1' entLogicalDescr.2 == 'Acme OSPF v1.1'
entLogicalType.2 == ospf entLogicalType.2 == ospf
entLogicalCommunity.2 == 'public-ospf2' entLogicalCommunity.2 == 'public-ospf2'
entLogicalTAddress.2 == 124.125.126.127:161 entLogicalTAddress.2 == 192.0.2.1:161
entLogicalTDomain.2 == snmpUDPDomain entLogicalTDomain.2 == snmpUDPDomain
entLogicalContextEngineID.2 == '' entLogicalContextEngineID.2 == ''
entLogicalContextName.2 == '' entLogicalContextName.2 == ''
2 logical bridges: 2 logical bridges:
entLogicalDescr.3 == 'Acme Bridge v2.1.1' entLogicalDescr.3 == 'Acme Bridge v2.1.1'
entLogicalType.3 == dot1dBridge entLogicalType.3 == dot1dBridge
entLogicalCommunity.3 == 'public-bridge1' entLogicalCommunity.3 == 'public-bridge1'
entLogicalTAddress.3 == 124.125.126.127:161 entLogicalTAddress.3 == 192.0.2.1:161
entLogicalTDomain.3 == snmpUDPDomain entLogicalTDomain.3 == snmpUDPDomain
entLogicalContextEngineID.3 == '' entLogicalContextEngineID.3 == ''
entLogicalContextName.3 == '' entLogicalContextName.3 == ''
entLogicalDescr.4 == 'Acme Bridge v2.1.1' entLogicalDescr.4 == 'Acme Bridge v2.1.1'
entLogicalType.4 == dot1dBridge entLogicalType.4 == dot1dBridge
entLogicalCommunity.4 == 'public-bridge2' entLogicalCommunity.4 == 'public-bridge2'
entLogicalTAddress.4 == 124.125.126.127:161 entLogicalTAddress.4 == 192.0.2.1:161
entLogicalTDomain.4 == snmpUDPDomain entLogicalTDomain.4 == snmpUDPDomain
entLogicalContextEngineID.4 == '' entLogicalContextEngineID.4 == ''
entLogicalContextName.4 == '' entLogicalContextName.4 == ''
Logical to Physical Mappings: Logical to Physical Mappings:
1st OSPF instance: uses module 1-port 1 1st OSPF instance: uses module 1-port 1
entLPPhysicalIndex.1.5 == 5 entLPPhysicalIndex.1.5 == 5
2nd OSPF instance: uses module 2-port 1 2nd OSPF instance: uses module 2-port 1
entLPPhysicalIndex.2.9 == 9 entLPPhysicalIndex.2.9 == 9
1st bridge group: uses module 1, all ports 1st bridge group: uses module 1, all ports
[ed. -- Note that these mappings are included in the table since [ed. -- Note that these mappings are included in the table because
another logical entity (1st OSPF) utilizes one of the another logical entity (1st OSPF) utilizes one of the
ports. If this were not the case, then a single mapping ports. If this were not the case, then a single mapping
to the module (e.g., entLPPhysicalIndex.3.4) would be to the module (e.g., entLPPhysicalIndex.3.4) would be
present instead. ] present instead. ]
entLPPhysicalIndex.3.5 == 5 entLPPhysicalIndex.3.5 == 5
entLPPhysicalIndex.3.6 == 6 entLPPhysicalIndex.3.6 == 6
entLPPhysicalIndex.3.7 == 7 entLPPhysicalIndex.3.7 == 7
2nd bridge group: uses module 2, all ports 2nd bridge group: uses module 2, all ports
entLPPhysicalIndex.4.9 == 9 entLPPhysicalIndex.4.9 == 9
skipping to change at page 54, line 14 skipping to change at page 49, line 46
Physical to Logical to MIB Alias Mappings -- entAliasMappingTable: Physical to Logical to MIB Alias Mappings -- entAliasMappingTable:
Example 1: ifIndex values are global to all logical entities Example 1: ifIndex values are global to all logical entities
entAliasMappingIdentifier.5.0 == ifIndex.1 entAliasMappingIdentifier.5.0 == ifIndex.1
entAliasMappingIdentifier.6.0 == ifIndex.2 entAliasMappingIdentifier.6.0 == ifIndex.2
entAliasMappingIdentifier.7.0 == ifIndex.3 entAliasMappingIdentifier.7.0 == ifIndex.3
entAliasMappingIdentifier.9.0 == ifIndex.4 entAliasMappingIdentifier.9.0 == ifIndex.4
entAliasMappingIdentifier.10.0 == ifIndex.5 entAliasMappingIdentifier.10.0 == ifIndex.5
entAliasMappingIdentifier.11.0 == ifIndex.6 entAliasMappingIdentifier.11.0 == ifIndex.6
Example 2: ifIndex values are not shared by all logical entities Example 2: ifIndex values are not shared by all logical entities;
(Bridge-1 uses ifIndex values 101 - 103 and Bridge-2 uses
ifIndex values 204-206.)
entAliasMappingIdentifier.5.0 == ifIndex.1 entAliasMappingIdentifier.5.0 == ifIndex.1
entAliasMappingIdentifier.5.3 == ifIndex.101 entAliasMappingIdentifier.5.3 == ifIndex.101
entAliasMappingIdentifier.6.0 == ifIndex.2 entAliasMappingIdentifier.6.0 == ifIndex.2
entAliasMappingIdentifier.6.3 == ifIndex.102 entAliasMappingIdentifier.6.3 == ifIndex.102
entAliasMappingIdentifier.7.0 == ifIndex.3 entAliasMappingIdentifier.7.0 == ifIndex.3
entAliasMappingIdentifier.7.3 == ifIndex.103 entAliasMappingIdentifier.7.3 == ifIndex.103
entAliasMappingIdentifier.9.0 == ifIndex.4 entAliasMappingIdentifier.9.0 == ifIndex.4
entAliasMappingIdentifier.9.3 == ifIndex.204 entAliasMappingIdentifier.9.4 == ifIndex.204
entAliasMappingIdentifier.10.0 == ifIndex.5 entAliasMappingIdentifier.10.0 == ifIndex.5
entAliasMappingIdentifier.10.3 == ifIndex.205 entAliasMappingIdentifier.10.4 == ifIndex.205
entAliasMappingIdentifier.11.0 == ifIndex.6 entAliasMappingIdentifier.11.0 == ifIndex.6
entAliasMappingIdentifier.11.3 == ifIndex.206 entAliasMappingIdentifier.11.4 == ifIndex.206
Physical Containment Tree -- entPhysicalContainsTable Physical Containment Tree -- entPhysicalContainsTable
chassis has two containers: chassis has two containers:
entPhysicalChildIndex.1.2 == 2 entPhysicalChildIndex.1.2 == 2
entPhysicalChildIndex.1.3 == 3 entPhysicalChildIndex.1.3 == 3
container 1 has a module: container 1 has a module:
entPhysicalChildIndex.2.4 == 4 entPhysicalChildIndex.2.4 == 4
container 2 has a module: container 2 has a module:
entPhysicalChildIndex.3.8 == 8 entPhysicalChildIndex.3.8 == 8
module 1 has 3 ports: module 1 has 3 ports:
entPhysicalChildIndex.4.5 == 5 entPhysicalChildIndex.4.5 == 5
entPhysicalChildIndex.4.6 == 6 entPhysicalChildIndex.4.6 == 6
entPhysicalChildIndex.4.7 == 7 entPhysicalChildIndex.4.7 == 7
module 2 has 3 ports: module 2 has 3 ports:
entPhysicalChildIndex.8.9 == 9 entPhysicalChildIndex.8.9 == 9
entPhysicalChildIndex.8.10 == 10 entPhysicalChildIndex.8.10 == 10
entPhysicalChildIndex.1.11 == 11 entPhysicalChildIndex.8.11 == 11
4.2. Repeaters 4.2. Repeaters
A 3-slot Hub with 2 backplane ethernet segments. Slot three is The second example is a 3-slot Hub with 2 backplane ethernet
empty, and the remaining slots contain ethernet repeater modules. segments. Slot three is empty, and the remaining slots contain
ethernet repeater modules.
Note that this example assumes an older Repeater MIB Note that this example assumes an older Repeater MIB implementation,
implementation, (RFC 1516 [RFC1516]) rather than the new Repeater (RFC 1516 [RFC1516]) rather than the new Repeater MIB (RFC 2108
MIB (RFC 2108 [RFC2108]). The new version contains an object [RFC2108]). The new version contains an object called
called 'rptrPortRptrId', which should be used to identify repeater 'rptrPortRptrId', which should be used to identify repeater port
port groupings, rather than with community strings or contexts. groupings, rather than using community strings or contexts.
Physical entities -- entPhysicalTable: Physical entities -- entPhysicalTable:
1 Field-replaceable physical chassis: 1 Field-replaceable physical chassis:
entPhysicalDescr.1 == 'Acme Chassis Model 110' entPhysicalDescr.1 == 'Acme Chassis Model 110'
entPhysicalVendorType.1 == acmeProducts.chassisTypes.2 entPhysicalVendorType.1 == acmeProducts.chassisTypes.2
entPhysicalContainedIn.1 == 0 entPhysicalContainedIn.1 == 0
entPhysicalClass.1 == chassis(3) entPhysicalClass.1 == chassis(3)
entPhysicalParentRelPos.1 == 0 entPhysicalParentRelPos.1 == 0
entPhysicalName.1 == '110-B' entPhysicalName.1 == '110-B'
entPhysicalHardwareRev.1 == 'A(1.02.00)' entPhysicalHardwareRev.1 == 'A(1.02.00)'
skipping to change at page 60, line 24 skipping to change at page 55, line 41
entPhysicalModelName.14 == '' entPhysicalModelName.14 == ''
entPhysicalAlias.14 == '' entPhysicalAlias.14 == ''
entPhysicalAssetID.14 == '' entPhysicalAssetID.14 == ''
entPhysicalIsFRU.14 == false(2) entPhysicalIsFRU.14 == false(2)
Logical entities -- entLogicalTable; with SNMPv3 support Logical entities -- entLogicalTable; with SNMPv3 support
Repeater 1--comprised of any ports attached to backplane 1 Repeater 1--comprised of any ports attached to backplane 1
entLogicalDescr.1 == 'Acme repeater v3.1' entLogicalDescr.1 == 'Acme repeater v3.1'
entLogicalType.1 == snmpDot3RptrMgt entLogicalType.1 == snmpDot3RptrMgt
entLogicalCommunity.1 'public-repeater1' entLogicalCommunity.1 'public-repeater1'
entLogicalTAddress.1 == 124.125.126.127:161 entLogicalTAddress.1 == 192.0.2.1:161
entLogicalTDomain.1 == snmpUDPDomain entLogicalTDomain.1 == snmpUDPDomain
entLogicalContextEngineID.1 == '80000777017c7d7e7f'H entLogicalContextEngineID.1 == '80000777017c7d7e7f'H
entLogicalContextName.1 == 'repeater1' entLogicalContextName.1 == 'repeater1'
Repeater 2--comprised of any ports attached to backplane 2: Repeater 2--comprised of any ports attached to backplane 2:
entLogicalDescr.2 == 'Acme repeater v3.1' entLogicalDescr.2 == 'Acme repeater v3.1'
entLogicalType.2 == snmpDot3RptrMgt entLogicalType.2 == snmpDot3RptrMgt
entLogicalCommunity.2 == 'public-repeater2' entLogicalCommunity.2 == 'public-repeater2'
entLogicalTAddress.2 == 124.125.126.127:161 entLogicalTAddress.2 == 192.0.2.1:161
entLogicalTDomain.2 == snmpUDPDomain entLogicalTDomain.2 == snmpUDPDomain
entLogicalContextEngineID.2 == '80000777017c7d7e7f'H entLogicalContextEngineID.2 == '80000777017c7d7e7f'H
entLogicalContextName.2 == 'repeater2' entLogicalContextName.2 == 'repeater2'
Logical to Physical Mappings -- entLPMappingTable: Logical to Physical Mappings -- entLPMappingTable:
repeater1 uses backplane 1, slot 1-ports 1 & 2, slot 2-port 1 repeater1 uses backplane 1, slot 1-ports 1 & 2, slot 2-port 1
[ed. -- Note that a mapping to the module is not included, [ed. -- Note that a mapping to the module is not included,
since in this example represents a port-switchable hub. because this example represents a port-switchable hub.
Even though all ports on the module could belong to the Even though all ports on the module could belong to the
same repeater as a matter of configuration, the LP port same repeater as a matter of configuration, the LP port
mappings should not be replaced dynamically with a single mappings should not be replaced dynamically with a single
mapping for the module (e.g., entLPPhysicalIndex.1.7). mapping for the module (e.g., entLPPhysicalIndex.1.7).
If all ports on the module shared a single backplane connection, If all ports on the module shared a single backplane connection,
then a single mapping for the module would be more appropriate. ] then a single mapping for the module would be more appropriate. ]
entLPPhysicalIndex.1.2 == 2 entLPPhysicalIndex.1.2 == 2
entLPPhysicalIndex.1.8 == 8 entLPPhysicalIndex.1.8 == 8
entLPPhysicalIndex.1.9 == 9 entLPPhysicalIndex.1.9 == 9
entLPPhysicalIndex.1.13 == 13 entLPPhysicalIndex.1.13 == 13
repeater2 uses backplane 2, slot 1-ports 3 & 4, slot 2-port 2 repeater2 uses backplane 2, slot 1-ports 3 & 4, slot 2-port 2
entLPPhysicalIndex.2.3 == 3 entLPPhysicalIndex.2.3 == 3
entLPPhysicalIndex.2.10 == 10 entLPPhysicalIndex.2.10 == 10
entLPPhysicalIndex.2.11 == 11 entLPPhysicalIndex.2.11 == 11
entLPPhysicalIndex.2.14 == 14 entLPPhysicalIndex.2.14 == 14
skipping to change at page 61, line 37 skipping to change at page 57, line 4
entPhysicalChildIndex.1.3 == 3 entPhysicalChildIndex.1.3 == 3
entPhysicalChildIndex.1.4 == 4 entPhysicalChildIndex.1.4 == 4
entPhysicalChildIndex.1.5 == 5 entPhysicalChildIndex.1.5 == 5
entPhysicalChildIndex.1.6 == 6 entPhysicalChildIndex.1.6 == 6
container 1 has a module: container 1 has a module:
entPhysicalChildIndex.4.7 == 7 entPhysicalChildIndex.4.7 == 7
container 2 has a module container 2 has a module
entPhysicalChildIndex.5.12 == 12 entPhysicalChildIndex.5.12 == 12
[ed. - in this example, container 3 is empty.] [ed. -- in this example, container 3 is empty.]
module 1 has 4 ports: module 1 has 4 ports:
entPhysicalChildIndex.7.8 == 8 entPhysicalChildIndex.7.8 == 8
entPhysicalChildIndex.7.9 == 9 entPhysicalChildIndex.7.9 == 9
entPhysicalChildIndex.7.10 == 10 entPhysicalChildIndex.7.10 == 10
entPhysicalChildIndex.7.11 == 11 entPhysicalChildIndex.7.11 == 11
module 2 has 2 ports: module 2 has 2 ports:
entPhysicalChildIndex.12.13 == 13 entPhysicalChildIndex.12.13 == 13
entPhysicalChildIndex.12.14 == 14 entPhysicalChildIndex.12.14 == 14
skipping to change at page 62, line 26 skipping to change at page 57, line 37
entPhysicalDescr entPhysicalDescr
entPhysicalVendorType entPhysicalVendorType
entPhysicalHardwareRev entPhysicalHardwareRev
entPhysicalFirmwareRev entPhysicalFirmwareRev
entPhysicalSoftwareRev entPhysicalSoftwareRev
entPhysicalSerialNum entPhysicalSerialNum
entPhysicalMfgName entPhysicalMfgName
entPhysicalModelName entPhysicalModelName
These objects expose information about the physical entities within These objects expose information about the physical entities
a managed system, which may be used to identify the vendor, model, within a managed system, which may be used to identify the vendor,
and version information of each system component. model, and version information of each system component.
entPhysicalAssetID entPhysicalAssetID
This object can allow asset identifiers for various system This object can allow asset identifiers for various system
components to be exposed, in the event this MIB object is actually components to be exposed, in the event this MIB object is actually
configured by an NMS application. configured by an NMS application.
entLogicalDescr entLogicalDescr
entLogicalType entLogicalType
skipping to change at page 63, line 27 skipping to change at page 58, line 36
sending them over the network via SNMP. Not all versions of SNMP sending them over the network via SNMP. Not all versions of SNMP
provide features for such a secure environment. provide features for such a secure environment.
SNMPv1 by itself is not a secure environment. Even if the network SNMPv1 by itself is not a secure environment. Even if the network
itself is secure (for example by using IPSec), even then, there is itself is secure (for example by using IPSec), even then, there is
no control as to who on the secure network is allowed to access and no control as to who on the secure network is allowed to access and
GET/SET (read/change/create/delete) the objects in this MIB. GET/SET (read/change/create/delete) the objects in this MIB.
It is recommended that the implementers consider the security It is recommended that the implementers consider the security
features as provided by the SNMPv3 framework. Specifically, the features as provided by the SNMPv3 framework. Specifically, the
use of the User-based Security Model RFC 2574 [RFC2574] and the use of the User-based Security Model RFC 3414 [RFC3414] and the
View-based Access Control Model RFC 2575 [RFC2575] is recommended. View-based Access Control Model RFC 3415 [RFC3415] is recommended.
It is then a customer/user responsibility to ensure that the SNMP It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly entity giving access to an instance of this MIB, is properly
configured to give access to the objects only to those principals configured to give access to the objects only to those principals
(users) that have legitimate rights to indeed GET or SET (users) that have legitimate rights to indeed GET or SET
(change/create/delete) them. (change/create/delete) them.
6. IANA Considerations 6. IANA Considerations
The MIB module in this document uses the following IANA-assigned The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
entityMIB { mib-2 47 } entityMIB { mib-2 47 }
Editor's Note (to be removed prior to publication): this draft
makes no additional requests of the IANA.
7. Acknowledgements 7. Acknowledgements
This memo has been produced by the IETF's Entity MIB working group. This memo has been produced by the IETF's Entity MIB working group.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2026] [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
Bradner, S., "The Internet Standards Process -- Revision 3", RFC "Structure of Management Information Version 2
2026, October, 1996.
[RFC2396]
Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource
Identifiers (URI): Generic Syntax", RFC 2396, August 1998.
[RFC2578]
McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M.,
and S. Waldbusser, "Structure of Management Information Version 2
(SMIv2)", STD 58, RFC 2578, April 1999. (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., "Textual Conventions for SMIv2", STD 58, RFC 2579,
and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC April 1999.
2579, April 1999.
[RFC2580] [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., "Conformance Statements for SMIv2", STD 58, RFC 2580,
and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC April 1999.
2580, April 1999.
[RFC3411] [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Architecture for Describing Simple Network Management
Describing Simple Network Management Protocol (SNMP) Management Protocol (SNMP) Management Frameworks", STD 62, RFC
Frameworks", STD 62, RFC 3411, December 2002. 3411, December 2002.
[RFC3417] [RFC3417] Presuhn, R., "Transport Mappings for the Simple Network
R. Presuhn, Ed., "Transport Mappings for the Simple Network Management Protocol (SNMP)", STD 62, RFC 3417, December
Management Protocol (SNMP)", STD 62, RFC 3417, December 2002. 2002.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter,
"Uniform Resource Identifier (URI): Generic Syntax",
STD 66, RFC 3986, January 2005.
8.2. Informative References 8.2. Informative References
[RFC1157] [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin,
Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network "Simple Network Management Protocol", STD 15, RFC 1157,
Management Protocol", STD 15, RFC 1157, May 1990. May 1990.
[RFC1493] [RFC1493] Decker, E., Langille, P., Rijsinghani, A., and K.
Decker, E., Langille, P., Rijsinghani, A., and K. McCloghrie, McCloghrie, "Definitions of Managed Objects for
"Definitions of Managed Objects for Bridges", RFC 1493, July, 1993. Bridges", RFC 1493, July 1993.
[RFC1516] [RFC1516] McMaster, D. and K. McCloghrie, "Definitions of Managed
McMaster, D., and K. McCloghrie, "Definitions of Managed Objects Objects for IEEE 802.3 Repeater Devices", RFC 1516,
for IEEE 802.3 Repeater Devices", RFC 1516, September, 1993. September 1993.
[RFC2037] [RFC2037] McCloghrie, K. and A. Bierman, "Entity MIB using
McCloghrie, K., and A. Bierman, "Entity MIB using SMIv2", RFC 2037, SMIv2", RFC 2037, October 1996.
October 1996.
[RFC2108] [RFC2108] de Graaf, K., Romascanu, D., McMaster, D., and K.
de Graaf, K., Romascanu, D., McMaster, D., and K. McCloghrie, McCloghrie, "Definitions of Managed Objects for IEEE
"Definitions of Managed Objects for IEEE 802.3 Repeater Devices 802.3 Repeater Devices using SMIv2", RFC 2108, February
using SMIv2", RFC 2108, February, 1997. 1997.
[RFC2863] [RFC2737] McCloghrie, K. and A. Bierman, "Entity MIB (Version
McCloghrie, K., and F. Kastenholz, "The Interfaces Group MIB", RFC 2)", RFC 2737, December 1999.
2863, June, 2000.
[RFC2737] [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
McCloghrie, K., and A. Bierman, "Entity MIB (Version 2)", RFC 2737, MIB", RFC 2863, June 2000.
December 1999.
[RFC3406] [RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P.
Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, "Uniform Faltstrom, "Uniform Resource Names (URN) Namespace
Resource Names (URN) Namespace Definition Mechanisms", RFC 3406, Definition Mechanisms", BCP 66, RFC 3406, October 2002.
October 2002.
[RFC3410] [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and "Introduction and Applicability Statements for
Applicability Statements for Internet- Standard Management Internet-Standard Management Framework", RFC 3410,
Framework", RFC 3410, December 2002. December 2002.
[RFCCLEIURN] [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security
Tesink, K., and Robert H. Fox, "A Uniform Resource Name (URN) Model (USM) for version 3 of the Simple Network
Namespace for the CLEI Code", Work in progress, November 7, 2004. Management Protocol (SNMPv3)", STD 62, RFC 3414,
December 2002.
[T1.213] [RFC3415] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
ATIS T1.213-2001, "Coded Identification of Equipment Entities in Access Control Model (VACM) for the Simple Network
the North American Telecommunications System for Information Management Protocol (SNMP)", STD 62, RFC 3415, December
Exchange", 2001, www.ansi.org. 2002.
[T1.213a] [RFCYYYY] Tesink, K. and R. Fox, "A Uniform Resource Name (URN)
ATIS T1.213a, "Supplement to T1.213-2001, Coded Identification of Namespace for the CLEI Code", RFC YYYY, August 2005.
Equipment Entities in the North American Telecommunications System
for Information Exchange, to correct the representation of the [T1.213] ATIS T1.213-2001, "Coded Identification of Equipment
Basic Code in Figure B.1", 2001, www.ansi.org. Entities in the North American Telecommunications
System for Information Exchange", 2001, www.ansi.org.
[T1.213a] ATIS T1.213a, "Supplement to T1.213-2001, Coded
Identification of Equipment Entities in the North
American Telecommunications System for Information
Exchange, to correct the representation of the Basic
Code in Figure B.1", 2001, www.ansi.org.
Authors' Addresses Authors' Addresses
Andy Bierman Andy Bierman
Cisco Systems, Inc.
170 West Tasman Drive EMail: ietf@andybierman.com
San Jose, CA 95134 USA
Phone: +1 408-527-3711
Email: abierman@cisco.com
Keith McCloghrie Keith McCloghrie
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134 USA San Jose, CA 95134 USA
Phone: +1 408-526-5260 Phone: +1 408-526-5260
Email: kzm@cisco.com EMail: kzm@cisco.com
Intellectual Property Statement Full Copyright Statement
Copyright (C) The Internet Society (2005).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed Intellectual Property Rights or other rights that might be claimed to
to pertain to the implementation or use of the technology described pertain to the implementation or use of the technology described in
in this document or the extent to which any license under such this document or the extent to which any license under such rights
rights might or might not be available; nor does it represent that might or might not be available; nor does it represent that it has
it has made any independent effort to identify any such rights. made any independent effort to identify any such rights. Information
Information on the procedures with respect to rights in RFC on the procedures with respect to rights in RFC documents can be
documents can be found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use attempt made to obtain a general license or permission for the use of
of such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository specification can be obtained from the IETF on-line IPR repository at
at http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf- this standard. Please address the information to the IETF at ietf-
ipr@ietf.org. ipr@ietf.org.
Disclaimer of Validity Acknowledgement
This document and the information contained herein are provided on
an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT
THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR
ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2005). This document is
subject to the rights, licenses and restrictions contained in BCP
78, and except as set forth therein, the authors retain all their
rights.
Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 

This html diff was produced by rfcdiff 1.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/