draft-ietf-entmib-entmib-01.txt   draft-ietf-entmib-entmib-02.txt 
Draft Entity MIB January 14, 1996 Draft Entity MIB January 22, 1996
<draft-ietf-entmib-entmib-01.txt> <draft-ietf-entmib-entmib-02.txt>
Entity MIB Entity MIB
14 January 1996 22 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 January 14, 1996 Draft Entity MIB January 22, 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 SNMPv1 agent.
Draft Entity MIB January 14, 1996 Draft Entity MIB January 22, 1996
2. The SNMPv2 Network Management Framework 2. The SNMPv1 Network Management Framework
The SNMPv2 Network Management Framework consists of four major The SNMPv1 Network Management Framework presently consists of two 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
objects for the Internet suite of protocols. objects for the Internet suite of protocols.
o RFC 1445 [3] which defines the administrative and other
architectural aspects of the framework.
o RFC 1448 [4] which defines the protocol used for network access to
managed objects.
The Framework permits new objects to be defined for the purpose of The Framework permits new objects to be defined for the purpose of
experimentation and evaluation. experimentation and evaluation.
2.1. Object Definitions 2.1. Object Definitions
Managed objects are accessed via a virtual information store, termed the Managed objects are accessed via a virtual information store, termed the
Management Information Base or MIB. Objects in the MIB are defined Management Information Base or MIB. Objects in the MIB are defined
using the subset of Abstract Syntax Notation One (ASN.1) defined in the using the subset of Abstract Syntax Notation One (ASN.1) defined in the
SMI. In particular, each object type is named by an OBJECT IDENTIFIER, SMI. In particular, each object type is named by an OBJECT IDENTIFIER,
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 January 14, 1996 Draft Entity MIB January 22, 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 presently true
at least 3 standard MIBs, and is likely to become true for more and more for at least 3 standard MIBs, and is likely to become true for more and
MIBs as time passes. For example: more 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;
- multiple repeaters supported by a single agent; - multiple repeaters supported by a single agent;
- multiple OSPF backbone areas, each one operating as part of its own - multiple OSPF backbone areas, each one operating as part of its own
Autonomous System, and each identified by the same area-id (e.g., Autonomous System, and each identified by the same area-id (e.g.,
0.0.0.0), supported inside a single router with one agent. 0.0.0.0), supported inside a single router with one agent.
The fact that it is a single agent in each of these cases implies there The fact that it is a single agent in each of these cases implies there
is some relationship which binds all of these entities together. is some relationship which binds all of these entities together.
Effectively, there is some "overall" physical entity which houses the Effectively, there is some "overall" physical entity which houses the
sum of the things managed by that one agent, i.e., there are multiple sum of the things managed by that one agent, i.e., there are multiple
"logical" entities within a single physical entity. Sometimes, the "logical" entities within a single physical entity. Sometimes, the
overall physical entity contains multiple (smaller) physical entities overall physical entity contains multiple (smaller) physical entities
and each logical entity is associated with a particular such physical and each logical entity is associated with a particular physical entity.
entity. Sometimes, the overall physical entity is a "compound" of Sometimes, the overall physical entity is a "compound" of multiple
multiple physical entities (e.g., a stack of stackable hubs). physical entities (e.g., a stack of stackable hubs).
What is needed is a way to determine exactly what logical entities are What is needed is a way to determine exactly what logical entities are
managed by the agent (either by SNMPv1 or SNMPv2), and thereby to be managed by the agent (either by SNMPv1 or SNMPv2), and thereby to be
able to communicate with the agent about a particular logical entity. able to communicate with the agent about a particular logical entity.
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 SNMPv1 message (although that
be useful in the future). Rather, it is sufficient, and in some might 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. Terms 3.1. Terms
Some new terms are used throughout this document: Some new terms are used throughout this document:
Draft Entity MIB January 14, 1996 Draft Entity MIB January 22, 1996
- Naming Scope - Naming Scope
A "naming scope" represents the set of information that may be A "naming scope" represents the set of information that may be
potentially accessed through a single SNMP operation. All instances potentially accessed through a single SNMPv1 operation. All
within the naming scope share the same unique identifier space. For instances within the naming scope share the same unique identifier
SNMPv1, a naming scope is identified by the value of the associated space. For SNMPv1, a naming scope is identified by the value of the
'entLogicalCommunity' instance. associated 'entLogicalCommunity' instance.
- Logical Entity - Logical Entity
A managed system contains one or more logical entities, each A managed system contains one or more logical entities, each
represented by at most one instantiation of each of a particular represented by at most one instantiation of each of a particular
set of MIB objects. A set of management functions is associated set of MIB objects. A set of management functions is associated
with each logical entity. Examples of logical entities include with each logical entity. Examples of logical entities include
routers, bridges, print-servers, etc. routers, bridges, print-servers, etc.
- Physical Entity - Physical Entity
A "physical entity" or "physical component" represents an A "physical entity" or "physical component" represents an
skipping to change at page 5, line 38 skipping to change at page 5, line 38
backplanes, sensors, daughter-cards, power supplies, the overall backplanes, sensors, daughter-cards, power supplies, the overall
chassis) which can be managed via functions associated with one or chassis) which can be managed via functions associated with one or
more logical entities are included in the MIB. more logical entities are included in the MIB.
- Containment Tree - Containment Tree
Each physical component may optionally be modeled as 'contained' Each physical component may optionally be modeled as 'contained'
within another physical component. A "containment-tree" is the within another physical component. A "containment-tree" is the
conceptual sequence of entPhysicalIndex values which uniquely conceptual sequence of entPhysicalIndex values which uniquely
specifies the exact physical location of a physical component specifies the exact physical location of a physical component
within the managed system. It is generated by 'following and within the managed system. It is generated by 'following and
recording' each 'entPhysicalContainedIn' instance until a value of recording' each 'entPhysicalContainedIn' instance 'up the tree
zero (indicating no further containment) is found. towards the root', until a value of zero indicating no further
containment is found.
It is suggested that physical containment-trees retain their It is required that physical containment-trees retain their
identity across reboots. Specifically, two identical hardware identity across reboots. Specifically, two identical hardware
configurations should produce the same set of containment-trees for configurations should produce the same set of containment-trees for
every corresponding entry in the entPhysicalTable (i.e. the same every corresponding entry in the entPhysicalTable (i.e. the same
set of entPhysicalEntries with the same entPhysicalIndex values, set of entPhysicalEntries with the same entPhysicalIndex values,
[ed. want to say anything about container/containee guidelines Note that chassis slots, which are capable of accepting one or more
here?] module types from one or more vendors, are modeled as containers in
this MIB. The value of entPhysicalContainedIn for a particular
'module' entity (entPhysicalClass value of 'module(9)') should be
Draft Entity MIB January 14, 1996 Draft Entity MIB January 22, 1996
equal to an entPhysicalIndex that represents the parent 'container'
entity (associated entPhysicalClass value of ('container(5)'). An
agent should represent both empty and full containers in the
entPhysicalTable.
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.
Note that different logical entities may 'share' the same naming scope Note that different logical entities may 'share' the same naming scope
(and therefore the same values of entLogicalCommunity). In such a case, (and therefore the same values of entLogicalCommunity). In such a case,
individual logical entities can be identified by examining the individual logical entities can be identified by examining the
skipping to change at page 6, line 40 skipping to change at page 7, line 5
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.
Draft Entity MIB January 22, 1996
3.5. Relationship to the Interfaces MIB 3.5. Relationship to the Interfaces MIB
The Entity MIB contains a mapping table identifying physical components The Entity MIB contains a mapping table identifying physical components
that have 'external values' (e.g. ifIndex) associated with them within a that have 'external values' (e.g. ifIndex) associated with them within a
given naming scope. This table can be used to identify the physical given naming scope. This table can be used to identify the physical
location of each interface in the ifTable. Since ifIndex values in location of each interface in the ifTable. Since ifIndex values in
different contexts are not related to one another, the interface to different contexts are not related to one another, the interface to
physical component associations are relative to a specific logical physical component associations are relative to a specific logical
entity within the agent. entity within the agent.
Draft Entity MIB January 14, 1996
[ed. say anything about entAliasMappingTable and ifIndex renumbering?]
3.6. Relationship to the Other MIBs 3.6. Relationship to the Other MIBs
The Entity MIB contains a mapping table identifying physical components The Entity MIB contains a mapping table identifying physical components
that have identifiers from other standard MIBs associated with them. that have identifiers from other standard MIBs associated with them.
For example, this table can be used along with the physical mapping For example, this table can be used along with the physical mapping
table to identify the physical location of each repeater port in the table to identify the physical location of each repeater port in the
rptrPortTable, 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.7. Re-Configuration of Entities 3.7. Re-Configuration of Entities
skipping to change at page 7, line 39 skipping to change at page 8, line 4
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. The entPhysicalContainsTable provides efficient 'ifIndex.12', or both. The entPhysicalContainsTable provides efficient
discovery of the containment relationships of all physical entities discovery of the containment relationships of all physical entities
(also derivable from 'entPhysicalContainedIn' values). (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
Draft Entity MIB January 22, 1996
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 entPhysicalEntry 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
SNMPv1 access to the MIB information for the logical entity.
Draft Entity MIB January 14, 1996
SNMPv2 and/or SNMPv1 access to the MIB information for the logical
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 entLogicalIndex,
entLogicalIndex pairs and 'alias' object identifier values. This allows entPhysicalIndex pairs and 'alias' object identifier values. This
resources managed with other MIBs (e.g. repeater ports, bridge ports, allows resources managed with other MIBs (e.g. repeater ports, bridge
physical and logical interfaces) to be identified in the physical entity ports, physical and logical interfaces) to be identified in the physical
hierarchy. Note that each alias identifier is only relevant in a entity hierarchy. Note that each alias identifier is only relevant in a
particular naming scope. particular naming scope.
The entPhysicalContainsTable contains simple mappings between The entPhysicalContainsTable contains simple mappings between
'entPhysicalContainsIn' values for each container/containee relationship 'entPhysicalContainedIn' values for each container/containee
in the managed system. The indexing of this table allows an NMS to relationship in the managed system. The indexing of this table allows an
quickly discover the 'entPhysicalIndex' values for all children of a NMS to quickly discover the 'entPhysicalIndex' values for all children
given physical entity. of a given physical entity.
3.9. Multiple Agents 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 SNMPv1 architecture, that the number of agents is
transparent to a network management station. transparent to a network management station.
Draft Entity MIB January 14, 1996 Draft Entity MIB January 22, 1996
4. Definitions 4. Definitions
ENTITY-MIB DEFINITIONS ::= BEGIN ENTITY-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, experimental, MODULE-IDENTITY, OBJECT-TYPE,
IpAddress experimental, NOTIFICATION-TYPE
FROM SNMPv2-SMI FROM SNMPv2-SMI
DisplayString, AutonomousType, TruthValue DisplayString, AutonomousType, TruthValue
FROM SNMPv2-TC FROM SNMPv2-TC
Context TAddress
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 "9601020000Z" LAST-UPDATED "9601200000Z"
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 10, 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 January 14, 1996 Draft Entity MIB January 22, 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 10, 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,
entPhysicalClass INTEGER entPhysicalClass INTEGER,
entPhysicalParentRelPos INTEGER
} }
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 }
entPhysicalDescr OBJECT-TYPE Draft Entity MIB January 22, 1996
Draft Entity MIB January 14, 1996
entPhysicalDescr OBJECT-TYPE
SYNTAX DisplayString SYNTAX DisplayString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A textual description of physical entity." "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
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An indication of the vendor-specific hardware type of the "An indication of the vendor-specific hardware type of the
physical entity. Note that this is different from the physical entity. Note that this is different from the
definition of MIB-II's sysObjectID. definition of MIB-II's sysObjectID.
An agent should set this object to a enterprise-specific An agent should set this object to a enterprise-specific
registration identifier value indicating the specific registration identifier value indicating the specific
equipment type in detail. The associated instance of the equipment type in detail. The associated instance of
entPhysicalClass object should be used to indicate the entPhysicalClass should be used to indicate the general type
general type of hardware device. of hardware device.
If no vendor-specific registration identifier exists for If no vendor-specific registration identifier exists for
this physical entity, then the value { 0 0 } is returned. If this physical entity, then the value { 0 0 } is returned. If
the value is unknown by this agent, then the special value the value is unknown by this agent, then the special value
'entPClassUnknown' is returned." 'entPClassUnknown' is returned."
::= { entPhysicalEntry 3 } ::= { entPhysicalEntry 3 }
entPhysicalContainedIn OBJECT-TYPE entPhysicalContainedIn OBJECT-TYPE
SYNTAX INTEGER (0..2147483647) SYNTAX INTEGER (0..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 12, line 5 skipping to change at page 12, line 5
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 }
entPhysicalClass OBJECT-TYPE entPhysicalClass OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
Draft Entity MIB January 14, 1996 Draft Entity MIB January 22, 1996
unknown(2), unknown(2),
chassis(3), chassis(3),
backplane(4), backplane(4),
container(5), -- slot or daughter-card holder container(5), -- slot or daughter-card holder
powerSupply(6), powerSupply(6),
fan(7), fan(7),
sensor(8), sensor(8),
module(9), module(9), -- plug-in card or daughter-card
port(10) 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 the standard enumeration An agent should set this object to the standard enumeration
value which most accurately indicates the general class of value which most accurately indicates the general class of
the physical entity, or the primary class if there is more the physical entity, or the primary class if there is more
than one. than one.
If no appropriate standard registration identifier exists If no appropriate standard registration identifier exists
for this physical entity, then the value 'other(1)' is for this physical entity, then the value 'other(1)' is
returned. If the value is unknown by this agent, then the returned. If the value is unknown by this agent, then the
value 'unknown(2)' is returned." value 'unknown(2)' is returned."
::= { entPhysicalEntry 5 } ::= { entPhysicalEntry 5 }
Draft Entity MIB January 14, 1996 entPhysicalParentRelPos OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An indication of the position of this 'child' component
among all its 'sibling' components. The numbering is
relative to the 'parent' component. A component's parent is
identified by the associated instance of the
entPhysicalContainedIn object. An NMS may use this value to
compare against other entPhysicalEntries with the same
parent (same value of entPhysicalContainedIn).
This value should match any external labeling of the
physical component if possible. For example, an
entPhysicalEntry representing entPhysicalParentRelPos value
of '10'. The entPhysicalContainedIn instance should equal
the entPhysicalIndex for the parent (module 3). The
Draft Entity MIB January 22, 1996
entPhysicalParentRelPos instance associated with the parent
should be equal to '3'.
If the physical position of this component does not match
any external labeling, then user documentation or other
external reference material should be used to determine the
parent-relative position. If this is not possible, then the
the agent should assign an arbitrary ordering to a given set
of 'sibling' components, perhaps based on internal
representation of the components.
If the agent cannot determine the parent-relative position
for some reason, or if the associated value of
entPhysicalContainedIn is '0', then the value '0' is
returned. Otherwise a positive integer is returned,
indicating the parent-relative position of this physical
entity.
Parent-relative ordering should start from '1' and continue
to 'N', where 'N' represents the highest positioned child
entity. Note that this ordering may be sparse or dense,
depending on agent implementation. The actual values
returned are not globally meaningful, as each 'parent'
component may use different numbering algorithms. The
ordering is only meaningful among siblings of the same
parent component.
The agent should retain parent-relative position values
across reboots, either through algorithmic assignment or use
of non-volatile storage."
::= { entPhysicalEntry 6 }
Draft Entity MIB January 22, 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 13, line 32 skipping to change at page 14, line 32
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,
entLogicalCommunity OCTET STRING, entLogicalCommunity OCTET STRING,
entLogicalIpAddress IpAddress entLogicalTAddress TAddress,
entLogicalTDomain OBJECT IDENTIFIER
} }
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 January 14, 1996 Draft Entity MIB January 22, 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 15, line 5 skipping to change at page 16, line 5
accessed with read-write privileges). accessed with read-write privileges).
A conformant SNMP agent may wish to conserve naming scopes A conformant SNMP agent may wish to conserve naming scopes
by representing multiple logical entities in a single 'main' by representing multiple logical entities in a single 'main'
naming scope. This is possible when the logical entities naming scope. This is possible when the logical entities
represented by the same value of entLogicalCommunity have no represented by the same value of entLogicalCommunity have no
object instances in common. For example, 'bridge1' and object instances in common. For example, 'bridge1' and
'repeater1' may be part of the main naming scope, but two 'repeater1' may be part of the main naming scope, but two
additional community strings are needed to represent additional community strings are needed to represent
Draft Entity MIB January 14, 1996 Draft Entity MIB January 22, 1996
'bridge2' and 'repeater2'. 'bridge2' and 'repeater2'.
Logical entities 'bridge1' and 'repeater1' would be Logical entities 'bridge1' and 'repeater1' would be
represented by sysOREntries associated with the 'main' represented by sysOREntries associated with the 'main'
naming scope. 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 4 } ::= { entLogicalEntry 4 }
entLogicalIpAddress OBJECT-TYPE entLogicalTAddress OBJECT-TYPE
SYNTAX IpAddress SYNTAX TAddress
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 transport service address by which the logical entity
management information for this logical entity can be receives network management traffic, formatted according to
obtained. For agents not accessible via SNMPv1, the value the corresponding value of entLogicalTDomain. For
of this object is 0.0.0.0." snmpUDPDomain, entLogicalTAddress is formatted as a 4-octet
IP Address concatenated with a 2-octet UDP port number."
::= { entLogicalEntry 5 } ::= { entLogicalEntry 5 }
Draft Entity MIB January 14, 1996 entLogicalTDomain OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the kind of transport service by which the
logical entity receives network management traffic.
Possible values for this object are presently found in the
Transport Mappings for SNMPv2 document (RFC 1449 [8]). [ed
-- RFC 1449 is now historic]"
::= { entLogicalEntry 6 }
Draft Entity MIB January 22, 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 18, 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 January 14, 1996 Draft Entity MIB January 22, 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 logical entity/ physical component pair may have an
number of external identifier (alias) bindings." arbitrary number of external identifier (alias) bindings."
INDEX { entLogicalIndex, entPhysicalIndex, 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)
skipping to change at page 18, line 5 skipping to change at page 19, 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 January 14, 1996 Draft Entity MIB January 22, 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 related 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 January 14, 1996 Draft Entity MIB January 22, 1996
-- physical mapping table -- physical mapping table
entPhysicalContainsTable OBJECT-TYPE entPhysicalContainsTable OBJECT-TYPE
SYNTAX SEQUENCE OF EntPhysicalContainsEntry SYNTAX SEQUENCE OF EntPhysicalContainsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table which exposes the container/containee relationships "A table which exposes the container/containee relationships
between physical entities." between physical entities."
::= { entityMIBObjects 5 } ::= { entityMIBObjects 5 }
skipping to change at page 20, line 5 skipping to change at page 21, line 5
entPhysicalChildIndex OBJECT-TYPE entPhysicalChildIndex 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 entPhysicalIndex for the contained physical "The value of entPhysicalIndex for the contained physical
entity." entity."
::= { entPhysicalContainsEntry 1 } ::= { entPhysicalContainsEntry 1 }
Draft Entity MIB January 14, 1996 Draft Entity MIB January 22, 1996
-- last change timestamp for the whole MIB -- last change timestamp for the whole MIB
entLastConfigChangeTime OBJECT-TYPE entLastChangeTime OBJECT-TYPE
SYNTAX Timestamp SYNTAX Timestamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the time any of these events "The value of sysUpTime at the time any of these events
occur: occur:
* a conceptual row is created or deleted in any of these tables: * a conceptual row is created or deleted in any of these tables:
- entPhysicalTable - entPhysicalTable
- entLogicalTable - entLogicalTable
- entLPMappingTable - entLPMappingTable
skipping to change at page 20, line 30 skipping to change at page 21, line 30
- entPhysicalContainsTable - entPhysicalContainsTable
* any instance in the following list of objects changes value: * any instance in the following list of objects changes value:
- entPhysicalDescr - entPhysicalDescr
- entPhysicalVendorType - entPhysicalVendorType
- entPhysicalContainedIn - entPhysicalContainedIn
- entPhysicalClass - entPhysicalClass
- entLogicalDescr - entLogicalDescr
- entLogicalType - entLogicalType
- entLogicalCommunity - entLogicalCommunity
- entLogicalIpAddress - entLogicalTAddress
- entLogicalTDomain
- entAliasIdentifier - entAliasIdentifier
" "
::= { entityMIBObjects 6 } ::= { entityMIBObjects 6 }
Draft Entity MIB January 14, 1996 Draft Entity MIB January 22, 1996
-- Entity MIB Trap Definitions -- Entity MIB Trap Definitions
entityMIBTraps OBJECT IDENTIFIER ::= { entityMIB 2 } entityMIBTraps OBJECT IDENTIFIER ::= { entityMIB 2 }
entConfigChange NOTIFICATION-TYPE entConfigChange NOTIFICATION-TYPE
OBJECTS { OBJECTS {
entLastChangeTime entLastChangeTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entConfigChange trap is sent when the value of "An entConfigChange trap is sent when the value of
entLastConfigChangeTime changes. It can be utilized by an entLastChangeTime changes. It can be utilized by an NMS to
NMS to trigger logical/physical entity table maintenance trigger logical/physical entity table maintenance polls.
polls. This trap is throttled by the agent. This trap is throttled by the agent.
The value of entLastChangeTime at the time the config- The value of entLastChangeTime at the time the
change-event is generated by the agent is encoded at the entConfigChange event is detected by the agent is encoded as
only var-bind in the trap. a var-bind in the trap. This should be the same value as the
sysUpTime instance included in the trap, but may not be if
trap generation is delayed at all within the agent.
An agent must take care not to generate more than one An agent must take care not to generate more than one
entLastChangeTime 'trap-event' in a five second period (a entConfigChange 'trap-event' in a five second period, where
'trap-event' is the transmission of a single trap PDU to a a 'trap-event' is the transmission of a single trap PDU to a
list of trap receivers). If additional configuration list of trap destinations. If additional configuration
changes occur within the five second 'throttling' period, changes occur within the five second 'throttling' period,
then the agent should discard all but the most recent trap- then these events should be discarded by the agent. An NMS
event (if any), rather than queueing them and generating should periodically check the value of entLastChangeTime to
trap-events (one every five seconds) in sequence. " detect any missed entConfigChange events due to throttling.
::= { entityMIBTraps 1 } ::= { entityMIBTraps 1 }
Draft Entity MIB January 14, 1996 Draft Entity MIB January 22, 1996
-- conformance information -- conformance information
entityConformance OBJECT IDENTIFIER ::= { entityMIB 3 } entityConformance OBJECT IDENTIFIER ::= { entityMIB 3 }
entityCompliances OBJECT IDENTIFIER ::= { entityConformance 1 } entityCompliances OBJECT IDENTIFIER ::= { entityConformance 1 }
entityGroups OBJECT IDENTIFIER ::= { entityConformance 2 } entityGroups OBJECT IDENTIFIER ::= { entityConformance 2 }
-- compliance statements -- compliance statements
entityCompliance MODULE-COMPLIANCE entityCompliance MODULE-COMPLIANCE
skipping to change at page 22, line 31 skipping to change at page 23, line 31
MANDATORY-GROUPS { entityGroup } MANDATORY-GROUPS { entityGroup }
::= { entityCompliances 1 } ::= { entityCompliances 1 }
-- units of conformance -- units of conformance
entityGroup OBJECT-GROUP entityGroup OBJECT-GROUP
OBJECTS { entPhysicalDescr, OBJECTS { entPhysicalDescr,
entPhysicalVendorType, entPhysicalVendorType,
entPhysicalContainedIn, entPhysicalContainedIn,
entPhysicalClass, entPhysicalClass,
entPhysicalParentRelPos,
entLogicalDescr, entLogicalDescr,
entLogicalType, entLogicalType,
entLogicalCommunity, entLogicalCommunity,
entLogicalIpAddress, entLogicalTAddress,
entLogicalTDomain,
entLPPhysicalIndex, entLPPhysicalIndex,
entAliasIdentifier, entAliasIdentifier,
entPhysicalChildIndex, entPhysicalChildIndex,
entLastChangeTime, entLastChangeTime,
entConfigChange -- separate conformance group needed for trap?? entConfigChange
} }
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 }
Draft Entity MIB January 22, 1996
END END
Draft Entity MIB January 14, 1996 Draft Entity MIB January 22, 1996
5. Usage Examples 5. Usage Examples
The following sections iterate the instance values for two example
networking devices. These examples are kept simple to make them more
understandable. Auxillary components, such as fans, sensors, empty
slots, and sub-modules are not shown, but should be modeled in real
implementations.
5.1. Router/Bridge 5.1. Router/Bridge
A bi-lingual (SNMPv1 and SNMPv2) router containing two slots. Each slot An SNMPv1 router containing two slots. Each slot contains a 3 port
contains a 3 port router/bridge module. Each port is represented in the router/bridge module. Each port is represented in the ifTable. There
ifTable. There are two logical instances of OSPF running and two 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
entPhysicalClass.1 == chassis(3) entPhysicalClass.1 == chassis(3)
entPhysicalParentRelPos.1 == 0
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
entPhysicalClass.2 == container(5) entPhysicalClass.2 == container(5)
entPhysicalParentRelPos.2 == 1
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
entPhysicalClass.3 == container(5) entPhysicalClass.3 == container(5)
entPhysicalParentRelPos.3 == 2
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
entPhysicalClass.4 == module(9) entPhysicalClass.4 == module(9)
entPhysicalParentRelPos.4 == 1
entPhysicalDescr.5 == "Acme Router Ethernet Port 1" entPhysicalDescr.5 == "Acme Router Ethernet Port 1"
Draft Entity MIB January 22, 1996
entPhysicalVendorType.5 == acmeProducts.portTypes.2 entPhysicalVendorType.5 == acmeProducts.portTypes.2
entPhysicalContainedIn.5 == 4 entPhysicalContainedIn.5 == 4
entPhysicalClass.5 == port(10) entPhysicalClass.5 == port(10)
entPhysicalParentRelPos.5 == 1
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
entPhysicalClass.6 == port(10) entPhysicalClass.6 == port(10)
entPhysicalParentRelPos.6 == 2
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
entPhysicalClass.7 == port(10) entPhysicalClass.7 == port(10)
entPhysicalParentRelPos.7 == 3
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
entPhysicalClass.8 == module(9) entPhysicalClass.8 == module(9)
entPhysicalParentRelPos.8 == 1
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
entPhysicalClass.9 == port(10) entPhysicalClass.9 == port(10)
entPhysicalParentRelPos.9 == 1
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
entPhysicalClass.10 == port(10) entPhysicalClass.10 == port(10)
entPhysicalParentRelPos.10 == 2
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
entPhysicalClass.11 == port(10) entPhysicalClass.11 == port(10)
entPhysicalParentRelPos.11 == 3
Logical entities -- entLogicalTable Logical entities -- entLogicalTable
2 OSPF instances: 2 OSPF instances:
entLogicalDescr.1 == "ospf-1" entLogicalDescr.1 == "ospf-1"
Draft Entity MIB January 22, 1996
entLogicalType.1 == ospf entLogicalType.1 == ospf
entLogicalCommunity.1 == "public-ospf1" entLogicalCommunity.1 == "public-ospf1"
entLogicalIpAddress.1 == 124.125.126.127 entLogicalTAddress.1 == 124.125.126.127:161
entLogicalTDomain.1 == snmpUDPDomain
entLogicalDescr.2 == "ospf-2" entLogicalDescr.2 == "ospf-2"
entLogicalType.2 == ospf entLogicalType.2 == ospf
entLogicalCommunity.2 == "public-ospf2" entLogicalCommunity.2 == "public-ospf2"
entLogicalIpAddress.2 == 124.125.126.127 entLogicalTAddress.2 == 124.125.126.127:161
entLogicalTDomain.2 == snmpUDPDomain
2 logical bridges: 2 logical bridges:
entLogicalDescr.3 == "bridge1" entLogicalDescr.3 == "bridge1"
entLogicalType.3 == dod1dBridge entLogicalType.3 == dod1dBridge
entLogicalCommunity.3 == "public-bridge1" entLogicalCommunity.3 == "public-bridge1"
entLogicalIpAddress.3 == 124.125.126.127 entLogicalTAddress.3 == 124.125.126.127:161
entLogicalTDomain.3 == snmpUDPDomain
entLogicalDescr.4 == "bridge2" entLogicalDescr.4 == "bridge2"
entLogicalType.4 == dod1dBridge entLogicalType.4 == dod1dBridge
Draft Entity MIB January 14, 1996
entLogicalCommunity.4 == "public-bridge2" entLogicalCommunity.4 == "public-bridge2"
entLogicalIpAddress.4 == 124.125.126.127 entLogicalTAddress.4 == 124.125.126.127:161
entLogicalTDomain.4 == snmpUDPDomain
Logical to Physical Mappings: Logical to Physical Mappings:
1st OSPF instance: uses module 1-port 1 1st OSPF instance: uses module 1-port 1
entLPPhysicalIndex.1.5 == 5 entLPPhysicalIndex.1.5 == 5
2nd OSPF instance: uses module 2-port 1 2nd OSPF instance: uses module 2-port 1
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
skipping to change at page 25, line 31 skipping to change at page 28, line 4
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
Logical to Physical to Alias Mappings -- entAliasMappingTable: Logical to Physical to Alias Mappings -- entAliasMappingTable:
Bridge 1 uses Ports 1..3 on Slot 1 Bridge 1 uses Ports 1..3 on Slot 1
entAliasIdentifier.3.5.1 == dot1dBasePort.1 entAliasIdentifier.3.5.1 == dot1dBasePort.1
entAliasIdentifier.3.5.2 == ifIndex.1 entAliasIdentifier.3.5.2 == ifIndex.1
Draft Entity MIB January 22, 1996
entAliasIdentifier.3.6.1 == dot1dBasePort.2 entAliasIdentifier.3.6.1 == dot1dBasePort.2
entAliasIdentifier.3.6.2 == ifIndex.2 entAliasIdentifier.3.6.2 == ifIndex.2
entAliasIdentifier.3.7.1 == dot1dBasePort.3 entAliasIdentifier.3.7.1 == dot1dBasePort.3
entAliasIdentifier.3.7.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.4.9.1 == dot1dBasePort.1 entAliasIdentifier.4.9.1 == dot1dBasePort.1
entAliasIdentifier.4.9.2 == ifIndex.1 entAliasIdentifier.4.9.2 == ifIndex.1
skipping to change at page 26, line 4 skipping to change at page 28, line 28
entAliasIdentifier.4.10.2 == ifIndex.2 entAliasIdentifier.4.10.2 == ifIndex.2
entAliasIdentifier.4.11.1 == dot1dBasePort.3 entAliasIdentifier.4.11.1 == dot1dBasePort.3
entAliasIdentifier.4.11.2 == ifIndex.3 entAliasIdentifier.4.11.2 == ifIndex.3
Physical Containment Tree -- entPhysicalContainsTable Physical Containment Tree -- entPhysicalContainsTable
chassis has two containers: chassis has two containers:
entPhysicalChildIndex.1.2 = 2 entPhysicalChildIndex.1.2 = 2
entPhysicalChildIndex.1.3 = 3 entPhysicalChildIndex.1.3 = 3
container 1 has a module: container 1 has a module:
Draft Entity MIB January 14, 1996
entPhysicalChildIndex.2.4 = 4 entPhysicalChildIndex.2.4 = 4
container 2 has a module container 2 has a module
entPhysicalChildIndex.3.8 = 8 entPhysicalChildIndex.3.8 = 8
module 1 has some ports: module 1 has some ports:
entPhysicalChildIndex.4.5 = 5 entPhysicalChildIndex.4.5 = 5
entPhysicalChildIndex.4.6 = 6 entPhysicalChildIndex.4.6 = 6
entPhysicalChildIndex.4.7 = 7 entPhysicalChildIndex.4.7 = 7
skipping to change at page 26, line 30 skipping to change at page 29, line 4
entPhysicalChildIndex.1.11 = 11 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:
Draft Entity MIB January 22, 1996
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
entPhysicalClass.1 == chassis(3) entPhysicalClass.1 == chassis(3)
entPhysicalParentRelPos.1 == 0
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
entPhysicalClass.2 == backplane(4) entPhysicalClass.2 == backplane(4)
entPhysicalParentRelPos.2 == 1
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
entPhysicalClass.3 == backplane(4) entPhysicalClass.3 == backplane(4)
entPhysicalParentRelPos.3 == 2
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
entPhysicalClass.4 == container(5) entPhysicalClass.4 == container(5)
entPhysicalParentRelPos.4 == 1
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
entPhysicalClass.5 == container(5) entPhysicalClass.5 == container(5)
entPhysicalParentRelPos.5 == 2
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
entPhysicalClass.6 == container(5) entPhysicalClass.6 == container(5)
entPhysicalParentRelPos.6 == 3
Slot 1 contains a plug-in module with 4 10-BaseT ports: Slot 1 contains a plug-in module with 4 10-BaseT ports:
entPhysicalDescr.7 == "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
entPhysicalClass.7 == module(9) entPhysicalClass.7 == module(9)
entPhysicalParentRelPos.7 == 1
Draft Entity MIB January 22, 1996
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
entPhysicalClass.8 == port(10) entPhysicalClass.8 == port(10)
entPhysicalParentRelPos.8 == 1
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
entPhysicalClass.9 == port(10) entPhysicalClass.9 == port(10)
entPhysicalParentRelPos.9 == 2
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
entPhysicalClass.10 == port(10) entPhysicalClass.10 == port(10)
entPhysicalParentRelPos.10 == 3
entPhysicalDescr.11 == "10Base-T Port 4" entPhysicalDescr.11 == "10Base-T Port 4"
entPhysicalVendorType.11 == acmeProducts.portTypes.10 entPhysicalVendorType.11 == acmeProducts.portTypes.10
entPhysicalContainedIn.11 == 7 entPhysicalContainedIn.11 == 7
entPhysicalClass.11 == port(10) entPhysicalClass.11 == port(10)
entPhysicalParentRelPos.11 == 4
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
entPhysicalClass.12 == module(9) entPhysicalClass.12 == module(9)
entPhysicalParentRelPos.12 == 1
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 == 12 entPhysicalContainedIn.13 == 12
Draft Entity MIB January 14, 1996
entPhysicalClass.13 == port(10) entPhysicalClass.13 == port(10)
entPhysicalParentRelPos.13 == 1
entPhysicalDescr.14 == "10Base-T Port 2" entPhysicalDescr.14 == "10Base-T Port 2"
entPhysicalVendorType.14 == acmeProducts.portTypes.10 entPhysicalVendorType.14 == acmeProducts.portTypes.10
entPhysicalContainedIn.14 == 12 entPhysicalContainedIn.14 == 12
entPhysicalClass.14 == port(10) entPhysicalClass.14 == port(10)
entPhysicalParentRelPos.14 == 2
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
Draft Entity MIB January 22, 1996
entLogicalDescr.1 == "repeater1" entLogicalDescr.1 == "repeater1"
entLogicalType.1 == snmpDot3RptrMgt entLogicalType.1 == snmpDot3RptrMgt
entLogicalCommunity.1 "public-repeater1" entLogicalCommunity.1 "public-repeater1"
entLogicalIpAddress.1 124.125.126.128 entLogicalTAddress.1 == 124.125.126.127:161
entLogicalTDomain.1 == snmpUDPDomain
Repeater 2--comprised of any ports attached to backplane 2: Repeater 2--comprised of any ports attached to backplane 2:
entLogicalDescr.2 == "repeater2" entLogicalDescr.2 == "repeater2"
entLogicalType.2 == snmpDot3RptrMgt entLogicalType.2 == snmpDot3RptrMgt
entLogicalCommunity.2 == "public-repeater2" entLogicalCommunity.2 == "public-repeater2"
entLogicalIpAddress.2 == 124.125.126.128 entLogicalTAddress.2 == 124.125.126.127:161
entLogicalTDomain.2 == snmpUDPDomain
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
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
skipping to change at page 29, line 5 skipping to change at page 31, line 45
repeater1 uses slot 1-ports 1 & 2, slot 2-port 1 repeater1 uses slot 1-ports 1 & 2, slot 2-port 1
entAliasIdentifier.1.8.1 == rptrPortGroupIndex.1.1 entAliasIdentifier.1.8.1 == rptrPortGroupIndex.1.1
entAliasIdentifier.1.9.1 == rptrPortGroupIndex.1.2 entAliasIdentifier.1.9.1 == rptrPortGroupIndex.1.2
entAliasIdentifier.1.13.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.2.10.1 == rptrPortGroupIndex.1.3 entAliasIdentifier.2.10.1 == rptrPortGroupIndex.1.3
entAliasIdentifier.2.11.1 == rptrPortGroupIndex.1.4 entAliasIdentifier.2.11.1 == rptrPortGroupIndex.1.4
entAliasIdentifier.2.14.1 == rptrPortGroupIndex.2.2 entAliasIdentifier.2.14.1 == rptrPortGroupIndex.2.2
Draft Entity MIB January 14, 1996
Physical Containment Tree -- entPhysicalContainsTable Physical Containment Tree -- entPhysicalContainsTable
chassis has two backplanes and three containers: chassis has two backplanes and three containers:
entPhysicalChildIndex.1.2 = 2 entPhysicalChildIndex.1.2 = 2
entPhysicalChildIndex.1.3 = 3 entPhysicalChildIndex.1.3 = 3
entPhysicalChildIndex.1.4 = 4 entPhysicalChildIndex.1.4 = 4
entPhysicalChildIndex.1.5 = 5 entPhysicalChildIndex.1.5 = 5
Draft Entity MIB January 22, 1996
entPhysicalChildIndex.1.6 = 6 entPhysicalChildIndex.1.6 = 6
container 1 has a module: container 1 has a module:
entPhysicalChildIndex.4.7 = 7 entPhysicalChildIndex.4.7 = 7
container 2 has a module container 2 has a module
entPhysicalChildIndex.5.12 = 12 entPhysicalChildIndex.5.12 = 12
-- container 3 is empty -- container 3 is empty
module 1 has some ports: module 1 has some ports:
entPhysicalChildIndex.7.8 = 8 entPhysicalChildIndex.7.8 = 8
entPhysicalChildIndex.7.9 = 9 entPhysicalChildIndex.7.9 = 9
entPhysicalChildIndex.7.10 = 10 entPhysicalChildIndex.7.10 = 10
entPhysicalChildIndex.7.11 = 11 entPhysicalChildIndex.7.11 = 11
module 2 has some ports: module 2 has some ports:
entPhysicalChildIndex.12.13 = 13 entPhysicalChildIndex.12.13 = 13
entPhysicalChildIndex.12.14 = 14 entPhysicalChildIndex.12.14 = 14
Draft Entity MIB January 14, 1996 Draft Entity MIB January 22, 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 January 14, 1996 Draft Entity MIB January 22, 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 32, line 5 skipping to change at page 34, line 40
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 January 14, 1996 [8] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Transport
Mappings for version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1449, SNMP Research, Inc., Hughes LAN Systems, Dover
Beach Consulting, Inc., Carnegie Mellon University, April 1993.
Draft Entity MIB January 22, 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 33, line 5 skipping to change at page 36, 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 January 14, 1996 Draft Entity MIB January 22, 1996
Table of Contents Table of Contents
1 Introduction .................................................... 2 1 Introduction .................................................... 2
2 The SNMPv2 Network Management Framework ......................... 3 2 The SNMPv1 Network Management Framework ......................... 3
2.1 Object Definitions ............................................ 3 2.1 Object Definitions ............................................ 3
3 Overview ........................................................ 4 3 Overview ........................................................ 4
3.1 Terms ......................................................... 4 3.1 Terms ......................................................... 4
3.2 Relationship to Community Strings ............................. 6 3.2 Relationship to Community Strings ............................. 6
3.3 Relationship to Proxy Mechanisms .............................. 6 3.3 Relationship to Proxy Mechanisms .............................. 6
3.4 Relationship to a Chassis MIB ................................. 6 3.4 Relationship to a Chassis MIB ................................. 6
3.5 Relationship to the Interfaces MIB ............................ 6 3.5 Relationship to the Interfaces MIB ............................ 7
3.6 Relationship to the Other MIBs ................................ 7 3.6 Relationship to the Other MIBs ................................ 7
3.7 Re-Configuration of Entities .................................. 7 3.7 Re-Configuration of Entities .................................. 7
3.8 MIB Structure ................................................. 7 3.8 MIB Structure ................................................. 7
3.9 Multiple Agents ............................................... 8 3.9 Multiple Agents ............................................... 8
4 Definitions ..................................................... 9 4 Definitions ..................................................... 9
5 Usage Examples .................................................. 23 5 Usage Examples .................................................. 25
5.1 Router/Bridge ................................................. 23 5.1 Router/Bridge ................................................. 25
5.2 Repeaters ..................................................... 26 5.2 Repeaters ..................................................... 28
6 Acknowledgements ................................................ 30 6 Acknowledgements ................................................ 33
7 References ...................................................... 31 7 References ...................................................... 34
8 Security Considerations ......................................... 32 8 Security Considerations ......................................... 35
9 Authors' Addresses .............................................. 32 9 Authors' Addresses .............................................. 35
 End of changes. 

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