draft-ietf-entmib-entmib-04.txt   draft-ietf-entmib-entmib-05.txt 
<draft-ietf-entmib-entmib-04.txt> | <draft-ietf-entmib-entmib-05.txt>
Entity MIB Entity MIB
20 May 1996 | 29 May 1996
Keith McCloghrie Keith McCloghrie
Cisco Systems Inc. Cisco Systems Inc.
kzm@cisco.com kzm@cisco.com
Andy Bierman Andy Bierman
Cisco Systems Inc. Cisco Systems Inc.
abierman@cisco.com abierman@cisco.com
Status of this Memo Status of this Memo
skipping to change at page 3, line 22 skipping to change at page 3, line 22
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
for the Internet suite of protocols. for the Internet suite of protocols.
o the protocol, RFC 1157 [6] and/or RFC 1905 [4], - the protocol for o the protocol, RFC 1157 [6] and/or RFC 1905 [4], - the protocol for
accessing managed information. accessing managed information.
Textual conventions are defined in RFC 1903 [3], and conformance Textual conventions are defined in RFC 1903 [3], and conformance
statements are defined in RFC 1905 [5]. statements are defined in RFC 1904 [5].
The Framework permits new objects to be defined for the purpose of The Framework permits new objects to be defined for the purpose of
experimentation and evaluation. experimentation and evaluation.
2.1. Object Definitions 2.1. Object Definitions
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. Objects in the MIB are defined Management Information Base or MIB. Objects in the MIB are defined
using the subset of Abstract Syntax Notation One (ASN.1) defined in the using the subset of Abstract Syntax Notation One (ASN.1) defined in the
SMI. In particular, each object type is named by an OBJECT IDENTIFIER, SMI. In particular, each object type is named by an OBJECT IDENTIFIER,
skipping to change at page 6, line 7 skipping to change at page 6, line 7
within another physical component. A "containment-tree" is the within another physical component. A "containment-tree" is the
conceptual sequence of entPhysicalIndex values which uniquely conceptual sequence of entPhysicalIndex values which uniquely
specifies the exact physical location of a physical component specifies the exact physical location of a physical component
within the managed system. It is generated by 'following and within the managed system. It is generated by 'following and
recording' each 'entPhysicalContainedIn' instance 'up the tree recording' each 'entPhysicalContainedIn' instance 'up the tree
towards the root', until a value of zero indicating no further towards the root', until a value of zero indicating no further
containment is found. containment is found.
Draft Entity MIB May 1996 Draft Entity MIB May 1996
Note that chassis slots, which are capable of accepting one or more - Note that chassis slots, which are capable of accepting one or more
module types from one or more vendors, are modeled as containers in module types from one or more vendors, are modeled as containers in
this MIB. The value of entPhysicalContainedIn for a particular this MIB. The value of entPhysicalContainedIn for a particular
'module' entity (entPhysicalClass value of 'module(9)') should be 'module' entity (entPhysicalClass value of 'module(9)') should be
equal to an entPhysicalIndex that represents the parent 'container' equal to an entPhysicalIndex that represents the parent 'container'
entity (associated entPhysicalClass value of ('container(5)'). An entity (associated entPhysicalClass value of ('container(5)'). An
agent should represent both empty and full containers in the agent should represent both empty and full containers in the
entPhysicalTable. entPhysicalTable.
3.2. Relationship to Community Strings 3.2. Relationship to Community Strings
skipping to change at page 7, line 28 skipping to change at page 7, line 28
3.5. Relationship to the Interfaces MIB 3.5. Relationship to the Interfaces MIB
The Entity MIB contains a mapping table identifying physical components The Entity MIB contains a mapping table identifying physical components
that have 'external values' (e.g. ifIndex) associated with them within a that have 'external values' (e.g. ifIndex) associated with them within a
given naming scope. This table can be used to identify the physical given naming scope. This table can be used to identify the physical
location of each interface in the ifTable [7]. Since ifIndex values in location of each interface in the ifTable [7]. Since ifIndex values in
different contexts are not related to one another, the interface to different contexts are not related to one another, the interface to
physical component associations are relative to the same logical entity physical component associations are relative to the same logical entity
within the agent. within the agent.
The Entity MIB also contains an 'entPhysicalName' object, which extends + The Entity MIB also contains an 'entPhysicalName' object, which extends
the semantics of the ifName object from the Interfaces MIB [7] to all + the semantics of the ifName object from the Interfaces MIB [7] to all
types of physical components. + types of physical components.
3.6. Relationship to the Other MIBs 3.6. Relationship to the Other MIBs
The Entity MIB contains a mapping table identifying physical components The Entity MIB contains a mapping table identifying physical components
that have identifiers from other standard MIBs associated with them. that have identifiers from other standard MIBs associated with them.
For example, this table can be used along with the physical mapping For example, this table can be used along with the physical mapping
table to identify the physical location of each repeater port in the table to identify the physical location of each repeater port in the
rptrPortTable, or each interface in the ifTable. rptrPortTable, or each interface in the ifTable.
3.7. Relationship to Naming Scopes 3.7. Relationship to Naming Scopes
skipping to change at page 9, line 9 skipping to change at page 9, line 9
ACCESS clause, i.e., none are write-able. This is another conscious ACCESS clause, i.e., none are write-able. This is another conscious
decision by the authors to limit this MIB's scope. It is possible that decision by the authors to limit this MIB's scope. It is possible that
this restriction could be lifted after implementation experience, and this restriction could be lifted after implementation experience, and
additional tables (using the AUGMENTS clause) added for configuration additional tables (using the AUGMENTS clause) added for configuration
and extended entity information. and extended entity information.
Draft Entity MIB May 1996 Draft Entity MIB May 1996
3.10. MIB Structure 3.10. MIB Structure
The Entity MIB contains four groups: + The Entity MIB contains four groups:
- 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
Describes the associations between the physical entities, logical | Describes the associations between the physical entities, logical
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.
3.10.1. entityPhysical Group | 3.10.1. entityPhysical Group
This group contains a single table to identify system components, called | This group contains a single table to identify system components, called
the entPhysicalTable. | the entPhysicalTable.
The entPhysicalTable contains one row per physical entity, and must | The entPhysicalTable contains one row per physical entity, and must
always contains at least one row for an "overall" physical entity. Each always contains at least one row for an "overall" physical entity. Each
row is indexed by an arbitrary, small integer, and contains a row is indexed by an arbitrary, small integer, and contains a
description and type of the physical entity. It also optionally description and type of the physical entity. It also optionally
contains the index number of another entPhysicalEntry indicating a contains the index number of another entPhysicalEntry indicating a
containment relationship between the two. containment relationship between the two.
3.10.2. entityLogical Group 3.10.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
SNMPv1 or SNMPv2C [9] access to the MIB information for the logical | SNMPv1 or SNMPv2C [9] access to the MIB information for the logical
entity. entity.
Draft Entity MIB May 1996 Draft Entity MIB May 1996
3.10.3. entityMapping Group 3.10.3. entityMapping Group
This group contains a three tables to identify associations between + This group contains a 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. the same physical component.
The entAliasMappingTable contains mappings between entLogicalIndex, The entAliasMappingTable contains mappings between entLogicalIndex,
entPhysicalIndex pairs and 'alias' object identifier values. This entPhysicalIndex pairs and 'alias' object identifier values. This
allows resources managed with other MIBs (e.g. repeater ports, bridge allows resources managed with other MIBs (e.g. repeater ports, bridge
skipping to change at page 10, line 33 skipping to change at page 10, line 33
particular naming scope. particular naming scope.
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.
3.10.4. entityGeneral Group 3.10.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 system configuration last changed. + part of the system configuration last changed.
3.11. Multiple Agents 3.11. 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
Draft Entity MIB May 1996 Draft Entity MIB May 1996
skipping to change at page 12, line 15 skipping to change at page 12, line 15
Draft Entity MIB May 1996 Draft Entity MIB May 1996
4. Definitions 4. Definitions
ENTITY-MIB DEFINITIONS ::= BEGIN ENTITY-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
experimental, NOTIFICATION-TYPE experimental, NOTIFICATION-TYPE
FROM SNMPv2-SMI FROM SNMPv2-SMI
TDomain, TAddress, DisplayString, TDomain, TAddress, DisplayString, TEXTUAL-CONVENTION,
AutonomousType, TruthValue, RowPointer, TimeStamp | AutonomousType, RowPointer, TimeStamp
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF; FROM SNMPv2-CONF;
entityMIB MODULE-IDENTITY entityMIB MODULE-IDENTITY
LAST-UPDATED "9605160000Z" | LAST-UPDATED "9605160000Z"
ORGANIZATION "IETF ENTMIB Working Group" ORGANIZATION "IETF ENTMIB Working Group"
CONTACT-INFO CONTACT-INFO
" Keith McCloghrie " WG E-mail: entmib@cisco.com
Subscribe: majordomo@cisco.com
msg body: subscribe entmib
Keith McCloghrie
ENTMIB Working Group Chair ENTMIB Working Group Chair
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
Andy Bierman Andy Bierman
ENTMIB Working Group Editor ENTMIB Working Group Editor
Cisco Systems Inc. Cisco Systems Inc.
skipping to change at page 12, line 47 skipping to change at page 12, line 51
San Jose, CA 95134 San Jose, CA 95134
408-527-3711 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."
::= { experimental xx } ::= { experimental xx }
entityMIBObjects OBJECT IDENTIFIER ::= { entityMIB 1 } entityMIBObjects OBJECT IDENTIFIER ::= { entityMIB 1 }
entityPhysical OBJECT IDENTIFIER ::= { entityMIBObjects 1 } + -- MIB contains four groups
entityLogical OBJECT IDENTIFIER ::= { entityMIBObjects 2 } +
entityMapping OBJECT IDENTIFIER ::= { entityMIBObjects 3 } +
entityGeneral OBJECT IDENTIFIER ::= { entityMIBObjects 4 } +
Draft Entity MIB May 1996 Draft Entity MIB May 1996
PhysicalIndex ::= TEXTUAL-CONVENTION + entityPhysical OBJECT IDENTIFIER ::= { entityMIBObjects 1 }
STATUS current + entityLogical OBJECT IDENTIFIER ::= { entityMIBObjects 2 }
DESCRIPTION + entityMapping OBJECT IDENTIFIER ::= { entityMIBObjects 3 }
"An arbitrary value which uniquely identifies the physical + entityGeneral OBJECT IDENTIFIER ::= { entityMIBObjects 4 }
entity. The value is a small positive integer; index values +
for different physical entities are not necessarily + -- Textual Conventions
contiguous." + PhysicalIndex ::= TEXTUAL-CONVENTION
SYNTAX INTEGER (1..2147483647) + STATUS current
DESCRIPTION
"An arbitrary value which uniquely identifies the physical
entity. The value is a small positive integer; index values
for different physical entities are not necessarily
contiguous."
SYNTAX INTEGER (1..2147483647)
Draft Entity MIB May 1996 Draft Entity MIB May 1996
-- The Physical Entity Table -- The Physical Entity Table
entPhysicalTable OBJECT-TYPE entPhysicalTable OBJECT-TYPE
SYNTAX SEQUENCE OF EntPhysicalEntry SYNTAX SEQUENCE OF EntPhysicalEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains one row per physical entity. There is "This table contains one row per physical entity. There is
always at least one row for an 'overall' physical entity." always at least one row for an 'overall' physical entity."
::= { entityPhysical 1 } | ::= { entityPhysical 1 }
entPhysicalEntry OBJECT-TYPE entPhysicalEntry OBJECT-TYPE
SYNTAX EntPhysicalEntry SYNTAX EntPhysicalEntry
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 objects (entPhysicalDescr, + Each entry provides objects (entPhysicalDescr,
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 INTEGER, entPhysicalIndex PhysicalIndex,
entPhysicalDescr DisplayString, entPhysicalDescr DisplayString,
entPhysicalVendorType AutonomousType, entPhysicalVendorType AutonomousType,
entPhysicalContainedIn INTEGER, entPhysicalContainedIn INTEGER,
entPhysicalClass INTEGER, entPhysicalClass INTEGER,
entPhysicalParentRelPos INTEGER, | entPhysicalParentRelPos INTEGER,
entPhysicalName DisplayString | entPhysicalName DisplayString
} }
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 }
Draft Entity MIB May 1996 Draft Entity MIB May 1996
entPhysicalDescr OBJECT-TYPE entPhysicalDescr OBJECT-TYPE
SYNTAX DisplayString SYNTAX DisplayString
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 }
entPhysicalVendorType OBJECT-TYPE entPhysicalVendorType OBJECT-TYPE
SYNTAX AutonomousType SYNTAX AutonomousType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An indication of the vendor-specific hardware type of the "An indication of the vendor-specific hardware type of the
physical entity. Note that this is different from the physical entity. Note that this is different from the
definition of MIB-II's sysObjectID. definition of MIB-II's sysObjectID.
An agent should set this object to a enterprise-specific An agent should set this object to a enterprise-specific
registration identifier value indicating the specific registration identifier value indicating the specific
equipment type in detail. The associated instance of | equipment type in detail. The associated instance of
entPhysicalClass is used | entPhysicalClass is used to indicate the general type of
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 INTEGER (0..2147483647) SYNTAX INTEGER (0..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 16, line 42 skipping to change at page 16, line 42
for this physical entity, then the value 'other(1)' is for this physical entity, then the value 'other(1)' is
returned. If the value is unknown by this agent, then the returned. If the value is unknown by this agent, then the
value 'unknown(2)' is returned." value 'unknown(2)' is returned."
::= { entPhysicalEntry 5 } ::= { entPhysicalEntry 5 }
entPhysicalParentRelPos OBJECT-TYPE entPhysicalParentRelPos OBJECT-TYPE
SYNTAX INTEGER (-1..2147483647) SYNTAX INTEGER (-1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An indication of the relative position of this 'child' | "An indication of the relative position of this 'child'
component among all its 'sibling' components. Sibling | component among all its 'sibling' components. Sibling
components are defined as entPhysicalEntries which share the | components are defined as entPhysicalEntries which share the
same instance values of each of the entPhysicalContainedIn | same instance values of each of the entPhysicalContainedIn
and entPhysicalClass objects. | and entPhysicalClass objects.
An NMS can use this object to identify the relative ordering + An NMS can use this object to identify the relative ordering
for all sibling components of a particular parent + for all sibling components of a particular parent
(identified by the entPhysicalContainedIn instance in each + (identified by the entPhysicalContainedIn instance in each
sibling entry). + sibling entry).
Draft Entity MIB May 1996 Draft Entity MIB May 1996
This value should match any external labeling of the This value should match any external labeling of the
physical component if possible. For example, for a module physical component if possible. For example, for a module
labeled as 'card #3', entPhysicalParentRelPos should have labeled as 'card #3', entPhysicalParentRelPos should have
the value '3'. the value '3'.
If the physical position of this component does not match If the physical position of this component does not match
any external numbering or clearly visible ordering, then any external numbering or clearly visible ordering, then
skipping to change at page 17, line 28 skipping to change at page 17, line 28
of 'sibling' components, perhaps based on internal of 'sibling' components, perhaps based on internal
representation of the components. representation of the components.
If the agent cannot determine the parent-relative position If the agent cannot determine the parent-relative position
for some reason, or if the associated value of for some reason, or if the associated value of
entPhysicalContainedIn is '0', then the value '-1' is entPhysicalContainedIn is '0', then the value '-1' is
returned. Otherwise a non-negative integer is returned, returned. Otherwise a non-negative integer is returned,
indicating the parent-relative position of this physical indicating the parent-relative position of this physical
entity. entity.
Parent-relative ordering normally starts from '1' and | Parent-relative ordering normally starts from '1' and
continues to 'N', | continues to 'N', where 'N' represents the highest
where 'N' represents the highest positioned child entity. | positioned child entity. However, if the physical entities
However, if the physical entities (e.g. slots) are labeled | (e.g. slots) are labeled from a starting position of zero,
from a starting position of zero, then the first sibling | then the first sibling should be associated with a
should be associated with a entPhysicalParentRelPos value of | entPhysicalParentRelPos value of '0'. Note that this
'0'. | ordering may be sparse or dense, depending on agent
Note that this ordering may be sparse or dense, depending on implementation.
agent implementation. +
The actual values returned are not globally meaningful, as The actual values returned are not globally meaningful, as
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 DisplayString
MAX-ACCESS read-only + MAX-ACCESS read-only
STATUS current
Draft Entity MIB May 1996 Draft Entity MIB May 1996
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. +
If there is no local name, or this object is otherwise not + If there is no local name, or this object is otherwise not
applicable, then this object contains a zero-length string." + applicable, then this object contains a zero-length string."
::= { entPhysicalEntry 7 } + ::= { entPhysicalEntry 7 }
Draft Entity MIB May 1996 Draft Entity MIB May 1996
-- The Logical Entity Table
entLogicalTable OBJECT-TYPE
SYNTAX SEQUENCE OF EntLogicalEntry SYNTAX SEQUENCE OF EntLogicalEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains one row per logical entity." "This table contains one row per logical entity."
::= { entityLogical 1 } | ::= { entityLogical 1 }
entLogicalEntry OBJECT-TYPE entLogicalEntry OBJECT-TYPE
SYNTAX EntLogicalEntry SYNTAX EntLogicalEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
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 }
skipping to change at page 19, line 46 skipping to change at page 19, line 47
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 is a small positive integer; index values entity. The value is a small positive integer; index values
for different logical entities are are not necessarily for different logical entities are are not necessarily
contiguous." contiguous."
::= { entLogicalEntry 1 } ::= { entLogicalEntry 1 }
entLogicalDescr OBJECT-TYPE - entLogicalDescr OBJECT-TYPE
SYNTAX DisplayString SYNTAX DisplayString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A textual description of the logical entity. This object |
Draft Entity MIB May 1996 Draft Entity MIB May 1996
should contain a string which identifies the manufacturer's | "A textual description of the logical entity. This object
name for the logical entity, and should be set to a distinct | should contain a string which identifies the manufacturer's
value for each version of the logical entity. " | name for the logical entity, and should be set to a distinct
value for each version of the logical entity. "
::= { entLogicalEntry 2 } ::= { entLogicalEntry 2 }
entLogicalType OBJECT-TYPE entLogicalType OBJECT-TYPE
SYNTAX AutonomousType SYNTAX AutonomousType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An indication of the type of logical entity. This will "An indication of the type of logical entity. This will
typically be the OBJECT IDENTIFIER name of the node in the typically be the OBJECT IDENTIFIER name of the node in the
SMI's naming hierarchy which represents the major MIB SMI's naming hierarchy which represents the major MIB
skipping to change at page 21, line 27 skipping to change at page 21, line 27
of this object is the empty-string." of this object is the empty-string."
::= { entLogicalEntry 4 } ::= { entLogicalEntry 4 }
entLogicalTAddress OBJECT-TYPE entLogicalTAddress OBJECT-TYPE
SYNTAX TAddress SYNTAX TAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The transport service address by which the logical entity "The transport service address by which the logical entity
receives network management traffic, formatted according to receives network management traffic, formatted according to
the corresponding value of entLogicalTDomain. | the corresponding value of entLogicalTDomain.
For snmpUDPDomain, a TAddress is 6 octets long, the initial | For snmpUDPDomain, a TAddress is 6 octets long, the initial
4 octets containing the IP-address in network-byte order and | 4 octets containing the IP-address in network-byte order and
the last 2 containing the UDP port in network-byte order. | the last 2 containing the UDP port in network-byte order.
Consult 'Transport Mappings for Version 2 of the Simple | Consult 'Transport Mappings for Version 2 of the Simple
Network Management Protocol' [8] for further information on | Network Management Protocol' [8] for further information on
snmpUDPDomain." | snmpUDPDomain."
::= { entLogicalEntry 5 } ::= { entLogicalEntry 5 }
entLogicalTDomain OBJECT-TYPE entLogicalTDomain OBJECT-TYPE
SYNTAX TDomain SYNTAX TDomain
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the kind of transport service by which the "Indicates the kind of transport service by which the
logical entity receives network management traffic. logical entity receives network management traffic.
Possible values for this object are presently found in the Possible values for this object are presently found in the
skipping to change at page 22, line 42 skipping to change at page 22, line 42
but additional mappings between the bridge and each of the but additional mappings between the bridge and each of the
ports on that module would be redundant (since the ports on that module would be redundant (since the
entPhysicalContainedIn hierarchy can provide the same entPhysicalContainedIn hierarchy can provide the same
information). If, on the other hand, more than one bridge information). If, on the other hand, more than one bridge
was utilizing ports on this module, then mappings between was utilizing ports on this module, then mappings between
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 current 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. It association is not specifically identified in this entry. It
Draft Entity MIB May 1996 Draft Entity MIB May 1996
is expected that sufficient information exists in the MIBs is expected that sufficient information exists in the MIBs
used to manage a particular logical entity to infer how 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 INTEGER entLPPhysicalIndex PhysicalIndex
} }
entLPPhysicalIndex OBJECT-TYPE entLPPhysicalIndex OBJECT-TYPE
SYNTAX PhysicalIndex | SYNTAX PhysicalIndex
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current 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 }
Draft Entity MIB May 1996 Draft Entity MIB May 1996
-- logical entity/component to alias table -- logical entity/component to alias table
entAliasMappingTable OBJECT-TYPE entAliasMappingTable OBJECT-TYPE
SYNTAX SEQUENCE OF EntAliasMappingEntry SYNTAX SEQUENCE OF EntAliasMappingEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains zero or more rows, representing | "This table contains zero or more rows, representing
mappings of logical entity and physical component to | mappings of logical entity and physical component to
external MIB identifiers. | external MIB identifiers. Each physical port in the system
Each physical port in the system may be associated with a may be associated with a mapping to an external identifier,
mapping to an external identifier, which itself is which itself is associated with a particular logical
associated with a particular logical entity's naming scope. entity's naming scope. A wildcard mechanism is provided to
A wildcard mechanism is provided to indicate that an indicate that an identifier is associated with more than one
identifier is associated with more than one logical entity." logical entity."
::= { entityMapping 2 } | ::= { entityMapping 2 }
entAliasMappingEntry OBJECT-TYPE entAliasMappingEntry OBJECT-TYPE
SYNTAX EntAliasMappingEntry SYNTAX EntAliasMappingEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about a particular physical equipment, logical "Information about a particular physical equipment, logical
entity to external identifier binding. Each logical entity to external identifier binding. Each logical
entity/physical component pair may be associated with one entity/physical component pair may be associated with one
alias mapping. The logical entity index may also be used as alias mapping. The logical entity index may also be used as
skipping to change at page 27, line 18 skipping to change at page 27, line 18
entPhysicalContainsTable OBJECT-TYPE entPhysicalContainsTable OBJECT-TYPE
SYNTAX SEQUENCE OF EntPhysicalContainsEntry SYNTAX SEQUENCE OF EntPhysicalContainsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table which exposes the container/containee relationships "A table which exposes the container/containee relationships
between physical entities. This table provides equivalent between physical entities. This table provides equivalent
information found by constructing the virtual containment information found by constructing the virtual containment
tree for a given entPhysicalTable but in a more direct tree for a given entPhysicalTable but in a more direct
format." format."
::= { entityMapping 3 } | ::= { entityMapping 3 }
entPhysicalContainsEntry OBJECT-TYPE entPhysicalContainsEntry OBJECT-TYPE
SYNTAX EntPhysicalContainsEntry SYNTAX EntPhysicalContainsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A single container/containee relationship." "A single container/containee relationship."
INDEX { entPhysicalIndex, entPhysicalChildIndex } INDEX { entPhysicalIndex, entPhysicalChildIndex }
::= { entPhysicalContainsTable 1 } ::= { entPhysicalContainsTable 1 }
EntPhysicalContainsEntry ::= SEQUENCE { EntPhysicalContainsEntry ::= SEQUENCE {
entPhysicalChildIndex INTEGER entPhysicalChildIndex PhysicalIndex
} }
entPhysicalChildIndex OBJECT-TYPE entPhysicalChildIndex OBJECT-TYPE
SYNTAX PhysicalIndex | SYNTAX PhysicalIndex
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of entPhysicalIndex for the contained physical "The value of entPhysicalIndex for the contained physical
entity." entity."
::= { entPhysicalContainsEntry 1 } ::= { entPhysicalContainsEntry 1 }
Draft Entity MIB May 1996 Draft Entity MIB May 1996
-- last change timestamp for the whole MIB -- last change timestamp for the whole MIB
entLastChangeTime OBJECT-TYPE entLastChangeTime OBJECT-TYPE
SYNTAX TimeStamp | SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the time any of these events "The value of sysUpTime at the time any of these events
occur: occur:
* a conceptual row is created or deleted in any * a conceptual row is created or deleted in any
of these tables: of these tables:
- entPhysicalTable - entPhysicalTable
- entLogicalTable - entLogicalTable
- entLPMappingTable - entLPMappingTable
- entAliasMappingTable - entAliasMappingTable
- entPhysicalContainsTable - entPhysicalContainsTable
* any instance in the following list of objects * any instance in the following list of objects
changes value: changes value:
- entPhysicalDescr - entPhysicalDescr
- entPhysicalVendorType - entPhysicalVendorType
- entPhysicalContainedIn - entPhysicalContainedIn
- entPhysicalClass - entPhysicalClass
- entPhysicalParentRelPos + - entPhysicalParentRelPos
- entPhysicalName + - entPhysicalName
- entLogicalDescr - entLogicalDescr
- entLogicalType - entLogicalType
- entLogicalCommunity - entLogicalCommunity
- entLogicalTAddress - entLogicalTAddress
- entLogicalTDomain - entLogicalTDomain
- entAliasMappingIdentifier - entAliasMappingIdentifier "
" ::= { entityGeneral 1 }
::= { entityGeneral 1 } |
Draft Entity MIB May 1996 Draft Entity MIB May 1996
-- Entity MIB Trap Definitions -- Entity MIB Trap Definitions
entityMIBTraps OBJECT IDENTIFIER ::= { entityMIB 2 } entityMIBTraps OBJECT IDENTIFIER ::= { entityMIB 2 }
entConfigChange NOTIFICATION-TYPE entConfigChange NOTIFICATION-TYPE
STATUS current - STATUS current
DESCRIPTION DESCRIPTION
"An entConfigChange trap is sent when the value of "An entConfigChange trap is sent when the value of
entLastChangeTime changes. It can be utilized by an NMS to entLastChangeTime changes. It can be utilized by an NMS to
trigger logical/physical entity table maintenance polls. trigger logical/physical entity table maintenance polls.
This trap is throttled by the agent. This trap is throttled by the agent.
An agent must not generate more than | An agent must not generate more than one entConfigChange
one entConfigChange 'trap-event' in a five second period, 'trap-event' in a five second period, where a 'trap-event'
where a 'trap-event' is the transmission of a single trap is the transmission of a single trap PDU to a list of trap
PDU to a list of trap destinations. If additional destinations. If additional configuration changes occur
configuration changes occur within the five second within the five second 'throttling' period, then these
'throttling' period, then these events should be discarded events should be discarded by the agent. An NMS should
by the agent. An NMS should periodically check the value of periodically check the value of entLastChangeTime to detect
entLastChangeTime to detect any missed entConfigChange any missed entConfigChange events due to throttling or
events due to throttling or transmission loss." transmission loss."
::= { entityMIBTraps 1 } ::= { entityMIBTraps 1 }
Draft Entity MIB May 1996 Draft Entity MIB May 1996
-- conformance information -- conformance information
entityConformance OBJECT IDENTIFIER ::= { entityMIB 3 } entityConformance OBJECT IDENTIFIER ::= { entityMIB 3 }
entityCompliances OBJECT IDENTIFIER ::= { entityConformance 1 } entityCompliances OBJECT IDENTIFIER ::= { entityConformance 1 }
entityGroups OBJECT IDENTIFIER ::= { entityConformance 2 } entityGroups OBJECT IDENTIFIER ::= { entityConformance 2 }
-- compliance statements -- compliance statements
entityCompliance MODULE-COMPLIANCE entityCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SNMP entities which implement "The compliance statement for SNMP entities which implement
the Entity MIB." the Entity MIB."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { entityPhysicalGroup, | MANDATORY-GROUPS { entityPhysicalGroup,
entityLogicalGroup, | entityLogicalGroup,
entityMappingGroup, | entityMappingGroup,
entityGeneralGroup } | entityGeneralGroup }
::= { entityCompliances 1 } ::= { entityCompliances 1 }
-- MIB groupings -- MIB groupings
entityPhysicalGroup OBJECT-GROUP + entityPhysicalGroup OBJECT-GROUP
OBJECTS { + OBJECTS {
entPhysicalDescr, + entPhysicalDescr,
entPhysicalVendorType, + entPhysicalVendorType,
entPhysicalContainedIn, + entPhysicalContainedIn,
entPhysicalClass, + entPhysicalClass,
entPhysicalParentRelPos, + entPhysicalParentRelPos,
entPhysicalName + entPhysicalName
} + }
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 associated with logical entities, + physical system components associated with logical entities,
for which a single agent provides management information." + for which a single agent provides management information."
::= { entityGroups 1 } + ::= { entityGroups 1 }
entityLogicalGroup OBJECT-GROUP entityLogicalGroup OBJECT-GROUP
OBJECTS { OBJECTS {
entLogicalDescr, entLogicalDescr,
entLogicalType, entLogicalType,
entLogicalCommunity, entLogicalCommunity,
entLogicalTAddress, entLogicalTAddress,
entLogicalTDomain | entLogicalTDomain
Draft Entity MIB May 1996 Draft Entity MIB May 1996
} }
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 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,
entAliasLogicalIndexOrZero,
entAliasMappingIdentifier, entAliasMappingIdentifier,
entPhysicalChildIndex entPhysicalChildIndex
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to represent the "The collection of objects which are used to represent the
associations between multiple logical entities, physical | associations between multiple logical entities, physical
components, interfaces, and port | components, interfaces, and port identifiers for which a
identifiers for which a single agent provides management single agent provides management information."
information." ::= { entityGroups 3 }
::= { entityGroups 3 } |
entityGeneralGroup OBJECT-GROUP + entityGeneralGroup OBJECT-GROUP
OBJECTS { + OBJECTS {
entLastChangeTime + entLastChangeTime
} + }
STATUS current + STATUS current
DESCRIPTION + DESCRIPTION
"The collection of objects which are used to represent + "The collection of objects which are used to represent
general entity information for which a single agent provides + general entity information for which a single agent provides
management information." + management information."
::= { entityGroups 4 } + ::= { entityGroups 4 }
END END
Draft Entity MIB May 1996 Draft Entity MIB May 1996
5. Usage Examples 5. 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 more | networking devices. These examples are kept simple to make them more
understandable. Auxilary components, | understandable. Auxilary components, such as fans, sensors, empty slots,
such as fans, sensors, empty slots, and sub-modules are not shown, but and sub-modules are not shown, but might be modeled in real
might be modeled in real implementations. implementations.
5.1. Router/Bridge 5.1. Router/Bridge
A router containing two slots. Each slot contains a 3 port A router containing two slots. Each slot contains a 3 port
router/bridge module. Each port is represented in the ifTable. There router/bridge module. Each port is represented in the ifTable. There
are two logical instances of OSPF running and two logical bridges: are two logical instances of OSPF running and two logical bridges:
Physical entities -- entPhysicalTable: Physical entities -- entPhysicalTable:
1 Field-replaceable physical chassis: 1 Field-replaceable physical chassis:
entPhysicalDescr.1 == "Acme Chassis Model 100" entPhysicalDescr.1 == "Acme Chassis Model 100"
entPhysicalVendorType.1 == acmeProducts.chassisTypes.1 entPhysicalVendorType.1 == acmeProducts.chassisTypes.1
entPhysicalContainedIn.1 == 0 entPhysicalContainedIn.1 == 0
entPhysicalClass.1 == chassis(3) entPhysicalClass.1 == chassis(3)
entPhysicalParentRelPos.1 == 0 entPhysicalParentRelPos.1 == 0
entPhysicalName.1 == '100-A' + entPhysicalName.1 == '100-A'
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'
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'
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)
Draft Entity MIB May 1996 Draft Entity MIB May 1996
entPhysicalParentRelPos.4 == 1 entPhysicalParentRelPos.4 == 1
entPhysicalName.4 == 'M1' + entPhysicalName.4 == 'M1'
entPhysicalDescr.5 == "Acme Ethernet-100 Port Rev G" | entPhysicalDescr.5 == "Acme Ethernet-100 Port Rev G"
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'
entPhysicalDescr.6 == "Acme Ethernet-100 Port Rev G" | entPhysicalDescr.6 == "Acme Ethernet-100 Port Rev G"
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'
entPhysicalDescr.7 == "Acme Router-100 F-Port: Rev B" | entPhysicalDescr.7 == "Acme Router-100 F-Port: Rev B"
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'
Slot 2 contains another 3-port module: Slot 2 contains another 3-port module:
entPhysicalDescr.8 == "Acme Router-100 Comm Module: Rev C"| entPhysicalDescr.8 == "Acme Router-100 Comm Module: Rev C"
entPhysicalVendorType.8 == acmeProducts.moduleTypes.15 entPhysicalVendorType.8 == acmeProducts.moduleTypes.15
entPhysicalContainedIn.8 == 3 entPhysicalContainedIn.8 == 3
entPhysicalClass.8 == module(9) entPhysicalClass.8 == module(9)
entPhysicalParentRelPos.8 == 1 entPhysicalParentRelPos.8 == 1
entPhysicalName.8 == 'M1' + entPhysicalName.8 == 'M1'
entPhysicalDescr.9 == "Acme Fddi-100 Port Rev CC" | entPhysicalDescr.9 == "Acme Fddi-100 Port Rev CC"
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'
entPhysicalDescr.10 == "Acme Ethernet-100 Port Rev G" | entPhysicalDescr.10 == "Acme Ethernet-100 Port Rev G"
entPhysicalVendorType.10 == acmeProducts.portTypes.2 entPhysicalVendorType.10 == acmeProducts.portTypes.2
entPhysicalContainedIn.10 == 8 entPhysicalContainedIn.10 == 8
entPhysicalClass.10 == port(10) entPhysicalClass.10 == port(10)
entPhysicalParentRelPos.10 == 2 entPhysicalParentRelPos.10 == 2
entPhysicalName.10 == 'Ethernet A' + entPhysicalName.10 == 'Ethernet A'
Draft Entity MIB May 1996 Draft Entity MIB May 1996
entPhysicalDescr.11 == "Acme Ethernet-100 Port Rev G" | entPhysicalDescr.11 == "Acme Ethernet-100 Port Rev G"
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'
Logical entities -- entLogicalTable Logical entities -- entLogicalTable
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
entLogicalDescr.2 == "Acme OSPF v1.1" | entLogicalDescr.2 == "Acme OSPF v1.1"
entLogicalType.2 == ospf entLogicalType.2 == ospf
entLogicalCommunity.2 == "public-ospf2" entLogicalCommunity.2 == "public-ospf2"
entLogicalTAddress.2 == 124.125.126.127:161 entLogicalTAddress.2 == 124.125.126.127:161
entLogicalTDomain.2 == snmpUDPDomain entLogicalTDomain.2 == snmpUDPDomain
2 logical bridges: 2 logical bridges:
entLogicalDescr.3 == "Acme Bridge v2.1.1" | entLogicalDescr.3 == "Acme Bridge v2.1.1"
entLogicalType.3 == dod1dBridge entLogicalType.3 == dod1dBridge
entLogicalCommunity.3 == "public-bridge1" entLogicalCommunity.3 == "public-bridge1"
entLogicalTAddress.3 == 124.125.126.127:161 entLogicalTAddress.3 == 124.125.126.127:161
entLogicalTDomain.3 == snmpUDPDomain entLogicalTDomain.3 == snmpUDPDomain
entLogicalDescr.4 == "Acme Bridge v2.1.1" | entLogicalDescr.4 == "Acme Bridge v2.1.1"
entLogicalType.4 == dod1dBridge entLogicalType.4 == dod1dBridge
entLogicalCommunity.4 == "public-bridge2" entLogicalCommunity.4 == "public-bridge2"
entLogicalTAddress.4 == 124.125.126.127:161 entLogicalTAddress.4 == 124.125.126.127:161
entLogicalTDomain.4 == snmpUDPDomain entLogicalTDomain.4 == snmpUDPDomain
Logical to Physical Mappings: Logical to Physical Mappings:
1st OSPF instance: uses module 1-port 1 1st OSPF instance: uses module 1-port 1
entLPPhysicalIndex.1.5 == 5 entLPPhysicalIndex.1.5 == 5
2nd OSPF instance: uses module 2-port 1 2nd OSPF instance: uses module 2-port 1
skipping to change at page 36, line 27 skipping to change at page 36, line 27
5.2. Repeaters 5.2. Repeaters
A 3-slot Hub with 2 backplane ethernet segments. Slot three is empty, A 3-slot Hub with 2 backplane ethernet segments. Slot three is empty,
and the remaining slots contain ethernet repeater modules. [ed. -- Note and the remaining slots contain ethernet repeater modules. [ed. -- Note
that a replacement for the current Repeater MIB (RFC 1516) is likely to that a replacement for the current Repeater MIB (RFC 1516) is likely to
emerge soon, and it will no longer be necessary to access repeater MIB emerge soon, and it will no longer be necessary to access repeater MIB
data in different naming scopes.] data in different naming scopes.]
Physical entities -- entPhysicalTable: Physical entities -- entPhysicalTable:
1 Field-replaceable physical chassis: 1 Field-replaceable physical chassis:
entPhysicalDescr.1 == "Acme Chassis Model 110" | entPhysicalDescr.1 == "Acme Chassis Model 110"
entPhysicalVendorType.1 == acmeProducts.chassisTypes.2 entPhysicalVendorType.1 == acmeProducts.chassisTypes.2
entPhysicalContainedIn.1 == 0 entPhysicalContainedIn.1 == 0
entPhysicalClass.1 == chassis(3) entPhysicalClass.1 == chassis(3)
entPhysicalParentRelPos.1 == 0 entPhysicalParentRelPos.1 == 0
entPhysicalName.1 == '110-B' + entPhysicalName.1 == '110-B'
2 Chassis Ethernet Backplanes: 2 Chassis Ethernet Backplanes:
entPhysicalDescr.2 == "Acme Ethernet Backplane Type A" | entPhysicalDescr.2 == "Acme Ethernet Backplane Type A"
entPhysicalVendorType.2 == acmeProducts.backplaneTypes.1 entPhysicalVendorType.2 == acmeProducts.backplaneTypes.1
entPhysicalContainedIn.2 == 1 entPhysicalContainedIn.2 == 1
entPhysicalClass.2 == backplane(4) entPhysicalClass.2 == backplane(4)
entPhysicalParentRelPos.2 == 1 entPhysicalParentRelPos.2 == 1
entPhysicalName.2 == 'B1' + entPhysicalName.2 == 'B1'
entPhysicalDescr.3 == "Acme Ethernet Backplane Type A" | entPhysicalDescr.3 == "Acme Ethernet Backplane Type A"
entPhysicalVendorType.3 == acmeProducts.backplaneTypes.1 entPhysicalVendorType.3 == acmeProducts.backplaneTypes.1
entPhysicalContainedIn.3 == 1 entPhysicalContainedIn.3 == 1
entPhysicalClass.3 == backplane(4) entPhysicalClass.3 == backplane(4)
entPhysicalParentRelPos.3 == 2 entPhysicalParentRelPos.3 == 2
entPhysicalName.3 == 'B2' + entPhysicalName.3 == 'B2'
3 slots within the chassis: 3 slots within the chassis:
entPhysicalDescr.4 == "Acme Hub Slot Type RB" | entPhysicalDescr.4 == "Acme Hub Slot Type RB"
Draft Entity MIB May 1996 Draft Entity MIB May 1996
entPhysicalVendorType.4 == acmeProducts.slotTypes.5 entPhysicalVendorType.4 == acmeProducts.slotTypes.5
entPhysicalContainedIn.4 == 1 entPhysicalContainedIn.4 == 1
entPhysicalClass.4 == container(5) entPhysicalClass.4 == container(5)
entPhysicalParentRelPos.4 == 1 entPhysicalParentRelPos.4 == 1
entPhysicalName.4 == 'Slot 1' + entPhysicalName.4 == 'Slot 1'
entPhysicalDescr.5 == "Acme Hub Slot Type RB" | entPhysicalDescr.5 == "Acme Hub Slot Type RB"
entPhysicalVendorType.5 == acmeProducts.slotTypes.5 entPhysicalVendorType.5 == acmeProducts.slotTypes.5
entPhysicalContainedIn.5 == 1 entPhysicalContainedIn.5 == 1
entPhysicalClass.5 == container(5) entPhysicalClass.5 == container(5)
entPhysicalParentRelPos.5 == 2 entPhysicalParentRelPos.5 == 2
entPhysicalName.5 == 'Slot 2' + entPhysicalName.5 == 'Slot 2'
entPhysicalDescr.6 == "Acme Hub Slot Type RB" | entPhysicalDescr.6 == "Acme Hub Slot Type RB"
entPhysicalVendorType.6 == acmeProducts.slotTypes.5 entPhysicalVendorType.6 == acmeProducts.slotTypes.5
entPhysicalContainedIn.6 == 1 entPhysicalContainedIn.6 == 1
entPhysicalClass.6 == container(5) entPhysicalClass.6 == container(5)
entPhysicalParentRelPos.6 == 3 entPhysicalParentRelPos.6 == 3
entPhysicalName.6 == 'Slot 3' + entPhysicalName.6 == 'Slot 3'
Slot 1 contains a plug-in module with 4 10-BaseT ports: Slot 1 contains a plug-in module with 4 10-BaseT ports:
entPhysicalDescr.7 == "Acme 10Base-T Module 114 Rev A" | entPhysicalDescr.7 == "Acme 10Base-T Module 114 Rev A"
entPhysicalVendorType.7 == acmeProducts.moduleTypes.32 entPhysicalVendorType.7 == acmeProducts.moduleTypes.32
entPhysicalContainedIn.7 == 4 entPhysicalContainedIn.7 == 4
entPhysicalClass.7 == module(9) entPhysicalClass.7 == module(9)
entPhysicalParentRelPos.7 == 1 entPhysicalParentRelPos.7 == 1
entPhysicalName.7 == 'M1' + entPhysicalName.7 == 'M1'
entPhysicalDescr.8 == "Acme 10Base-T Port RB Rev A" | entPhysicalDescr.8 == "Acme 10Base-T Port RB Rev A"
entPhysicalVendorType.8 == acmeProducts.portTypes.10 entPhysicalVendorType.8 == acmeProducts.portTypes.10
entPhysicalContainedIn.8 == 7 entPhysicalContainedIn.8 == 7
entPhysicalClass.8 == port(10) entPhysicalClass.8 == port(10)
entPhysicalParentRelPos.8 == 1 entPhysicalParentRelPos.8 == 1
entPhysicalName.8 == 'Ethernet-A' + entPhysicalName.8 == 'Ethernet-A'
entPhysicalDescr.9 == "Acme 10Base-T Port RB Rev A" | entPhysicalDescr.9 == "Acme 10Base-T Port RB Rev A"
entPhysicalVendorType.9 == acmeProducts.portTypes.10 entPhysicalVendorType.9 == acmeProducts.portTypes.10
entPhysicalContainedIn.9 == 7 entPhysicalContainedIn.9 == 7
entPhysicalClass.9 == port(10) entPhysicalClass.9 == port(10)
entPhysicalParentRelPos.9 == 2 entPhysicalParentRelPos.9 == 2
entPhysicalName.9 == 'Ethernet-B' + entPhysicalName.9 == 'Ethernet-B'
entPhysicalDescr.10 == "Acme 10Base-T Port RB Rev B" | entPhysicalDescr.10 == "Acme 10Base-T Port RB Rev B"
entPhysicalVendorType.10 == acmeProducts.portTypes.10 entPhysicalVendorType.10 == acmeProducts.portTypes.10
entPhysicalContainedIn.10 == 7 entPhysicalContainedIn.10 == 7
Draft Entity MIB May 1996 Draft Entity MIB May 1996
entPhysicalClass.10 == port(10) entPhysicalClass.10 == port(10)
entPhysicalParentRelPos.10 == 3 entPhysicalParentRelPos.10 == 3
entPhysicalName.10 == 'Ethernet-C' + entPhysicalName.10 == 'Ethernet-C'
entPhysicalDescr.11 == "Acme 10Base-T Port RB Rev B" | entPhysicalDescr.11 == "Acme 10Base-T Port RB Rev B"
entPhysicalVendorType.11 == acmeProducts.portTypes.10 entPhysicalVendorType.11 == acmeProducts.portTypes.10
entPhysicalContainedIn.11 == 7 entPhysicalContainedIn.11 == 7
entPhysicalClass.11 == port(10) entPhysicalClass.11 == port(10)
entPhysicalParentRelPos.11 == 4 entPhysicalParentRelPos.11 == 4
entPhysicalName.11 == 'Ethernet-D' + entPhysicalName.11 == 'Ethernet-D'
Slot 2 contains another ethernet module with 2 ports. Slot 2 contains another ethernet module with 2 ports.
entPhysicalDescr.12 == "Acme 10Base-T Module Model 4 Rev A" | entPhysicalDescr.12 == "Acme 10Base-T Module Model 4 Rev A"
entPhysicalVendorType.12 == acmeProducts.moduleTypes.30 entPhysicalVendorType.12 == acmeProducts.moduleTypes.30
entPhysicalContainedIn.12 = 5 entPhysicalContainedIn.12 = 5
entPhysicalClass.12 == module(9) entPhysicalClass.12 == module(9)
entPhysicalParentRelPos.12 == 1 entPhysicalParentRelPos.12 == 1
entPhysicalName.12 == 'M1' + entPhysicalName.12 == 'M1'
entPhysicalDescr.13 == "Acme 802.3 AUI Port Rev A" | entPhysicalDescr.13 == "Acme 802.3 AUI Port Rev A"
entPhysicalVendorType.13 == acmeProducts.portTypes.11 entPhysicalVendorType.13 == acmeProducts.portTypes.11
entPhysicalContainedIn.13 == 12 entPhysicalContainedIn.13 == 12
entPhysicalClass.13 == port(10) entPhysicalClass.13 == port(10)
entPhysicalParentRelPos.13 == 1 entPhysicalParentRelPos.13 == 1
entPhysicalName.13 == 'AUI' + entPhysicalName.13 == 'AUI'
entPhysicalDescr.14 == "Acme 10Base-T Port RD Rev B" | entPhysicalDescr.14 == "Acme 10Base-T Port RD Rev B"
entPhysicalVendorType.14 == acmeProducts.portTypes.14 | entPhysicalVendorType.14 == acmeProducts.portTypes.14
entPhysicalContainedIn.14 == 12 entPhysicalContainedIn.14 == 12
entPhysicalClass.14 == port(10) entPhysicalClass.14 == port(10)
entPhysicalParentRelPos.14 == 2 entPhysicalParentRelPos.14 == 2
entPhysicalName.14 == 'E2' + entPhysicalName.14 == 'E2'
Logical entities -- entLogicalTable Logical entities -- entLogicalTable
Repeater 1--comprised of any ports attached to backplane 1 Repeater 1--comprised of any ports attached to backplane 1
entLogicalDescr.1 == "Acme repeater v3.1" | entLogicalDescr.1 == "Acme repeater v3.1"
entLogicalType.1 == snmpDot3RptrMgt entLogicalType.1 == snmpDot3RptrMgt
entLogicalCommunity.1 "public-repeater1" entLogicalCommunity.1 "public-repeater1"
entLogicalTAddress.1 == 124.125.126.127:161 entLogicalTAddress.1 == 124.125.126.127:161
entLogicalTDomain.1 == snmpUDPDomain entLogicalTDomain.1 == snmpUDPDomain
Repeater 2--comprised of any ports attached to backplane 2: Repeater 2--comprised of any ports attached to backplane 2:
entLogicalDescr.2 == "Acme repeater v3.1" | entLogicalDescr.2 == "Acme repeater v3.1"
entLogicalType.2 == snmpDot3RptrMgt entLogicalType.2 == snmpDot3RptrMgt
entLogicalCommunity.2 == "public-repeater2" entLogicalCommunity.2 == "public-repeater2"
Draft Entity MIB May 1996 Draft Entity MIB May 1996
entLogicalTAddress.2 == 124.125.126.127:161 entLogicalTAddress.2 == 124.125.126.127:161
entLogicalTDomain.2 == snmpUDPDomain entLogicalTDomain.2 == snmpUDPDomain
Logical to Physical Mappings -- entLPMappingTable: Logical to Physical Mappings -- entLPMappingTable:
 End of changes. 

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