< draft-bierman-entmib-compid-00.txt   draft-bierman-entmib-compid-01.txt >
<draft-bierman-entmib-compid-00.txt> Draft Entity MIB Extensions September 1997
Entity MIB Extensions for Persistent Component Identification
30 July 1997 <draft-bierman-entmib-compid-01.txt>
Entity MIB Extensions for Persistent Component Identification
18 September 1997
Andy Bierman Andy Bierman
Cisco Systems Inc. Cisco Systems Inc.
abierman@cisco.com abierman@cisco.com
Keith McCloghrie Keith McCloghrie
Cisco Systems Inc. Cisco Systems Inc.
kzm@cisco.com kzm@cisco.com
Status of this Memo Status of this Memo
skipping to change at page 2, line ? skipping to change at page 2, line 5
Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe), Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe),
ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim).
1. Introduction 1. Introduction
This memo defines an experimental portion of the Management Information This memo defines an experimental portion of the Management Information
Base (MIB) for use with network management protocols in the Internet Base (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 physical topology identification and discovery. managing physical topology identification and discovery.
Draft Entity MIB Extensions July 1997 Draft Entity MIB Extensions September 1997
2. The SNMP Network Management Framework 2. The SNMP Network Management Framework
The SNMP Network Management Framework presently consists of three major The SNMP Network Management Framework presently consists of three major
components. They are: components. They are:
o the SMI, described in RFC 1902 [1], - the mechanisms used for o the SMI, described in RFC 1902 [1], - the mechanisms used for
describing and naming objects for the purpose of management. describing and naming objects for the purpose of management.
o the MIB-II, STD 17, RFC 1213 [2], - the core set of managed objects o the MIB-II, STD 17, RFC 1213 [2], - the core set of managed objects
skipping to change at page 3, line 5 skipping to change at page 2, line 48
object instance serves to uniquely identify a specific instantiation of object instance serves to uniquely identify a specific instantiation of
the object. For human convenience, we often use a textual string, the object. For human convenience, we often use a textual string,
termed the descriptor, to refer to the object type. termed the descriptor, to refer to the object type.
3. Overview 3. Overview
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 [7]. represented with the Entity MIB [7].
Draft Entity MIB Extensions July 1997
This document defines extensions to the Entity MIB to address this need. This document defines extensions to the Entity MIB to address this need.
Draft Entity MIB Extensions September 1997
4. Entity MIB Extensions 4. Entity MIB Extensions
4.1. MIB Structure 4.1. MIB Structure
The Entity Extensions MIB contains a single group: The Entity Extensions MIB contains a single group:
- Entity Physical Extensions Group - Entity Physical Extensions Group
4.1.1. Entity Physical Extensions Group 4.1.1. Entity Physical Extensions Group
This group contains a single table, called the entPhysicalXTable, which This group contains a single table, called the entPhysicalXTable, which
augments the entPhysicalTable. Each entPhysicalXEntry provides a augments the entPhysicalTable. Each entPhysicalXEntry provides a
DisplayString which can be used by an NMS as a non-volatile alias string writable string object, 'entPhysicalAlias', which can be used by an NMS
for the physical component. as a non-volatile 'alias' (or label) for the physical component.
The entPhysicalAlias object is different from the ifAlias version in
several ways:
- SnmpAdminString SYNTAX
The Interfaces MIB [8] version is defined as a DisplayString [3].
The Entity MIB [7] version is defined as an SnmpAdminString [9].
- SIZE (0..32)
The maximum length of the entPhysicalAlias string is half that of
the ifAlias object.
- MIN-ACCESS
Maintaining a non-volatile string for every physical component
represented in the entPhysicalTable can be costly and unnecessary.
An agent may choose to algorithmically generate entPhysicalAlias
strings for particular entries (based on the entPhysicalClass
value).
4.2. Definitions 4.2. Definitions
ENTITY-EXTENSIONS-MIB DEFINITIONS ::= BEGIN ENTITY-EXTENSIONS-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE MODULE-IDENTITY, OBJECT-TYPE
FROM SNMPv2-SMI FROM SNMPv2-SMI
DisplayString
FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
SnmpAdminString
Draft Entity MIB Extensions September 1997
FROM SNMP-FRAMEWORK-MIB
entPhysicalEntry, entityMIBObjects, entityCompliances, entPhysicalEntry, entityMIBObjects, entityCompliances,
entityGroups, entityPhysicalGroup entityGroups, entityPhysicalGroup
FROM ENTITY-MIB; FROM ENTITY-MIB;
entityXMIB MODULE-IDENTITY entityXMIB MODULE-IDENTITY
LAST-UPDATED "9703170000Z" LAST-UPDATED "9709150000Z"
ORGANIZATION "Cisco Systems, Inc." ORGANIZATION "IETF Entity MIB Working Group"
CONTACT-INFO CONTACT-INFO
"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
408-527-3711 408-527-3711
abierman@cisco.com abierman@cisco.com
Draft Entity MIB Extensions July 1997
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
408-526-5260 408-526-5260
kzm@cisco.com" kzm@cisco.com"
DESCRIPTION DESCRIPTION
"The extension MIB module for physical entity information." "The extension MIB module for physical entity information."
::= { experimental xx } ::= { experimental xx }
-- *********************************************************** -- ***********************************************************
-- --
-- E N T I T Y P H Y S I C A L E X T E N S I O N S -- E N T I T Y P H Y S I C A L E X T E N S I O N S
-- --
-- *********************************************************** -- ***********************************************************
-- entPhysicalTable extensions -- entPhysicalTable extensions
entityPhysicalX OBJECT IDENTIFIER ::= { entityMIBObjects 5 } entityPhysicalX OBJECT IDENTIFIER ::= { entityMIBObjects 5 }
entPhysicalXTable OBJECT-TYPE entPhysicalXTable OBJECT-TYPE
SYNTAX SEQUENCE OF EntPhysicalXEntry SYNTAX SEQUENCE OF EntPhysicalXEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains one row per physical element "This table contains one row per physical element
represented in the entPhysicalTable." represented in the entPhysicalTable."
::= { entityPhysicalX 1 } ::= { entityPhysicalX 1 }
Draft Entity MIB Extensions September 1997
entPhysicalXEntry OBJECT-TYPE entPhysicalXEntry OBJECT-TYPE
SYNTAX EntPhysicalXEntry SYNTAX EntPhysicalXEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about a particular physical entity. "Information about a particular physical entity."
Each entry provides an object (entPhysicalAlias) to help an
NMS uniquely identify a physical entity with a DisplayString
stored in non-volatile and re-created after a reboot."
AUGMENTS { entPhysicalEntry } AUGMENTS { entPhysicalEntry }
::= { entPhysicalXTable 1 } ::= { entPhysicalXTable 1 }
EntPhysicalXEntry ::= SEQUENCE { EntPhysicalXEntry ::= SEQUENCE {
entPhysicalAlias DisplayString entPhysicalAlias SnmpAdminString
} }
Draft Entity MIB Extensions July 1997
entPhysicalAlias OBJECT-TYPE entPhysicalAlias OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..48)) 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 an physical entity, the value
of entPhysicalAlias associated with that entity is the of entPhysicalAlias associated with that entity is set to
zero-length string. As and when a value is written into an the zero-length string. An agent may instead choose to set
instance of entPhysicalAlias through a network management the value to a locally unique default value instead of a
set operation, then the agent must retain the supplied value zero-length string.
in the entPhysicalAlias instance associated with the same
physical entity for as long as that entity remains If write access is implemented for an instance of
instantiated, including across all re- entPhysicalAlias, and a value is written into the instance,
initializations/reboots of the network management system, the agent must retain the supplied value in the
including those which result in a change of the physical entPhysicalAlias instance associated with the same physical
entity's entPhysicalIndex value." entity for as long as that entity remains instantiated,
including across all re-initializations/reboots of the
network management system, including those which result in a
change of the physical entity's entPhysicalIndex value."
::= { entPhysicalXEntry 1 } ::= { entPhysicalXEntry 1 }
-- conformance information -- conformance information
-- compliance statements -- compliance statements
entityXCompliance MODULE-COMPLIANCE entityXCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SNMP entities which implement "The compliance statement for SNMP entities which implement
Draft Entity MIB Extensions September 1997
the entPhysicalXTable Entity MIB extension." the entPhysicalXTable Entity MIB extension."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
entityPhysicalGroup, entityPhysicalGroup,
entityPhysicalXGroup entityPhysicalXGroup
} }
OBJECT entPhysicalAlias
MIN-ACCESS read-only
DESCRIPTION
"Write access is required if the associated
entPhysicalClass value is equal to 'chassis(3)'.
Otherwise, write access is not required."
::= { entityCompliances 2 } ::= { entityCompliances 2 }
-- MIB groupings -- MIB groupings
entityPhysicalXGroup OBJECT-GROUP entityPhysicalXGroup OBJECT-GROUP
OBJECTS { OBJECTS {
entPhysicalAlias entPhysicalAlias
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
Draft Entity MIB Extensions July 1997
"The collection of objects which are used to represent "The collection of objects which are used to represent
extended physical topology information for which a single extended physical component information for which a single
agent provides management information." agent provides management information."
::= { entityGroups 5 } ::= { entityGroups 5 }
END END
Draft Entity MIB Extensions July 1997 Draft Entity MIB Extensions September 1997
5. References 5. References
[1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
S. Waldbusser, "Structure of Management Information for version 2 S. Waldbusser, "Structure of Management Information for version 2
of the Simple Network Management Protocol (SNMPv2)", RFC 1902, of the Simple Network Management Protocol (SNMPv2)", RFC 1902,
January 1996. January 1996.
[2] McCloghrie, K., and M. Rose, Editors, "Management Information Base [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base
for Network Management of TCP/IP-based internets: MIB-II", STD 17, for Network Management of TCP/IP-based internets: MIB-II", STD 17,
skipping to change at page 8, line 5 skipping to change at page 7, line 37
S. Waldbusser, "Conformance Statements for version 2 of the Simple S. Waldbusser, "Conformance Statements for version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC 1904, January 1996. Network Management Protocol (SNMPv2)", RFC 1904, January 1996.
[6] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network [6] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network
Management Protocol", RFC 1157, SNMP Research, Performance Systems Management Protocol", RFC 1157, SNMP Research, Performance Systems
International, MIT Laboratory for Computer Science, May 1990. International, MIT Laboratory for Computer Science, May 1990.
[7] McCloghrie, K., Bierman, A., "Entity MIB using SMIv2", RFC 2037, [7] McCloghrie, K., Bierman, A., "Entity MIB using SMIv2", RFC 2037,
Cisco Systems, October 1996. Cisco Systems, October 1996.
Draft Entity MIB Extensions July 1997 [8] McCloghrie, K., and Kastenholtz, F., "Interfaces Group Evolution",
RFC 1573, Hughes LAN Systems, FTP Software, January 1994.
[9] Harrington D., Wijnen, A., "An Architecture for Describing SNMP
Management Frameworks", draft-ietf-snmpv3-next-gen-arch-04.txt,
Cabletron Systems, IBM T.J. Watson Research, August 1997.
Draft Entity MIB Extensions September 1997
6. Security Considerations 6. Security Considerations
Security issues are not discussed in this memo. No additional security concerns are introduced due to implementation of
this MIB module. Refer to RFC 2037 [7] for information on any security
issues related to the Entity MIB.
7. Author's Address 7. Author's Address
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
Phone: 408-527-3711 Phone: 408-527-3711
Email: abierman@cisco.com 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 San Jose, CA 95134
Phone: 408-526-5260 Phone: 408-526-5260
Email: kzm@cisco.com Email: kzm@cisco.com
Draft Entity MIB Extensions July 1997 Draft Entity MIB Extensions September 1997
Table of Contents Table of Contents
1 Introduction .................................................... 1 1 Introduction .................................................... 1
2 The SNMP Network Management Framework ........................... 2 2 The SNMP Network Management Framework ........................... 2
2.1 Object Definitions ............................................ 2 2.1 Object Definitions ............................................ 2
3 Overview ........................................................ 2 3 Overview ........................................................ 2
4 Entity MIB Extensions ........................................... 3 4 Entity MIB Extensions ........................................... 3
4.1 MIB Structure ................................................. 3 4.1 MIB Structure ................................................. 3
4.1.1 Entity Physical Extensions Group ............................ 3 4.1.1 Entity Physical Extensions Group ............................ 3
 End of changes. 25 change blocks. 
40 lines changed or deleted 78 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/