draft-ietf-entmib-v3-01.txt   draft-ietf-entmib-v3-02.txt 
Entity MIB Working Group Keith McCloghrie Entity MIB Working Group Andy Bierman
Internet Draft Cisco Systems, Inc. Internet Draft Keith McCloghrie
Andy Bierman
Cisco Systems, Inc. Cisco Systems, Inc.
12 May 2003 27 August 2003
Entity MIB (Version 3) Entity MIB (Version 3)
<draft-ietf-entmib-v3-01.txt> <draft-ietf-entmib-v3-02.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 ?
1. Copyright Notice 1. Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2003). 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. logical and physical entities managed by a single SNMP agent. This
document specifies version 3 of the Entity MIB, which obsoletes version
2 (RFC 2737).
2. Table of Contents 2. Table of Contents
1 Copyright Notice ................................................ 1 1 Copyright Notice ................................................ 1
2 Table of Contents ............................................... 2 2 Table of Contents ............................................... 2
3 The SNMP Management Framework ................................... 3 3 The SNMP Management Framework ................................... 3
4 Overview ........................................................ 3 4 Overview ........................................................ 3
4.1 Terms ......................................................... 4 4.1 Terms ......................................................... 4
4.2 Relationship to Community Strings ............................. 5 4.2 Relationship to Community Strings ............................. 5
4.3 Relationship to SNMP Contexts ................................. 6 4.3 Relationship to SNMP Contexts ................................. 6
skipping to change at page 3, line 4 skipping to change at page 2, line ?
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 ................................................... 13
5 Definitions ..................................................... 14 5 Definitions ..................................................... 14
6 Usage Examples .................................................. 45 6 Usage Examples .................................................. 45
6.1 Router/Bridge ................................................. 45 6.1 Router/Bridge ................................................. 45
6.2 Repeaters ..................................................... 51 6.2 Repeaters ..................................................... 51
7 Intellectual Property ........................................... 59 7 Intellectual Property ........................................... 59
8 Acknowledgements ................................................ 59 8 Acknowledgements ................................................ 59
9 Normative References ............................................ 59 9 Normative References ............................................ 59
10 Informative References ......................................... 60 10 Informative References ......................................... 60
11 Security Considerations ........................................ 62 11 Security Considerations ........................................ 62
12 Authors' Addresses ............................................. 64 12 Authors' Addresses ............................................. 64
13 Full Copyright Statement ....................................... 65 13 Full Copyright Statement ....................................... 65
*** TOC line ***
*** TOC line ***
*** TOC line ***
*** TOC line ***
*** TOC line ***
*** TOC line ***
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
MIB are defined using the mechanisms defined in the Structure of MIB are defined using the mechanisms defined in the Structure of
skipping to change at page 13, line 46 skipping to change at page 13, line 46
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.
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
entPhysicalContainedIn, entPhysicalParentRelPos, entLogicalIndex, and entPhysicalParentRelPos, entLogicalIndex, and entAliasLogicalIndexOrZero
entAliasLogicalIndexOrZero objects. objects, and from INTEGER to PhysicalIndexOrZero for the
entPhysicalContainedIn object.
5. Definitions 5. Definitions
ENTITY-MIB DEFINITIONS ::= BEGIN ENTITY-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, mib-2, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, mib-2, NOTIFICATION-TYPE,
Integer32 Integer32
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 "200305110000Z" LAST-UPDATED "200308270000Z"
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
Keith McCloghrie Andy Bierman
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-527-3711
kzm@cisco.com abierman@cisco.com
Andy Bierman 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-527-3711 +1 408-526-5260
abierman@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.
REVISION "200305110000Z" Copyright (C) The Internet Society (2003). This
version of this MIB module is part of RFC xxxx; see
the RFC itself for full legal notices."
REVISION "200308270000Z"
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
- entPhysicalContainedIn SYNTAX changed from
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 "9610310000Z" REVISION "9610310000Z"
DESCRIPTION DESCRIPTION
"Initial version (version 1), published as "Initial version (version 1), published as
RFC 2037." RFC 2037."
::= { mib-2 47 } ::= { mib-2 47 }
entityMIBObjects OBJECT IDENTIFIER ::= { entityMIB 1 } entityMIBObjects OBJECT IDENTIFIER ::= { entityMIB 1 }
skipping to change at page 19, line 4 skipping to change at page 19, line 13
(entPhysicalContainedIn and entPhysicalParentRelPos) to help (entPhysicalContainedIn and entPhysicalParentRelPos) to help
an NMS relate the particular entry to other entries in this an NMS relate the particular entry to other entries in this
table." table."
INDEX { entPhysicalIndex } INDEX { entPhysicalIndex }
::= { entPhysicalTable 1 } ::= { entPhysicalTable 1 }
EntPhysicalEntry ::= SEQUENCE { EntPhysicalEntry ::= SEQUENCE {
entPhysicalIndex PhysicalIndex, entPhysicalIndex PhysicalIndex,
entPhysicalDescr SnmpAdminString, entPhysicalDescr SnmpAdminString,
entPhysicalVendorType AutonomousType, entPhysicalVendorType AutonomousType,
entPhysicalContainedIn Integer32, entPhysicalContainedIn PhysicalIndexOrZero,
entPhysicalClass PhysicalClass, entPhysicalClass PhysicalClass,
entPhysicalParentRelPos Integer32, entPhysicalParentRelPos Integer32,
entPhysicalName SnmpAdminString, entPhysicalName SnmpAdminString,
entPhysicalHardwareRev SnmpAdminString, entPhysicalHardwareRev SnmpAdminString,
entPhysicalFirmwareRev SnmpAdminString, entPhysicalFirmwareRev SnmpAdminString,
entPhysicalSoftwareRev SnmpAdminString, entPhysicalSoftwareRev SnmpAdminString,
entPhysicalSerialNum SnmpAdminString, entPhysicalSerialNum SnmpAdminString,
entPhysicalMfgName SnmpAdminString, entPhysicalMfgName SnmpAdminString,
entPhysicalModelName SnmpAdminString, entPhysicalModelName SnmpAdminString,
entPhysicalAlias SnmpAdminString, entPhysicalAlias SnmpAdminString,
skipping to change at page 20, line 15 skipping to change at page 20, line 24
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 }
entPhysicalContainedIn OBJECT-TYPE entPhysicalContainedIn OBJECT-TYPE
SYNTAX Integer32 (0..2147483647) SYNTAX PhysicalIndexOrZero
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.
skipping to change at page 64, line 7 skipping to change at page 64, line 7
based Security Model RFC 2574 [RFC2574] and the View-based Access based Security Model RFC 2574 [RFC2574] and the View-based Access
Control Model RFC 2575 [RFC2575] is recommended. Control Model RFC 2575 [RFC2575] is recommended.
It is then a customer/user responsibility to ensure that the SNMP entity It is then a customer/user responsibility to ensure that the SNMP entity
giving access to an instance of this MIB, is properly configured to give giving access to an instance of this MIB, is properly configured to give
access to the objects only to those principals (users) that have access to the objects only to those principals (users) that have
legitimate rights to indeed GET or SET (change/create/delete) them. legitimate rights to indeed GET or SET (change/create/delete) them.
12. Authors' Addresses 12. Authors' Addresses
Keith McCloghrie 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-526-5260 Phone: +1 408-527-3711
Email: kzm@cisco.com Email: abierman@cisco.com
Andy Bierman 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-527-3711 Phone: +1 408-526-5260
Email: abierman@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 (2003). 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
 End of changes. 

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