draft-ietf-entmib-state-01.txt   draft-ietf-entmib-state-02.txt 
Entity MIB Working Group S. Chisholm Entity MIB Working Group S. Chisholm
Internet Draft Nortel Networks Internet Draft Nortel Networks
Document: draft-ietf-entmib-state-01.txt D. Perkins Document: draft-ietf-entmib-state-02.txt D. Perkins
Category: Standards Track SNMPinfo & Category: Standards Track SNMPinfo
RiverStone Networks Expiration Date: June 2004 December 2003
Expiration Date: December 2003 June 2003
Entity State MIB Entity State MIB
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance This document is an Internet-Draft and is in full conformance
with all provisions of Section 10 of RFC2026. with all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 38 skipping to change at page 1, line 37
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes extensions to the entity MIB to In particular, it describes extensions to the Entity MIB to
provide information about the state of the entity. provide information about the state of the entity.
Table of Contents Table of Contents
1. The Internet-Standard Management Framework 1. The Internet-Standard Management Framework
2. Entity State 2. Entity State
2.1. Hierarchical State Management 2.1. Hierarchical State Management
2.2. State Relationships 2.2. Entity Redundancy
2.3. Physical Classes and State 3. Relationship to Other MIBs
2.4. Relation to Alarm MIB 3.1. Relation to Interfaces MIB
2.5. Entity Redundancy 3.2. Relation to Alarm MIB
3. Definitions 3.3. Relation to Bridge MIB
4. Security Considerations 3.4. Relation to Host Resource MIB
5. Authors' Addresses 4. Definitions
6. Acknowledgements 5. Security Considerations
7. References 6. Intellectual Property
8. Full Copyright Statement 7. Authors' Addresses
8. Acknowledgements
9. References
10. Full Copyright Statement
1. 1. The Internet-Standard Management Framework 1. 1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
2. Entity State 2. Entity State
The goal in adding state objects to the Entity MIB [RFC2737] is to The goal in adding state objects to the Entity MIB [RFC2737] is to
define a useful subset of the possible state attributes that could define a useful subset of the possible state attributes that could
be tracked for a given entity that both fit into the existing IETF be tracked for a given entity that both fit into the state models
model, as well as leveraged existing well-deployed models. The such as those used in the Interfaces MIB [RFC2863] as well as
entStateTable contains state objects that are a subset of the leverage existing well-deployed models. The entStateTable contains
popular ISO/OSI states that are also defined in ITU's X.731 state objects that are a subset of the popular ISO/OSI states that
specification [X.731]. Objects are defined to capture are also defined in ITU's X.731 specification [X.731]. Objects are
administrative, operational and usage states. In addition there are defined to capture administrative, operational and usage states. In
further state objects defined to provide additional information for addition there are further state objects defined to provide
these three basic states. additional information for these three basic states.
Administrative state indicates permission to use or prohibition Administrative state indicates permission to use or prohibition
against using the entity and is imposed through the management against using the entity and is imposed through the management
services. services.
Operational state indicates whether or not the entity is physically Operational state indicates whether or not the entity is physically
installed and working. Note that unlike the ifOperStatus [RFC2863], installed and working. Note that unlike the ifOperStatus [RFC2863],
this operational state is independent of the administrative state. this operational state is independent of the administrative state.
Usage state indicates whether or not the entity is in use at a Usage state indicates whether or not the entity is in use at a
specific instance, and if so, whether or not it currently has spare specific instance, and if so, whether or not it currently has spare
capacity to serve additional users. In the context of this MIB, the capacity to serve additional users. In the context of this MIB, the
user is equivalent to an entity, so this term us substituted. user is equivalent to an entity, so this term is substituted. This
state refers to the ability of the entity to service other entities
within its containment hierarchy.
Alarm state indicates whether or not there are any alarms active Alarm state indicates whether or not there are any alarms active
against the entity. In addition to those alarm status defined in against the entity. In addition to those alarm status defined in
X.731 [X.731], warning and indeterminate status are also defined to X.731 [X.731], warning and indeterminate status are also defined to
provide a more complete mapping to the Alarm MIB [Alarm-MIB]. provide a more complete mapping to the Alarm MIB [Alarm-MIB].
Standby state indicates whether the entity is currently running as Standby state indicates whether the entity is currently running as
hot standby, cold standby or is currently providing service. hot standby, cold standby or is currently providing service.
The terms state and status are used interchangeably in this memo. The terms state and status are used interchangeably in this memo.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
2.1 Hierarchical State Management 2.1 Hierarchical State Management
Physical entities exist within a containment hierarchy. This raises Physical entities exist within a containment hierarchy. This raises
some interesting issues not addresses in existing work on state some interesting issues not addressed in existing work on state
management [X.731]. management [X.731].
There are two types of state for an entity: There are two types of state for an entity:
1) The state of the entity independent of the states of its parents 1) The state of the entity independent of the states of its parents
and children in its containment hierarchy. This is often referred to and children in its containment hierarchy. This is often referred to
as raw state. as raw state.
2) The state of the entity, as it may be influenced by the state of 2) The state of the entity, as it may be influenced by the state of
its parents and children. This is often referred to as computed its parents and children. This is often referred to as computed
state. state.
All state objects in this memo are raw state. All state objects in this memo are raw state.
2.2 State Relationships 2.2 Entity Redundancy
The following section outlines all of the combinations of the three While this memo is not attempting to address the entire problem
basic states -administrative, operational and usage - and briefly space around redundancy, the entStateStandby object provides an
describes what each of these combinations of states means. It also important piece of state information for entities, which helps
compare this combination of states to that of the ifAdminStatus and identify which pieces of redundant equipment are currently providing
ifOperStatus objects of the Interfaces Group MIB [RFC2863] to both service, and which are waiting in either hot or cold standby mode.
provide insight to those familiar with these status objects as well
as to clarify the relationship between entities and interfaces, as 3 Relation to other MIBs
indicated by entAliasMappingIdentifier object in the Entity MIB
[RFC2737]. 3.1 Relationship to the Interfaces MIB
The Interfaces MIB [RFC2863] defines the ifAdminStatus object, which The Interfaces MIB [RFC2863] defines the ifAdminStatus object, which
has status of up, down and testing and the ifOperStatus object, has states of up, down and testing and the ifOperStatus object,
which has states of up, down, testing, unknown, dormant, notPresent which has states of up, down, testing, unknown, dormant, notPresent
and lowerLayerDown. and lowerLayerDown.
2.2.1 Admin State Locked, Operational State Disabled and Usage State Idle An ifAdminStatus of 'up' is equivalent to setting the entStateAdmin
object to 'unlocked'. An ifAdminStatus of 'down' is equivalent to
The entity is totally inoperable, it is not servicing any entities setting the entStateAdmin object to either 'locked' or
and it is also administratively prohibited from use. To make it 'shuttingDown', depending on a systems interpretation of 'down'.
available for use, both management permission and some corrective
action are necessary. This is similar to an ifAdminStatus of down
and ifOperStatus of down.
2.2.2 Admin State Locked, Operational State Enabled and Usage State Idle
The entity is partially or fully operable, it is not servicing any
entities but is administratively prohibited from use. To make it
available for use, only management permission is required. This is
similar to an ifAdminStatus of down and ifOperStatus of down.
2.2.3 Admin State Shutting Down, Operational State Enabled and Usage State
Active
The entity is partially or fully operable and in use, but usage is
administratively limited to current instances of use. For an
additional entity to gain access, management permission is required.
Otherwise, when all current entities have been removed from the
resource, the managed object will automatically transit to the
locked, enabled, and idle state. This is similar to the situation
described in [RFC2863] where ifAdminStatus transitions to down, but
the ifOperStatus's transition does not occur immediately, but rather
after a small time lag to complete certain operations before going
"down".
2.2.4 Admin State Shutting Down, Operational State Enabled and Usage State
Busy
The entity is partially or fully operable and in use, but usage is
administratively limited to current instances of use. In addition,
it has no spare capacity to provide for additional entities. For an
additional entity to gain access, besides waiting for an existing
entity to be removed, management permission is also required.
Otherwise, when all current entities have been removed from the
resource, the managed object will automatically transit to the
locked, enabled, idle state. This is similar to the situation
described in [RFC2863] where ifAdminStatus transitions to down, but
the ifOperStatus's transition does not occur immediately, but rather
after a small time lag to complete certain operations before going
"down".
2.2.5 Admin State Unlocked, Operational State Enabled and Usage State Idle
The entity is partially or fully operable, it is not actually in use
and is not administratively prohibited from use. This is similar to
an ifAdminStatus of up and ifOperStatus of up if the interface is
able to pass packets. If the interface is found to be operable, but
the interface is waiting for other, external, events to occur
before it can transmit or receive packets, then this is similar to
an ifAdminStatus of up and a ifOperStatus of dormant.
2.2.6 Admin State Unlocked, Operational State Enabled and Usage State Active
The entity is partially or fully operable, it is currently in use
and is not
administratively prohibited from use. It has sufficient spare
capacity to provide for additional entities. This is similar to an
ifAdminStatus of up and ifOperStatus of up.
2.2.7 Admin State Unlocked, Operational State Enabled and Usage State Busy
The entity is partially or fully operable, it is currently in use
and it is not administratively prohibited from use. Currently it has
no spare capacity to provide for additional entities. For an
additional entity to gain access, it is necessary to wait for an
existing entity to be removed or for some capacity increase to
occur. This is similar to an ifAdminStatus of up and ifOperStatus
of up.
2.2.8 Admin State Unlocked, Operational State Disabled and Usage State Idle
The entity is totally inoperable, it is servicing no entities but it
is not administratively prohibited from use. To make it available
for use, some corrective action is required. This is similar to an
ifAdminStatus of up and ifOperStatus of down. If the cause of the
interface being down is because of a lower layer being down, then
this is similar to an ifAdminStatus of up and an ifOperStatus of
lowerLayerDown.
2.3 Physical Classes and States
This section provides an overview of applying the states for the
basic physical classes as indicated by the entPhysicalClass object
in the Entity MIB [RFC2737]. The physical classes are chassis,
backplane, container, powerSupply, fan, sensor, module, port and
stack. All states can, in theory, be implemented for any class,
but some states or some values of states make less sense than
others, depending on the physical class of the entity.
2.3.1 Chassis
2.3.1.1 entStateAdmin
A value of unlocked for entStateAdmin means that this system is on.
A value of shuttingDown for entStateAdmin means that this system is
in the process of shutting down.
2.3.1.2 entStateOper
A value of enabled for entStateOper indicates that basic functions
of this system are functioning. A value of disabled for entStateOper
indicates a problem with basic functions on the system.
2.3.1.3 entStateUsage
Many chassis will come either fully populated or fully populated
with empty container entities, which can be filled independently and
therefore do not affect the entStateUsage of the chassis itself. In
both these cases and in the general case where the chassis can't
support any more direct child entities, entStateUsage will have a
value of busy. While an empty chassis might happen much in practice,
in this case the entStateUsage object would have a value of idle.
Likewise, if the chassis is partially used, then entStateUsage would
have a value of active.
2.3.1.4 entStateStandby
A value of hotStandby for enStateStandby indicates that the entire
system contained within this chassis is running as a hot standby for
another complete system, possibly contained within the same stack. A
value of coldStandby for enStateStandby indicates that the entire
system contained within this chassis is running as a cold standby
for another complete system, possibly contained within the same
stack. A value of providingService for enStateStandby indicates that
the entire system contained within this chassis is currently
providing service.
2.3.1.5 entStateAlarm
If this chassis is not contained within a stack, the alarm counts
indicated by entStateAlarm will be those alarms that are against the
general system, as appose sub-components within the containment
hierarchy.
2.3.2 BackPlane
2.3.2.1 entStateAdmin
A value of unlocked for entStateAdmin means that the backplane is
not administratively prevented from aggregating and forwarding
network traffic. A value of shutting down for entStateAdmin means
that the backplane will finish aggregating and forwarding the
network traffic is currently handling, but then transition to be
administratively locked. A value of locked for entStateAdmin means
that backplane is administratively prohibited from aggregating and
forwarding any network traffic.
2.3.2.2 entStateOper
A value of enabled for entStateOper means that the backplane is
partially or fully capable of aggregating and forwarding network
traffic. A value of disabled for entStateOper means that the
backplane is unable to aggregate and forward any network traffic.
2.3.2.3 entStateUsage
The entStateUsage for a backplane will busy.
2.3.2.4 entStateStandby
A value of hotStandby for enStateStandby indicates that the
backplane is running as a hot standby for another backplane within
this system. A value of coldStandby for enStateStandby indicates
that the backplane is running as a cold standby for another
backplane, possibly within this system. A value of providingService
for enStateStandby indicates that the backplane is currently
providing service.
2.3.2.5 entStateAlarm
Looking at the entStateAlarm gives a convenient way to see if there
are any alarms currently active against this backplane.
2.3.3 Container
2.3.3.1 entStatAdmin
A value of unlocked for entStateAdmin means it is administratively
possible to insert things into this container. A value of
shuttingDown for entStateAdmin could be used to reflect that
inserting objects into this container is administratively
prohibited. This value could also be used for systems that do not
support hot insertion of components.
2.3.3.2 entStateOper
It may not make sense for the entStateOper to have values other than
enabled.
2.3.3.3 entStateUsage
The container physical class could be used to indicate, among other
things, chassis slots or daughter-card holders. If the container is
empty, for example it has no modules in its slots, then
entStateUsage would have a value of idle. If the container is
partially used, for example it has modules in some but not all of
its slots, then entStateUsage would have a value of active. If the
container is full, for example it has no empty slots, then
entStateUsage would have a value of busy.
3.3.3.4 entStateStandby
Looking at the entStateStandby indicates whether this container is
currently providing service or acting as a backup for another
container.
2.3.3.5 entStateAlarm
If it is not possible to raise alarms against this chassis, the
entStateAlarm will have no alarms set.
2.3.4 PowerSupply
2.3.4.1 entStateAdmin
A value of locked for entStateAdmin means that the power supply has
been turned off. This only makes sense in the situation where there
is a backup power supply. A value of unlocked for entStateAdmin
means that the power supply is turned on.
2.3.4.2 entStateOper
A value of enabled for entStateOper means that the power supply is
operational. A value of disabled for entStateOper means that the
power supply is not functioning.
2.3.4.3 entStateUsage
A value of idle for entStateUsage means that the power supply is
providing no power to the system. A value of busy for entStateUsage
means that the power supply is providing power to the system.
2.3.3.4 entStateStandby
If this power supply is the currently providing power to the system,
then entStateStandby would have a value of providing service. If
this power supply is serving as a backup to a primary power supply,
then entStateStandby would have a value of hotstandby.
2.3.3.5 entStateAlarm
Looking at the entStateAlarm gives a convenient way to see if there
are any alarms currently active against this power supply.
2.3.5 Fan
2.3.5.1 entStateAdmin
Looking at the entStateAdmin and entStateOper provide useful
information to determine why a fan is not running. A value of locked
for entStateAdmin means that the fan is not running because it has
been administratively disabled.
2.3.5.2 entStateOper
A value of disabled for the entOperStatus indicates that the fan
itself is not operational. A value of enabled for the entOperStatus
indicates that the fan is working in theory and that cause of it not
operator may lie elsewhere.
2.3.5.3 entStateUsage
A value of busy for entStateUsage would indicate that the fan was
running. A value of idle for entStateUsage would indicate that the
fan was not actually running.
2.3.5.4 entStateStandby
If this fan is serving as a backup to a primary fan, then
entStateStandby would have a value of hotstandby. If this fan is the
currently providing service to the system, then entStateStandby
would have a value of providing service.
2.3.5.5 entStateAlarm
Looking at the entStateAlarm gives a convenient way to see if there
are any alarms currently active against this fan.
2.3.6 Sensor
2.3.6.1 entStateAdmin
A value of unlocked for entStateAdmin indicates that the sensor is
not administratively prohibited from sensing. A value of shutting
down for entStateAdmin indicates that the sensor will complete its
current readings and then shut down. A value of locked for
entStateAdmin indicates that the sensor is administratively
prohibited from sensing.
2.3.6.2 entStateOper
A value of enabled for entStateOper indicates that the sensor is
functioning properly. A value of disable for entStateOper indicates
that the sensor is totally inoperable.
2.3.6.3 entStateUsage
The value of entStateUsage will be busy.
2.3.6.4 entStateStandby
Looking at the entStateStandby indicates whether this sensor is
currently providing service or acting as a backup for another sensor.
2.3.6.5 entStateAlarm
Looking at the entStateAlarm gives a convenient way to see if there
are any alarms currently active against this sensor.
2.3.7 Module
2.3.7.1 entStateAdmin
For modules that support the functionality of being administratively
disabled, entStateAdmin object indicates whether the module is
administratively locked (disabled) or unlocked (enabled). Modules
that do not support disabling will always have a value of unlocked
for entStateAdmin.
2.3.7.2 entStateOper
A value of enabled for entStateOper indicates that this module is
partially or fully operational. A value of disabled for entStateOper
indicates that this module is totally inoperable.
2.3.7.3 entStateUsage
If a module comes fully populated with all possible child
components, or if there is not further room for child components,
then the value of entStateUsage will be busy. If it supports the
concept of dynamically added child components and there is room to
add more components, then entStateUsage will have a value of active.
If it supports the concept of dynamically added child components and
there are currently no children then entStateUsage will have a value
of idle.
2.3.7.4 entStateStandby
Looking at the entStateStandby indicates whether this module is
currently providing service or acting as a backup for another module.
2.3.7.5 entStateAlarm
Looking at the entStateAlarm gives a convenient way to see if there
are any alarms currently active against this module.
2.3.8 Port
2.3.8.1 entStateAdmin
A value of enabled for entStateAdmin means the port is not
administratively prohibited from passing network traffic. A value of
shutting down for entStateAdmin indicates that the port will pass
its current traffic and then transition to the locked state. A value
of locked for entStateAdmin indicates that the port is
administratively prohibited from passing network traffic.
2.3.8.2 entStateOper
A value of enabled for entStateOper means that the port is partially
or fully capable of forwarding network traffic. A value of disabled
for entStateOper means that the port is totally unable to forward
network traffic.
2.2.8.3 entStateUsage
A value of idle for entStateUsage indicates that the port is not
currently in use. A value of busy for entStateUsage indicates that
the port is in use.
2.3.8.4 entStateStandby
Looking at the entStateStandby indicates whether this port is
currently providing service or acting as a backup for another port.
2.3.8.5 entStateAlarm
Looking at the entStateAlarm gives a convenient way to see if there
are any alarms currently active against this port.
2.3.9 Stack
2.3.9.1 entStateAdmin
A value of unlocked for entStateAdmin means that this system is on.
A value of shuttingDown for entStateAdmin means that this system is
in the process of shutting down.
2.3.9.2 entStateOper
A value of enabled for entStateOper indicates that basic functions
of this system are functioning. A value of disabled for entStateOper
indicates a problem with basic functions on the system.
2.3.9.3 entStateUsage
If a stack comes fully populated with all possible child components,
or if there is not further room for child components, then the value
of entStateUsage will be busy. If it supports the concept of
dynamically added child components and there is room to add more
components, then entStateUsage will have a value of active. If it
supports the concept of dynamically added child components and there
are currently no children then entStateUsage will have a value of
idle.
2.3.9.4 entStateStandby
A value of hotStandby for enStateStandby indicates that the entire
system contained within this stack is running as a hot standby for
another complete system, possibly contained within the same parent
stack. A value of coldStandby for enStateStandby indicates that the
entire system contained within this stack is running as a cold
standby for another complete system, possibly contained within the
same parent stack. A value of providingService for enStateStandby
indicates that the entire system contained within this chassis is
currently providing service.
2.3.9.5 entStateAlarm
If this stack is not contained in within a parent stack, the alarm An ifOperStatus of 'up' is equivalent to an entStateOper value of
counts indicated by entStateAlarm will be those alarms that are 'enabled'. An ifOperStatus of 'down' due to operational failure is
against the general system, as appose sub-components within the equivalent to an entStateOper value of 'disabled'. An ifOperStatus
containment hierarchy. of 'down' due to being administratively disabled is equivalent to an
entStateAdmin value of 'locked' and an entStateOper value of either
'enabled' or 'disabled' depending on whether there are any known
issues that would prevent the entity from becoming operational when
its entStateAdmin is set to 'unlocked'. An ifOperStatus of
'unknown' is equivalent to an entStateOper value of 'notSupported'.
The ifOperStatus values of 'testing' and 'dormant' are not
explicitly supported by this MIB, but the state objects will be able
to reflect other aspects of the entities administrative and
operational state. The ifOperStatus values of 'notPresent' and
'lowerLayerDown' are in some ways computed states and so are
therefore not supported in this MIB. They can though be computed by
examining the states of entities within this objects containment
hierarchy and other available related states.
2.4 Relation to Alarm MIB 3.2 Relation to Alarm MIB
The entStateAlarm object indicates whether or not there are any The entStateAlarm object indicates whether or not there are any
active alarms against this entity. If there are active alarms, then active alarms against this entity. If there are active alarms, then
the alarmActiveTable in the Alarm MIB [Alarm MIB] should be searched the alarmActiveTable in the Alarm MIB [Alarm MIB] should be searched
for alarmActiveResourceId that match this entPhysicalIndex. for alarmActiveResourceId that match this entPhysicalIndex.
2.5 Entity Redundancy 3.3 Relation to Bridge MIB
While this memo is not attempting to address the entire problem For entities of physical type of 'port' that support the
space around redundancy, the entStateStandby object provides an dot1dStpPortEnable object in the Bridge MIB [RFC1493], a value of
important piece of state information for entities, which helps 'enabled' is equivalent to setting the entStateAdmin object to
identify which pieces of redundant equipment are currently 'unlocked'. Setting dot1dStpPortEnable to 'disabled' is equivalent
providing service, and which are waiting in either hot or cold to setting the entStateAdmin object to 'locked'.
standby mode.
3. Definitions 3.4 Relation to the Host Resources MIB
The hrDeviceStatus object in the Host Resources MIB [RFC2790]
provides an operational state for devices. For entities that
logically correspond to the concept of a device, a value of
'unknown' for hrDeviceStatus corresponds to an entStateOper value of
'notSupported'. A value of 'running' corresponds to an entStateOper
value of 'enabled'. A value of 'warning' also corresponds to an
entStateOper value of 'enabled', but with appropriate bits set in
the entStateAlarm object to indicate the alarms corresponding to the
unusual error condition detected. A value of 'testing' or 'down' is
equivalent to an entStateOper value of 'disabled'.
4. Definitions
ENTITY-STATE-MIB DEFINITIONS ::= BEGIN ENTITY-STATE-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION, DateAndTime TEXTUAL-CONVENTION, DateAndTime
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
entPhysicalIndex entPhysicalIndex
FROM ENTITY-MIB; FROM ENTITY-MIB;
entityStateMIB MODULE-IDENTITY entityStateMIB MODULE-IDENTITY
LAST-UPDATED "200306300000Z" LAST-UPDATED "200312180000Z"
ORGANIZATION "IETF Entity MIB Working Group" ORGANIZATION "IETF Entity MIB Working Group"
CONTACT-INFO CONTACT-INFO
" General Discussion: entmib@ietf.org " General Discussion: entmib@ietf.org
To Subscribe: To Subscribe:
http://www.ietf.org/mailman/listinfo/entmib http://www.ietf.org/mailman/listinfo/entmib
http://www.ietf.org/html.charters/entmib-charter.html http://www.ietf.org/html.charters/entmib-charter.html
Sharon Chisholm Sharon Chisholm
Nortel Networks Nortel Networks
PO Box 3511 Station C PO Box 3511 Station C
Ottawa, Ont. K1Y 4H7 Ottawa, Ont. K1Y 4H7
Canada Canada
schishol@nortelnetworks.com schishol@nortelnetworks.com
David T. Perkins David T. Perkins
skipping to change at page 14, line 14 skipping to change at page 6, line 29
http://www.ietf.org/html.charters/entmib-charter.html http://www.ietf.org/html.charters/entmib-charter.html
Sharon Chisholm Sharon Chisholm
Nortel Networks Nortel Networks
PO Box 3511 Station C PO Box 3511 Station C
Ottawa, Ont. K1Y 4H7 Ottawa, Ont. K1Y 4H7
Canada Canada
schishol@nortelnetworks.com schishol@nortelnetworks.com
David T. Perkins David T. Perkins
Riverstone Networks 548 Qualbrook Ct
5200 Great America Parkway San Jose, CA 95110
Santa Clara, CA 95054
USA USA
Phone: 408 394-8702
dperkins@snmpinfo.com dperkins@snmpinfo.com
" "
DESCRIPTION DESCRIPTION
"This MIB defines a state extension to the entity MIB. "This MIB defines a state extension to the Entity MIB.
Copyright (C) The Internet Society 2003. This version Copyright (C) The Internet Society 2003. This version
of this MIB module is part of RFC yyyy; see the RFC of this MIB module is part of RFC yyyy; see the RFC
itself for full legal notices." itself for full legal notices."
-- RFC Ed.: replace yyyy with actual RFC number & remove -- RFC Ed.: replace yyyy with actual RFC number & remove
-- this note -- this note
REVISION "200306300000Z" REVISION "200312180000Z"
DESCRIPTION DESCRIPTION
"Initial version, published as RFC YYYY." "Initial version, published as RFC YYYY."
-- RFC-Editor assigns yyyy -- RFC-Editor assigns yyyy
::= { mib-2 XX } -- to be assigned by IANA ::= { mib-2 XX } -- to be assigned by IANA
-- Textual conventions -- Textual conventions
AdminState ::= TEXTUAL-CONVENTION AdminState ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" Represents the various possible administrative states. " Represents the various possible administrative states.
A value of locked means the resource is administratively A value of 'locked' means the resource is administratively
prohibited from use. A value of shuttingDown means that prohibited from use. A value of 'shuttingDown' means that
usage is administratively limited to current instances of usage is administratively limited to current instances of
use. A value of unlocked means the resource is not use. A value of 'unlocked' means the resource is not
administratively prohibited from use." administratively prohibited from use."
REFERENCE REFERENCE
"ITU Recommendation X.731, 'Information Technology - Open "ITU Recommendation X.731, 'Information Technology - Open
Systems Interconnection - System Management: State Systems Interconnection - System Management: State
Management Function', 1992" Management Function', 1992"
SYNTAX INTEGER SYNTAX INTEGER
{ {
notSupported(1), notSupported(1),
locked(2), locked(2),
shuttingDown(3), shuttingDown(3),
unlocked(4) unlocked(4)
} }
OperState ::= TEXTUAL-CONVENTION OperState ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" Represents the possible values of operational states. " Represents the possible values of operational states.
A value of disabled means the resource is totally A value of 'disabled' means the resource is totally
inoperable. A value of enabled means the resource inoperable. A value of 'enabled' means the resource
is partially or fully operable." is partially or fully operable."
REFERENCE REFERENCE
"ITU Recommendation X.731, 'Information Technology - Open "ITU Recommendation X.731, 'Information Technology - Open
Systems Interconnection - System Management: State Systems Interconnection - System Management: State
Management Function', 1992" Management Function', 1992"
SYNTAX INTEGER SYNTAX INTEGER
{ {
notSupported (1), notSupported (1),
disabled(2), disabled(2),
enabled(3) enabled(3)
} }
UsageState ::= TEXTUAL-CONVENTION UsageState ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" Represents the possible values of usage states. " Represents the possible values of usage states.
A value of idle means the resource is servicing no users. A value of 'idle' means the resource is servicing no
A value of active means the resource is currently in use users. A value of 'active' means the resource is
and it has sufficient spare capacity to provide for currently in use and it has sufficient spare capacity
additional users. A value of busy means the resource is to provide for additional users. A value of 'busy'
currently in use, but it currently has no spare capacity means the resource is currently in use, but it
to provide for additional users." currently has no spare capacity to provide for
additional users."
REFERENCE REFERENCE
"ITU Recommendation X.731, 'Information Technology - Open "ITU Recommendation X.731, 'Information Technology - Open
Systems Interconnection - System Management: State Systems Interconnection - System Management: State
Management Function', 1992" Management Function', 1992"
SYNTAX INTEGER SYNTAX INTEGER
{ {
notSupported (1), notSupported (1),
idle(2), idle(2),
active(3), active(3),
busy(4) busy(4)
skipping to change at page 16, line 10 skipping to change at page 8, line 23
AlarmStatus ::= TEXTUAL-CONVENTION AlarmStatus ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the possible values of alarm status. "Represents the possible values of alarm status.
When no bits of this attribute are set, then none of the When no bits of this attribute are set, then none of the
status conditions described below are present. When the status conditions described below are present. When the
value of under repair is set, the resource is currently value of under repair is set, the resource is currently
being repaired. being repaired.
When the value of critical is set, one or more critical When the value of 'critical' is set, one or more critical
alarms are active against the resource. When the value of alarms are active against the resource. When the value of
major is set, one or more major alarms are active against 'major' is set, one or more major alarms are active against
the resource. When the value of minor is set, one or more the resource. When the value of 'minor' is set, one or more
minor alarms are active against the resource. When the minor alarms are active against the resource. When the
value of warning is set, one or more warning alarms are value of 'warning' is set, one or more warning alarms are
active against the resource. When the value of active against the resource. When the value of
indeterminate is set, one or more alarms of indeterminate 'indeterminate' is set, one or more alarms of
severity are active against the resource. indeterminate severity are active against the resource.
When the value of alarm outstanding is set, one or more When the value of 'alarmOutstanding' is set, one or more
alarms is active against the resource. The fault may or may alarms is active against the resource. The fault may or may
not be disabling. " not be disabling. "
REFERENCE REFERENCE
"ITU Recommendation X.731, 'Information Technology - Open "ITU Recommendation X.731, 'Information Technology - Open
Systems Interconnection - System Management: State Systems Interconnection - System Management: State
Management Function', 1992" Management Function', 1992"
SYNTAX BITS SYNTAX BITS
{ {
notSupported (0), notSupported (0),
underRepair(1), underRepair(1),
critical(2), critical(2),
major(3), major(3),
minor(4), minor(4),
alarmOutstanding(5), alarmOutstanding(5),
warning (6), -- Not defined in X.731 -- The following are not defined in X.733
indeterminate (7) -- Not defined in X.731 warning (6),
indeterminate (7)
} }
StandbyStatus ::= TEXTUAL-CONVENTION StandbyStatus ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" Represents the possible values of standby status. " Represents the possible values of standby status.
A value of hotStandby means the resource is not providing A value of 'hotStandby' means the resource is not
service, but is will be immediately able to take over the providing service, but is will be immediately able to
role of the resource to be backed-up, without the need for take over the role of the resource to be backed-up,
initialization activity, and will contain the same without the need for initialization activity, and will
information as the resource to be backed up. A value of contain the same information as the resource to be
coldStandy means that the resource is to back-up another backed up. A value of 'coldStandy' means that the
resource, but will not be immediately able to take over resource is to back-up another resource, but will not
the role of a resource to be backed up, and will require be immediately able to take over the role of a resource
some initialization activity. A value of providingService to be backed up, and will require some initialization
means the resource is providing service." activity. A value of 'providingService' means the
resource is providing service."
REFERENCE REFERENCE
"ITU Recommendation X.731, 'Information Technology - Open "ITU Recommendation X.731, 'Information Technology - Open
Systems Interconnection - System Management: State Systems Interconnection - System Management: State
Management Function', 1992" Management Function', 1992"
SYNTAX INTEGER SYNTAX INTEGER
{ {
notSupported (1), notSupported (1),
hotStandby(2), hotStandby(2),
coldStandby(3), coldStandby(3),
providingService(4) providingService(4)
skipping to change at page 17, line 50 skipping to change at page 10, line 16
entStateUsage UsageState, entStateUsage UsageState,
entStateAlarm AlarmStatus, entStateAlarm AlarmStatus,
entStateStandby StandbyStatus entStateStandby StandbyStatus
} }
entStateLastChanged OBJECT-TYPE entStateLastChanged OBJECT-TYPE
SYNTAX DateAndTime SYNTAX DateAndTime
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The value of this object is the date and DESCRIPTION "The value of this object is the date and
time when state/status of the component time when state/status of the entity
last changed, or zero." last changed, or zero."
::= { entStateEntry 1 } ::= { entStateEntry 1 }
entStateAdmin OBJECT-TYPE entStateAdmin OBJECT-TYPE
SYNTAX AdminState SYNTAX AdminState
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The administrative state for this entity." "The administrative state for this entity. A value
of 'notSupported' means that this entity is unable
to report administrative state. This object can not
be administratively set to 'notSupported'. For
entities that do not support administrative state,
changing the value of this object to something other
than 'notSupported' is not permitted. A value of
'inconsistentValue' will be returned in either case.
Some physical entities exhibit only a subset of the
remaining administrative state values. Some entities
cannot be locked, and hence this object exhibits only
the 'unlocked' state. Other entities can not be shutdown
gracefully, and hence this object does not exhibit the
'shuttingDown' state. A value of 'inconsistentValue'
will be returned if attempts are made to set this
object to values not supported by its administrative
model."
::= { entStateEntry 2 } ::= { entStateEntry 2 }
entStateOper OBJECT-TYPE entStateOper OBJECT-TYPE
SYNTAX OperState SYNTAX OperState
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The operational state for this entity." "The operational state for this entity. A value
of 'notSupported' means that this entity is unable
to report operational state.
Note that unlike the state model used within the
Interfaces MIB [RFC2863], this object does not follow
the administrative state. An administrative state of
down does not predict an operational state
of disabled.
A value of 'disabled' means that an entity is totally
inoperable and unable to provide service both to entities
within its containment hierarchy, as defined by having
a value of entPhysicalContainedIn that refers to this
entity, or to other receivers of its service as defined
in ways outside the scope of this MIB.
A value of 'enabled' means that an entity is fully or
partially operable and able to provide service both to
entities within its containment hierarchy, as defined
by having a value of entPhysicalContainedIn that
refers to this entity, or to other receivers of its
service as defined in ways outside the scope of this
MIB."
::= { entStateEntry 3 } ::= { entStateEntry 3 }
entStateUsage OBJECT-TYPE entStateUsage OBJECT-TYPE
SYNTAX UsageState SYNTAX UsageState
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The usage state for this entity." "The usage state for this entity. A value of
'notSupported' means that this entity is unable to
report usage state.
Note that in the context of a physical entity, this
object refers to an entity's ability to service more
physical entities in a containment hierarchy. A value
of 'idle' means this entity is able to contain other
entities but that no other entity is currently
contained within this entity, as would have been
demonstrated by a value of entPhysicalContainedIn
that referenced this entity.
A value of 'active' means that at least one entity is
contained within this entity and therefore has a value
of entPhysicalContainedIn that references this entity,
but that it could handle more. A value of 'busy' means
that the entity is unable to handle any additional
entities being contained in it, as demonstrated by
having a value of entPhysicalContainedIn that refers to
this entity.
Some entities will exhibit only a subset of the
usage state values. Entities that are unable to ever
service any entities within a containment hierarchy will
always have a usage state of 'busy'. Some entities will
only ever be able to support one entity within its
containment hierarchy and will therefore only exhibit
values of 'idle' and 'busy'."
::= { entStateEntry 4 } ::= { entStateEntry 4 }
entStateAlarm OBJECT-TYPE entStateAlarm OBJECT-TYPE
SYNTAX AlarmStatus SYNTAX AlarmStatus
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The alarm status for this entity. It does not include "The alarm status for this entity. It does not include
the severity of alarms raised on child components." the alarms raised on child components within its
containment hierarchy, as defined by a value of
entPhysicalContainedIn that references this entity.
A value of 'notSupported' means that this entity is
unable to report alarm state. Note that this differs
from 'indeterminate' which means that that alarm state
is supported and there are alarms against this entity,
but the severity of some of the alarms is not known.
If no bits are set, then this entity supports reporting
of alarms, but there are currently no active alarms
against this entity.
"
::= { entStateEntry 5 } ::= { entStateEntry 5 }
entStateStandby OBJECT-TYPE entStateStandby OBJECT-TYPE
SYNTAX StandbyStatus SYNTAX StandbyStatus
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The standby status for this entity." "The standby status for this entity. A value of
'notSupported' means that this entity is unable to
report standby state.
Some entities will exhibit only a subset of the
remaining standby state values. If this entity does
not have a standby, this object will always be
'providingService'."
::= { entStateEntry 6 } ::= { entStateEntry 6 }
-- Notifications -- Notifications
entStateTraps OBJECT IDENTIFIER ::= { entityStateMIB 2 } entStateTraps OBJECT IDENTIFIER ::= { entityStateMIB 2 }
entStateTrapPrefix OBJECT IDENTIFIER ::= { entStateTraps 0 } entStateTrapPrefix OBJECT IDENTIFIER ::= { entStateTraps 0 }
entStateOperEnabled NOTIFICATION-TYPE entStateOperEnabled NOTIFICATION-TYPE
OBJECTS { entStateAdmin, OBJECTS { entStateAdmin,
entStateAlarm entStateAlarm
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The entity is operational. The entity this "An entStateOperEnabled trap signifies that the SNMP
notification refers can be identified by entity, acting in an agent role, has detected that the
entStateOper object for one of its entities has left
the 'disabled' state and transitioned into the 'enabled'
state.
The entity this notification refers can be identified by
extracting the entPhysicalIndex from one of the extracting the entPhysicalIndex from one of the
variable bindings." variable bindings."
::= { entStateTrapPrefix 1 } ::= { entStateTrapPrefix 1 }
entStateOperDisabled NOTIFICATION-TYPE entStateOperDisabled NOTIFICATION-TYPE
OBJECTS { entStateAdmin, OBJECTS { entStateAdmin,
entStateAlarm } entStateAlarm }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The entity is not operational. The entity this "An entStateOperDisabled trap signifies that the SNMP
notification refers can be identified by entity, acting in an agent role, has detected that the
entStateOper object for one of its entities has left
the 'enabled' state and transitioned into the
'disabled' state.
The entity this notification refers can be identified by
extracting the entPhysicalIndex from one of the extracting the entPhysicalIndex from one of the
variable bindings." variable bindings."
::= { entStateTrapPrefix 2 } ::= { entStateTrapPrefix 2 }
-- Conformance and Compliance -- Conformance and Compliance
entStateConformance OBJECT IDENTIFIER ::= { entityStateMIB 3 } entStateConformance OBJECT IDENTIFIER ::= { entityStateMIB 3 }
entStateCompliances OBJECT IDENTIFIER entStateCompliances OBJECT IDENTIFIER
::= { entStateConformance 1 } ::= { entStateConformance 1 }
entStateCompliance MODULE-COMPLIANCE entStateCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for systems supporting "The compliance statement for systems supporting
the Entity State MIB." the Entity State MIB."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
entStateGroup entStateGroup
} }
GROUP entStateNotificationsGroup
DESCRIPTION
"This group is optional."
OBJECT entStateAdmin OBJECT entStateAdmin
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { entStateCompliances 1 } ::= { entStateCompliances 1 }
entStateGroups OBJECT IDENTIFIER ::= { entStateConformance 2 } entStateGroups OBJECT IDENTIFIER ::= { entStateConformance 2 }
entStateGroup OBJECT-GROUP entStateGroup OBJECT-GROUP
OBJECTS { OBJECTS {
skipping to change at page 20, line 18 skipping to change at page 14, line 34
entStateOperEnabled, entStateOperEnabled,
entStateOperDisabled entStateOperDisabled
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Standard Entity State Notification group." "Standard Entity State Notification group."
::= { entStateGroups 2} ::= { entStateGroups 2}
END END
4. Security Considerations 5. Security Considerations
There is one management object defined in this MIB that has a There is one management object defined in this MIB that has a
MAX-ACCESS clause of read-write. The object may be considered MAX-ACCESS clause of read-write. The object may be considered
sensitive or vulnerable in some network environments. The support sensitive or vulnerable in some network environments. The support
for SET operations in a non-secure environment without proper for SET operations in a non-secure environment without proper
protection can have a negative effect on network operations. protection can have a negative effect on network operations.
The following object is defined with a MAX-ACCESS clause of The following object is defined with a MAX-ACCESS clause of
read-write: entStateAdmin. read-write: entStateAdmin.
skipping to change at page 20, line 48 skipping to change at page 15, line 13
authentication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (entities) that have legitimate the objects only to those principals (entities) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
5. Authors' Addresses Note that setting the entStateAdmin to 'locked' or 'shuttingDown'
can cause disruption of services ranging from those running on a
port to those on an entire device, depending on the type of entity.
Access to this object should be properly protected.
Access to the objects defined in this MIB allows one to figure out
what the active and standby resources in a network are. This
information can be used to optimize attacks on networks so even
read-only access to this MIB should be properly protected.
6. Intellectual Property
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances
of licenses to be made available, or the result of an attempt made
to obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification
can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
7. Authors' Addresses
Sharon Chisholm Sharon Chisholm
Nortel Networks Nortel Networks
PO Box 3511, Station C PO Box 3511, Station C
Ottawa, Ontario, K1Y 4H7 Ottawa, Ontario, K1Y 4H7
Canada Canada
Email: schishol@nortelnetworks.com Email: schishol@nortelnetworks.com
David T. Perkins David T. Perkins
Riverstone Networks 548 Qualbrook Ct
5200 Great America Parkway San Jose, CA 95110
Santa Clara, CA 95054
USA USA
Phone: 408 394-8702
Email: dperkins@snmpinfo.com Email: dperkins@snmpinfo.com
6. Acknowledgments 8. Acknowledgments
This document is a product of the Entity MIB Working Group. This document is a product of the Entity MIB Working Group.
7. References 9. References
7.1 Normative 9.1 Normative
[ALARM-MIB] Chisholm, S., Romascanu, D., "Alarm MIB", [ALARM-MIB] Chisholm, S., Romascanu, D., "Alarm MIB",
draft-ietf-disman-alarm-mib-10.txt, April 2003 draft-ietf-disman-alarm-mib-16.txt, November 2003
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Structure of Management Rose, M. and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999. 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
skipping to change at page 21, line 45 skipping to change at page 16, line 42
Rose, M. and S. Waldbusser, "Conformance Statements for Rose, M. and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
[RFC2737] McCloghrie, K., Bierman, A., "Entity MIB (Version 2)", [RFC2737] McCloghrie, K., Bierman, A., "Entity MIB (Version 2)",
December 1999. December 1999.
[X.731] ITU Recommendation X.731, "Information Technology - Open [X.731] ITU Recommendation X.731, "Information Technology - Open
Systems Interconnection - System Management: State Systems Interconnection - System Management: State
Management Function", 1992 Management Function", 1992
7.2 Informative References 8.2 Informative References
[RFC1493] Decker, E., Langille, P., Rijsinghani, A., McCloghrie, K.,
"Definitions of Managed Objects for Bridges", RFC 1493,
July 1993
[RFC2790] Waldbusser, S., Grillo, P., "Host Resources MIB",
RFC 2790, March 2000
[RFC2863] McCloghrie, K., Kastenholz, F., "The Interfaces Group
MIB using SMIv2", RFC2863, June 2000
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
8. Full Copyright Statement 10. Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any kind, and distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
 End of changes. 

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