draft-ietf-entmib-v3-03.txt   draft-ietf-entmib-v3-04.txt 
Entity MIB Working Group Andy Bierman Entity MIB Working Group Andy Bierman
Internet Draft Keith McCloghrie Internet Draft Keith McCloghrie
Cisco Systems, Inc. Cisco Systems, Inc.
28 August 2003 22 January 2004
Entity MIB (Version 3) Entity MIB (Version 3)
<draft-ietf-entmib-v3-03.txt> <draft-ietf-entmib-v3-04.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026 [RFC2026]. provisions of Section 10 of RFC2026 [RFC2026].
Internet-Drafts are working documents of the Internet Engineering Task Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups. Note that other groups Force (IETF), its areas, and its working groups. Note that other groups
may also distribute working documents as Internet-Drafts. may also distribute working documents as Internet-Drafts.
skipping to change at page 2, line ? skipping to change at page 2, line ?
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Distribution of this document is unlimited. Please send comments to the Distribution of this document is unlimited. Please send comments to the
Entity MIB Working Group, <entmib@ietf.org>. Entity MIB Working Group, <entmib@ietf.org>.
1. Copyright Notice 1. Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
"Abstract" "Abstract"
This memo defines a portion of the Management Information Base (MIB) for This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community. In use with network management protocols in the Internet community. In
particular, it describes managed objects used for managing multiple particular, it describes managed objects used for managing multiple
logical and physical entities managed by a single SNMP agent. This logical and physical entities managed by a single SNMP agent. This
document specifies version 3 of the Entity MIB, which obsoletes version document specifies version 3 of the Entity MIB, which obsoletes version
2 (RFC 2737). 2 (RFC 2737).
skipping to change at page 2, line ? skipping to change at page 2, line ?
4.12.5 entityNotifications Group .................................. 12 4.12.5 entityNotifications Group .................................. 12
4.13 Multiple Agents .............................................. 12 4.13 Multiple Agents .............................................. 12
4.14 Changes Since RFC 2037 ....................................... 12 4.14 Changes Since RFC 2037 ....................................... 12
4.14.1 Textual Conventions ........................................ 12 4.14.1 Textual Conventions ........................................ 12
4.14.2 New entPhysicalTable Objects ............................... 12 4.14.2 New entPhysicalTable Objects ............................... 12
4.14.3 New entLogicalTable Objects ................................ 13 4.14.3 New entLogicalTable Objects ................................ 13
4.14.4 Bugfixes ................................................... 13 4.14.4 Bugfixes ................................................... 13
4.15 Changes Since RFC 2737 ....................................... 13 4.15 Changes Since RFC 2737 ....................................... 13
4.15.1 Textual Conventions ........................................ 13 4.15.1 Textual Conventions ........................................ 13
4.15.2 Deprecated Objects ......................................... 13 4.15.2 Deprecated Objects ......................................... 13
4.15.3 Bugfixes ................................................... 13 4.15.3 Bugfixes ................................................... 14
5 Definitions ..................................................... 14 5 Definitions ..................................................... 15
6 Usage Examples .................................................. 45 6 Usage Examples .................................................. 46
6.1 Router/Bridge ................................................. 45 6.1 Router/Bridge ................................................. 46
6.2 Repeaters ..................................................... 51
7 Intellectual Property ........................................... 59
8 Acknowledgements ................................................ 59 6.2 Repeaters ..................................................... 52
9 Normative References ............................................ 59 7 Intellectual Property ........................................... 60
10 Informative References ......................................... 60 8 Acknowledgements ................................................ 60
11 Security Considerations ........................................ 62 9 Normative References ............................................ 60
12 Authors' Addresses ............................................. 64 10 Informative References ......................................... 61
13 Full Copyright Statement ....................................... 65 11 Security Considerations ........................................ 63
12 Authors' Addresses ............................................. 65
13 Full Copyright Statement ....................................... 66
3. The SNMP Management Framework 3. 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 of RFC Internet-Standard Management Framework, please refer to section 7 of RFC
3410 [RFC3410]. 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed the Managed objects are accessed via a virtual information store, termed the
Management Information Base or MIB. MIB objects are generally accessed Management Information Base or MIB. MIB objects are generally accessed
through the Simple Network Management Protocol (SNMP). Objects in the through the Simple Network Management Protocol (SNMP). Objects in the
skipping to change at page 11, line 36 skipping to change at page 11, line 36
implementation of this table may be omitted by the agent. Note that implementation of this table may be omitted by the agent. Note that
this table is deprecated in version 3 of the Entity MIB. this table is deprecated in version 3 of the Entity MIB.
The entAliasMappingTable contains mappings between entLogicalIndex, The entAliasMappingTable contains mappings between entLogicalIndex,
entPhysicalIndex pairs and 'alias' object identifier values. This entPhysicalIndex pairs and 'alias' object identifier values. This
allows resources managed with other MIBs (e.g., repeater ports, bridge allows resources managed with other MIBs (e.g., repeater ports, bridge
ports, physical and logical interfaces) to be identified in the physical ports, physical and logical interfaces) to be identified in the physical
entity hierarchy. Note that each alias identifier is only relevant in a entity hierarchy. Note that each alias identifier is only relevant in a
particular naming scope. If an agent represents a single logical particular naming scope. If an agent represents a single logical
entity, or multiple logical entities within a single naming scope, then entity, or multiple logical entities within a single naming scope, then
implementation of this table may be omitted by the agent. implementation of this table may be omitted by the agent. Note that
this table is deprecated in version 3 of the Entity MIB.
The entPhysicalContainsTable contains simple mappings between The entPhysicalContainsTable 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 allows an relationship in the managed system. The indexing of this table allows an
NMS to quickly discover the 'entPhysicalIndex' values for all children NMS to quickly discover the 'entPhysicalIndex' values for all children
of a given physical entity. of a given physical entity.
4.12.4. entityGeneral Group 4.12.4. entityGeneral Group
This group contains general information relating to the other object This group contains general information relating to the other object
skipping to change at page 13, line 43 skipping to change at page 13, line 43
extended to support a new enumeration for central processing units. extended to support a new enumeration for central processing units.
4.15.2. Deprecated Objects 4.15.2. Deprecated Objects
The entLPMappingTable has been deprecated because no implementations The entLPMappingTable has been deprecated because no implementations
have been found which support this table. The entLPPhysicalIndex has have been found which support this table. The entLPPhysicalIndex has
been removed from the entityMappingGroup. This OBJECT-GROUP has been been removed from the entityMappingGroup. This OBJECT-GROUP has been
updated (entityMappingGroupRev1) as well as the Entity MIB MODULE- updated (entityMappingGroupRev1) as well as the Entity MIB MODULE-
CONFORMANCE statement. CONFORMANCE statement.
The entAliasMappingTable has been deprecated because two independent
implementations have not been found which support this table. The
entAliasMappingIdentifier object has been removed from the
entityMappingGroup. This OBJECT-GROUP has been updated
(entityMappingGroupRev1) as well as the Entity MIB MODULE-CONFORMANCE
statement.
4.15.3. Bugfixes 4.15.3. Bugfixes
The syntax was changed from INTEGER to Integer32 for the The syntax was changed from INTEGER to Integer32 for the
entPhysicalParentRelPos, entLogicalIndex, and entAliasLogicalIndexOrZero entPhysicalParentRelPos, entLogicalIndex, and entAliasLogicalIndexOrZero
objects, and from INTEGER to PhysicalIndexOrZero for the objects, and from INTEGER to PhysicalIndexOrZero for the
entPhysicalContainedIn object. entPhysicalContainedIn object.
5. Definitions 5. Definitions
ENTITY-MIB DEFINITIONS ::= BEGIN ENTITY-MIB DEFINITIONS ::= BEGIN
skipping to change at page 14, line 22 skipping to change at page 15, line 22
FROM SNMPv2-SMI FROM SNMPv2-SMI
TDomain, TAddress, TEXTUAL-CONVENTION, TDomain, TAddress, TEXTUAL-CONVENTION,
AutonomousType, RowPointer, TimeStamp, TruthValue AutonomousType, RowPointer, TimeStamp, TruthValue
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 "200308280000Z" LAST-UPDATED "200401210000Z"
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. Cisco Systems Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
skipping to change at page 15, line 4 skipping to change at page 16, line 4
+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 (2003). This Copyright (C) The Internet Society (2003). This
version of this MIB module is part of RFC xxxx; see version of this MIB module is part of RFC xxxx; see
the RFC itself for full legal notices." the RFC itself for full legal notices."
REVISION "200308280000Z" REVISION "200401210000Z"
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
- PhysicalIndexOrZero TC - PhysicalIndexOrZero TC
Changes: Changes:
- entLPMappingTable deprecated - entLPMappingTable deprecated
- entAliasMappingTable deprecated
- entPhysicalContainedIn SYNTAX changed from - entPhysicalContainedIn SYNTAX changed from
INTEGER to PhysicalIndexOrZero INTEGER to PhysicalIndexOrZero
This version published as RFC xxxx (to be This version published as RFC xxxx (to be
assigned by the RFC Editor)." assigned by the RFC Editor)."
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."
skipping to change at page 33, line 33 skipping to change at page 34, line 33
DESCRIPTION DESCRIPTION
"The value of this object identifies the index value of a "The value of this object identifies the index value of a
particular entPhysicalEntry associated with the indicated particular entPhysicalEntry associated with the indicated
entLogicalEntity." entLogicalEntity."
::= { entLPMappingEntry 1 } ::= { entLPMappingEntry 1 }
-- logical entity/component to alias table -- logical entity/component to alias table
entAliasMappingTable OBJECT-TYPE entAliasMappingTable OBJECT-TYPE
SYNTAX SEQUENCE OF EntAliasMappingEntry SYNTAX SEQUENCE OF EntAliasMappingEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS deprecated
DESCRIPTION DESCRIPTION
"This table contains zero or more rows, representing "This table contains zero or more rows, representing
mappings of logical entity and physical component to mappings of logical entity and physical component to
external MIB identifiers. Each physical port in the system external MIB identifiers. Each physical port in the system
may be associated with a mapping to an external identifier, may be associated with a mapping to an external identifier,
which itself is associated with a particular logical which itself is associated with a particular logical
entity's naming scope. A 'wildcard' mechanism is provided entity's naming scope. A 'wildcard' mechanism is provided
to indicate that an identifier is associated with more than to indicate that an identifier is associated with more than
one logical entity." one logical entity."
::= { entityMapping 2 } ::= { entityMapping 2 }
entAliasMappingEntry OBJECT-TYPE entAliasMappingEntry OBJECT-TYPE
SYNTAX EntAliasMappingEntry SYNTAX EntAliasMappingEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS deprecated
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 which represent
physical ports (i.e. associated entPhysicalClass value is physical ports (i.e. associated entPhysicalClass value is
skipping to change at page 34, line 27 skipping to change at page 35, line 27
::= { 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 deprecated
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 which 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
skipping to change at page 35, line 25 skipping to change at page 36, line 25
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 any zero-indexed entry. 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 deprecated
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 Since only physical ports are modeled in this table, only
entries which represent interfaces or ports are allowed. If entries which 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
skipping to change at page 44, line 12 skipping to change at page 45, line 12
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent the "The collection of objects which are 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 }
entityMappingGroupRev1 OBJECT-GROUP entityMappingGroupRev1 OBJECT-GROUP
OBJECTS { OBJECTS {
entAliasMappingIdentifier,
entPhysicalChildIndex entPhysicalChildIndex
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent the "The collection of objects which are 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 8 } ::= { entityGroups 8 }
skipping to change at page 65, line 7 skipping to change at page 66, line 7
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
13. Full Copyright Statement 13. Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it or others, and derivative works that comment on or otherwise explain it or
assist in its implementation may be prepared, copied, published and assist in its implementation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind, distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are included provided that the above copyright notice and this paragraph are included
on all such copies and derivative works. However, this document itself on all such copies and derivative works. However, this document itself
may not be modified in any way, such as by removing the copyright notice may not be modified in any way, such as by removing the copyright notice
or references to the Internet Society or other Internet organizations, or references to the Internet Society or other Internet organizations,
except as needed for the purpose of developing Internet standards in except as needed for the purpose of developing Internet standards in
 End of changes. 

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