As per Relevance of the word represent, we have this rfc below:
Network Working Group K.
Request for Comments: 2037 A.
Category: Standards Track Cisco
October 1996
Entity MIB using SMIv
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
Table of
1. Introduction .............................................. 2
2. The SNMP Network Management Framework ..................... 2
2.1 Object Definitions ....................................... 2
3. Overview .................................................. 3
3.1 Terms .................................................... 4
3.2 Relationship to Community Strings ........................ 5
3.3 Relationship to Proxy Mechanisms ......................... 5
3.4 Relationship to a Chassis MIB ............................ 5
3.5 Relationship to the Interfaces MIB ....................... 6
3.6 Relationship to the Other MIBs ........................... 6
3.7 Relationship to Naming Scopes ............................ 6
3.8 Multiple Instances of the Entity MIB ..................... 7
3.9 Re-Configuration of Entities ............................. 7
3.10 MIB Structure ........................................... 7
3.10.1 entityPhysical Group .................................. 8
3.10.2 entityLogical Group ................................... 8
3.10.3 entityMapping Group ................................... 8
3.10.4 entityGeneral Group ................................... 9
3.10.5 entityNotifications Group ............................. 9
3.11 Multiple Agents ......................................... 9
4. Definitions ............................................... 10
5. Usage Examples ............................................ 26
5.1 Router/Bridge ............................................ 26
5.2 Repeaters ................................................ 30
6. Acknowledgements .......................................... 33
7. References ................................................ 34
8. Security Considerations ................................... 35
9. Authors' Addresses ........................................ 35
McCloghrie & Bierman Standards Track [Page 1]
RFC 2037 Entity MIB using SMIv2 October 1996
1.
This memo defines a portion of the Management Information Base (MIB
for use with network management protocols in the Internet community
In particular, it describes managed objects used for
multiple logical and physical entities managed by a single
agent
2. The SNMP Network Management
The SNMP Network Management Framework presently consists of
major components. They are
o the SMI, described in RFC 1902 [1], - the mechanisms used
describing and naming objects for the purpose of management
o the MIB-II, STD 17, RFC 1213 [2], - the core set of
objects for the Internet suite of protocols
o the protocol, RFC 1157 [6] and/or RFC 1905 [4], - the
for accessing managed information
Textual conventions are defined in RFC 1903 [3], and
statements are defined in RFC 1904 [5].
The Framework permits new objects to be defined for the purpose
experimentation and evaluation
This memo specifies a MIB module that is compliant to the SNMPv2 SMI
A semantically identical MIB conforming to the SNMPv1 SMI can
produced through the appropriate translation
2.1. Object
Managed objects are accessed via a virtual information store,
the Management Information Base or MIB. Objects in the MIB
defined using the subset of Abstract Syntax Notation One (ASN.1)
defined in the SMI. In particular, each object type is named by
OBJECT IDENTIFIER, an administratively assigned name. The
type together with an object instance serves to uniquely identify
specific instantiation of the object. For human convenience,
often use a textual string, termed the descriptor, to refer to
object type
McCloghrie & Bierman Standards Track [Page 2]
RFC 2037 Entity MIB using SMIv2 October 1996
3.
There is a need for a standardized way of representing a single
which supports multiple instances of one MIB. This is presently
for at least 3 standard MIBs, and is likely to become true for
and more MIBs as time passes. For example
- multiple instances of a bridge supported within a
device having a single agent
- multiple repeaters supported by a single agent
- multiple OSPF backbone areas, each one operating as
of its own Autonomous System, and each identified by
same area-id (e.g., 0.0.0.0), supported inside a
router with one agent
The fact that it is a single agent in each of these cases
there is some relationship which binds all of these
together. Effectively, there is some "overall" physical entity
houses the sum of the things managed by that one agent, i.e.,
are multiple "logical" entities within a single physical entity
Sometimes, the overall physical entity contains multiple (smaller
physical entities and each logical entity is associated with
particular physical entity. Sometimes, the overall physical
is a "compound" of multiple physical entities (e.g., a stack
stackable hubs).
What is needed is a way to determine exactly what logical
are managed by the agent (either by SNMPv1 or SNMPv2), and thereby
be able to communicate with the agent about a particular
entity. When different logical entities are associated
different physical entities within the overall physical entity, it
also useful to be able to use this information to distinguish
logical entities
In these situations, there is no need for varbinds for
logical entities to be referenced in the same SNMP message (
that might be useful in the future). Rather, it is sufficient,
in some situations preferable, to have the context/community in
message identify the logical entity to which the varbinds apply
McCloghrie & Bierman Standards Track [Page 3]
RFC 2037 Entity MIB using SMIv2 October 1996
3.1.
Some new terms are used throughout this document
- Naming
A "naming scope" represents the set of information that may
potentially accessed through a single SNMP operation. All
within the naming scope share the same unique identifier space.
SNMPv1, a naming scope is identified by the value of the
'entLogicalCommunity' instance
- Multi-Scoped
A MIB object, for which identical instance values
different managed information in different naming scopes, is
a "multi-scoped" MIB object
- Single-Scoped
A MIB object, for which identical instance values identify the
managed information in different naming scopes, is called
"single-scoped" MIB object
- Logical
A managed system contains one or more logical entities,
represented by at most one instantiation of each of a
set of MIB objects. A set of management functions is
with each logical entity. Examples of logical entities
routers, bridges, print-servers, etc
- Physical
A "physical entity" or "physical component" represents
identifiable physical resource within a managed system. Zero
more logical entities may utilize a physical resource at any
time. It is an implementation-specific manner as to which
components are represented by an agent in the EntPhysicalTable
Typically, physical resources (e.g. communications ports
backplanes, sensors, daughter-cards, power supplies, the
chassis) which can be managed via functions associated with one
more logical entities are included in the MIB
- Containment
Each physical component may optionally be modeled as 'contained
within another physical component. A "containment-tree" is
conceptual sequence of entPhysicalIndex values which
specifies the exact physical location of a physical
within the managed system. It is generated by 'following
recording' each 'entPhysicalContainedIn' instance 'up the
towards the root', until a value of zero indicating no
containment is found
McCloghrie & Bierman Standards Track [Page 4]
RFC 2037 Entity MIB using SMIv2 October 1996
Note that chassis slots, which are capable of accepting one or
module types from one or more vendors, are modeled as containers
this MIB. The value of entPhysicalContainedIn for a
'module' entity (entPhysicalClass value of 'module(9)') must
equal to an entPhysicalIndex that represents the parent 'container
entity (associated entPhysicalClass value of ('container(5)').
agent must represent both empty and full containers in
entPhysicalTable
3.2. Relationship to Community
For community-based SNMP, distinguishing between different
entities is one (but not the only) purpose of the community
[6]. This is accommodated by representing each community string as
logical entity
Note that different logical entities may share the same naming
(and therefore the same values of entLogicalCommunity). This
possible, providing they have no need for the same instance of a
object to represent different managed information
3.3. Relationship to Proxy
The Entity MIB is designed to allow functional component discovery
The administrative relationships between different logical
are not visible in any Entity MIB tables. An NMS cannot
whether MIB instances in different naming scopes are realized
or remotely (e.g. via some proxy mechanism) by examining
particular Entity MIB objects
The management of administrative framework functions is not
explicit goal of the Entity MIB WG at this time. This new area
functionality may be revisited after some operational experience
the Entity MIB is gained
Note that a network administrator will likely be able to
community strings with naming scopes with proprietary mechanisms,
a matter of configuration. There are no mechanisms for
naming scopes defined in this MIB
3.4. Relationship to a Chassis
Some readers may recall that a previous IETF working group
to define a Chassis MIB. No consensus was reached by that
group, possibly because its scope was too broad. As such, it is
the purpose of this MIB to be a "Chassis MIB replacement", nor is
within the scope of this MIB to contain all the information
might be necessary to manage a "chassis". On the other hand,
McCloghrie & Bierman Standards Track [Page 5]
RFC 2037 Entity MIB using SMIv2 October 1996
entities represented by an implementation of this MIB might well
contained in a chassis
3.5. Relationship to the Interfaces
The Entity MIB contains a mapping table identifying
components that have 'external values' (e.g. ifIndex) associated
them within a given naming scope. This table can be used to
the physical location of each interface in the ifTable [7].
ifIndex values in different contexts are not related to one another
the interface to physical component associations are relative to
same logical entity within the agent
The Entity MIB also contains an 'entPhysicalName' object,
approximates the semantics of the ifName object from the
MIB [7] for all types of physical components
3.6. Relationship to the Other
The Entity MIB contains a mapping table identifying
components that have identifiers from other standard MIBs
with them. For example, this table can be used along with
physical mapping table to identify the physical location of
repeater port in the rptrPortTable, or each interface in the ifTable
3.7. Relationship to Naming
There is some question as to which MIB objects may be returned
a given naming scope. MIB objects which are not multi-scoped within
managed system are likely to ignore context information
implementation. In such a case, it is likely such objects will
returned in all naming scopes (e.g. not just the 'main'
scope).
For example, a community string used to access the
information for logical device 'bridge2' may allow access to all
non-bridge related objects in the 'main' naming scope, as well as
second instance of the Bridge MIB
It is an implementation-specific matter as to the isolation
single-scoped MIB objects by the agent. An agent may wish to
the objects returned in a particular naming scope to just the multi
scoped objects in that naming scope (e.g. system group and the
MIB). In this case, all single-scoped management information
belong to a common naming scope (e.g. 'main'), which itself
contain some multi-scoped objects (e.g. system group).
McCloghrie & Bierman Standards Track [Page 6]
RFC 2037 Entity MIB using SMIv2 October 1996
3.8. Multiple Instances of the Entity
It is possible that more than one agent exists in a managed system
and in such cases, multiple instances of the Entity MIB (
the same managed objects) may be available to an NMS
In order to reduce complexity for agent implementation,
instances of the Entity MIB are not required to be equivalent or
consistent. An NMS may be able to 'align' instances returned
different agents by examining the columns of each table, but vendor
specific identifiers and (especially) index values are likely to
different. Each agent may be managing different subsets of the
chassis as well
When all of a physically-modular device is represented by a
agent, the entry for which entPhysicalContainedIn has the value
would likely have 'chassis' as the value of its entPhysicalClass
alternatively, for an agent on a module where the agent
only the physical entities on that module (not those on
modules), the entry for which entPhysicalContainedIn has the
zero would likely have 'module' as the value of its entPhysicalClass
An agent implementation of the entLogicalTable is not required
contain information about logical entities managed primarily by
agents. That is, the entLogicalTAddress and entLogicalTDomain
in the entLogicalTable are provided to support an
multiplexing mechanism, not to identify other SNMP agents
Note that the Entity MIB is a single-scoped MIB, in the event
agent represents the MIB in different naming scopes
3.9. Re-Configuration of
All the MIB objects defined in this MIB have at most a read-
MAX-ACCESS clause, i.e., none are write-able. This is a
decision by the working group to limit this MIB's scope. It
possible that this restriction could be lifted after
experience, by means of additional tables (using the AUGMENTS clause
for configuration and extended entity information
3.10. MIB
The Entity MIB contains five conformance groups
- entityPhysical
Describes the physical entities managed by a single agent
McCloghrie & Bierman Standards Track [Page 7]
RFC 2037 Entity MIB using SMIv2 October 1996
- entityLogical
Describes the logical entities managed by a single agent
- entityMapping
Describes the associations between the physical entities
logical entities, interfaces, and non-interface ports
by a single agent
-entityGeneral
Describes general system attributes shared by
all types of entities managed by a single agent
-entityNotifications
Contains status indication notifications
3.10.1. entityPhysical
This group contains a single table to identify physical
components, called the entPhysicalTable
The entPhysicalTable contains one row per physical entity, and
always contains at least one row for an "overall" physical entity
Each row is indexed by an arbitrary, small integer, and contains
description and type of the physical entity. It also
contains the index number of another entPhysicalEntry indicating
containment relationship between the two
3.10.2. entityLogical
This group contains a single table to identify logical entities
called the entLogicalTable
The entLogicalTable contains one row per logical entity. Each row
indexed by an arbitrary, small integer and contains a name
description, and type of the logical entity. It also
information to allow SNMPv1 or SNMPv2C [9] access to the
information for the logical entity
3.10.3. entityMapping
This group contains a three tables to identify associations
different system components
The entLPMappingTable contains mappings between
values (logical entities) and entPhysicalIndex values (the
components supporting that entity). A logical entity can map to
than one physical component, and more than one logical entity can
to (share) the same physical component
McCloghrie & Bierman Standards Track [Page 8]
RFC 2037 Entity MIB using SMIv2 October 1996
The entAliasMappingTable contains mappings between entLogicalIndex
entPhysicalIndex pairs and 'alias' object identifier values.
allows resources managed with other MIBs (e.g. repeater ports,
ports, physical and logical interfaces) to be identified in
physical entity hierarchy. Note that each alias identifier is
relevant in a particular naming scope
The entPhysicalContainsTable contains simple mappings
'entPhysicalContainedIn' values for each container/
relationship in the managed system. The indexing of this table
an NMS to quickly discover the 'entPhysicalIndex' values for
children of a given physical entity
3.10.4. entityGeneral
This group contains general information relating to the other
groups
At this time, the entGeneral group contains a single scalar
(entLastChangeTime), which represents the value of sysUptime when
part of the system configuration last changed
3.10.5. entityNotifications
This group contains notification definitions relating to the
status of the Entity MIB instantiation
3.11. Multiple
Even though a primary motivation for this MIB is to represent
multiple logical entities supported by a single agent, it is
possible to use it to represent multiple logical entities
by multiple agents (in the same "overall" physical entity). Indeed
it is implicit in the SNMP architecture, that the number of agents
transparent to a network management station
However, there is no agreement at this time as to the degree
cooperation which should be expected for agent implementations
Therefore, multiple agents within the same managed system are free
implement the Entity MIB independently. (Refer the section
"Multiple Instances of the Entity MIB" for more details).
McCloghrie & Bierman Standards Track [Page 9]
RFC 2037 Entity MIB using SMIv2 October 1996
4.
ENTITY-MIB DEFINITIONS ::=
MODULE-IDENTITY, OBJECT-TYPE
mib-2, NOTIFICATION-
FROM SNMPv2-
TDomain, TAddress, DisplayString, TEXTUAL-CONVENTION
AutonomousType, RowPointer,
FROM SNMPv2-
MODULE-COMPLIANCE, OBJECT-
FROM SNMPv2-CONF
entityMIB MODULE-
LAST-UPDATED "9605160000Z
ORGANIZATION "IETF ENTMIB Working Group
CONTACT-
" WG E-mail: entmib@cisco.
Subscribe: majordomo@cisco.
msg body: subscribe
Keith
ENTMIB Working Group
Cisco Systems Inc
170 West Tasman
San Jose, CA 95134
408-526-5260
kzm@cisco.
Andy
ENTMIB Working Group
Cisco Systems Inc
170 West Tasman
San Jose, CA 95134
408-527-3711
abierman@cisco.com
"The MIB module for representing multiple
entities supported by a single SNMP agent."
::= { mib-2 47 }
entityMIBObjects OBJECT IDENTIFIER ::= { entityMIB 1 }
-- MIB contains four
entityPhysical OBJECT IDENTIFIER ::= { entityMIBObjects 1 }
entityLogical OBJECT IDENTIFIER ::= { entityMIBObjects 2 }
McCloghrie & Bierman Standards Track [Page 10]
RFC 2037 Entity MIB using SMIv2 October 1996
entityMapping OBJECT IDENTIFIER ::= { entityMIBObjects 3 }
entityGeneral OBJECT IDENTIFIER ::= { entityMIBObjects 4 }
-- Textual
PhysicalIndex ::= TEXTUAL-
STATUS
"An arbitrary value which uniquely identifies the
entity. The value is a small positive integer; index
for different physical entities are not
contiguous."
SYNTAX INTEGER (1..2147483647)
PhysicalClass ::= TEXTUAL-
STATUS
"An enumerated value which provides an indication of
general hardware type of a particular physical entity."
SYNTAX INTEGER {
other(1),
unknown(2),
chassis(3),
backplane(4),
container(5), -- e.g. slot or daughter-card
powerSupply(6),
fan(7),
sensor(8),
module(9), -- e.g. plug-in card or daughter-
port(10)
}
-- The Physical Entity
entPhysicalTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"This table contains one row per physical entity. There
always at least one row for an 'overall' physical entity."
::= { entityPhysical 1 }
entPhysicalEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
McCloghrie & Bierman Standards Track [Page 11]
RFC 2037 Entity MIB using SMIv2 October 1996
"Information about a particular physical entity
Each entry provides objects (entPhysicalDescr
entPhysicalVendorType, and entPhysicalClass) to help an
identify and characterize the entry, and
(entPhysicalContainedIn and entPhysicalParentRelPos) to
an NMS relate the particular entry to other entries in
table."
INDEX { entPhysicalIndex }
::= { entPhysicalTable 1 }
EntPhysicalEntry ::= SEQUENCE {
entPhysicalIndex PhysicalIndex
entPhysicalDescr DisplayString
entPhysicalVendorType AutonomousType
entPhysicalContainedIn INTEGER
entPhysicalClass PhysicalClass
entPhysicalParentRelPos INTEGER
entPhysicalName
entPhysicalIndex OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"The index for this entry."
::= { entPhysicalEntry 1 }
entPhysicalDescr OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"A textual description of physical entity. This
should contain a string which identifies the manufacturer'
name for the physical entity, and should be set to
distinct value for each version or model of the
entity. "
::= { entPhysicalEntry 2 }
entPhysicalVendorType OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"An indication of the vendor-specific hardware type of
McCloghrie & Bierman Standards Track [Page 12]
RFC 2037 Entity MIB using SMIv2 October 1996
physical entity. Note that this is different from
definition of MIB-II's sysObjectID
An agent should set this object to a enterprise-
registration identifier value indicating the
equipment type in detail. The associated instance
entPhysicalClass is used to indicate the general type
hardware device
If no vendor-specific registration identifier exists
this physical entity, or the value is unknown by this agent
then the value { 0 0 } is returned."
::= { entPhysicalEntry 3 }
entPhysicalContainedIn OBJECT-
SYNTAX INTEGER (0..2147483647)
MAX-ACCESS read-
STATUS
"The value of entPhysicalIndex for the physical entity
'contains' this physical entity. A value of zero
this physical entity is not contained in any other
entity. Note that the set of 'containment'
define a strict hierarchy; that is, recursion is
allowed."
::= { entPhysicalEntry 4 }
entPhysicalClass OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"An indication of the general hardware type of the
entity
An agent should set this object to the standard
value which most accurately indicates the general class
the physical entity, or the primary class if there is
than one
If no appropriate standard registration identifier
for this physical entity, then the value 'other(1)'
returned. If the value is unknown by this agent, then
value 'unknown(2)' is returned."
::= { entPhysicalEntry 5 }
entPhysicalParentRelPos OBJECT-
SYNTAX INTEGER (-1..2147483647)
McCloghrie & Bierman Standards Track [Page 13]
RFC 2037 Entity MIB using SMIv2 October 1996
MAX-ACCESS read-
STATUS
"An indication of the relative position of this 'child
component among all its 'sibling' components.
components are defined as entPhysicalEntries which share
same instance values of each of the
and entPhysicalClass objects
An NMS can use this object to identify the relative
for all sibling components of a particular
(identified by the entPhysicalContainedIn instance in
sibling entry).
This value should match any external labeling of
physical component if possible. For example, for a
labeled as 'card #3', entPhysicalParentRelPos should
the value '3'.
If the physical position of this component does not
any external numbering or clearly visible ordering,
user documentation or other external reference
should be used to determine the parent-relative position.
this is not possible, then the the agent should assign
consistent (but possibly arbitrary) ordering to a given
of 'sibling' components, perhaps based on
representation of the components
If the agent cannot determine the parent-relative
for some reason, or if the associated value
entPhysicalContainedIn is '0', then the value '-1'
returned. Otherwise a non-negative integer is returned
indicating the parent-relative position of this
entity
Parent-relative ordering normally starts from '1'
continues to 'N', where 'N' represents the
positioned child entity. However, if the physical
(e.g. slots) are labeled from a starting position of zero
then the first sibling should be associated with
entPhysicalParentRelPos value of '0'. Note that
ordering may be sparse or dense, depending on
implementation
The actual values returned are not globally meaningful,
each 'parent' component may use different
algorithms. The ordering is only meaningful among
of the same parent component
McCloghrie & Bierman Standards Track [Page 14]
RFC 2037 Entity MIB using SMIv2 October 1996
The agent should retain parent-relative position
across reboots, either through algorithmic assignment or
of non-volatile storage."
::= { entPhysicalEntry 6 }
entPhysicalName OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The textual name of the physical entity. The value of
object should be the name of the component as assigned
the local device and should be suitable for use in
entered at the device's `console'. This might be a
name, such as `console' or a simple component number (e.g
port or module number), such as `1', depending on
physical component naming syntax of the device
If there is no local name, or this object is otherwise
applicable, then this object contains a zero-length string
Note that the value of entPhysicalName for two
entities will be the same in the event that the
interface does not distinguish between them, e.g., slot-1
and the card in slot-1."
::= { entPhysicalEntry 7 }
-- The Logical Entity
entLogicalTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"This table contains one row per logical entity. At
one entry must exist."
::= { entityLogical 1 }
entLogicalEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Information about a particular logical entity.
may be managed by this agent or other SNMP agents (possibly
in the same chassis."
INDEX { entLogicalIndex }
::= { entLogicalTable 1 }
McCloghrie & Bierman Standards Track [Page 15]
RFC 2037 Entity MIB using SMIv2 October 1996
EntLogicalEntry ::= SEQUENCE {
entLogicalIndex INTEGER
entLogicalDescr DisplayString
entLogicalType AutonomousType
entLogicalCommunity OCTET STRING
entLogicalTAddress TAddress
entLogicalTDomain
entLogicalIndex OBJECT-
SYNTAX INTEGER (1..2147483647)
MAX-ACCESS not-
STATUS
"The value of this object uniquely identifies the
entity. The value is a small positive integer; index
for different logical entities are are not
contiguous."
::= { entLogicalEntry 1 }
entLogicalDescr OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"A textual description of the logical entity. This
should contain a string which identifies the manufacturer'
name for the logical entity, and should be set to a
value for each version of the logical entity. "
::= { entLogicalEntry 2 }
entLogicalType OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"An indication of the type of logical entity. This
typically be the OBJECT IDENTIFIER name of the node in
SMI's naming hierarchy which represents the major
module, or the majority of the MIB modules, supported by
logical entity. For example
a logical entity of a regular host/router -> mib-2
a logical entity of a 802.1d bridge -> dot1
a logical entity of a 802.3 repeater -> snmpDot3
If an appropriate node in the SMI's naming hierarchy
be identified, the value 'mib-2' should be used."
::= { entLogicalEntry 3 }
McCloghrie & Bierman Standards Track [Page 16]
RFC 2037 Entity MIB using SMIv2 October 1996
entLogicalCommunity OBJECT-
SYNTAX OCTET STRING (SIZE (1..255))
MAX-ACCESS read-
STATUS
"An SNMPv1 or SNMPv2C community-string which can be used
access detailed management information for this
entity. The agent should allow read access with
community string (to an appropriate subset of all
objects) and may also choose to return a community
based on the privileges of the request used to read
object. Note that an agent may choose to return a
string with read-only privileges, even if this object
accessed with a read-write community string. However,
agent must take care not to return a community string
allows more privileges than the community string used
access this object
A compliant SNMP agent may wish to conserve naming scopes
representing multiple logical entities in a single 'main
naming scope. This is possible when the logical
represented by the same value of entLogicalCommunity have
object instances in common. For example, 'bridge1'
'repeater1' may be part of the main naming scope, but
least one additional community string is needed to
'bridge2' and 'repeater2'.
Logical entities 'bridge1' and 'repeater1' would
represented by sysOREntries associated with the 'main
naming scope
For agents not accessible via SNMPv1 or SNMPv2C, the
of this object is the empty-string."
::= { entLogicalEntry 4 }
entLogicalTAddress OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The transport service address by which the logical
receives network management traffic, formatted according
the corresponding value of entLogicalTDomain
For snmpUDPDomain, a TAddress is 6 octets long, the
4 octets containing the IP-address in network-byte order
the last 2 containing the UDP port in network-byte order
Consult 'Transport Mappings for Version 2 of the
McCloghrie & Bierman Standards Track [Page 17]
RFC 2037 Entity MIB using SMIv2 October 1996
Network Management Protocol' (RFC 1906 [8]) for
information on snmpUDPDomain."
::= { entLogicalEntry 5 }
entLogicalTDomain OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"Indicates the kind of transport service by which
logical entity receives network management traffic
Possible values for this object are presently found in
Transport Mappings for SNMPv2 document (RFC 1906 [8])."
::= { entLogicalEntry 6 }
entLPMappingTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"This table contains zero or more rows of logical entity
physical equipment associations. For each logical
known by this agent, there are zero or more mappings to
physical resources which are used to realize that
entity
An agent should limit the number and nature of entries
this table such that only meaningful and non-
information is returned. For example, in a system
contains a single power supply, mappings between
entities and the power supply are not useful and should
be included
Also, only the most appropriate physical component which
closest to the root of a particular containment tree
be identified in an entLPMapping entry
For example, suppose a bridge is realized on a
module, and all ports on that module are ports on
bridge. A mapping between the bridge and the module would
useful, but additional mappings between the bridge and
of the ports on that module would be redundant (since
entPhysicalContainedIn hierarchy can provide the
information). If, on the other hand, more than one
was utilizing ports on this module, then mappings
each bridge and the ports it used would be appropriate
Also, in the case of a single backplane repeater, a
McCloghrie & Bierman Standards Track [Page 18]
RFC 2037 Entity MIB using SMIv2 October 1996
for the backplane to the single repeater entity is
necessary."
::= { entityMapping 1 }
entLPMappingEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Information about a particular logical entity to
equipment association. Note that the nature of
association is not specifically identified in this entry.
is expected that sufficient information exists in the
used to manage a particular logical entity to infer
physical component information is utilized."
INDEX { entLogicalIndex, entLPPhysicalIndex }
::= { entLPMappingTable 1 }
EntLPMappingEntry ::= SEQUENCE {
entLPPhysicalIndex
entLPPhysicalIndex OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of this object identifies the index value of
particular entPhysicalEntry associated with the
entLogicalEntity."
::= { entLPMappingEntry 1 }
-- logical entity/component to alias
entAliasMappingTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"This table contains zero or more rows,
mappings of logical entity and physical component
external MIB identifiers. Each physical port in the
may be associated with a mapping to an external identifier
which itself is associated with a particular
entity's naming scope. A 'wildcard' mechanism is provided
indicate that an identifier is associated with more than
logical entity."
::= { entityMapping 2 }
McCloghrie & Bierman Standards Track [Page 19]
RFC 2037 Entity MIB using SMIv2 October 1996
entAliasMappingEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"Information about a particular physical equipment,
entity to external identifier binding. Each
entity/physical component pair may be associated with
alias mapping. The logical entity index may also be used
a 'wildcard' (refer to the entAliasLogicalIndexOrZero
DESCRIPTION clause for details.)
Note that only entPhysicalIndex values which
physical ports (i.e. associated entPhysicalClass value
'port(10)') are permitted to exist in this table."
INDEX { entPhysicalIndex, entAliasLogicalIndexOrZero }
::= { entAliasMappingTable 1 }
EntAliasMappingEntry ::= SEQUENCE {
entAliasLogicalIndexOrZero INTEGER
entAliasMappingIdentifier
entAliasLogicalIndexOrZero OBJECT-
SYNTAX INTEGER (0..2147483647)
MAX-ACCESS not-
STATUS
"The value of this object uniquely identifies the
entity which defines the naming scope for the
instance of the 'entAliasMappingIdentifier' object
If this object has a non-zero value, then it identifies
logical entity named by the same value of entLogicalIndex
If this object has a value of zero, then the mapping
the physical component and the alias identifier for
entAliasMapping entry is associated with all
logical entities. That is, a value of zero (the
mapping) identifies any logical entity which does not
an explicit entry in this table for a
entPhysicalIndex/entAliasMappingIdentifier pair
For example, to indicate that a particular interface (e.g
physical component 33) is identified by the same value
ifIndex for all logical entities, the following
might exist
McCloghrie & Bierman Standards Track [Page 20]
RFC 2037 Entity MIB using SMIv2 October 1996
entAliasMappingIdentifier.33.0 = ifIndex.5
In the event an entPhysicalEntry is associated
for some logical entities, additional
entries may exist, e.g.:
entAliasMappingIdentifier.33.0 = ifIndex.6
entAliasMappingIdentifier.33.4 = ifIndex.1
entAliasMappingIdentifier.33.5 = ifIndex.1
entAliasMappingIdentifier.33.10 = ifIndex.12
Note that entries with non-zero
index values have precedence over any zero-indexed entry.
this example, all logical entities except 4, 5, and 10,
associate physical entity 33 with ifIndex.6."
::= { entAliasMappingEntry 1 }
entAliasMappingIdentifier OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of this object identifies a particular
row associated with the indicated entPhysicalIndex
entLogicalIndex pair
Since only physical ports are modeled in this table,
entries which represent interfaces or ports are allowed.
an ifEntry exists on behalf of a particular physical port
then this object should identify the associated 'ifEntry'.
For repeater ports, the appropriate row in
'rptrPortGroupTable' should be identified instead
For example, suppose a physical port was represented
entPhysicalEntry.3, entLogicalEntry.15 existed for
repeater, and entLogicalEntry.22 existed for a bridge.
there might be two related instances
entAliasMappingIdentifier
entAliasMappingIdentifier.3.15 == rptrPortGroupIndex.5.2
entAliasMappingIdentifier.3.22 == ifIndex.17
It is possible that other mappings (besides interfaces
repeater ports) may be defined in the future, as required
Bridge ports are identified by examining the Bridge MIB
appropriate ifEntries associated with each 'dot1dBasePort',
and are thus not represented in this table."
::= { entAliasMappingEntry 2 }
McCloghrie & Bierman Standards Track [Page 21]
RFC 2037 Entity MIB using SMIv2 October 1996
-- physical mapping
entPhysicalContainsTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"A table which exposes the container/containee
between physical entities. This table provides
information found by constructing the virtual
tree for a given entPhysicalTable but in a more
format."
::= { entityMapping 3 }
entPhysicalContainsEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"A single container/containee relationship."
INDEX { entPhysicalIndex, entPhysicalChildIndex }
::= { entPhysicalContainsTable 1 }
EntPhysicalContainsEntry ::= SEQUENCE {
entPhysicalChildIndex
entPhysicalChildIndex OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of entPhysicalIndex for the contained
entity."
::= { entPhysicalContainsEntry 1 }
-- last change time stamp for the whole
entLastChangeTime OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of sysUpTime at the time any of these
occur
* a conceptual row is created or deleted in
of these tables
-
-
-
McCloghrie & Bierman Standards Track [Page 22]
RFC 2037 Entity MIB using SMIv2 October 1996
-
-
* any instance in the following list of
changes value
-
-
-
-
-
-
-
-
-
-
-
- entAliasMappingIdentifier "
::= { entityGeneral 1 }
-- Entity MIB Trap
entityMIBTraps OBJECT IDENTIFIER ::= { entityMIB 2 }
entityMIBTrapPrefix OBJECT IDENTIFIER ::= { entityMIBTraps 0 }
entConfigChange NOTIFICATION-
STATUS
"An entConfigChange trap is sent when the value
entLastChangeTime changes. It can be utilized by an NMS
trigger logical/physical entity table maintenance polls
An agent must not generate more than one
'trap-event' in a five second period, where a 'trap-event
is the transmission of a single trap PDU to a list of
destinations. If additional configuration changes
within the five second 'throttling' period, then
trap-events should be suppressed by the agent. An NMS
periodically check the value of entLastChangeTime to
any missed entConfigChange trap-events, e.g. due
throttling or transmission loss."
::= { entityMIBTrapPrefix 1 }
-- conformance
entityConformance OBJECT IDENTIFIER ::= { entityMIB 3 }
entityCompliances OBJECT IDENTIFIER ::= { entityConformance 1 }
entityGroups OBJECT IDENTIFIER ::= { entityConformance 2 }
-- compliance
McCloghrie & Bierman Standards Track [Page 23]
RFC 2037 Entity MIB using SMIv2 October 1996
entityCompliance MODULE-
STATUS
"The compliance statement for SNMP entities which
the Entity MIB."
MODULE -- this
MANDATORY-GROUPS { entityPhysicalGroup
entityLogicalGroup
entityMappingGroup
entityGeneralGroup
entityNotificationsGroup }
::= { entityCompliances 1 }
-- MIB
entityPhysicalGroup OBJECT-
OBJECTS {
entPhysicalDescr
entPhysicalVendorType
entPhysicalContainedIn
entPhysicalClass
entPhysicalParentRelPos
}
STATUS
"The collection of objects which are used to
physical system components, for which a single
provides management information."
::= { entityGroups 1 }
entityLogicalGroup OBJECT-
OBJECTS {
entLogicalDescr
entLogicalType
entLogicalCommunity
entLogicalTAddress
}
STATUS
"The collection of objects which are used to represent
list of logical entities for which a single agent
management information."
::= { entityGroups 2 }
entityMappingGroup OBJECT-
OBJECTS {
McCloghrie & Bierman Standards Track [Page 24]
RFC 2037 Entity MIB using SMIv2 October 1996
entLPPhysicalIndex
entAliasMappingIdentifier
}
STATUS
"The collection of objects which are used to represent
associations between multiple logical entities,
components, interfaces, and port identifiers for which
single agent provides management information."
::= { entityGroups 3 }
entityGeneralGroup OBJECT-
OBJECTS {
}
STATUS
"The collection of objects which are used to
general entity information for which a single agent
management information."
::= { entityGroups 4 }
entityNotificationsGroup NOTIFICATION-
NOTIFICATIONS { entConfigChange }
STATUS
"The collection of notifications used to indicate Entity
data consistency and general status information."
::= { entityGroups 5 }
McCloghrie & Bierman Standards Track [Page 25]
RFC 2037 Entity MIB using SMIv2 October 1996
5. Usage
The following sections iterate the instance values for two
networking devices. These examples are kept simple to make them
understandable. Auxiliary components, such as fans, sensors,
slots, and sub-modules are not shown, but might be modeled in
implementations
5.1. Router/
A router containing two slots. Each slot contains a 3
router/bridge module. Each port is represented in the ifTable.
are two logical instances of OSPF running and two logical bridges
Physical entities -- entPhysicalTable
1 Field-replaceable physical chassis
entPhysicalDescr.1 == "Acme Chassis Model 100"
entPhysicalVendorType.1 == acmeProducts.chassisTypes.1
entPhysicalContainedIn.1 == 0
entPhysicalClass.1 == chassis(3)
entPhysicalParentRelPos.1 == 0
entPhysicalName.1 == '100-A
2 slots within the chassis
entPhysicalDescr.2 == "Acme Chassis Slot Type AA
entPhysicalVendorType.2 == acmeProducts.slotTypes.1
entPhysicalContainedIn.2 == 1
entPhysicalClass.2 == container(5)
entPhysicalParentRelPos.2 == 1
entPhysicalName.2 == 'S1'
entPhysicalDescr.3 == "Acme Chassis Slot Type AA
entPhysicalVendorType.3 == acmeProducts.slotTypes.1
entPhysicalContainedIn.3 == 1
entPhysicalClass.3 == container(5)
entPhysicalParentRelPos.3 == 2
entPhysicalName.3 == 'S2'
2 Field-replaceable modules
Slot 1 contains a module with 3 ports
entPhysicalDescr.4 == "Acme Router-100"
entPhysicalVendorType.4 == acmeProducts.moduleTypes.14
entPhysicalContainedIn.4 == 2
entPhysicalClass.4 == module(9)
entPhysicalParentRelPos.4 == 1
entPhysicalName.4 == 'M1'
entPhysicalDescr.5 == "Acme Ethernet-100 Port Rev G
McCloghrie & Bierman Standards Track [Page 26]
RFC 2037 Entity MIB using SMIv2 October 1996
entPhysicalVendorType.5 == acmeProducts.portTypes.2
entPhysicalContainedIn.5 == 4
entPhysicalClass.5 == port(10)
entPhysicalParentRelPos.5 == 1
entPhysicalName.5 == 'P1'
entPhysicalDescr.6 == "Acme Ethernet-100 Port Rev G
entPhysicalVendorType.6 == acmeProducts.portTypes.2
entPhysicalContainedIn.6 == 4
entPhysicalClass.6 == port(10)
entPhysicalParentRelPos.6 == 2
entPhysicalName.6 == 'P2'
entPhysicalDescr.7 == "Acme Router-100 F-Port: Rev B
entPhysicalVendorType.7 == acmeProducts.portTypes.3
entPhysicalContainedIn.7 == 4
entPhysicalClass.7 == port(10)
entPhysicalParentRelPos.7 == 3
entPhysicalName.7 == 'P3'
Slot 2 contains another 3-port module
entPhysicalDescr.8 == "Acme Router-100 Comm Module: Rev C
entPhysicalVendorType.8 == acmeProducts.moduleTypes.15
entPhysicalContainedIn.8 == 3
entPhysicalClass.8 == module(9)
entPhysicalParentRelPos.8 == 1
entPhysicalName.8 == 'M2'
entPhysicalDescr.9 == "Acme Fddi-100 Port Rev CC
entPhysicalVendorType.9 == acmeProducts.portTypes.5
entPhysicalContainedIn.9 == 8
entPhysicalClass.9 == port(10)
entPhysicalParentRelPos.9 == 1
entPhysicalName.9 == 'FDDI Primary
entPhysicalDescr.10 == "Acme Ethernet-100 Port Rev G
entPhysicalVendorType.10 == acmeProducts.portTypes.2
entPhysicalContainedIn.10 == 8
entPhysicalClass.10 == port(10)
entPhysicalParentRelPos.10 == 2
entPhysicalName.10 == 'Ethernet A
entPhysicalDescr.11 == "Acme Ethernet-100 Port Rev G
entPhysicalVendorType.11 == acmeProducts.portTypes.2
entPhysicalContainedIn.11 == 8
entPhysicalClass.11 == port(10)
entPhysicalParentRelPos.11 == 3
entPhysicalName.11 == 'Ethernet B
McCloghrie & Bierman Standards Track [Page 27]
RFC 2037 Entity MIB using SMIv2 October 1996
Logical entities --
2 OSPF instances
entLogicalDescr.1 == "Acme OSPF v1.1"
entLogicalType.1 ==
entLogicalCommunity.1 == "public-ospf1"
entLogicalTAddress.1 == 124.125.126.127:161
entLogicalTDomain.1 ==
entLogicalDescr.2 == "Acme OSPF v1.1"
entLogicalType.2 ==
entLogicalCommunity.2 == "public-ospf2"
entLogicalTAddress.2 == 124.125.126.127:161
entLogicalTDomain.2 ==
2 logical bridges
entLogicalDescr.3 == "Acme Bridge v2.1.1"
entLogicalType.3 == dod1
entLogicalCommunity.3 == "public-bridge1"
entLogicalTAddress.3 == 124.125.126.127:161
entLogicalTDomain.3 ==
entLogicalDescr.4 == "Acme Bridge v2.1.1"
entLogicalType.4 == dod1
entLogicalCommunity.4 == "public-bridge2"
entLogicalTAddress.4 == 124.125.126.127:161
entLogicalTDomain.4 ==
Logical to Physical Mappings
1st OSPF instance: uses module 1-port 1
entLPPhysicalIndex.1.5 == 5
2nd OSPF instance: uses module 2-port 1
entLPPhysicalIndex.2.9 == 9
1st bridge group: uses module 1, all
[ed. -- Note that these mappings are included in the table
another logical entity (1st OSPF) utilizes one of
ports. If this were not the case, then a single
to the module (e.g. entLPPhysicalIndex.3.4) would
present instead. ]
entLPPhysicalIndex.3.5 == 5
entLPPhysicalIndex.3.6 == 6
entLPPhysicalIndex.3.7 == 7
2nd bridge group: uses module 2, all
entLPPhysicalIndex.4.9 == 9
entLPPhysicalIndex.4.10 == 10
McCloghrie & Bierman Standards Track [Page 28]
RFC 2037 Entity MIB using SMIv2 October 1996
entLPPhysicalIndex.4.11 == 11
Physical to Logical to MIB Alias Mappings -- entAliasMappingTable
Example 1: ifIndex values are global to all logical
entAliasMappingIdentifier.5.0 == ifIndex.1
entAliasMappingIdentifier.6.0 == ifIndex.2
entAliasMappingIdentifier.7.0 == ifIndex.3
entAliasMappingIdentifier.9.0 == ifIndex.4
entAliasMappingIdentifier.10.0 == ifIndex.5
entAliasMappingIdentifier.11.0 == ifIndex.6
Example 2: ifIndex values are not shared by all logical
entAliasMappingIdentifier.5.0 == ifIndex.1
entAliasMappingIdentifier.5.3 == ifIndex.101
entAliasMappingIdentifier.6.0 == ifIndex.2
entAliasMappingIdentifier.6.3 == ifIndex.102
entAliasMappingIdentifier.7.0 == ifIndex.3
entAliasMappingIdentifier.7.3 == ifIndex.103
entAliasMappingIdentifier.9.0 == ifIndex.4
entAliasMappingIdentifier.9.3 == ifIndex.204
entAliasMappingIdentifier.10.0 == ifIndex.5
entAliasMappingIdentifier.10.3 == ifIndex.205
entAliasMappingIdentifier.11.0 == ifIndex.6
entAliasMappingIdentifier.11.3 == ifIndex.206
Physical Containment Tree --
chassis has two containers
entPhysicalChildIndex.1.2 = 2
entPhysicalChildIndex.1.3 = 3
container 1 has a module
entPhysicalChildIndex.2.4 = 4
container 2 has a module
entPhysicalChildIndex.3.8 = 8
module 1 has 3 ports
entPhysicalChildIndex.4.5 = 5
entPhysicalChildIndex.4.6 = 6
entPhysicalChildIndex.4.7 = 7
module 2 has 3 ports
entPhysicalChildIndex.8.9 = 9
entPhysicalChildIndex.8.10 = 10
entPhysicalChildIndex.1.11 = 11
McCloghrie & Bierman Standards Track [Page 29]
RFC 2037 Entity MIB using SMIv2 October 1996
5.2.
A 3-slot Hub with 2 backplane ethernet segments. Slot three
empty, and the remaining slots contain ethernet repeater modules
[ed. -- Note that a replacement for the current Repeater MIB (
1516) is likely to emerge soon, and it will no longer be necessary
access repeater MIB data in different naming scopes.]
Physical entities -- entPhysicalTable
1 Field-replaceable physical chassis
entPhysicalDescr.1 == "Acme Chassis Model 110"
entPhysicalVendorType.1 == acmeProducts.chassisTypes.2
entPhysicalContainedIn.1 == 0
entPhysicalClass.1 == chassis(3)
entPhysicalParentRelPos.1 == 0
entPhysicalName.1 == '110-B
2 Chassis Ethernet Backplanes
entPhysicalDescr.2 == "Acme Ethernet Backplane Type A
entPhysicalVendorType.2 == acmeProducts.backplaneTypes.1
entPhysicalContainedIn.2 == 1
entPhysicalClass.2 == backplane(4)
entPhysicalParentRelPos.2 == 1
entPhysicalName.2 == 'B1'
entPhysicalDescr.3 == "Acme Ethernet Backplane Type A
entPhysicalVendorType.3 == acmeProducts.backplaneTypes.1
entPhysicalContainedIn.3 == 1
entPhysicalClass.3 == backplane(4)
entPhysicalParentRelPos.3 == 2
entPhysicalName.3 == 'B2'
3 slots within the chassis
entPhysicalDescr.4 == "Acme Hub Slot Type RB
entPhysicalVendorType.4 == acmeProducts.slotTypes.5
entPhysicalContainedIn.4 == 1
entPhysicalClass.4 == container(5)
entPhysicalParentRelPos.4 == 1
entPhysicalName.4 == 'Slot 1'
entPhysicalDescr.5 == "Acme Hub Slot Type RB
entPhysicalVendorType.5 == acmeProducts.slotTypes.5
entPhysicalContainedIn.5 == 1
entPhysicalClass.5 == container(5)
entPhysicalParentRelPos.5 == 2
entPhysicalName.5 == 'Slot 2'
entPhysicalDescr.6 == "Acme Hub Slot Type RB
McCloghrie & Bierman Standards Track [Page 30]
RFC 2037 Entity MIB using SMIv2 October 1996
entPhysicalVendorType.6 == acmeProducts.slotTypes.5
entPhysicalContainedIn.6 == 1
entPhysicalClass.6 == container(5)
entPhysicalParentRelPos.6 == 3
entPhysicalName.6 == 'Slot 3'
Slot 1 contains a plug-in module with 4 10-BaseT ports
entPhysicalDescr.7 == "Acme 10Base-T Module 114 Rev A
entPhysicalVendorType.7 == acmeProducts.moduleTypes.32
entPhysicalContainedIn.7 == 4
entPhysicalClass.7 == module(9)
entPhysicalParentRelPos.7 == 1
entPhysicalName.7 == 'M1'
entPhysicalDescr.8 == "Acme 10Base-T Port RB Rev A
entPhysicalVendorType.8 == acmeProducts.portTypes.10
entPhysicalContainedIn.8 == 7
entPhysicalClass.8 == port(10)
entPhysicalParentRelPos.8 == 1
entPhysicalName.8 == 'Ethernet-A
entPhysicalDescr.9 == "Acme 10Base-T Port RB Rev A
entPhysicalVendorType.9 == acmeProducts.portTypes.10
entPhysicalContainedIn.9 == 7
entPhysicalClass.9 == port(10)
entPhysicalParentRelPos.9 == 2
entPhysicalName.9 == 'Ethernet-B
entPhysicalDescr.10 == "Acme 10Base-T Port RB Rev B
entPhysicalVendorType.10 == acmeProducts.portTypes.10
entPhysicalContainedIn.10 == 7
entPhysicalClass.10 == port(10)
entPhysicalParentRelPos.10 == 3
entPhysicalName.10 == 'Ethernet-C
entPhysicalDescr.11 == "Acme 10Base-T Port RB Rev B
entPhysicalVendorType.11 == acmeProducts.portTypes.10
entPhysicalContainedIn.11 == 7
entPhysicalClass.11 == port(10)
entPhysicalParentRelPos.11 == 4
entPhysicalName.11 == 'Ethernet-D
Slot 2 contains another ethernet module with 2 ports
entPhysicalDescr.12 == "Acme 10Base-T Module Model 4 Rev A
entPhysicalVendorType.12 == acmeProducts.moduleTypes.30
entPhysicalContainedIn.12 = 5
entPhysicalClass.12 == module(9)
entPhysicalParentRelPos.12 == 1
McCloghrie & Bierman Standards Track [Page 31]
RFC 2037 Entity MIB using SMIv2 October 1996
entPhysicalName.12 == 'M2'
entPhysicalDescr.13 == "Acme 802.3 AUI Port Rev A
entPhysicalVendorType.13 == acmeProducts.portTypes.11
entPhysicalContainedIn.13 == 12
entPhysicalClass.13 == port(10)
entPhysicalParentRelPos.13 == 1
entPhysicalName.13 == 'AUI
entPhysicalDescr.14 == "Acme 10Base-T Port RD Rev B
entPhysicalVendorType.14 == acmeProducts.portTypes.14
entPhysicalContainedIn.14 == 12
entPhysicalClass.14 == port(10)
entPhysicalParentRelPos.14 == 2
entPhysicalName.14 == 'E2'
Logical entities --
Repeater 1--comprised of any ports attached to backplane 1
entLogicalDescr.1 == "Acme repeater v3.1"
entLogicalType.1 == snmpDot3
entLogicalCommunity.1 "public-repeater1"
entLogicalTAddress.1 == 124.125.126.127:161
entLogicalTDomain.1 ==
Repeater 2--comprised of any ports attached to backplane 2:
entLogicalDescr.2 == "Acme repeater v3.1"
entLogicalType.2 == snmpDot3
entLogicalCommunity.2 == "public-repeater2"
entLogicalTAddress.2 == 124.125.126.127:161
entLogicalTDomain.2 ==
Logical to Physical Mappings -- entLPMappingTable
repeater1 uses backplane 1, slot 1-ports 1 & 2, slot 2-port 1
[ed. -- Note that a mapping to the module is not included
since in this example represents a port-switchable hub
Even though all ports on the module could belong to
same repeater as a matter of configuration, the LP
mappings should not be replaced dynamically with a
mapping for the module (e.g. entLPPhysicalIndex.1.7).
If all ports on the module shared a single backplane connection
then a single mapping for the module would be more appropriate. ]
entLPPhysicalIndex.1.2 == 2
entLPPhysicalIndex.1.8 == 8
entLPPhysicalIndex.1.9 == 9
entLPPhysicalIndex.1.13 == 13
McCloghrie & Bierman Standards Track [Page 32]
RFC 2037 Entity MIB using SMIv2 October 1996
repeater2 uses backplane 2, slot 1-ports 3 & 4, slot 2-port 2
entLPPhysicalIndex.2.3 == 3
entLPPhysicalIndex.2.10 == 10
entLPPhysicalIndex.2.11 == 11
entLPPhysicalIndex.2.14 == 14
Physical to Logical to MIB Alias Mappings -- entAliasMappingTable
Repeater Port Identifier values are shared by both repeaters
entAliasMappingIdentifier.8.0 == rptrPortGroupIndex.1.1
entAliasMappingIdentifier.9.0 == rptrPortGroupIndex.1.2
entAliasMappingIdentifier.10.0 == rptrPortGroupIndex.1.3
entAliasMappingIdentifier.11.0 == rptrPortGroupIndex.1.4
entAliasMappingIdentifier.13.0 == rptrPortGroupIndex.2.1
entAliasMappingIdentifier.14.0 == rptrPortGroupIndex.2.2
Physical Containment Tree --
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
entPhysicalChildIndex.5.12 = 12
[ed. - in this example, container 3 is empty.]
module 1 has 4 ports
entPhysicalChildIndex.7.8 = 8
entPhysicalChildIndex.7.9 = 9
entPhysicalChildIndex.7.10 = 10
entPhysicalChildIndex.7.11 = 11
module 2 has 2 ports
entPhysicalChildIndex.12.13 = 13
entPhysicalChildIndex.12.14 = 14
6.
This document was produced by the IETF Entity MIB Working Group
McCloghrie & Bierman Standards Track [Page 33]
RFC 2037 Entity MIB using SMIv2 October 1996
7.
[1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M.,
S. Waldbusser, "Structure of Management Information for version 2
of the Simple Network Management Protocol (SNMPv2)", RFC 1902,
January 1996.
[2] McCloghrie, K., and M. Rose, Editors, "Management Information
for Network Management of TCP/IP-based internets: MIB-II", STD 17,
RFC 1213, Hughes LAN Systems, Performance Systems International
March 1991.
[3] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M.,
S. Waldbusser, "Textual Conventions for version 2 of the
Network Management Protocol (SNMPv2)", RFC 1903, January 1996.
[4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M.,
S. Waldbusser, "Protocol Operations for version 2 of the
Network Management Protocol (SNMPv2)", RFC 1905, January 1996.
[5] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M.,
S. Waldbusser, "Conformance Statements for version 2 of the
Network Management Protocol (SNMPv2)", RFC 1904, January 1996.
[6] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple
Management Protocol", RFC 1157, SNMP Research, Performance
International, MIT Laboratory for Computer Science, May 1990.
[7] McCloghrie, K., and Kastenholtz, F., "Interfaces Group Evolution",
RFC 1573, Hughes LAN Systems, FTP Software, January 1994.
[8] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M.,
S. Waldbusser, "Transport Mappings for version 2 of the
Network Management Protocol (SNMPv2)", RFC 1906, January 1996.
[9] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M.,
S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901,
January 1996.
McCloghrie & Bierman Standards Track [Page 34]
RFC 2037 Entity MIB using SMIv2 October 1996
8. Security
In order to implement this MIB, an agent must make certain
information available about various logical and physical
within a managed system, which may be considered sensitive in
network environments
Therefore, a network administrator may wish to employ instance-
access control, and configure the Entity MIB access (i.e.,
strings in SNMPv1 and SNMPv2C), such that certain instances
this MIB (e.g., entLogicalCommunity, or entire entLogicalEntries
entPhysicalEntries, and associated mapping table entries),
excluded from particular MIB views
9. Authors'
Keith
Cisco Systems, Inc
170 West Tasman
San Jose, CA 95134
Phone: 408-526-5260
EMail: kzm@cisco.
Andy
Cisco Systems, Inc
170 West Tasman
San Jose, CA 95134
Phone: 408-527-3711
EMail: abierman@cisco.
McCloghrie & Bierman Standards Track [Page 35]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
