draft-ietf-entmib-v3-05.txt   draft-ietf-entmib-v3-06.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.
22 October 2004 07 January 2005
Entity MIB (Version 3) Entity MIB (Version 3)
<draft-ietf-entmib-v3-05.txt> <draft-ietf-entmib-v3-06.txt>
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 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. aware will be disclosed, in accordance with Section 6 of RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet- Drafts documents at any time. It is inappropriate to use Internet- Drafts
as reference material or to cite them other than as "work in as reference material or to cite them other than as "work in
progress". progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/1id-abstracts.html
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
This document may not be modified, and derivative works of it may
not be created, except to publish it as an RFC and to translate it
into languages other than English.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2005). All Rights Reserved.
Abstract Abstract
This memo defines a portion of the Management Information Base This memo defines a portion of the Management Information Base
(MIB) for use with network management protocols in the Internet (MIB) for use with network management protocols in the Internet
community. In particular, it describes managed objects used for community. In particular, it describes managed objects used for
managing multiple logical and physical entities managed by a single managing multiple logical and physical entities managed by a single
SNMP agent. This document specifies version 3 of the Entity MIB, SNMP agent. This document specifies version 3 of the Entity MIB,
which obsoletes version 2 (RFC 2737). which obsoletes version 2 (RFC 2737).
skipping to change at page 2, line ? skipping to change at page 2, line ?
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 ............................ 7
2.6 Relationship to the Interfaces MIB ....................... 7 2.6 Relationship to the Interfaces MIB ....................... 7
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 ............................ 8
2.9 Multiple Instances of the Entity MIB ..................... 8 2.9 Multiple Instances of the Entity MIB ..................... 8
2.10 Re-Configuration of Entities ............................ 9 2.10 Re-Configuration of Entities ............................ 9
2.11 Textual Convention Change ............................... 9 2.11 Textual Convention Change ............................... 9
2.12 MIB Structure ........................................... 9 2.12 MIB Structure ........................................... 9
2.12.1 entityPhysical Group .................................. 10 2.12.1 entityPhysical Group .................................. 10
2.12.2 entityLogical Group ................................... 11 2.12.2 entityLogical Group ................................... 12
2.12.3 entityMapping Group ................................... 12 2.12.3 entityMapping Group ................................... 12
2.12.4 entityGeneral Group ................................... 12 2.12.4 entityGeneral Group ................................... 13
2.12.5 entityNotifications Group ............................. 13 2.12.5 entityNotifications Group ............................. 13
2.13 Multiple Agents ......................................... 13 2.13 Multiple Agents ......................................... 13
2.14 Changes Since RFC 2037 .................................. 13 2.14 Changes Since RFC 2037 .................................. 14
2.14.1 Textual Conventions ................................... 13 2.14.1 Textual Conventions ................................... 14
2.14.2 New entPhysicalTable Objects .......................... 13 2.14.2 New entPhysicalTable Objects .......................... 14
2.14.3 New entLogicalTable Objects ........................... 14 2.14.3 New entLogicalTable Objects ........................... 14
2.14.4 Bugfixes .............................................. 14 2.14.4 Bugfixes .............................................. 15
2.15 Changes Since RFC 2737 .................................. 14 2.15 Changes Since RFC 2737 .................................. 15
2.15.1 Textual Conventions ................................... 14 2.15.1 Textual Conventions ................................... 15
2.15.2 New Objects ........................................... 15 2.15.2 New Objects ........................................... 15
2.15.3 Deprecated Objects .................................... 15 2.15.3 Bugfixes .............................................. 15
2.15.4 Bugfixes .............................................. 15
3 Definitions ................................................ 16 3 Definitions ................................................ 16
4 Usage Examples ............................................. 48 4 Usage Examples ............................................. 48
4.1 Router/Bridge ............................................ 48 4.1 Router/Bridge ............................................ 48
4.2 Repeaters ................................................ 54 4.2 Repeaters ................................................ 55
5 Security Considerations .................................... 62 5 Security Considerations .................................... 62
6 IANA Considerations ........................................ 64 6 IANA Considerations ........................................ 64
7 Acknowledgements ........................................... 64 7 Acknowledgements ........................................... 64
8 References ................................................. 64 8 References ................................................. 64
8.1 Normative References ..................................... 64 8.1 Normative References ..................................... 64
8.2 Informative References ................................... 65 8.2 Informative References ................................... 65
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
skipping to change at page 4, line 40 skipping to change at page 4, line 36
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 [RFC3411]). Implementation experience has shown that 3411 [RFC3411]). Implementation experience has shown that
additional physical component attributes are also desirable. additional 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 that have emerged
since the publication of the second Entity MIB (RFC 2737 since the publication of the second Entity MIB (RFC 2737
[RFC2737]). There is a need for identifying physical entities [RFC2737]). There is a need for identifying physical entities
which are central processing units (CPUs) and a need to provide a which are central processing units (CPUs) and a need to provide a
textual convention which identifies an entPhysicalIndex value or textual convention which identifies an entPhysicalIndex value or
zero, where the value zero has application-specific semantics. zero, where the value zero has application-specific semantics. Two
new objects have been added to the entPhysicalTable to identify the
manufacturing date and provide additional URIs for a particular
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 instances
within the naming scope share the same unique identifier space. within the naming scope share the same unique identifier space.
For SNMPv1, a naming scope is identified by the value of the For SNMPv1, a naming scope is identified by the value of the
skipping to change at page 11, line 28 skipping to change at page 11, line 28
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. object is not instantiated.
- entPhysicalUris - entPhysicalUris
This object provides additional identification information about This object provides additional identification information about
the physical entity. This object may be used to encode for example the physical entity.
a URI containing a Common Language Equipment Identifier (CLEI) URI
[reference TBD] for the managed physical entity. If no additional The object contains one or more Uniform Resource Identifiers (URIs)
identification information is known or supported about the physical and therefore the syntax of this object must conform to RFC 2396
entity the object is not instantiated. [RFC2396] section 2. Uniform Resource Names (URNs), RFC 3406
[RFC3406], are resource identifiers with the specific requirements
for enabling location independent identification of a resource, as
well as longevity of reference. URNs are part of the larger URI
family with the specific goal of providing persistent naming of
resources. URI schemes and URN name spaces are registered by IANA
(see http://www.iana.org/assignments/uri-schemes and
http://www.iana.org/assignments/urn-namespaces).
The entPhysicalUris object may be used to encode for example a URI
containing a Common Language Equipment Identifier (CLEI) URI for
the managed physical entity. The URN name space for CLEIs is
defined in [RFC CLEIURN], and the CLEI format is defined in
[T1.213][T1.213a]. For example, an entPhysicalUris instance may
have the value of
URN:CLEI:D4CE18B7AA
[RFC2396] and [RFCCLEIURN] identify this as a URI in the CLEI URN
name space, and the specific CLEI code, D4CE18B7AA is based on the
example provided in [T1.213a].
Multiple URIs may be present and are separated by white space
characters. Leading and trailing white space characters are
ignored.
If no additional identification information is known or supported
about the physical entity 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 indexed by an arbitrary, small integer and contains a name, is 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
skipping to change at page 15, line 15 skipping to change at page 15, line 37
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 to provide the date of manufacturing of the entPhysicalTable 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 provide additional identification information about the physical to 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) URI.
2.15.3. Deprecated Objects 2.15.3. Bugfixes
The entLPMappingTable has been deprecated because no
implementations have been found which support this table. The
entLPPhysicalIndex has been removed from the entityMappingGroup.
This OBJECT-GROUP has been updated (entityMappingGroupRev1) as well
as the Entity MIB MODULE-CONFORMANCE statement.
2.15.4. Bugfixes
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 16, line 23
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 "200410220000Z" LAST-UPDATED "200501070000Z"
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 16, line 48 skipping to change at page 16, line 48
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 (2004). 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 xxxx; see
the RFC itself for full legal notices." the RFC itself for full legal notices."
-- RFC Ed.: replace xxxx with actual RFC number & remove this notice -- RFC Ed.: replace xxxx with actual RFC number & remove this notice
REVISION "200410220000Z" REVISION "200501070000Z"
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
- entPhysicalMfgDate object - entPhysicalMfgDate object
- entPhysicalUris object - entPhysicalUris object
Changes: Changes:
- entLPMappingTable deprecated
- 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 xxxx."
-- RFC Ed.: replace xxxx with actual RFC number & remove this notice -- RFC Ed.: replace xxxx with actual RFC number & remove this notice
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.
skipping to change at page 30, line 10 skipping to change at page 30, line 10
all entPhysicalEntries which represent components that are all entPhysicalEntries which represent components that are
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
"The manufacturing date for the physical entity." "The manufacturing date for the physical entity. The value
'0000000000000000'H is returned if the manufacturing date of
the entity in unknown."
::= { 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 2396 therefore the syntax of this object must conform to RFC
[RFC2396] section 2. Multiple URIs may be separated by white 2396, section 2.
space characters."
Multiple URIs may be present and are separated by white
space characters. Leading and trailing white space
characters are ignored.
If no additional identification information is known or
supported about the physical entity the object is not
instantiated. A zero length octet string may also be
returned in this case."
REFERENCE REFERENCE
"RFC 2396, Uniform Resource Identifiers (URI): Generic "RFC 2396, 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
skipping to change at page 34, line 44 skipping to change at page 35, line 8
contextName pair. contextName pair.
If no value has been configured by the agent, a zero-length If no value has been configured by the agent, a zero-length
string is returned, or the agent may choose not to string is returned, or the agent may choose not to
instantiate this object at all." instantiate this object at all."
::= { 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 deprecated 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 which
skipping to change at page 35, line 36 skipping to change at page 35, line 45
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
STATUS deprecated STATUS current
DESCRIPTION DESCRIPTION
"Information about a particular logical entity to physical "Information about a particular logical entity to physical
equipment association. Note that the nature of the equipment association. Note that the nature of the
association is not specifically identified in this entry. association is not specifically identified in this entry.
It is expected that sufficient information exists in the It is expected that sufficient information exists in the
MIBs used to manage a particular logical entity to infer how MIBs used to manage a particular logical entity to infer how
physical component information is utilized." physical component information is utilized."
INDEX { entLogicalIndex, entLPPhysicalIndex } INDEX { entLogicalIndex, entLPPhysicalIndex }
::= { entLPMappingTable 1 } ::= { entLPMappingTable 1 }
EntLPMappingEntry ::= SEQUENCE { EntLPMappingEntry ::= SEQUENCE {
entLPPhysicalIndex PhysicalIndex entLPPhysicalIndex PhysicalIndex
} }
entLPPhysicalIndex OBJECT-TYPE entLPPhysicalIndex OBJECT-TYPE
SYNTAX PhysicalIndex SYNTAX PhysicalIndex
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS current
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
skipping to change at page 43, line 32 skipping to change at page 43, line 39
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 which model all MIB object instances within a single naming
scope." scope."
GROUP entityMappingGroupRev1 GROUP entityMappingGroup
DESCRIPTION DESCRIPTION
"Implementation of the entPhysicalContainsTable is mandatory "Implementation of the entPhysicalContainsTable is mandatory
for all agents. Implementation of the entAliasMappingTable for all agents. Implementation of the entLPMappingTable and
is not mandatory for agents which model all MIB object entAliasMappingTables are not mandatory for agents which
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 which
cannot identify serial number information for physical cannot identify serial number information for physical
skipping to change at page 45, line 28 skipping to change at page 45, line 35
list of logical entities for which a single agent provides list of 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 deprecated 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 3 } ::= { entityGroups 3 }
entityGeneralGroup OBJECT-GROUP entityGeneralGroup OBJECT-GROUP
OBJECTS { OBJECTS {
entLastChangeTime entLastChangeTime
skipping to change at page 46, line 46 skipping to change at page 47, line 8
entLogicalContextEngineID, entLogicalContextEngineID,
entLogicalContextName entLogicalContextName
} }
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
OBJECTS {
entAliasMappingIdentifier,
entPhysicalChildIndex
}
STATUS current
DESCRIPTION
"The collection of objects which are used to represent the
associations between multiple logical entities, physical
components, interfaces, and port identifiers for which a
single agent provides management information."
::= { entityGroups 8 }
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 which are used to represent
physical system components, for which a single agent physical system components, for which a single agent
provides management information. This group augments the provides management information. This group augments the
objects contained in the entityPhysicalGroup." objects contained in the entityPhysicalGroup."
::= { entityGroups 9 } ::= { 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 understandable. Auxiliary components, such as fans, sensors, more understandable. Auxiliary components, such as fans, sensors,
empty slots, and sub-modules are not shown, but might be modeled in empty slots, and sub-modules are not shown, but might be modeled in
real implementations. real implementations.
skipping to change at page 48, line 37 skipping to change at page 48, line 37
entPhysicalName.1 == '100-A' entPhysicalName.1 == '100-A'
entPhysicalHardwareRev.1 == 'A(1.00.02)' entPhysicalHardwareRev.1 == 'A(1.00.02)'
entPhysicalSoftwareRev.1 == '' entPhysicalSoftwareRev.1 == ''
entPhysicalFirmwareRev.1 == '' entPhysicalFirmwareRev.1 == ''
entPhysicalSerialNum.1 == 'C100076544' entPhysicalSerialNum.1 == 'C100076544'
entPhysicalMfgName.1 == 'Acme' entPhysicalMfgName.1 == 'Acme'
entPhysicalModelName.1 == '100' entPhysicalModelName.1 == '100'
entPhysicalAlias.1 == 'cl-SJ17-3-006:rack1:rtr-U3' entPhysicalAlias.1 == 'cl-SJ17-3-006:rack1:rtr-U3'
entPhysicalAssetID.1 == '0007372293' entPhysicalAssetID.1 == '0007372293'
entPhysicalIsFRU.1 == true(1) entPhysicalIsFRU.1 == true(1)
entPhysicalMfgDate.1 == '2002-5-26,13:30:30.0,-4:0'
entPhysicalUris.1 == 'URN:CLEI:CNME120ARA'
2 slots within the chassis: 2 slots within the chassis:
entPhysicalDescr.2 == 'Acme Chassis Slot Type AA' entPhysicalDescr.2 == 'Acme Chassis Slot Type AA'
entPhysicalVendorType.2 == acmeProducts.slotTypes.1 entPhysicalVendorType.2 == acmeProducts.slotTypes.1
entPhysicalContainedIn.2 == 1 entPhysicalContainedIn.2 == 1
entPhysicalClass.2 == container(5) entPhysicalClass.2 == container(5)
entPhysicalParentRelPos.2 == 1 entPhysicalParentRelPos.2 == 1
entPhysicalName.2 == 'S1' entPhysicalName.2 == 'S1'
entPhysicalHardwareRev.2 == 'B(1.00.01)' entPhysicalHardwareRev.2 == 'B(1.00.01)'
entPhysicalSoftwareRev.2 == '' entPhysicalSoftwareRev.2 == ''
entPhysicalFirmwareRev.2 == '' entPhysicalFirmwareRev.2 == ''
entPhysicalSerialNum.2 == '' entPhysicalSerialNum.2 == ''
entPhysicalMfgName.2 == 'Acme' entPhysicalMfgName.2 == 'Acme'
entPhysicalModelName.2 == 'AA' entPhysicalModelName.2 == 'AA'
entPhysicalAlias.2 == '' entPhysicalAlias.2 == ''
entPhysicalAssetID.2 == '' entPhysicalAssetID.2 == ''
entPhysicalIsFRU.2 == false(2) entPhysicalIsFRU.2 == false(2)
entPhysicalMfgDate.2 == '2002-7-26,12:22:12.0,-4:0'
entPhysicalUris.2 == 'URN:CLEI:CNME123ARA'
entPhysicalDescr.3 == 'Acme Chassis Slot Type AA' entPhysicalDescr.3 == 'Acme Chassis Slot Type AA'
entPhysicalVendorType.3 = acmeProducts.slotTypes.1 entPhysicalVendorType.3 = acmeProducts.slotTypes.1
entPhysicalContainedIn.3 == 1 entPhysicalContainedIn.3 == 1
entPhysicalClass.3 == container(5) entPhysicalClass.3 == container(5)
entPhysicalParentRelPos.3 == 2 entPhysicalParentRelPos.3 == 2
entPhysicalName.3 == 'S2' entPhysicalName.3 == 'S2'
entPhysicalHardwareRev.3 == '1.00.07' entPhysicalHardwareRev.3 == '1.00.07'
entPhysicalSoftwareRev.3 == '' entPhysicalSoftwareRev.3 == ''
entPhysicalFirmwareRev.3 == '' entPhysicalFirmwareRev.3 == ''
entPhysicalSerialNum.3 == '' entPhysicalSerialNum.3 == ''
entPhysicalMfgName.3 == 'Acme' entPhysicalMfgName.3 == 'Acme'
entPhysicalModelName.3 == 'AA' entPhysicalModelName.3 == 'AA'
entPhysicalAlias.3 == '' entPhysicalAlias.3 == ''
entPhysicalAssetID.3 == '' entPhysicalAssetID.3 == ''
entPhysicalIsFRU.3 == false(2) entPhysicalIsFRU.3 == false(2)
entPhysicalMfgDate.3 == '2002-7-26,12:12:12.0,-4:0'
entPhysicalUris.3 == 'URN:CLEI:CNME123ARA'
2 Field-replaceable modules: 2 Field-replaceable modules:
Slot 1 contains a module with 3 ports: Slot 1 contains a module with 3 ports:
entPhysicalDescr.4 == 'Acme Router-100' entPhysicalDescr.4 == 'Acme Router-100'
entPhysicalVendorType.4 == acmeProducts.moduleTypes.14 entPhysicalVendorType.4 == acmeProducts.moduleTypes.14
entPhysicalContainedIn.4 == 2 entPhysicalContainedIn.4 == 2
entPhysicalClass.4 == module(9) entPhysicalClass.4 == module(9)
entPhysicalParentRelPos.4 == 1 entPhysicalParentRelPos.4 == 1
entPhysicalName.4 == 'M1' entPhysicalName.4 == 'M1'
entPhysicalHardwareRev.4 == '1.00.07' entPhysicalHardwareRev.4 == '1.00.07'
entPhysicalSoftwareRev.4 == '1.4.1' entPhysicalSoftwareRev.4 == '1.4.1'
entPhysicalFirmwareRev.4 == 'A(1.1)' entPhysicalFirmwareRev.4 == 'A(1.1)'
entPhysicalSerialNum.4 == 'C100087363' entPhysicalSerialNum.4 == 'C100087363'
entPhysicalMfgName.4 == 'Acme' entPhysicalMfgName.4 == 'Acme'
entPhysicalModelName.4 == 'R100-FE' entPhysicalModelName.4 == 'R100-FE'
entPhysicalAlias.4 == 'rtr-U3:m1:SJ17-3-eng' entPhysicalAlias.4 == 'rtr-U3:m1:SJ17-3-eng'
entPhysicalAssetID.4 == '0007372462' entPhysicalAssetID.4 == '0007372462'
entPhysicalIsFRU.4 == true(1) entPhysicalIsFRU.4 == true(1)
entPhysicalMfgDate.4 == '2003-7-18,13:30:30.0,-4:0'
entPhysicalUris.4 == 'URN:CLEI:CNRU123CAA'
entPhysicalDescr.5 == 'Acme Ethernet-100 Port' entPhysicalDescr.5 == 'Acme Ethernet-100 Port'
entPhysicalVendorType.5 == acmeProducts.portTypes.2 entPhysicalVendorType.5 == acmeProducts.portTypes.2
entPhysicalContainedIn.5 == 4 entPhysicalContainedIn.5 == 4
entPhysicalClass.5 == port(10) entPhysicalClass.5 == port(10)
entPhysicalParentRelPos.5 == 1 entPhysicalParentRelPos.5 == 1
entPhysicalName.5 == 'P1' entPhysicalName.5 == 'P1'
entPhysicalHardwareRev.5 == 'G(1.02)' entPhysicalHardwareRev.5 == 'G(1.02)'
entPhysicalSoftwareRev.5 == '' entPhysicalSoftwareRev.5 == ''
entPhysicalFirmwareRev.5 == '1.1' entPhysicalFirmwareRev.5 == '1.1'
entPhysicalSerialNum.5 == '' entPhysicalSerialNum.5 == ''
entPhysicalMfgName.5 == 'Acme' entPhysicalMfgName.5 == 'Acme'
entPhysicalModelName.5 == 'FE-100' entPhysicalModelName.5 == 'FE-100'
entPhysicalAlias.5 == '' entPhysicalAlias.5 == ''
entPhysicalAssetID.5 == '' entPhysicalAssetID.5 == ''
entPhysicalIsFRU.5 == false(2) entPhysicalIsFRU.5 == false(2)
entPhysicalMfgDate.5 == '2003-7-18,14:20:22.0,-4:0'
entPhysicalUris.5 == 'URN:CLEI:CNMES23ARA'
entPhysicalDescr.6 == 'Acme Ethernet-100 Port' entPhysicalDescr.6 == 'Acme Ethernet-100 Port'
entPhysicalVendorType.6 == acmeProducts.portTypes.2 entPhysicalVendorType.6 == acmeProducts.portTypes.2
entPhysicalContainedIn.6 == 4 entPhysicalContainedIn.6 == 4
entPhysicalClass.6 == port(10) entPhysicalClass.6 == port(10)
entPhysicalParentRelPos.6 == 2 entPhysicalParentRelPos.6 == 2
entPhysicalName.6 == 'P2' entPhysicalName.6 == 'P2'
entPhysicalHardwareRev.6 == 'G(1.02)' entPhysicalHardwareRev.6 == 'G(1.02)'
entPhysicalSoftwareRev.6 == '' entPhysicalSoftwareRev.6 == ''
entPhysicalFirmwareRev.6 == '1.1' entPhysicalFirmwareRev.6 == '1.1'
entPhysicalSerialNum.6 == '' entPhysicalSerialNum.6 == ''
entPhysicalMfgName.6 == 'Acme' entPhysicalMfgName.6 == 'Acme'
entPhysicalModelName.6 == 'FE-100' entPhysicalModelName.6 == 'FE-100'
entPhysicalAlias.6 == '' entPhysicalAlias.6 == ''
entPhysicalAssetID.6 == '' entPhysicalAssetID.6 == ''
entPhysicalIsFRU.6 == false(2) entPhysicalIsFRU.6 == false(2)
entPhysicalMfgDate.6 == '2003-7-19,10:15:15.0,-4:0'
entPhysicalUris.6 == 'URN:CLEI:CNMES23ARA'
entPhysicalDescr.7 == 'Acme Router-100 FDDI-Port' entPhysicalDescr.7 == 'Acme Router-100 FDDI-Port'
entPhysicalVendorType.7 == acmeProducts.portTypes.3 entPhysicalVendorType.7 == acmeProducts.portTypes.3
entPhysicalContainedIn.7 == 4 entPhysicalContainedIn.7 == 4
entPhysicalClass.7 == port(10) entPhysicalClass.7 == port(10)
entPhysicalParentRelPos.7 == 3 entPhysicalParentRelPos.7 == 3
entPhysicalName.7 == 'P3' entPhysicalName.7 == 'P3'
entPhysicalHardwareRev.7 == 'B(1.03)' entPhysicalHardwareRev.7 == 'B(1.03)'
entPhysicalSoftwareRev.7 == '2.5.1' entPhysicalSoftwareRev.7 == '2.5.1'
entPhysicalFirmwareRev.7 == '2.5F' entPhysicalFirmwareRev.7 == '2.5F'
skipping to change at page 51, line 17 skipping to change at page 51, line 27
entPhysicalName.8 == 'M2' entPhysicalName.8 == 'M2'
entPhysicalHardwareRev.8 == '2.01.00' entPhysicalHardwareRev.8 == '2.01.00'
entPhysicalSoftwareRev.8 == '3.0.7' entPhysicalSoftwareRev.8 == '3.0.7'
entPhysicalFirmwareRev.8 == 'A(1.2)' entPhysicalFirmwareRev.8 == 'A(1.2)'
entPhysicalSerialNum.8 == 'C100098732' entPhysicalSerialNum.8 == 'C100098732'
entPhysicalMfgName.8 == 'Acme' entPhysicalMfgName.8 == 'Acme'
entPhysicalModelName.8 == 'C100' entPhysicalModelName.8 == 'C100'
entPhysicalAlias.8 == 'rtr-U3:m2:SJ17-2-eng' entPhysicalAlias.8 == 'rtr-U3:m2:SJ17-2-eng'
entPhysicalAssetID.8 == '0007373982' entPhysicalAssetID.8 == '0007373982'
entPhysicalIsFRU.8 == true(1) entPhysicalIsFRU.8 == true(1)
entPhysicalMfgDate.8 == '2002-5-26,13:30:15.0,-4:0'
entPhysicalUris.8 == 'URN:CLEI:CNRT321MAA'
entPhysicalDescr.9 == 'Acme Fddi-100 Port' entPhysicalDescr.9 == 'Acme Fddi-100 Port'
entPhysicalVendorType.9 == acmeProducts.portTypes.5 entPhysicalVendorType.9 == acmeProducts.portTypes.5
entPhysicalContainedIn.9 == 8 entPhysicalContainedIn.9 == 8
entPhysicalClass.9 == port(10) entPhysicalClass.9 == port(10)
entPhysicalParentRelPos.9 == 1 entPhysicalParentRelPos.9 == 1
entPhysicalName.9 == 'FDDI Primary' entPhysicalName.9 == 'FDDI Primary'
entPhysicalHardwareRev.9 == 'CC(1.07)' entPhysicalHardwareRev.9 == 'CC(1.07)'
entPhysicalSoftwareRev.9 == '2.0.34' entPhysicalSoftwareRev.9 == '2.0.34'
entPhysicalFirmwareRev.9 == '1.1' entPhysicalFirmwareRev.9 == '1.1'
skipping to change at page 52, line 4 skipping to change at page 52, line 16
entPhysicalName.10 == 'Ethernet A' entPhysicalName.10 == 'Ethernet A'
entPhysicalHardwareRev.10 == 'G(1.04)' entPhysicalHardwareRev.10 == 'G(1.04)'
entPhysicalSoftwareRev.10 == '' entPhysicalSoftwareRev.10 == ''
entPhysicalFirmwareRev.10 == '1.3' entPhysicalFirmwareRev.10 == '1.3'
entPhysicalSerialNum.10 == '' entPhysicalSerialNum.10 == ''
entPhysicalMfgName.10 == 'Acme' entPhysicalMfgName.10 == 'Acme'
entPhysicalModelName.10 == 'FE-100' entPhysicalModelName.10 == 'FE-100'
entPhysicalAlias.10 == '' entPhysicalAlias.10 == ''
entPhysicalAssetID.10 == '' entPhysicalAssetID.10 == ''
entPhysicalIsFRU.10 == false(2) entPhysicalIsFRU.10 == false(2)
entPhysicalMfgDate.10 == '2002-7-26,13:30:15.0,-4:0'
entPhysicalUris.10 == 'URN:CLEI:CNMES23ARA'
entPhysicalDescr.11 == 'Acme Ethernet-100 Port' entPhysicalDescr.11 == 'Acme Ethernet-100 Port'
entPhysicalVendorType.11 == acmeProducts.portTypes.2 entPhysicalVendorType.11 == acmeProducts.portTypes.2
entPhysicalContainedIn.11 == 8 entPhysicalContainedIn.11 == 8
entPhysicalClass.11 == port(10) entPhysicalClass.11 == port(10)
entPhysicalParentRelPos.11 == 3 entPhysicalParentRelPos.11 == 3
entPhysicalName.11 == 'Ethernet B' entPhysicalName.11 == 'Ethernet B'
entPhysicalHardwareRev.11 == 'G(1.04)' entPhysicalHardwareRev.11 == 'G(1.04)'
entPhysicalSoftwareRev.11 == '' entPhysicalSoftwareRev.11 == ''
entPhysicalFirmwareRev.11 == '1.3' entPhysicalFirmwareRev.11 == '1.3'
entPhysicalSerialNum.11 == '' entPhysicalSerialNum.11 == ''
entPhysicalMfgName.11 == 'Acme' entPhysicalMfgName.11 == 'Acme'
entPhysicalModelName.11 == 'FE-100' entPhysicalModelName.11 == 'FE-100'
entPhysicalAlias.11 == '' entPhysicalAlias.11 == ''
entPhysicalAssetID.11 == '' entPhysicalAssetID.11 == ''
entPhysicalIsFRU.11 == false(2) entPhysicalIsFRU.11 == false(2)
entPhysicalMfgDate.11 == '2002-8-16,15:35:15.0,-4:0'
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 == 124.125.126.127:161
entLogicalTDomain.1 == snmpUDPDomain entLogicalTDomain.1 == snmpUDPDomain
entLogicalContextEngineID.1 == '' entLogicalContextEngineID.1 == ''
entLogicalContextName.1 == '' entLogicalContextName.1 == ''
skipping to change at page 65, line 40 skipping to change at page 65, line 40
using SMIv2", RFC 2108, February, 1997. using SMIv2", RFC 2108, February, 1997.
[RFC2863] [RFC2863]
McCloghrie, K., and F. Kastenholz, "The Interfaces Group MIB", RFC McCloghrie, K., and F. Kastenholz, "The Interfaces Group MIB", RFC
2863, June, 2000. 2863, June, 2000.
[RFC2737] [RFC2737]
McCloghrie, K., and A. Bierman, "Entity MIB (Version 2)", RFC 2737, McCloghrie, K., and A. Bierman, "Entity MIB (Version 2)", RFC 2737,
December 1999. December 1999.
[RFC3406]
Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, "Uniform
Resource Names (URN) Namespace Definition Mechanisms", RFC 3406,
October 2002.
[RFC3410] [RFC3410]
Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and
Applicability Statements for Internet- Standard Management Applicability Statements for Internet- Standard Management
Framework", RFC 3410, December 2002. Framework", RFC 3410, December 2002.
[RFCCLEIURN]
Tesink, K., and Robert H. Fox, "A Uniform Resource Name (URN)
Namespace for the CLEI Code", Work in progress, November 7, 2004.
[T1.213]
ATIS T1.213-2001, "Coded Identification of Equipment 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. Cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134 USA San Jose, CA 95134 USA
Phone: +1 408-527-3711 Phone: +1 408-527-3711
Email: abierman@cisco.com Email: abierman@cisco.com
Keith McCloghrie Keith McCloghrie
skipping to change at page 67, line 14 skipping to change at page 68, line 14
an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT
THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR
ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE. PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2004). This document is Copyright (C) The Internet Society (2005). This document is
subject to the rights, licenses and restrictions contained in BCP subject to the rights, licenses and restrictions contained in BCP
78, and except as set forth therein, the authors retain all their 78, and except as set forth therein, the authors retain all their
rights. rights.
Acknowledgment 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.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/