< draft-ietf-entmib-v2-05.txt   draft-ietf-entmib-v2-06.txt >
Entity MIB Working Group Keith McCloghrie Entity MIB Working Group Keith McCloghrie
Internet Draft Cisco Systems, Inc. Internet Draft Cisco Systems, Inc.
Andy Bierman Andy Bierman
Cisco Systems, Inc. Cisco Systems, Inc.
24 June 1999 22 August 1999
Entity MIB (Version 2) Entity MIB (Version 2)
<draft-ietf-entmib-v2-05.txt> <draft-ietf-entmib-v2-06.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 ?
5.1 Terms ......................................................... 5 5.1 Terms ......................................................... 5
5.2 Relationship to Community Strings ............................. 6 5.2 Relationship to Community Strings ............................. 6
5.3 Relationship to SNMP Contexts ................................. 6 5.3 Relationship to SNMP Contexts ................................. 6
5.4 Relationship to Proxy Mechanisms .............................. 7 5.4 Relationship to Proxy Mechanisms .............................. 7
5.5 Relationship to a Chassis MIB ................................. 7 5.5 Relationship to a Chassis MIB ................................. 7
5.6 Relationship to the Interfaces MIB ............................ 7 5.6 Relationship to the Interfaces MIB ............................ 7
5.7 Relationship to the Other MIBs ................................ 8 5.7 Relationship to the Other MIBs ................................ 8
5.8 Relationship to Naming Scopes ................................. 8 5.8 Relationship to Naming Scopes ................................. 8
5.9 Multiple Instances of the Entity MIB .......................... 8 5.9 Multiple Instances of the Entity MIB .......................... 8
5.10 Re-Configuration of Entities ................................. 9 5.10 Re-Configuration of Entities ................................. 9
5.11 MIB Structure ................................................ 9 5.11 Textual Convention Change .................................... 9
5.11.1 entityPhysical Group ....................................... 10 5.12 MIB Structure ................................................ 10
5.11.2 entityLogical Group ........................................ 11 5.12.1 entityPhysical Group ....................................... 10
5.11.3 entityMapping Group ........................................ 11 5.12.2 entityLogical Group ........................................ 11
5.11.4 entityGeneral Group ........................................ 12 5.12.3 entityMapping Group ........................................ 11
5.11.5 entityNotifications Group .................................. 12 5.12.4 entityGeneral Group ........................................ 12
5.12 Multiple Agents .............................................. 12 5.12.5 entityNotifications Group .................................. 12
5.13 Change Log ................................................... 12 5.13 Multiple Agents .............................................. 12
5.13.1 Version 00 ................................................. 13 5.14 Change Log ................................................... 13
5.13.2 Version 01 ................................................. 13 5.14.1 Version 00 ................................................. 13
5.13.3 Version 02 ................................................. 14 5.14.2 Version 01 ................................................. 14
5.13.4 Version 03 ................................................. 14 5.14.3 Version 02 ................................................. 14
5.13.5 Version 04 ................................................. 14 5.14.4 Version 03 ................................................. 14
5.13.6 Version 05 ................................................. 15 5.14.5 Version 04 ................................................. 15
5.14.6 Version 05 ................................................. 15
5.14.7 Version 06 ................................................. 15
6 Definitions ..................................................... 16 6 Definitions ..................................................... 16
7 Usage Examples .................................................. 44 7 Usage Examples .................................................. 44
7.1 Router/Bridge ................................................. 44 7.1 Router/Bridge ................................................. 44
7.2 Repeaters ..................................................... 50 7.2 Repeaters ..................................................... 50
8 Intellectual Property ........................................... 58 8 Intellectual Property ........................................... 58
9 Acknowledgements ................................................ 58 9 Acknowledgements ................................................ 58
10 References ..................................................... 58 10 References ..................................................... 58
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
skipping to change at page 9, line 32 skipping to change at page 9, line 32
represents the MIB in different naming scopes. represents the MIB in different naming scopes.
5.10. Re-Configuration of Entities 5.10. Re-Configuration of Entities
Most of the MIB objects defined in this MIB have at most a read-only Most of the MIB objects defined in this MIB have at most a read-only
MAX-ACCESS clause. This is a conscious decision by the working group to MAX-ACCESS clause. This is a conscious decision by the working group to
limit this MIB's scope. The second version of the Entity MIB allows a limit this MIB's scope. The second version of the Entity MIB allows a
network administrator to configure some common attributes of physical network administrator to configure some common attributes of physical
components. components.
5.11. MIB Structure 5.11. Textual Convention Change
Version 1 of the Entity MIB contains three MIB objects defined with the
(now obsolete) DisplayString textual convention. In version 2 of the
Entity MIB, the syntax for these objects has been updated to use the
(now preferred) SnmpAdminString textual convention.
The working group realizes that this change is not strictly supported by
SMIv2. In our judgment, the alternative of deprecating the old objects
and defining new objects would have a more adverse impact on backward
compatibility and interoperability, given the particular semantics of
these objects.
5.12. MIB Structure
The Entity MIB contains five groups of MIB objects: The Entity MIB contains five groups of MIB objects:
- entityPhysical group - entityPhysical group
Describes the physical entities managed by a single agent. Describes the physical entities managed by a single agent.
- entityLogical group - entityLogical group
Describes the logical entities managed by a single agent. Describes the logical entities managed by a single agent.
- entityMapping group - entityMapping group
skipping to change at page 10, line 12 skipping to change at page 10, line 27
entities, interfaces, and non-interface ports managed by a single entities, interfaces, and non-interface ports managed by a single
agent. agent.
- entityGeneral group - entityGeneral group
Describes general system attributes shared by potentially all types Describes general system attributes shared by potentially all types
of entities managed by a single agent. of entities managed by a single agent.
- entityNotifications group - entityNotifications group
Contains status indication notifications. Contains status indication notifications.
5.11.1. entityPhysical Group 5.12.1. entityPhysical Group
This group contains a single table to identify physical system This group contains a single table to identify physical system
components, called the entPhysicalTable. components, called the entPhysicalTable.
The entPhysicalTable contains one row per physical entity, and must The entPhysicalTable contains one row per physical entity, and must
always contain at least one row for an "overall" physical entity, which always contain at least one row for an "overall" physical entity, which
should have an entPhysicalClass value of 'stack(11)', 'chassis(3)' or should have an entPhysicalClass value of 'stack(11)', 'chassis(3)' or
'module(9)'. 'module(9)'.
Each row is indexed by an arbitrary, small integer, and contains a Each row is indexed by an arbitrary, small integer, and contains a
skipping to change at page 11, line 10 skipping to change at page 11, line 24
contained within another physical entity). contained within another physical entity).
- entPhysicalSerialNum - entPhysicalSerialNum
This string is provided to store a vendor-specific serial number This string is provided to store a vendor-specific serial number
string for physical components. This is a writable object in case string for physical components. This is a writable object in case
an agent cannot identify the serial numbers of all installed an agent cannot identify the serial numbers of all installed
physical entities, and a network administrator wishes to configure physical entities, and a network administrator wishes to configure
the non-volatile serial number strings manually (via an NMS the non-volatile serial number strings manually (via an NMS
application). application).
5.11.2. entityLogical Group 5.12.2. entityLogical Group
This group contains a single table to identify logical entities, called This group contains a single table to identify logical entities, called
the entLogicalTable. the entLogicalTable.
The entLogicalTable contains one row per logical entity. Each row is The entLogicalTable contains one row per logical entity. Each row is
indexed by an arbitrary, small integer and contains a name, description, indexed by an arbitrary, small integer and contains a name, description,
and type of the logical entity. It also contains information to allow and type of the logical entity. It also contains information to allow
access to the MIB information for the logical entity. This includes SNMP access to the MIB information for the logical entity. This includes SNMP
versions that use a community name (with some form of implied context versions that use a community name (with some form of implied context
representation) and SNMP versions that use the SNMP ARCH [RFC2571] representation) and SNMP versions that use the SNMP ARCH [RFC2571]
method of context identification. method of context identification.
If a agent represents multiple logical entities with this MIB, then this If a agent represents multiple logical entities with this MIB, then this
group must be implemented for all logical entities known to the agent. group must be implemented for all logical entities known to the agent.
If an agent represents a single logical entity, or multiple logical If an agent represents a single logical entity, or multiple logical
entities within a single naming scope, then implementation of this group entities within a single naming scope, then implementation of this group
may be omitted by the agent. may be omitted by the agent.
5.11.3. entityMapping Group 5.12.3. entityMapping Group
This group contains three tables to identify associations between This group contains three tables to identify associations between
different system components. different system components.
The entLPMappingTable contains mappings between entLogicalIndex values The entLPMappingTable contains mappings between entLogicalIndex values
(logical entities) and entPhysicalIndex values (the physical components (logical entities) and entPhysicalIndex values (the physical components
supporting that entity). A logical entity can map to more than one supporting that entity). A logical entity can map to more than one
physical component, and more than one logical entity can map to (share) physical component, and more than one logical entity can map to (share)
the same physical component. If an agent represents a single logical the same physical component. 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
skipping to change at page 12, line 14 skipping to change at page 12, line 28
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.
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.
5.11.4. entityGeneral Group 5.12.4. entityGeneral Group
This group contains general information relating to the other object This group contains general information relating to the other object
groups. groups.
At this time, the entGeneral group contains a single scalar object At this time, the entGeneral group contains a single scalar object
(entLastChangeTime), which represents the value of sysUptime when any (entLastChangeTime), which represents the value of sysUptime when any
part of the Entity MIB configuration last changed. part of the Entity MIB configuration last changed.
5.11.5. entityNotifications Group 5.12.5. entityNotifications Group
This group contains notification definitions relating to the overall This group contains notification definitions relating to the overall
status of the Entity MIB instantiation. status of the Entity MIB instantiation.
5.12. Multiple Agents 5.13. Multiple Agents
Even though a primary motivation for this MIB is to represent the Even though a primary motivation for this MIB is to represent the
multiple logical entities supported by a single agent, it is also multiple logical entities supported by a single agent, it is also
possible to use it to represent multiple logical entities supported by possible to use it to represent multiple logical entities supported by
multiple agents (in the same "overall" physical entity). Indeed, it is multiple agents (in the same "overall" physical entity). Indeed, it is
implicit in the SNMP architecture, that the number of agents is implicit in the SNMP architecture, that the number of agents is
transparent to a network management station. transparent to a network management station.
However, there is no agreement at this time as to the degree of However, there is no agreement at this time as to the degree of
cooperation which should be expected for agent implementations. cooperation which should be expected for agent implementations.
Therefore, multiple agents within the same managed system are free to Therefore, multiple agents within the same managed system are free to
implement the Entity MIB independently. (Refer the section on "Multiple implement the Entity MIB independently. (Refer the section on "Multiple
Instances of the Entity MIB" for more details). Instances of the Entity MIB" for more details).
5.13. Change Log 5.14. Change Log
The following changes have been made since publication of the original The following changes have been made since publication of the original
Entity MIB [RFC2037]. Entity MIB [RFC2037].
5.13.1. Version 00 5.14.1. Version 00
- Clarified description of the PhysicalClass textual convention. - Clarified description of the PhysicalClass textual convention.
Added a new enumeration. Added a new enumeration.
- Added RevisionString and SnmpEngineIdOrZero textual conventions to - Added RevisionString and SnmpEngineIdOrZero textual conventions to
support new entPhysicalTable and entLogicalTable objects support new entPhysicalTable and entLogicalTable objects
- Fixed bug in entPhysicalParentRelPos DESCRIPTION clause - Fixed bug in entPhysicalParentRelPos DESCRIPTION clause
- Added entPhysicalHardwareRev, FirmwareRev, and SoftwareRev objects - Added entPhysicalHardwareRev, FirmwareRev, and SoftwareRev objects
skipping to change at page 13, line 39 skipping to change at page 14, line 5
incorrect (1..255) and is now (0..255). The description clause has incorrect (1..255) and is now (0..255). The description clause has
also been clarified. This object is now deprecated. also been clarified. This object is now deprecated.
- Added entLogicalContextEngineID and entLogicalContextName objects - Added entLogicalContextEngineID and entLogicalContextName objects
to provide an SNMP context for SNMPv3 access on behalf of a logical to provide an SNMP context for SNMPv3 access on behalf of a logical
entity. entity.
- Changed entLastChangeTime object description to generalize the - Changed entLastChangeTime object description to generalize the
events which cause an update to the last change timestamp. events which cause an update to the last change timestamp.
5.13.2. Version 01 5.14.2. Version 01
- Removed the RevisionString TC. - Removed the RevisionString TC.
- Changed the entPhysicalHardwareRev, entPhysicalFirmwareRev, and - Changed the entPhysicalHardwareRev, entPhysicalFirmwareRev, and
entPhysicalSoftwareRev SYNTAX from RevisionString to entPhysicalSoftwareRev SYNTAX from RevisionString to
SnmpAdminString SnmpAdminString
- Made logical entity objects optional for agents with a single - Made logical entity objects optional for agents with a single
'default naming scope' 'default naming scope'
- Fixed conformance section bugs - Fixed conformance section bugs
- Clarified containment rules for removable physical components - Clarified containment rules for removable physical components
5.13.3. Version 02 5.14.3. Version 02
- Added term definition for 'parent entity'. - Added term definition for 'parent entity'.
- Added entPhysicalIsFRU object. - Added entPhysicalIsFRU object.
- Clarify modeling double-high modules. - Clarify modeling double-high modules.
- Clarify scope of some entPhysicalEntry attributes. - Clarify scope of some entPhysicalEntry attributes.
- Clarify instantiation guidelines of some entPhysicalTable strings. - Clarify instantiation guidelines of some entPhysicalTable strings.
- Fix typos and deleted some obsolete intro text. - Fix typos and deleted some obsolete intro text.
- Relax trap throttling requirement from 'must' to 'should'. - Relax trap throttling requirement from 'must' to 'should'.
- Change instances of the term 'trap' to 'notification', to align - Change instances of the term 'trap' to 'notification', to align
with SNMPv3 terminology. with SNMPv3 terminology.
- Update Usage Examples section for Version 2 objects. - Update Usage Examples section for Version 2 objects.
5.13.4. Version 03 5.14.4. Version 03
- Added REVISION clauses to the MIB. - Added REVISION clauses to the MIB.
- Removed language allowing an agent to omit certain SnmpAdminString - Removed language allowing an agent to omit certain SnmpAdminString
based MIB instances. A zero-length string string must be returned based MIB instances. A zero-length string string must be returned
instead. instead.
- Updated I-D boilerplate. - Updated I-D boilerplate.
- Updated reference identification format. - Updated reference identification format.
5.13.5. Version 04 5.14.5. Version 04
- Updated SNMP boilerplate and references. - Updated SNMP boilerplate and references.
- Changed 'main' naming scope to 'default' naming scope to be more - Changed 'main' naming scope to 'default' naming scope to be more
consistent with SNMPv3 default context. consistent with SNMPv3 default context.
- Removed the 'in-progress' REVISION clauses from the MIB. - Removed the 'in-progress' REVISION clauses from the MIB.
- Updated Security Considerations section. - Updated Security Considerations section.
- Clarified some text regarding specific versions of SNMP. - Clarified some text regarding specific versions of SNMP.
5.13.6. Version 05 5.14.6. Version 05
- Shortened the document title. - Shortened the document title.
- Renamed the SnmpEngineIdOrZero TC to be SnmpEngineIdOrNone. - Renamed the SnmpEngineIdOrZero TC to be SnmpEngineIdOrNone.
- Changed the entLogicalContextEngineID SYNTAX to SnmpEngineIdOrNone. - Changed the entLogicalContextEngineID SYNTAX to SnmpEngineIdOrNone.
- Clarified description of the SnmpEngineIdOrNone TC for zero-length - Clarified description of the SnmpEngineIdOrNone TC for zero-length
strings. strings.
5.14.7. Version 06
- Changed syntax from DisplayString to SnmpAdminString for the
entPhysicalDescr, entPhysicalName, and entLogicalDescr objects.
- Removed DisplayString from the IMPORTS clause.
- Added 'Textual Convention Change' section, which documents this
change.
6. Definitions 6. 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
FROM SNMPv2-SMI FROM SNMPv2-SMI
TDomain, TAddress, DisplayString, 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 "9906230000Z" LAST-UPDATED "9908220000Z"
ORGANIZATION "IETF ENTMIB Working Group" ORGANIZATION "IETF ENTMIB Working Group"
CONTACT-INFO CONTACT-INFO
" WG E-mail: entmib@cisco.com " WG E-mail: entmib@cisco.com
Subscribe: majordomo@cisco.com Subscribe: majordomo@cisco.com
msg body: subscribe entmib msg body: subscribe entmib
Keith McCloghrie Keith McCloghrie
ENTMIB Working Group Chair ENTMIB Working Group Chair
Cisco Systems Inc. Cisco Systems Inc.
170 West Tasman Drive 170 West Tasman Drive
skipping to change at page 16, line 46 skipping to change at page 16, line 46
Andy Bierman Andy Bierman
ENTMIB Working Group Editor ENTMIB Working Group Editor
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-527-3711
abierman@cisco.com" abierman@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 "9906230000Z" REVISION "9908220000Z"
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 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."
skipping to change at page 20, line 27 skipping to change at page 20, line 27
entPhysicalVendorType, and entPhysicalClass) to help an NMS entPhysicalVendorType, and entPhysicalClass) to help an NMS
identify and characterize the entry, and objects identify and characterize the entry, and objects
(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 DisplayString, entPhysicalDescr SnmpAdminString,
entPhysicalVendorType AutonomousType, entPhysicalVendorType AutonomousType,
entPhysicalContainedIn INTEGER, entPhysicalContainedIn INTEGER,
entPhysicalClass PhysicalClass, entPhysicalClass PhysicalClass,
entPhysicalParentRelPos INTEGER, entPhysicalParentRelPos INTEGER,
entPhysicalName DisplayString, 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,
entPhysicalAssetID SnmpAdminString, entPhysicalAssetID SnmpAdminString,
entPhysicalIsFRU TruthValue entPhysicalIsFRU TruthValue
} }
entPhysicalIndex OBJECT-TYPE entPhysicalIndex OBJECT-TYPE
SYNTAX PhysicalIndex SYNTAX PhysicalIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The index for this entry." "The index for this entry."
::= { entPhysicalEntry 1 } ::= { entPhysicalEntry 1 }
entPhysicalDescr OBJECT-TYPE entPhysicalDescr OBJECT-TYPE
SYNTAX DisplayString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A textual description of physical entity. This object "A textual description of physical entity. This object
should contain a string which identifies the manufacturer's should contain a string which identifies the manufacturer's
name for the physical entity, and should be set to a name for the physical entity, and should be set to a
distinct value for each version or model of the physical distinct value for each version or model of the physical
entity. " entity. "
::= { entPhysicalEntry 2 } ::= { entPhysicalEntry 2 }
skipping to change at page 23, line 45 skipping to change at page 23, line 45
each 'parent' component may use different numbering each 'parent' component may use different numbering
algorithms. The ordering is only meaningful among siblings algorithms. The ordering is only meaningful among siblings
of the same parent component. of the same parent component.
The agent should retain parent-relative position values The agent should retain parent-relative position values
across reboots, either through algorithmic assignment or use across reboots, either through algorithmic assignment or use
of non-volatile storage." of non-volatile storage."
::= { entPhysicalEntry 6 } ::= { entPhysicalEntry 6 }
entPhysicalName OBJECT-TYPE entPhysicalName OBJECT-TYPE
SYNTAX DisplayString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The textual name of the physical entity. The value of this "The textual name of the physical entity. The value of this
object should be the name of the component as assigned by object should be the name of the component as assigned by
the local device and should be suitable for use in commands the local device and should be suitable for use in commands
entered at the device's `console'. This might be a text entered at the device's `console'. This might be a text
name, such as `console' or a simple component number (e.g., name, such as `console' or a simple component number (e.g.,
port or module number), such as `1', depending on the port or module number), such as `1', depending on the
physical component naming syntax of the device. physical component naming syntax of the device.
skipping to change at page 29, line 33 skipping to change at page 29, line 33
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about a particular logical entity. Entities "Information about a particular logical entity. Entities
may be managed by this agent or other SNMP agents (possibly) may be managed by this agent or other SNMP agents (possibly)
in the same chassis." in the same chassis."
INDEX { entLogicalIndex } INDEX { entLogicalIndex }
::= { entLogicalTable 1 } ::= { entLogicalTable 1 }
EntLogicalEntry ::= SEQUENCE { EntLogicalEntry ::= SEQUENCE {
entLogicalIndex INTEGER, entLogicalIndex INTEGER,
entLogicalDescr DisplayString, entLogicalDescr SnmpAdminString,
entLogicalType AutonomousType, entLogicalType AutonomousType,
entLogicalCommunity OCTET STRING, entLogicalCommunity OCTET STRING,
entLogicalTAddress TAddress, entLogicalTAddress TAddress,
entLogicalTDomain TDomain, entLogicalTDomain TDomain,
entLogicalContextEngineID SnmpEngineIdOrNone, entLogicalContextEngineID SnmpEngineIdOrNone,
entLogicalContextName SnmpAdminString entLogicalContextName SnmpAdminString
} }
entLogicalIndex OBJECT-TYPE entLogicalIndex OBJECT-TYPE
SYNTAX INTEGER (1..2147483647) SYNTAX INTEGER (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object uniquely identifies the logical "The value of this object uniquely identifies the logical
entity. The value should be a small positive integer; index entity. The value should be a small positive integer; index
values for different logical entities are are not values for different logical entities are are not
necessarily contiguous." necessarily contiguous."
::= { entLogicalEntry 1 } ::= { entLogicalEntry 1 }
entLogicalDescr OBJECT-TYPE entLogicalDescr OBJECT-TYPE
SYNTAX DisplayString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A textual description of the logical entity. This object "A textual description of the logical entity. This object
should contain a string which identifies the manufacturer's should contain a string which identifies the manufacturer's
name for the logical entity, and should be set to a distinct name for the logical entity, and should be set to a distinct
value for each version of the logical entity. " value for each version of the logical entity. "
::= { entLogicalEntry 2 } ::= { entLogicalEntry 2 }
entLogicalType OBJECT-TYPE entLogicalType OBJECT-TYPE
 End of changes. 27 change blocks. 
39 lines changed or deleted 64 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/