draft-ietf-entmib-entmib-00.txt   draft-ietf-entmib-entmib-01.txt 
Draft Entity MIB November 17 1995 Draft Entity MIB January 14, 1996
<draft-ietf-entmib-entmib-01.txt>
Entity MIB Entity MIB
<draft-ietf-entmib-entmib-00.txt>
17 November 1995 14 January 1996
Keith McCloghrie Keith McCloghrie
Cisco Systems Inc. Cisco Systems Inc.
kzm@cisco.com kzm@cisco.com
Andy Bierman Andy Bierman
Bierman Consulting Bierman Consulting
abierman@west.net abierman@west.net
Status of this Memo Status of this Memo
skipping to change at page 2, line 5 skipping to change at page 2, line 5
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference material time. It is inappropriate to use Internet- Drafts as reference material
or to cite them other than as ``work in progress.'' or to cite them other than as ``work in progress.''
To learn the current status of any Internet-Draft, please check the To learn the current status of any Internet-Draft, please check the
``1id-abstracts.txt'' listing contained in the Internet- Drafts Shadow ``1id-abstracts.txt'' listing contained in the Internet- Drafts Shadow
Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe), Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe),
ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim).
Draft Entity MIB November 17 1995 Draft Entity MIB January 14, 1996
1. Introduction 1. Introduction
This memo defines an experimental portion of the Management Information This memo defines an experimental portion of the Management Information
Base (MIB) for use with network management protocols in the Internet Base (MIB) for use with network management protocols in the Internet
community. In particular, it describes managed objects used for community. In particular, it describes managed objects used for
managing multiple logical entities managed by a single SNMP agent. managing multiple logical entities managed by a single SNMP agent.
Draft Entity MIB November 17 1995 Draft Entity MIB January 14, 1996
2. The SNMPv2 Network Management Framework 2. The SNMPv2 Network Management Framework
The SNMPv2 Network Management Framework consists of four major The SNMPv2 Network Management Framework consists of four major
components. They are: components. They are:
o RFC 1442 [1] which defines the SMI, the mechanisms used for o RFC 1442 [1] which defines the SMI, the mechanisms used for
describing and naming objects for the purpose of management. describing and naming objects for the purpose of management.
o STD 17, RFC 1213 [2] defines MIB-II, the core set of managed o STD 17, RFC 1213 [2] defines MIB-II, the core set of managed
skipping to change at page 4, line 5 skipping to change at page 4, line 5
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,
an administratively assigned name. The object type together with an an administratively assigned name. The object type together with an
object instance serves to uniquely identify a specific instantiation of object instance serves to uniquely identify a specific instantiation of
the object. For human convenience, we often use a textual string, the object. For human convenience, we often use a textual string,
termed the descriptor, to refer to the object type. termed the descriptor, to refer to the object type.
Draft Entity MIB November 17 1995 Draft Entity MIB January 14, 1996
3. Overview 3. Overview
There is a need for a standardized way of representing a single agent There is a need for a standardized way of representing a single agent
which supports multiple instances of one MIB. This is already true for which supports multiple instances of one MIB. This is already true for
at least 3 standard MIBs, and is likely to become true for more and more at least 3 standard MIBs, and is likely to become true for more and more
MIBs as time passes. For example: MIBs as time passes. For example:
- multiple instances of a bridge supported within a single device - multiple instances of a bridge supported within a single device
having a single agent; having a single agent;
skipping to change at page 4, line 46 skipping to change at page 4, line 46
When different logical entities are associated with different physical When different logical entities are associated with different physical
entities within the overall physical entity, it is also useful to be entities within the overall physical entity, it is also useful to be
able to use this information to distinguish between logical entities. able to use this information to distinguish between logical entities.
In these situations, there is no need for varbinds for multiple logical In these situations, there is no need for varbinds for multiple logical
entities to be referenced in the same SNMP message (although that might entities to be referenced in the same SNMP message (although that might
be useful in the future). Rather, it is sufficient, and in some be useful in the future). Rather, it is sufficient, and in some
situations preferable, to have the context/community in the message situations preferable, to have the context/community in the message
identify the logical entity to which the varbinds apply. identify the logical entity to which the varbinds apply.
3.1. Relationship to Contexts 3.1. Terms
For SNMPv2, in simple scenarios, a SNMPv2 context [5] will correspond Some new terms are used throughout this document:
directly to a logical entity. However, in the general case, there is a
Draft Entity MIB November 17 1995 Draft Entity MIB January 14, 1996
many-to-many correspondence between an entry in the contextTable and an - Naming Scope
entry in the entLogicalTable. A "naming scope" represents the set of information that may be
potentially accessed through a single SNMP operation. All instances
within the naming scope share the same unique identifier space. For
SNMPv1, a naming scope is identified by the value of the associated
'entLogicalCommunity' instance.
On the one hand, each logical entity is associated with exactly one - Logical Entity
value of contextLocalEntity. However, it is possible to have multiple A managed system contains one or more logical entities, each
logical entities associated with the same value of contextLocalEntity. represented by at most one instantiation of each of a particular
For example, the logical entities, 'bridge1' and 'repeater1', may be set of MIB objects. A set of management functions is associated
represented in an agent's main context, even though different contexts with each logical entity. Examples of logical entities include
may be used to represent logical entities 'bridge2' and 'repeater2'. routers, bridges, print-servers, etc.
On the other hand, a single value of contextLocalEntity can be - Physical Entity
associated with multiple contexts (multiple entries in the contextTable) A "physical entity" or "physical component" represents an
when each has the same value of contextLocalEntity, but a different identifiable physical resource within a managed system. Zero or
value of contextLocalTime. more logical entities may utilize a physical resource at any given
time. It is an implementation-specific manner as to which physical
components are represented by an agent in the EntPhysicalTable.
Typically, physical resources (e.g. communications ports,
backplanes, sensors, daughter-cards, power supplies, the overall
chassis) which can be managed via functions associated with one or
more logical entities are included in the MIB.
- Containment Tree
Each physical component may optionally be modeled as 'contained'
within another physical component. A "containment-tree" is the
conceptual sequence of entPhysicalIndex values which uniquely
specifies the exact physical location of a physical component
within the managed system. It is generated by 'following and
recording' each 'entPhysicalContainedIn' instance until a value of
zero (indicating no further containment) is found.
It is suggested that physical containment-trees retain their
identity across reboots. Specifically, two identical hardware
configurations should produce the same set of containment-trees for
every corresponding entry in the entPhysicalTable (i.e. the same
set of entPhysicalEntries with the same entPhysicalIndex values,
[ed. want to say anything about container/containee guidelines
here?]
Draft Entity MIB January 14, 1996
3.2. Relationship to Community Strings 3.2. Relationship to Community Strings
For SNMPv1, distinguishing between different logical entities is one For SNMPv1, distinguishing between different logical entities is one
(but not the only) purpose of the community string [6]. This is (but not the only) purpose of the community string [6]. This is
accommodated by representing each community string as a logical entity. accommodated by representing each community string as a logical entity.
3.3. Relationship to a Chassis MIB Note that different logical entities may 'share' the same naming scope
(and therefore the same values of entLogicalCommunity). In such a case,
individual logical entities can be identified by examining the
sysORTable within the same naming scope.
3.3. Relationship to Proxy Mechanisms
The Entity MIB is designed to allow functional component discovery. The
administrative relationships between different logical entities are not
visible in any Entity MIB tables.
The management of administrative framework functions is not an explicit
goal of the Entity MIB WG at this time. This new area of functionality
may be revisited after some operational experience with the Entity MIB
is gained.
3.4. Relationship to a Chassis MIB
Some readers may recall that a previous IETF working group attempted to Some readers may recall that a previous IETF working group attempted to
define a Chassis MIB. No consensus was reached by that working group, define a Chassis MIB. No consensus was reached by that working group,
possibly because its scope was too broad. As such, it is not the possibly because its scope was too broad. As such, it is not the
purpose of this MIB to be a "Chassis MIB replacement", nor is it within purpose of this MIB to be a "Chassis MIB replacement", nor is it within
the scope of this MIB to contain all the information which might be the scope of this MIB to contain all the information which might be
necessary to manage a "chassis". On the other hand, the entities necessary to manage a "chassis". On the other hand, the entities
represented by an implementation of this MIB might well be contained in represented by an implementation of this MIB might well be contained in
a chassis. a chassis.
3.4. 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 context. This table can be used to identify the physical location given naming scope. This table can be used to identify the physical
of each interface in the ifTable. Since ifIndex values in different location of each interface in the ifTable. Since ifIndex values in
contexts are not related to one another, the interface to physical different contexts are not related to one another, the interface to
component associations are relative to a specific logical entity within physical component associations are relative to a specific logical
entity within the agent.
Draft Entity MIB November 17 1995 Draft Entity MIB January 14, 1996
the agent. [ed. say anything about entAliasMappingTable and ifIndex renumbering?]
3.5. 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, each bridge port in the dot1dBasePortTable, or each rptrPortTable, each bridge port in the dot1dBasePortTable, or each
ifIndex in the ifTable. ifIndex in the ifTable.
3.6. Re-Configuration of Entities 3.7. Re-Configuration of Entities
All the MIB objects defined in this MIB have at most a read-only MAX- All the MIB objects defined in this MIB have at most a read-only MAX-
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. this restriction could be lifted after implementation experience.
3.7. MIB Structure 3.8. MIB Structure
This MIB contains four tables: the entPhysicalTable and the This MIB contains five tables: the entPhysicalTable and the
entLogicalTable each provide a list of entities. The entLPMappingTable entLogicalTable each provide a list of entities. The entLPMappingTable
provides mappings between logical and physical entities. The provides mappings between logical and physical entities. The
entAliasMappingTable provides mappings between physical components and entAliasMappingTable provides mappings between physical components and
associated identifiers from other MIBs. For example, a physical repeater associated identifiers from other MIBs. For example, a physical repeater
port may be associated with an instance of 'rptrPortGroupIndex.1.5', or port may be associated with an instance of 'rptrPortGroupIndex.1.5', or
'ifIndex.12', or both. 'ifIndex.12', or both. The entPhysicalContainsTable provides efficient
discovery of the containment relationships of all physical entities
(also derivable from 'entPhysicalContainedIn' values).
The entPhysicalTable contains one row per physical entity, and should The entPhysicalTable contains one row per physical entity, and should
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 row in the same table indicating a contains the index number of another row in the same table indicating a
containment relationship between the two. containment relationship between the two.
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
SNMPv2 and/or SNMPv1 access to the MIB information for the logical
Draft Entity MIB November 17 1995 Draft Entity MIB January 14, 1996
SNMPv2 and/or SNMPv1 access to the MIB information for the logical
entity. entity.
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 entPhysicalIndex, The entAliasMappingTable contains mappings between entPhysicalIndex,
entLogicalIndex pairs and 'alias' object identifier values. This allows entLogicalIndex pairs and 'alias' object identifier values. This allows
resources managed with other MIBs (e.g. repeater ports, bridge ports, resources managed with other MIBs (e.g. repeater ports, bridge ports,
physical and logical interfaces) to be identified in the physical entity physical and logical interfaces) to be identified in the physical entity
hierarchy. hierarchy. Note that each alias identifier is only relevant in a
particular naming scope.
3.8. Multiple Agents The entPhysicalContainsTable contains simple mappings between
'entPhysicalContainsIn' values for each container/containee relationship
in the managed system. The indexing of this table allows an NMS to
quickly discover the 'entPhysicalIndex' values for all children of a
given physical entity.
3.9. 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.
Draft Entity MIB November 17 1995 Draft Entity MIB January 14, 1996
4. Definitions 4. Definitions
ENTITY-MIB DEFINITIONS ::= BEGIN ENTITY-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, experimental, MODULE-IDENTITY, OBJECT-TYPE, experimental,
IpAddress IpAddress
FROM SNMPv2-SMI FROM SNMPv2-SMI
DisplayString, AutonomousType, TruthValue DisplayString, AutonomousType, TruthValue
FROM SNMPv2-TC FROM SNMPv2-TC
Context Context
FROM SNMPv2-PARTY-MIB FROM SNMPv2-PARTY-MIB
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF; FROM SNMPv2-CONF;
entityMIB MODULE-IDENTITY entityMIB MODULE-IDENTITY
LAST-UPDATED "9511170000Z" LAST-UPDATED "9601020000Z"
ORGANIZATION "IETF ENTMIB Working Group" ORGANIZATION "IETF ENTMIB Working Group"
CONTACT-INFO CONTACT-INFO
" Keith McCloghrie " Keith McCloghrie
Cisco Systems Inc. Cisco Systems Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
408-526-5260 408-526-5260
kzm@cisco.com kzm@cisco.com
Andy Bierman Andy Bierman
skipping to change at page 9, line 5 skipping to change at page 10, line 5
Ventura, CA 93001 Ventura, CA 93001
805-648-2028 805-648-2028
abierman@west.net" abierman@west.net"
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 }
Draft Entity MIB November 17 1995 Draft Entity MIB January 14, 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."
skipping to change at page 9, line 37 skipping to change at page 10, line 37
each agent must be consistent, but not necessarily each agent must be consistent, but not necessarily
identical." identical."
INDEX { entPhysicalIndex } INDEX { entPhysicalIndex }
::= { entPhysicalTable 1 } ::= { entPhysicalTable 1 }
EntPhysicalEntry ::= SEQUENCE { EntPhysicalEntry ::= SEQUENCE {
entPhysicalIndex INTEGER, entPhysicalIndex INTEGER,
entPhysicalDescr DisplayString, entPhysicalDescr DisplayString,
entPhysicalVendorType AutonomousType, entPhysicalVendorType AutonomousType,
entPhysicalContainedIn INTEGER, entPhysicalContainedIn INTEGER,
entPhysicalIsRemovable TruthValue, entPhysicalClass INTEGER
entPhysicalClass AutonomousType
} }
entPhysicalIndex OBJECT-TYPE entPhysicalIndex 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 physical "The value of this object uniquely identifies the physical
entity. The value is a small positive integer; index values entity. The value is a small positive integer; index values
for different physical entities are not necessarily for different physical entities are not necessarily
contiguous." contiguous."
::= { entPhysicalEntry 1 } ::= { entPhysicalEntry 1 }
Draft Entity MIB November 17 1995
entPhysicalDescr OBJECT-TYPE entPhysicalDescr OBJECT-TYPE
Draft Entity MIB January 14, 1996
SYNTAX DisplayString SYNTAX DisplayString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A textual description of physical entity." "A textual description of physical entity."
::= { entPhysicalEntry 2 } ::= { entPhysicalEntry 2 }
entPhysicalVendorType OBJECT-TYPE entPhysicalVendorType OBJECT-TYPE
SYNTAX AutonomousType SYNTAX AutonomousType
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 10, line 49 skipping to change at page 11, line 48
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of entPhysicalIndex for the physical entity which "The value of entPhysicalIndex for the physical entity which
'contains' this physical entity. A value of zero indicates 'contains' this physical entity. A value of zero indicates
this physical entity is not contained in any other physical this physical entity is not contained in any other physical
entity. Note that the set of 'containment' relationships entity. Note that the set of 'containment' relationships
define a strict hierarchy; that is, recursion is not define a strict hierarchy; that is, recursion is not
allowed." allowed."
::= { entPhysicalEntry 4 } ::= { entPhysicalEntry 4 }
entPhysicalIsRemovable OBJECT-TYPE entPhysicalClass OBJECT-TYPE
SYNTAX TruthValue SYNTAX INTEGER {
MAX-ACCESS read-only other(1),
Draft Entity MIB November 17 1995
STATUS current Draft Entity MIB January 14, 1996
DESCRIPTION
"An indication of the physical characteristics of specified
component. A value of 'true(1)' indicates that this
entPhysicalEntry represents a field-replaceable unit. A
value of 'false(2)' indicates a physical component that
cannot be replaced by a user or equipment installer."
::= { entPhysicalEntry 5 }
entPhysicalClass OBJECT-TYPE unknown(2),
SYNTAX AutonomousType chassis(3),
backplane(4),
container(5), -- slot or daughter-card holder
powerSupply(6),
fan(7),
sensor(8),
module(9),
port(10)
-- some others here that I forgot?
}
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An indication of the general hardware type of the physical "An indication of the general hardware type of the physical
entity. entity.
An agent should set this object to a standard registration An agent should set this object to the standard enumeration
identifier value (from the entPClassTypes sub-tree) which value which most accurately indicates the general class of
most accurately indicates the general class of the physical the physical entity, or the primary class if there is more
entity. than one.
If no appropriate standard registration identifier exists If no appropriate standard registration identifier exists
for this physical entity, then the value { 0 0 } 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
special value 'entPClassUnknown' is returned." value 'unknown(2)' is returned."
::= { entPhysicalEntry 6 } ::= { entPhysicalEntry 5 }
Draft Entity MIB November 17 1995 Draft Entity MIB January 14, 1996
-- The Logical Entity Table -- The Logical Entity Table
entLogicalTable OBJECT-TYPE entLogicalTable OBJECT-TYPE
SYNTAX SEQUENCE OF EntLogicalEntry SYNTAX SEQUENCE OF EntLogicalEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains one row per logical entity." "This table contains one row per logical entity."
::= { entityMIBObjects 2 } ::= { entityMIBObjects 2 }
skipping to change at page 12, line 31 skipping to change at page 13, line 31
"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 DisplayString,
entLogicalType AutonomousType, entLogicalType AutonomousType,
entLogicalLocalEntityName OCTET STRING,
entLogicalContext Context,
entLogicalCommunity OCTET STRING, entLogicalCommunity OCTET STRING,
entLogicalIpAddress IpAddress entLogicalIpAddress IpAddress
} }
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 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 }
Draft Entity MIB November 17 1995 Draft Entity MIB January 14, 1996
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 logical entity." "A textual description of logical entity."
::= { entLogicalEntry 2 } ::= { entLogicalEntry 2 }
entLogicalType OBJECT-TYPE entLogicalType OBJECT-TYPE
skipping to change at page 13, line 31 skipping to change at page 14, line 31
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
module, or the majority of the MIB modules, supported by the module, or the majority of the MIB modules, supported by the
logical entity. For example: logical entity. For example:
a logical entity of a regular host/router -> mib-2 a logical entity of a regular host/router -> mib-2
a logical entity of a 802.1d bridge -> dot1dBridge a logical entity of a 802.1d bridge -> dot1dBridge
a logical entity of a 802.3 repeater -> a logical entity of a 802.3 repeater ->
snmpDot3RptrMgmt" snmpDot3RptrMgmt"
::= { entLogicalEntry 3 } ::= { entLogicalEntry 3 }
entLogicalLocalEntityName OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..255))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A name associated with the logical entity. This name and
the SNMPv2 contextLocalEntity [RFC-1447] for the
corresponding local context have the same value. Note that
multiple contexts may have the same value of
contextLocalEntity, each having a different value of
contextLocalTime.
A conformant SNMPv2 agent may wish to conserve contexts by
representing multiple logical entities in a single 'main'
context. This is possible when the logical entities
represented by the same value of contextLocalEntity have no
object instances in common. For example, 'bridge1' and
'repeater1' may be part of the main context, but two
additional entries are needed to represent 'bridge2' and
'repeater2'.
Draft Entity MIB November 17 1995
Logical entities 'bridge1' and 'repeater1' would be
represented by sysOREntries associated with the 'main'
context.
For agents not accessible via SNMPv2, the value of this
object is the empty string."
::= { entLogicalEntry 4 }
entLogicalContext OBJECT-TYPE
SYNTAX Context
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An SNMPv2 context containing detailed management
information for this logical entity. If more than one
context is associated with this logical entity, then the
agent should choose a 'primary' context for the logical
entity; e.g. the context whose associated value of
contextLocalTime is equal to 'currentTime'.
Other contexts (for different values of contextLocalTime)
may be derived from the entLogicalLocalEntityName according
to whatever conventions are used for context naming.
For agents not accessible via SNMPv2, this object would have
the value 0.0.
[TBD 1: the issue of which Parties to use along with this
context is considered beyond the scope of the Entity MIB.
TBD 2: this part of the entLogicalTable will change to
reflect the new SNMPv2 administrative model.] "
::= { entLogicalEntry 5 }
entLogicalCommunity OBJECT-TYPE entLogicalCommunity OBJECT-TYPE
SYNTAX OCTET STRING SYNTAX OCTET STRING
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A SNMPv1 community-string which can be used to access "A SNMPv1 community-string which can be used to access
detailed management information for this logical entity. detailed management information for this logical entity.
The agent should allow read access with this community The agent should allow read access with this community
string (to an appropriate subset of all managed objects) and string (to an appropriate subset of all managed objects) and
may also choose to return a community string based on the may also choose to return a community string based on the
privileges of the request used to read this object (e.g. privileges of the request used to read this object (e.g.
only return a string having read-write privileges when only return a string having read-write privileges when
accessed with read-write privileges).
Draft Entity MIB November 17 1995 A conformant SNMP agent may wish to conserve naming scopes
by representing multiple logical entities in a single 'main'
naming scope. This is possible when the logical entities
represented by the same value of entLogicalCommunity have no
object instances in common. For example, 'bridge1' and
'repeater1' may be part of the main naming scope, but two
additional community strings are needed to represent
accessed with read-write privileges). Draft Entity MIB January 14, 1996
'bridge2' and 'repeater2'.
Logical entities 'bridge1' and 'repeater1' would be
represented by sysOREntries associated with the 'main'
naming scope.
For agents not accessible via SNMPv1, the value of this For agents not accessible via SNMPv1, the value of this
object is the empty-string." object is the empty-string."
::= { entLogicalEntry 6 } ::= { entLogicalEntry 4 }
entLogicalIpAddress OBJECT-TYPE entLogicalIpAddress OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP-address of the SNMPv1 agent from which detailed "The IP-address of the SNMPv1 agent from which detailed
management information for this logical entity can be management information for this logical entity can be
obtained. For agents not accessible via SNMPv1, the value obtained. For agents not accessible via SNMPv1, the value
of this object is 0.0.0.0." of this object is 0.0.0.0."
::= { entLogicalEntry 7 } ::= { entLogicalEntry 5 }
Draft Entity MIB November 17 1995 Draft Entity MIB January 14, 1996
-- entLPMappingTable: for each entity index, there are N -- entLPMappingTable: for each entity index, there are N
-- rows, each representing a physical component -- rows, each representing a physical component
-- that is associated with the indicated entity -- that is associated with the indicated entity
-- --
-- entity to component table -- entity to component table
entLPMappingTable OBJECT-TYPE entLPMappingTable OBJECT-TYPE
SYNTAX SEQUENCE OF EntLPMappingEntry SYNTAX SEQUENCE OF EntLPMappingEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 17, line 5 skipping to change at page 17, line 5
entLPPhysicalIndex OBJECT-TYPE entLPPhysicalIndex OBJECT-TYPE
SYNTAX INTEGER (1..2147483647) SYNTAX INTEGER (1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object identifies a particular "The value of this object identifies a particular
entPhysicalEntry associated with the indicated entPhysicalEntry associated with the indicated
entLogicalEntity." entLogicalEntity."
::= { entLPMappingEntry 1 } ::= { entLPMappingEntry 1 }
Draft Entity MIB November 17 1995 Draft Entity MIB January 14, 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 of logical entity, "This table contains zero or more rows of logical entity,
and physical component to external identifier associations." and physical component to external identifier associations."
::= { entityMIBObjects 4 } ::= { entityMIBObjects 4 }
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. Note that the same entity to external identifier binding. Note that the same
physical component-logical entity pair may have an arbitrary physical component-logical entity pair may have an arbitrary
number of external identifier (alias) bindings." number of external identifier (alias) bindings."
INDEX { entPhysicalIndex, entLogicalIndex, entAliasMappingIndex } INDEX { entLogicalIndex, entPhysicalIndex, entAliasMappingIndex }
::= { entAliasMappingTable 1 } ::= { entAliasMappingTable 1 }
EntAliasMappingEntry ::= SEQUENCE { EntAliasMappingEntry ::= SEQUENCE {
entAliasMappingIndex INTEGER, entAliasMappingIndex INTEGER,
entAliasIdentifier OBJECT IDENTIFIER entAliasIdentifier OBJECT IDENTIFIER
} }
entAliasMappingIndex OBJECT-TYPE entAliasMappingIndex OBJECT-TYPE
SYNTAX INTEGER (1..2147483647) SYNTAX INTEGER (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 18, line 5 skipping to change at page 18, line 5
necessarily contiguous." necessarily contiguous."
::= { entAliasMappingEntry 1 } ::= { entAliasMappingEntry 1 }
entAliasIdentifier OBJECT-TYPE entAliasIdentifier OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object identifies a particular MIB "The value of this object identifies a particular MIB
Draft Entity MIB November 17 1995 Draft Entity MIB January 14, 1996
instance associated with the indicated entPhysicalEntry and instance associated with the indicated entPhysicalEntry and
entLogicalEntry pair. entLogicalEntry pair.
For example, suppose a physical port was represented by For example, suppose a physical port was represented by
entPhysicalEntry.3, and entLogicalEntry.1 existed for a entPhysicalEntry.3, and entLogicalEntry.1 existed for a
repeater, entLogicalEntry.2 existed for a bridge, and the repeater, entLogicalEntry.2 existed for a bridge, and the
bridge port was also represented in the ifTable. Then there bridge port was also represented in the ifTable. Then there
might be three associated instances of entAliasIdentifier: might be three associated instances of entAliasIdentifier:
entAliasIdentifier.3.1.1 == rptrPortGroupIndex.5.2 entAliasIdentifier.3.1.1 == rptrPortGroupIndex.5.2
entAliasIdentifier.3.2.1 == dot1dBasePort.2 entAliasIdentifier.3.2.1 == dot1dBasePort.2
entAliasIdentifier.3.2.2 == ifIndex.2 " entAliasIdentifier.3.2.2 == ifIndex.2 "
::= { entAliasMappingEntry 2 } ::= { entAliasMappingEntry 2 }
Draft Entity MIB November 17 1995 Draft Entity MIB January 14, 1996
entPClassTypes OBJECT IDENTIFIER ::= { entityMIBObjects 5 }
entPClassUnknown OBJECT IDENTIFIER ::= { entPClassTypes 1 }
entPClassChassis OBJECT IDENTIFIER ::= { entPClassTypes 2 }
entPClassBackplanes OBJECT IDENTIFIER ::= { entPClassTypes 3 }
entPClassNetBackplane OBJECT IDENTIFIER ::= { entPClassBackplanes 1 }
entPClassPowerBackplane OBJECT IDENTIFIER ::= { entPClassBackplanes 2 }
entPClassSlot OBJECT IDENTIFIER ::= { entPClassTypes 4 } -- physical mapping table
entPhysicalContainsTable OBJECT-TYPE
SYNTAX SEQUENCE OF EntPhysicalContainsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table which exposes the container/containee relationships
between physical entities."
::= { entityMIBObjects 5 }
entPClassPowerSupply OBJECT IDENTIFIER ::= { entPClassTypes 5 } entPhysicalContainsEntry OBJECT-TYPE
SYNTAX EntPhysicalContainsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A single container/containee relationship."
INDEX { entPhysicalIndex, entPhysicalChildIndex }
::= { entPhysicalContainsTable 1 }
entPClassFan OBJECT IDENTIFIER ::= { entPClassTypes 6 } EntPhysicalContainsEntry ::= SEQUENCE {
entPhysicalChildIndex INTEGER
}
entPClassSensors OBJECT IDENTIFIER ::= { entPClassTypes 7 } entPhysicalChildIndex OBJECT-TYPE
SYNTAX INTEGER (1..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of entPhysicalIndex for the contained physical
entity."
::= { entPhysicalContainsEntry 1 }
entPClassTempSensor OBJECT IDENTIFIER ::= { entPClassSensors 1 } Draft Entity MIB January 14, 1996
entPClassGenModules OBJECT IDENTIFIER ::= { entPClassTypes 8 } -- last change timestamp for the whole MIB
entLastConfigChangeTime OBJECT-TYPE
SYNTAX Timestamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time any of these events
occur:
* a conceptual row is created or deleted in any of these tables:
- entPhysicalTable
- entLogicalTable
- entLPMappingTable
- entAliasMappingTable
- entPhysicalContainsTable
entPClassNetModules OBJECT IDENTIFIER ::= { entPClassTypes 9 } * any instance in the following list of objects changes value:
- entPhysicalDescr
- entPhysicalVendorType
- entPhysicalContainedIn
- entPhysicalClass
- entLogicalDescr
- entLogicalType
- entLogicalCommunity
- entLogicalIpAddress
- entAliasIdentifier
"
::= { entityMIBObjects 6 }
entPClassNetRepeater OBJECT IDENTIFIER ::= { entPClassNetModules 1 } Draft Entity MIB January 14, 1996
entPClassNetRouter OBJECT IDENTIFIER ::= { entPClassNetModules 2 } -- Entity MIB Trap Definitions
entityMIBTraps OBJECT IDENTIFIER ::= { entityMIB 2 }
entPClassNetBridge OBJECT IDENTIFIER ::= { entPClassNetModules 3 } entConfigChange NOTIFICATION-TYPE
OBJECTS {
entLastChangeTime
}
STATUS current
DESCRIPTION
"An entConfigChange trap is sent when the value of
entLastConfigChangeTime changes. It can be utilized by an
NMS to trigger logical/physical entity table maintenance
polls. This trap is throttled by the agent.
entPClassTermServer OBJECT IDENTIFIER ::= { entPClassNetModules 4 } The value of entLastChangeTime at the time the config-
change-event is generated by the agent is encoded at the
only var-bind in the trap.
entPClassPort OBJECT IDENTIFIER ::= { entPClassTypes 10 } An agent must take care not to generate more than one
entLastChangeTime 'trap-event' in a five second period (a
'trap-event' is the transmission of a single trap PDU to a
list of trap receivers). If additional configuration
changes occur within the five second 'throttling' period,
then the agent should discard all but the most recent trap-
event (if any), rather than queueing them and generating
trap-events (one every five seconds) in sequence. "
::= { entityMIBTraps 1 }
Draft Entity MIB November 17 1995 Draft Entity MIB January 14, 1996
-- conformance information -- conformance information
entityConformance OBJECT IDENTIFIER ::= { entityMIB 3 }
entityConformance OBJECT IDENTIFIER ::= { entityMIB 2 }
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 SNMPv2 entities "The compliance statement for SNMPv2 entities
which implement the Entity MIB." which implement the Entity MIB."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { entityGroup } MANDATORY-GROUPS { entityGroup }
::= { entityCompliances 1 } ::= { entityCompliances 1 }
-- units of conformance -- units of conformance
entityGroup OBJECT-GROUP entityGroup OBJECT-GROUP
OBJECTS { entPhysicalDescr, entPhysicalVendorType, OBJECTS { entPhysicalDescr,
entPhysicalContainedIn, entPhysicalIsRemovable, entPhysicalVendorType,
entPhysicalContainedIn,
entPhysicalClass, entPhysicalClass,
entLogicalDescr, entLogicalType, entLogicalDescr,
entLogicalLocalEntityName, entLogicalContext, entLogicalType,
entLogicalCommunity, entLogicalIpAddress, entLogicalCommunity,
entLPPhysicalIndex, entAliasIdentifier entLogicalIpAddress,
entLPPhysicalIndex,
entAliasIdentifier,
entPhysicalChildIndex,
entLastChangeTime,
entConfigChange -- separate conformance group needed for trap??
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The collection of objects which are used to "The collection of objects which are used to
represent the multiple logical entities, represent the multiple logical entities,
physical components, interfaces, and port physical components, interfaces, and port
alias identifiers for which a single agent alias identifiers for which a single agent
provides MIB information." provides MIB information."
::= { entityGroups 1 } ::= { entityGroups 1 }
END END
Draft Entity MIB November 17 1995 Draft Entity MIB January 14, 1996
5. Usage Examples 5. Usage Examples
5.1. Router/Bridge 5.1. Router/Bridge
A bi-lingual (SNMPv1 and SNMPv2) router containing two slots. Each slot A bi-lingual (SNMPv1 and SNMPv2) router containing two slots. Each slot
contains a 3 port router/bridge module. Each port is represented in the contains a 3 port router/bridge module. Each port is represented in the
ifTable. There are two logical instances of OSPF running and two ifTable. There are two logical instances of OSPF running and two
logical bridges: 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
entPhysicalIsRemovable.1 == true(1) entPhysicalClass.1 == chassis(3)
entPhysicalClass.1 == entPClassChassis
2 slots within the chassis: 2 slots within the chassis:
entPhysicalDescr.2 == "Acme Router Chassis Slot 1" entPhysicalDescr.2 == "Acme Router Chassis Slot 1"
entPhysicalVendorType.2 == acmeProducts.slotTypes.1 entPhysicalVendorType.2 == acmeProducts.slotTypes.1
entPhysicalContainedIn.2 == 1 entPhysicalContainedIn.2 == 1
entPhysicalIsRemovable.2 == false(2) entPhysicalClass.2 == container(5)
entPhysicalClass.2 == entPClassSlot
entPhysicalDescr.3 == "Acme Router Chassis Slot 2" entPhysicalDescr.3 == "Acme Router Chassis Slot 2"
entPhysicalVendorType.3 == acmeProducts.slotTypes.1 entPhysicalVendorType.3 == acmeProducts.slotTypes.1
entPhysicalContainedIn.3 == 1 entPhysicalContainedIn.3 == 1
entPhysicalIsRemovable.3 == false(2) entPhysicalClass.3 == container(5)
entPhysicalClass.3 == entPClassSlot
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 Module Model 10" entPhysicalDescr.4 == "Acme Router Module Model 10"
entPhysicalVendorType.4 == acmeProducts.moduleTypes.14 entPhysicalVendorType.4 == acmeProducts.moduleTypes.14
entPhysicalContainedIn.4 == 2 entPhysicalContainedIn.4 == 2
entPhysicalIsRemovable.4 == true(1) entPhysicalClass.4 == module(9)
entPhysicalClass.4 == entPClassNetRouter
entPhysicalDescr.5 == "Acme Router Ethernet Port 1" entPhysicalDescr.5 == "Acme Router Ethernet Port 1"
entPhysicalVendorType.5 == acmeProducts.portTypes.2 entPhysicalVendorType.5 == acmeProducts.portTypes.2
entPhysicalContainedIn.5 == 4 entPhysicalContainedIn.5 == 4
entPhysicalIsRemovable.5 == false(2) entPhysicalClass.5 == port(10)
entPhysicalClass.5 == entPClassPort
Draft Entity MIB November 17 1995
entPhysicalDescr.6 == "Acme Router Ethernet Port 2" entPhysicalDescr.6 == "Acme Router Ethernet Port 2"
entPhysicalVendorType.6 == acmeProducts.portTypes.2 entPhysicalVendorType.6 == acmeProducts.portTypes.2
entPhysicalContainedIn.6 == 4 entPhysicalContainedIn.6 == 4
entPhysicalIsRemovable.6 == false(2) entPhysicalClass.6 == port(10)
entPhysicalClass.6 == entPClassPort
entPhysicalDescr.7 == "Acme Router Fddi Port 3" entPhysicalDescr.7 == "Acme Router Fddi Port 3"
Draft Entity MIB January 14, 1996
entPhysicalVendorType.7 == acmeProducts.portTypes.3 entPhysicalVendorType.7 == acmeProducts.portTypes.3
entPhysicalContainedIn.7 == 4 entPhysicalContainedIn.7 == 4
entPhysicalIsRemovable.7 == false(2) entPhysicalClass.7 == port(10)
entPhysicalClass.7 == entPClassPort
Slot 2 contains another 3-port module: Slot 2 contains another 3-port module:
entPhysicalDescr.8 == "Acme Router Module Model 11" entPhysicalDescr.8 == "Acme Router Module Model 11"
entPhysicalVendorType.8 == acmeProducts.moduleTypes.15 entPhysicalVendorType.8 == acmeProducts.moduleTypes.15
entPhysicalContainedIn.8 == 3 entPhysicalContainedIn.8 == 3
entPhysicalIsRemovable.8 == true(1) entPhysicalClass.8 == module(9)
entPhysicalClass.8 == entPClassNetRouter
entPhysicalDescr.9 == "Acme Router Fddi Port 1" entPhysicalDescr.9 == "Acme Router Fddi Port 1"
entPhysicalVendorType.9 == acmeProducts.portTypes.3 entPhysicalVendorType.9 == acmeProducts.portTypes.3
entPhysicalContainedIn.9 == 8 entPhysicalContainedIn.9 == 8
entPhysicalIsRemovable.9 == false(2) entPhysicalClass.9 == port(10)
entPhysicalClass.9 == entPClassPort
entPhysicalDescr.10 == "Acme Router Ethernet Port 2" entPhysicalDescr.10 == "Acme Router Ethernet Port 2"
entPhysicalVendorType.10 == acmeProducts.portTypes.2 entPhysicalVendorType.10 == acmeProducts.portTypes.2
entPhysicalContainedIn.10 == 8 entPhysicalContainedIn.10 == 8
entPhysicalIsRemovable.10 == false(2) entPhysicalClass.10 == port(10)
entPhysicalClass.10 == entPClassPort
entPhysicalDescr.11 == "Acme Router Ethernet Port 3" entPhysicalDescr.11 == "Acme Router Ethernet Port 3"
entPhysicalVendorType.11 == acmeProducts.portTypes.2 entPhysicalVendorType.11 == acmeProducts.portTypes.2
entPhysicalContainedIn.11 == 8 entPhysicalContainedIn.11 == 8
entPhysicalIsRemovable.11 == false(2) entPhysicalClass.11 == port(10)
entPhysicalClass.11 == entPClassPort
Logical entities -- entLogicalTable Logical entities -- entLogicalTable
2 OSPF instances: 2 OSPF instances:
entLogicalDescr.1 == "ospf-1" entLogicalDescr.1 == "ospf-1"
entLogicalType.1 == ospf entLogicalType.1 == ospf
entLogicalLocalEntityName.1 == "wan-gwty"
entLogicalContext.1 == { initialContextId
124 125 126 127 10 }
entLogicalCommunity.1 == "public-ospf1" entLogicalCommunity.1 == "public-ospf1"
Draft Entity MIB November 17 1995
entLogicalIpAddress.1 == 124.125.126.127 entLogicalIpAddress.1 == 124.125.126.127
entLogicalDescr.2 == "ospf-2" entLogicalDescr.2 == "ospf-2"
entLogicalType.2 == ospf entLogicalType.2 == ospf
entLogicalLocalEntityName.2 == "wan-gwty-ospf2"
entLogicalContext.2 == { initialContextId
124 125 126 127 11 }
entLogicalCommunity.2 == "public-ospf2" entLogicalCommunity.2 == "public-ospf2"
entLogicalIpAddress.2 == 124.125.126.127 entLogicalIpAddress.2 == 124.125.126.127
2 logical bridges: 2 logical bridges:
entLogicalDescr.3 == "bridge1" entLogicalDescr.3 == "bridge1"
entLogicalType.3 == dod1dBridge entLogicalType.3 == dod1dBridge
entLogicalLocalEntityName.3 == "wan-gwty-bridge1"
entLogicalContext.3 == { initialContextId
124 125 126 127 101 }
entLogicalCommunity.3 == "public-bridge1" entLogicalCommunity.3 == "public-bridge1"
entLogicalIpAddress.3 == 124.125.126.127 entLogicalIpAddress.3 == 124.125.126.127
entLogicalDescr.4 == "bridge2" entLogicalDescr.4 == "bridge2"
entLogicalType.4 == dod1dBridge entLogicalType.4 == dod1dBridge
entLogicalLocalEntityName.4 == "wan-gwty-bridge2"
entLogicalContext.4 == { initialContextId Draft Entity MIB January 14, 1996
124 125 126 127 102 }
entLogicalCommunity.4 == "public-bridge2" entLogicalCommunity.4 == "public-bridge2"
entLogicalIpAddress.4 == 124.125.126.127 entLogicalIpAddress.4 == 124.125.126.127
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
entLPPhysicalIndex.2.9 == 9 entLPPhysicalIndex.2.9 == 9
1st bridge group: uses module 1, all ports 1st bridge group: uses module 1, all ports
entLPPhysicalIndex.3.5 == 5 entLPPhysicalIndex.3.5 == 5
entLPPhysicalIndex.3.6 == 6 entLPPhysicalIndex.3.6 == 6
entLPPhysicalIndex.3.7 == 7 entLPPhysicalIndex.3.7 == 7
2nd bridge group: uses module 2, all ports 2nd bridge group: uses module 2, all ports
entLPPhysicalIndex.4.9 == 9 entLPPhysicalIndex.4.9 == 9
entLPPhysicalIndex.4.10 == 10 entLPPhysicalIndex.4.10 == 10
entLPPhysicalIndex.4.11 == 11 entLPPhysicalIndex.4.11 == 11
Physical/Logical to Alias Mappings -- entAliasMappingTable: Logical to Physical to Alias Mappings -- entAliasMappingTable:
Draft Entity MIB November 17 1995
Bridge 1 uses Ports 1..3 on Slot 1 Bridge 1 uses Ports 1..3 on Slot 1
entAliasIdentifier.5.3.1 == dot1dBasePort.1 entAliasIdentifier.3.5.1 == dot1dBasePort.1
entAliasIdentifier.5.3.2 == ifIndex.1 entAliasIdentifier.3.5.2 == ifIndex.1
entAliasIdentifier.6.3.1 == dot1dBasePort.2 entAliasIdentifier.3.6.1 == dot1dBasePort.2
entAliasIdentifier.6.3.2 == ifIndex.2 entAliasIdentifier.3.6.2 == ifIndex.2
entAliasIdentifier.7.3.1 == dot1dBasePort.3 entAliasIdentifier.3.7.1 == dot1dBasePort.3
entAliasIdentifier.7.3.2 == ifIndex.3 entAliasIdentifier.3.7.2 == ifIndex.3
Bridge 2 uses Ports 1..3 on Slot 2; uses same Bridge MIB and ifIndex Bridge 2 uses Ports 1..3 on Slot 2; uses same Bridge MIB and ifIndex
values as Bridge 1, but in a different context, and representing values as Bridge 1, but in a different context, and representing
different physical ports: different physical ports:
entAliasIdentifier.9.4.1 == dot1dBasePort.1 entAliasIdentifier.4.9.1 == dot1dBasePort.1
entAliasIdentifier.9.4.2 == ifIndex.1 entAliasIdentifier.4.9.2 == ifIndex.1
entAliasIdentifier.10.4.1 == dot1dBasePort.2 entAliasIdentifier.4.10.1 == dot1dBasePort.2
entAliasIdentifier.10.4.2 == ifIndex.2 entAliasIdentifier.4.10.2 == ifIndex.2
entAliasIdentifier.11.4.1 == dot1dBasePort.3 entAliasIdentifier.4.11.1 == dot1dBasePort.3
entAliasIdentifier.11.4.2 == ifIndex.3 entAliasIdentifier.4.11.2 == ifIndex.3
Physical Containment Tree -- entPhysicalContainsTable
chassis has two containers:
entPhysicalChildIndex.1.2 = 2
entPhysicalChildIndex.1.3 = 3
container 1 has a module:
Draft Entity MIB January 14, 1996
entPhysicalChildIndex.2.4 = 4
container 2 has a module
entPhysicalChildIndex.3.8 = 8
module 1 has some ports:
entPhysicalChildIndex.4.5 = 5
entPhysicalChildIndex.4.6 = 6
entPhysicalChildIndex.4.7 = 7
module 2 has some ports:
entPhysicalChildIndex.8.9 = 9
entPhysicalChildIndex.8.10 = 10
entPhysicalChildIndex.1.11 = 11
5.2. Repeaters 5.2. Repeaters
An SNMPv1 only, 3-slot Hub with 2 backplane ethernet segments. Slot An SNMPv1 only, 3-slot Hub with 2 backplane ethernet segments. Slot
three is empty, and the remaining slots contain ethernet repeater three is empty, and the remaining slots contain ethernet repeater
modules. modules.
Physical entities -- entPhysicalTable: Physical entities -- entPhysicalTable:
1 Field-replaceable physical chassis: 1 Field-replaceable physical chassis:
entPhysicalDescr.1 == "Acme Repeater Chassis Model 110" entPhysicalDescr.1 == "Acme Repeater Chassis Model 110"
entPhysicalVendorType.1 == acmeProducts.chassisTypes.2 entPhysicalVendorType.1 == acmeProducts.chassisTypes.2
entPhysicalContainedIn.1 == 0 entPhysicalContainedIn.1 == 0
entPhysicalIsRemovable.1 == true(1) entPhysicalClass.1 == chassis(3)
entPhysicalClass.1 == entPClassChassis
2 Chassis Ethernet Backplanes: 2 Chassis Ethernet Backplanes:
entPhysicalDescr.2 == "Ethernet Backplane 1" entPhysicalDescr.2 == "Ethernet Backplane 1"
entPhysicalVendorType.2 == acmeProducts.backplaneTypes.1 entPhysicalVendorType.2 == acmeProducts.backplaneTypes.1
entPhysicalContainedIn.2 == 1 entPhysicalContainedIn.2 == 1
entPhysicalIsRemovable.2 == false(2) entPhysicalClass.2 == backplane(4)
entPhysicalClass.2 == entPClassNetBackplane
entPhysicalDescr.3 == "Ethernet Backplane 2" entPhysicalDescr.3 == "Ethernet Backplane 2"
entPhysicalVendorType.3 == acmeProducts.backplaneTypes.1 entPhysicalVendorType.3 == acmeProducts.backplaneTypes.1
entPhysicalContainedIn.3 == 1 entPhysicalContainedIn.3 == 1
entPhysicalIsRemovable.3 == false(2) entPhysicalClass.3 == backplane(4)
entPhysicalClass.3 == entPClassNetBackplane
Draft Entity MIB November 17 1995
3 slots within the chassis: 3 slots within the chassis:
entPhysicalDescr.4 == "Acme Hub Slot 1" entPhysicalDescr.4 == "Acme Hub Slot 1"
entPhysicalVendorType.4 == acmeProducts.slotTypes.5 entPhysicalVendorType.4 == acmeProducts.slotTypes.5
entPhysicalContainedIn.4 == 1 entPhysicalContainedIn.4 == 1
entPhysicalIsRemovable.4 == false(2) entPhysicalClass.4 == container(5)
entPhysicalClass.4 == entPClassSlot
Draft Entity MIB January 14, 1996
entPhysicalDescr.5 == "Acme Hub Slot 2" entPhysicalDescr.5 == "Acme Hub Slot 2"
entPhysicalVendorType.5 == acmeProducts.slotTypes.5 entPhysicalVendorType.5 == acmeProducts.slotTypes.5
entPhysicalContainedIn.5 == 1 entPhysicalContainedIn.5 == 1
entPhysicalIsRemovable.5 == false(2) entPhysicalClass.5 == container(5)
entPhysicalClass.5 == entPClassSlot
entPhysicalDescr.6 == "Acme Hub Slot 3" entPhysicalDescr.6 == "Acme Hub Slot 3"
entPhysicalVendorType.6 == acmeProducts.slotTypes.5 entPhysicalVendorType.6 == acmeProducts.slotTypes.5
entPhysicalContainedIn.6 == 1 entPhysicalContainedIn.6 == 1
entPhysicalIsRemovable.6 == false(2) entPhysicalClass.6 == container(5)
entPhysicalClass.6 == entPClassSlot
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 == "10Base-T Module Model 14" entPhysicalDescr.7 == "10Base-T Module Model 14"
entPhysicalVendorType.7 == acmeProducts.moduleTypes.32 entPhysicalVendorType.7 == acmeProducts.moduleTypes.32
entPhysicalContainedIn.7 == 4 entPhysicalContainedIn.7 == 4
entPhysicalIsRemovable.7 == true(1) entPhysicalClass.7 == module(9)
entPhysicalClass.7 == entPClassNetRepeater
entPhysicalDescr.8 == "10Base-T Port 1" entPhysicalDescr.8 == "10Base-T Port 1"
entPhysicalVendorType.8 == acmeProducts.portTypes.10 entPhysicalVendorType.8 == acmeProducts.portTypes.10
entPhysicalContainedIn.8 == 7 entPhysicalContainedIn.8 == 7
entPhysicalIsRemovable.8 == false(2) entPhysicalClass.8 == port(10)
entPhysicalClass.8 == entPClassPort
entPhysicalDescr.9 == "10Base-T Port 2" entPhysicalDescr.9 == "10Base-T Port 2"
entPhysicalVendorType.9 == acmeProducts.portTypes.10 entPhysicalVendorType.9 == acmeProducts.portTypes.10
entPhysicalContainedIn.9 == 7 entPhysicalContainedIn.9 == 7
entPhysicalIsRemovable.9 == false(2) entPhysicalClass.9 == port(10)
entPhysicalClass.9 == entPClassPort
entPhysicalDescr.10 == "10Base-T Port 3" entPhysicalDescr.10 == "10Base-T Port 3"
entPhysicalVendorType.10 == acmeProducts.portTypes.10 entPhysicalVendorType.10 == acmeProducts.portTypes.10
entPhysicalContainedIn.10 == 7 entPhysicalContainedIn.10 == 7
entPhysicalIsRemovable.10 == false(2) entPhysicalClass.10 == port(10)
entPhysicalClass.10 == entPClassPort
entPhysicalDescr.11 == "10Base-T Port 4" entPhysicalDescr.11 == "10Base-T Port 4"
Draft Entity MIB November 17 1995
entPhysicalVendorType.11 == acmeProducts.portTypes.10 entPhysicalVendorType.11 == acmeProducts.portTypes.10
entPhysicalContainedIn.11 == 7 entPhysicalContainedIn.11 == 7
entPhysicalIsRemovable.11 == false(2) entPhysicalClass.11 == port(10)
entPhysicalClass.11 == entPClassPort
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" entPhysicalDescr.12 == "Acme 10Base-T Module Model 4"
entPhysicalVendorType.12 == acmeProducts.moduleTypes.30 entPhysicalVendorType.12 == acmeProducts.moduleTypes.30
entPhysicalContainedIn.12 = 5 entPhysicalContainedIn.12 = 5
entPhysicalIsRemovable.12 = true(1) entPhysicalClass.12 == module(9)
entPhysicalClass.12 == entPClassNetRepeater
entPhysicalDescr.13 == "802.3 AUI Port 1" entPhysicalDescr.13 == "802.3 AUI Port 1"
entPhysicalVendorType.13 == acmeProducts.portTypes.11 entPhysicalVendorType.13 == acmeProducts.portTypes.11
entPhysicalContainedIn.13 == 5 entPhysicalContainedIn.13 == 12
entPhysicalIsRemovable.13 == false(2)
entPhysicalClass.13 == entPClassPort Draft Entity MIB January 14, 1996
entPhysicalClass.13 == port(10)
entPhysicalDescr.14 == "10Base-T Port 2" entPhysicalDescr.14 == "10Base-T Port 2"
entPhysicalVendorType.14 == acmeProducts.portTypes.10 entPhysicalVendorType.14 == acmeProducts.portTypes.10
entPhysicalContainedIn.14 == 5 entPhysicalContainedIn.14 == 12
entPhysicalIsRemovable.14 == false(2) entPhysicalClass.14 == port(10)
entPhysicalClass.14 == entPClassPort
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 == "repeater1" entLogicalDescr.1 == "repeater1"
entLogicalType.1 == snmpDot3RptrMgt entLogicalType.1 == snmpDot3RptrMgt
entLogicalLocalEntityName.1 == ""
entLogicalContext.1 == { 0.0 }
entLogicalCommunity.1 "public-repeater1" entLogicalCommunity.1 "public-repeater1"
entLogicalIpAddress.1 124.125.126.128 entLogicalIpAddress.1 124.125.126.128
Repeater 2--comprised of any ports attached to backplane 2: Repeater 2--comprised of any ports attached to backplane 2:
entLogicalDescr.2 == "repeater2" entLogicalDescr.2 == "repeater2"
entLogicalType.2 == snmpDot3RptrMgt entLogicalType.2 == snmpDot3RptrMgt
entLogicalLocalEntityName.2 == ""
entLogicalContext.2 == { 0.0 }
entLogicalCommunity.2 == "public-repeater2" entLogicalCommunity.2 == "public-repeater2"
entLogicalIpAddress.2 == 124.125.126.128 entLogicalIpAddress.2 == 124.125.126.128
Logical to Physical Mappings -- entLPMappingTable: Logical to Physical Mappings -- entLPMappingTable:
repeater1 uses backplane 1, slot 1-ports 1 & 2, slot 2-port 1 repeater1 uses backplane 1, slot 1-ports 1 & 2, slot 2-port 1
entLPPhysicalIndex.1.2 == 2 entLPPhysicalIndex.1.2 == 2
Draft Entity MIB November 17 1995
entLPPhysicalIndex.1.8 == 8 entLPPhysicalIndex.1.8 == 8
entLPPhysicalIndex.1.9 == 9 entLPPhysicalIndex.1.9 == 9
entLPPhysicalIndex.1.13 == 13 entLPPhysicalIndex.1.13 == 13
repeater2 uses backplane 2, slot 1-ports 3 & 4, slot 2-port 2 repeater2 uses backplane 2, slot 1-ports 3 & 4, slot 2-port 2
entLPPhysicalIndex.2.3 == 3 entLPPhysicalIndex.2.3 == 3
entLPPhysicalIndex.2.10 == 10 entLPPhysicalIndex.2.10 == 10
entLPPhysicalIndex.2.11 == 11 entLPPhysicalIndex.2.11 == 11
entLPPhysicalIndex.2.14 == 14 entLPPhysicalIndex.2.14 == 14
Physical/Logical to Alias Mappings -- entAliasMappingTable: Logical to Physical to Alias Mappings -- entAliasMappingTable:
repeater1 uses slot 1-ports 1 & 2, slot 2-port 1 repeater1 uses slot 1-ports 1 & 2, slot 2-port 1
entAliasIdentifier.8.1.1 == rptrPortGroupIndex.1.1 entAliasIdentifier.1.8.1 == rptrPortGroupIndex.1.1
entAliasIdentifier.9.1.1 == rptrPortGroupIndex.1.2 entAliasIdentifier.1.9.1 == rptrPortGroupIndex.1.2
entAliasIdentifier.13.1.1 == rptrPortGroupIndex.2.1 entAliasIdentifier.1.13.1 == rptrPortGroupIndex.2.1
repeater2 uses slot 1-ports 3 & 4, slot 2-port 2 repeater2 uses slot 1-ports 3 & 4, slot 2-port 2
entAliasIdentifier.10.2.1 == rptrPortGroupIndex.1.3 entAliasIdentifier.2.10.1 == rptrPortGroupIndex.1.3
entAliasIdentifier.11.2.1 == rptrPortGroupIndex.1.4 entAliasIdentifier.2.11.1 == rptrPortGroupIndex.1.4
entAliasIdentifier.14.2.1 == rptrPortGroupIndex.2.2 entAliasIdentifier.2.14.1 == rptrPortGroupIndex.2.2
Draft Entity MIB November 17 1995 Draft Entity MIB January 14, 1996
Physical Containment Tree -- entPhysicalContainsTable
chassis has two backplanes and three containers:
entPhysicalChildIndex.1.2 = 2
entPhysicalChildIndex.1.3 = 3
entPhysicalChildIndex.1.4 = 4
entPhysicalChildIndex.1.5 = 5
entPhysicalChildIndex.1.6 = 6
container 1 has a module:
entPhysicalChildIndex.4.7 = 7
container 2 has a module
entPhysicalChildIndex.5.12 = 12
-- container 3 is empty
module 1 has some ports:
entPhysicalChildIndex.7.8 = 8
entPhysicalChildIndex.7.9 = 9
entPhysicalChildIndex.7.10 = 10
entPhysicalChildIndex.7.11 = 11
module 2 has some ports:
entPhysicalChildIndex.12.13 = 13
entPhysicalChildIndex.12.14 = 14
Draft Entity MIB January 14, 1996
6. Acknowledgements 6. Acknowledgements
This document was produced by the IETF Entity MIB Working Group. This document was produced by the IETF Entity MIB Working Group.
Draft Entity MIB November 17 1995 Draft Entity MIB January 14, 1996
7. References 7. References
[1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure [1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure
of Management Information for version 2 of the Simple Network of Management Information for version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1442, SNMP Research,Inc., Hughes Management Protocol (SNMPv2)", RFC 1442, SNMP Research,Inc., Hughes
LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon
University, April 1993. University, April 1993.
[2] McCloghrie, K., and M. Rose, Editors, "Management Information Base [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base
skipping to change at page 30, line 5 skipping to change at page 32, line 5
Simple Network Management Protocol (SNMPv2)", RFC 1447, Hughes LAN Simple Network Management Protocol (SNMPv2)", RFC 1447, Hughes LAN
Systems, Trusted Information Systems, April 1993. Systems, Trusted Information Systems, April 1993.
[6] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network [6] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network
Management Protocol", RFC 1157, SNMP Research, Performance Systems Management Protocol", RFC 1157, SNMP Research, Performance Systems
International, MIT Laboratory for Computer Science, May 1990. International, MIT Laboratory for Computer Science, May 1990.
[7] McCloghrie, K., and Kastenholtz, F., "Interfaces Group Evolution", [7] McCloghrie, K., and Kastenholtz, F., "Interfaces Group Evolution",
RFC 1573, Hughes LAN Systems, FTP Software, January 1994. RFC 1573, Hughes LAN Systems, FTP Software, January 1994.
Draft Entity MIB November 17 1995 Draft Entity MIB January 14, 1996
8. Security Considerations 8. Security Considerations
Security issues are not discussed in this memo. Security issues are not discussed in this memo.
9. Authors' Addresses 9. Authors' Addresses
Keith McCloghrie Keith McCloghrie
cisco Systems, Inc. cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive
skipping to change at page 31, line 5 skipping to change at page 33, line 5
Phone: 408-526-5260 Phone: 408-526-5260
Email: kzm@cisco.com Email: kzm@cisco.com
Andy Bierman Andy Bierman
Bierman Consulting Bierman Consulting
1200 Sagamore Lane 1200 Sagamore Lane
Ventura, CA 93001 Ventura, CA 93001
Phone: 805-648-2028 Phone: 805-648-2028
Email: abierman@west.net Email: abierman@west.net
Draft Entity MIB November 17 1995 Draft Entity MIB January 14, 1996
Table of Contents Table of Contents
1 Introduction .................................................... 2 1 Introduction .................................................... 2
2 The SNMPv2 Network Management Framework ......................... 3 2 The SNMPv2 Network Management Framework ......................... 3
2.1 Object Definitions ............................................ 3 2.1 Object Definitions ............................................ 3
3 Overview ........................................................ 4 3 Overview ........................................................ 4
3.1 Relationship to Contexts ...................................... 4 3.1 Terms ......................................................... 4
3.2 Relationship to Community Strings ............................. 5 3.2 Relationship to Community Strings ............................. 6
3.3 Relationship to a Chassis MIB ................................. 5 3.3 Relationship to Proxy Mechanisms .............................. 6
3.4 Relationship to the Interfaces MIB ............................ 5 3.4 Relationship to a Chassis MIB ................................. 6
3.5 Relationship to the Other MIBs ................................ 6 3.5 Relationship to the Interfaces MIB ............................ 6
3.6 Re-Configuration of Entities .................................. 6 3.6 Relationship to the Other MIBs ................................ 7
3.7 MIB Structure ................................................. 6 3.7 Re-Configuration of Entities .................................. 7
3.8 Multiple Agents ............................................... 7 3.8 MIB Structure ................................................. 7
4 Definitions ..................................................... 8 3.9 Multiple Agents ............................................... 8
5 Usage Examples .................................................. 21 4 Definitions ..................................................... 9
5.1 Router/Bridge ................................................. 21 5 Usage Examples .................................................. 23
5.2 Repeaters ..................................................... 24 5.1 Router/Bridge ................................................. 23
6 Acknowledgements ................................................ 28 5.2 Repeaters ..................................................... 26
7 References ...................................................... 29 6 Acknowledgements ................................................ 30
8 Security Considerations ......................................... 30 7 References ...................................................... 31
9 Authors' Addresses .............................................. 30 8 Security Considerations ......................................... 32
9 Authors' Addresses .............................................. 32
 End of changes. 

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