Entity MIB Working Group S. Chisholm
Internet Draft Nortel Networks
Document: draft-ietf-entmib-state-03.txt D. Perkins
Category: Standards Track SNMPinfo
Expiration Date: August 2004 February 2004
Entity State MIB
Status of this Memo
This document is an Internet-Draft and is in full conformance
with all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as
Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet-
Drafts as reference material or to cite them other than as
"work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Abstract
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes extensions to the Entity MIB to
provide information about the state of physical entities.
Table of Contents
1. The Internet-Standard Management Framework
2. Entity State
2.1. Hierarchical State Management
2.2. Entity Redundancy
3. Relationship to Other MIBs
3.1. Relation to Interfaces MIB
3.2. Relation to Alarm MIB
3.3. Relation to Bridge MIB
3.4. Relation to Host Resource MIB
4. Definitions
Chisholm & Perkins Standards Track [Page 1]
Entity State MIB February 2004
5. Security Considerations
6. Intellectual Property
7. Authors' Addresses
8. Acknowledgements
9. References
10. Full Copyright Statement
Chisholm & Perkins Standards Track [Page 2]
Entity State MIB February 2004
1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB
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
[RFC2580].
2. Entity State
The goal in adding state objects to the Entity MIB [RFC2737] is to
define a useful subset of the possible state attributes that could
be tracked for a given entity that both fit into the state models
such as those used in the Interfaces MIB [RFC2863] as well as
leverage existing well-deployed models. The entStateTable contains
state objects that are a subset of the popular ISO/OSI states that
are also defined in ITU's X.731 specification [X.731]. Objects are
defined to capture administrative, operational and usage states. In
addition there are further state objects defined to provide
additional information for these three basic states.
Administrative state indicates permission to use or prohibition
against using the entity and is imposed through the management
services.
Operational state indicates whether or not the entity is physically
installed and working. Note that unlike the ifOperStatus [RFC2863],
this operational state is independent of the administrative state.
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
capacity to serve additional users. In the context of this MIB, the
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
against the entity. In addition to those alarm status defined in
X.731 [X.731], warning and indeterminate status are also defined to
provide a more complete mapping to the Alarm MIB [Alarm-MIB].
Standby state indicates whether the entity is currently running as
hot standby, cold standby or is currently providing service.
Chisholm & Perkins Standards Track [Page 3]
Entity State MIB February 2004
The terms state and status are used interchangeably in this memo.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
2.1 Hierarchical State Management
Physical entities exist within a containment hierarchy. Physical
containment is defined by the entPhysicalContainedIn
object[RFC2737]. This raises some interesting issues not addressed
in existing work on state management [X.731].
There are two types of state for an entity:
1) The state of the entity independent of the states of its parents
and children in its containment hierarchy. This is often referred to
as raw state.
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
state.
All state objects in this memo are raw state.
2.2 Entity Redundancy
While this memo is not attempting to address the entire problem
space around redundancy, the entStateStandby object provides an
important piece of state information for entities, which helps
identify which pieces of redundant equipment are currently providing
service, and which are waiting in either hot or cold standby mode.
3 Relation to other MIBs
3.1 Relationship to the Interfaces MIB
The Interfaces MIB [RFC2863] defines the ifAdminStatus object, which
has states of up, down and testing and the ifOperStatus object,
which has states of up, down, testing, unknown, dormant, notPresent
and lowerLayerDown.
An ifAdminStatus of 'up' is equivalent to setting the entStateAdmin
object to 'unlocked'. An ifAdminStatus of 'down' is equivalent to
setting the entStateAdmin object to either 'locked' or
'shuttingDown', depending on a systems interpretation of 'down'.
An ifOperStatus of 'up' is equivalent to an entStateOper value of
'enabled'. An ifOperStatus of 'down' due to operational failure is
Chisholm & Perkins Standards Track [Page 4]
Entity State MIB February 2004
equivalent to an entStateOper value of 'disabled'. An ifOperStatus
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 'unavailable'.
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.
3.2 Relation to Alarm MIB
The entStateAlarm object indicates whether or not there are any
active alarms against this entity. If there are active alarms, then
the alarmActiveTable in the Alarm MIB [Alarm MIB] should be searched
for alarmActiveResourceId that match this entPhysicalIndex.
Alternatively, if the alarmActiveTable is queried first and an
active alarm with a value of alarmActiveResourceId that matches this
entPhysicalIndex is found, then entStateAlarm can be used to quickly
determine if there are additional active alarms against this
physical entity.
3.3 Relation to Bridge MIB
For entities of physical type of 'port' that support the
dot1dStpPortEnable object in the Bridge MIB [RFC1493], a value of
'enabled' is equivalent to setting the entStateAdmin object to
'unlocked'. Setting dot1dStpPortEnable to 'disabled' is equivalent
to setting the entStateAdmin object to 'locked'.
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
'unavailable'. 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'.
Chisholm & Perkins Standards Track [Page 5]
Entity State MIB February 2004
4. Definitions
ENTITY-STATE-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2
FROM SNMPv2-SMI
TEXTUAL-CONVENTION, DateAndTime
FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF
entPhysicalIndex
FROM ENTITY-MIB;
entityStateMIB MODULE-IDENTITY
LAST-UPDATED "200402150000Z"
ORGANIZATION "IETF Entity MIB Working Group"
CONTACT-INFO
" General Discussion: entmib@ietf.org
To Subscribe:
http://www.ietf.org/mailman/listinfo/entmib
http://www.ietf.org/html.charters/entmib-charter.html
Sharon Chisholm
Nortel Networks
PO Box 3511 Station C
Ottawa, Ont. K1Y 4H7
Canada
schishol@nortelnetworks.com
David T. Perkins
548 Qualbrook Ct
San Jose, CA 95110
USA
Phone: 408 394-8702
dperkins@snmpinfo.com
"
DESCRIPTION
"This MIB defines a state extension to the Entity MIB.
Copyright (C) The Internet Society 2004. This version
of this MIB module is part of RFC yyyy; see the RFC
itself for full legal notices."
-- RFC Ed.: replace yyyy with actual RFC number & remove
-- this note
REVISION "200402150000Z"
DESCRIPTION
"Initial version, published as RFC YYYY."
-- RFC-Editor assigns yyyy
::= { mib-2 XX } -- to be assigned by IANA
Chisholm & Perkins Standards Track [Page 6]
Entity State MIB February 2004
-- Textual conventions
AdminState ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" Represents the various possible administrative states.
A value of 'locked' means the resource is administratively
prohibited from use. A value of 'shuttingDown' means that
usage is administratively limited to current instances of
use. A value of 'unlocked' means the resource is not
administratively prohibited from use. A value of
'unavailable' means that this resource is unable to
report administrative state."
REFERENCE
"ITU Recommendation X.731, 'Information Technology - Open
Systems Interconnection - System Management: State
Management Function', 1992"
SYNTAX INTEGER
{
unavailable(1),
locked(2),
shuttingDown(3),
unlocked(4)
}
OperState ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" Represents the possible values of operational states.
A value of 'disabled' means the resource is totally
inoperable. A value of 'enabled' means the resource
is partially or fully operable. A value of 'testing'
means the resource is currently being tested
and cannot there fore report whether it is operational
or not. A value of 'unavailable' means that this
resource is unable to report operational state. "
REFERENCE
"ITU Recommendation X.731, 'Information Technology - Open
Systems Interconnection - System Management: State
Management Function', 1992"
SYNTAX INTEGER
{
unavailable (1),
disabled(2),
enabled(3),
testing (4)
}
Chisholm & Perkins Standards Track [Page 7]
Entity State MIB February 2004
UsageState ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" Represents the possible values of usage states.
A value of 'idle' means the resource is servicing no
users. A value of 'active' means the resource is
currently in use and it has sufficient spare capacity
to provide for additional users. A value of 'busy'
means the resource is currently in use, but it
currently has no spare capacity to provide for
additional users. A value of 'unavailable' means
that this resource is unable to report usage state."
REFERENCE
"ITU Recommendation X.731, 'Information Technology - Open
Systems Interconnection - System Management: State
Management Function', 1992"
SYNTAX INTEGER
{
unavailable (1),
idle(2),
active(3),
busy(4)
}
AlarmStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Represents the possible values of alarm status.
An Alarm [ALARM-MIB] is a persistent indication
of an error or warning condition.
When no bits of this attribute are set, then none
of the value of under repair is set, the resource is
currently being repaired, which depending on the
implementation, may make the other values in this bit
string unreliable.
When the value of 'critical' is set, one or more critical
alarms are active against the resource. When the value
of 'major' is set, one or more major alarms are active
against the resource. When the value of 'minor' is set,
one or more minor alarms are active against the resource.
When the value of 'warning' is set, one or more warning
alarms are active against the resource. When the value
of 'indeterminate' is set, one or more alarms whose of
perceived severity cannot be determined are active
against this resource.
When the value of 'alarmOutstanding' is set, one or more
alarms is active against the resource. The fault may
or may not be disabling. This bit provides a high-level
Chisholm & Perkins Standards Track [Page 8]
Entity State MIB February 2004
summary that can be used to determine whether or not
to examine the rest of the values. A value of
'unavailable' means that this resource is unable to
report alarm state."
REFERENCE
"ITU Recommendation X.731, 'Information Technology - Open
Systems Interconnection - System Management: State
Management Function', 1992"
SYNTAX BITS
{
unavailable (0),
underRepair(1),
critical(2),
major(3),
minor(4),
alarmOutstanding(5),
-- The following are not defined in X.733
warning (6),
indeterminate (7)
}
StandbyStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" Represents the possible values of standby status.
A value of 'hotStandby' means the resource is not
providing service, but it will be immediately able to
take over the role of the resource to be backed-up,
without the need for initialization activity, and will
contain the same information as the resource to be
backed up. A value of 'coldStandy' means that the
resource is to back-up another resource, but will not
be immediately able to take over the role of a resource
to be backed up, and will require some initialization
activity. A value of 'providingService' means the
resource is providing service. A value of
'unavailable' means that this resource is unable to
report standby state."
REFERENCE
"ITU Recommendation X.731, 'Information Technology - Open
Systems Interconnection - System Management: State
Management Function', 1992"
SYNTAX INTEGER
{
unavailable (1),
hotStandby(2),
coldStandby(3),
providingService(4)
}
Chisholm & Perkins Standards Track [Page 9]
Entity State MIB February 2004
-- Entity State Objects
entStateObjects OBJECT IDENTIFIER ::= { entityStateMIB 1 }
entStateTable OBJECT-TYPE
SYNTAX SEQUENCE OF EntStateEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of information about state/status of entities.
This is a sparse augment of the entPhysicalTable. Entries
appear in this table for values of
entPhysicalClass [RFC2737] that in this implementation
are able to report any of the state or status stored in
this table.
"
::= { entStateObjects 1 }
entStateEntry OBJECT-TYPE
SYNTAX EntStateEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"State information about this physical entity."
INDEX { entPhysicalIndex }
::= { entStateTable 1 }
EntStateEntry ::= SEQUENCE {
entStateLastChanged DateAndTime,
entStateAdmin AdminState,
entStateOper OperState,
entStateUsage UsageState,
entStateAlarm AlarmStatus,
entStateStandby StandbyStatus
}
entStateLastChanged OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this object is the date and
time when the value of any of entStateAdmin,
entStateOper, entStateUsage, entStateAlarm,
or entStateStandby changed for this entity.
If there has been no change since
the last re-initialization of the local system,
this object contains the date and time of
local system initialization. If there has been
no change since the entity was added to the
Chisholm & Perkins Standards Track [Page 10]
Entity State MIB February 2004
local system, this object contains the date and
time of the insertion"
::= { entStateEntry 1 }
entStateAdmin OBJECT-TYPE
SYNTAX AdminState
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The administrative state for this entity.
Setting this object to 'notSupported' will result
in an 'inconsistentValue' error. For entities that
do not support administrative state, all set
operations will result in an 'inconsistentValue'
error
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 }
entStateOper OBJECT-TYPE
SYNTAX OperState
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The operational state for this entity.
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, 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, or to other
receivers of its service as defined in ways outside the
scope of this MIB.
Chisholm & Perkins Standards Track [Page 11]
Entity State MIB February 2004
Note that some implementations may not be able to
accurately report entStateOper while the
entStateAdmin object has a value other than 'unlocked'.
In these cases, this object MUST have a value
of 'unavailable'."
::= { entStateEntry 3 }
entStateUsage OBJECT-TYPE
SYNTAX UsageState
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The usage state for this entity.
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.
A value of 'active' means that at least one entity is
contained within 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.
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 }
entStateAlarm OBJECT-TYPE
SYNTAX AlarmStatus
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The alarm status for this entity. It does not include
the alarms raised on child components within its
containment hierarchy.
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.
Chisholm & Perkins Standards Track [Page 12]
Entity State MIB February 2004
"
::= { entStateEntry 5 }
entStateStandby OBJECT-TYPE
SYNTAX StandbyStatus
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The standby status for this entity.
Some entities will exhibit only a subset of the
remaining standby state values. If this entity
cannot operate in a standby role, the value of this
object will always be 'providingService'."
::= { entStateEntry 6 }
-- Notifications
entStateNotifications OBJECT IDENTIFIER ::= { entityStateMIB 0 }
entStateOperEnabled NOTIFICATION-TYPE
OBJECTS { entStateAdmin,
entStateAlarm
}
STATUS current
DESCRIPTION
"An entStateOperEnabled Notification signifies that the
SNMP 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
variable bindings. The entStateAdmin and entStateAlarm
varbinds may be examined to find out additional
information on the administrative state at the time of
the operation state change as well to find out whether
there were any known alarms against the entity at that
time that may explain why the physical entity has become
operationally disabled."
::= { entStateNotifications 1 }
entStateOperDisabled NOTIFICATION-TYPE
OBJECTS { entStateAdmin,
entStateAlarm }
STATUS current
DESCRIPTION
"An entStateOperDisabled Notification signifies that the
SNMP 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.
Chisholm & Perkins Standards Track [Page 13]
Entity State MIB February 2004
The entity this notification refers can be identified by
extracting the entPhysicalIndex from one of the
variable bindings. The entStateAdmin and entStateAlarm
varbinds may be examined to find out additional
information on the administrative state at the time of
the operation state change as well to find out whether
there were any known alarms against the entity at that
time that may have affect on the physical entity's
ability to stay operationally enabled."
::= { entStateNotifications 2 }
-- Conformance and Compliance
entStateConformance OBJECT IDENTIFIER ::= { entityStateMIB 3 }
entStateCompliances OBJECT IDENTIFIER
::= { entStateConformance 1 }
entStateCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for systems supporting
the Entity State MIB."
MODULE -- this module
MANDATORY-GROUPS {
entStateGroup
}
GROUP entStateNotificationsGroup
DESCRIPTION
"This group is optional."
OBJECT entStateAdmin
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { entStateCompliances 1 }
entStateGroups OBJECT IDENTIFIER ::= { entStateConformance 2 }
entStateGroup OBJECT-GROUP
OBJECTS {
entStateLastChanged,
entStateAdmin,
entStateOper,
entStateUsage,
entStateAlarm,
entStateStandby
}
STATUS current
DESCRIPTION
"Standard Entity State group."
::= { entStateGroups 1}
Chisholm & Perkins Standards Track [Page 14]
Entity State MIB February 2004
entStateNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS {
entStateOperEnabled,
entStateOperDisabled
}
STATUS current
DESCRIPTION
"Standard Entity State Notification group."
::= { entStateGroups 2}
END
5. Security Considerations
There is one management object defined in this MIB that has a
MAX-ACCESS clause of read-write. The object may be considered
sensitive or vulnerable in some network environments. The support
for SET operations in a non-secure environment without proper
protection can have a negative effect on network operations.
The following object is defined with a MAX-ACCESS clause of
read-write: entStateAdmin.
SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec),
even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the
objects in this MIB module.
It is RECOMMENDED that implementers consider the security features
as provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to
the objects only to those principals (entities) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
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.
Chisholm & Perkins Standards Track [Page 15]
Entity State MIB February 2004
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
Nortel Networks
PO Box 3511, Station C
Ottawa, Ontario, K1Y 4H7
Canada
Email: schishol@nortelnetworks.com
David T. Perkins
548 Qualbrook Ct
San Jose, CA 95110
USA
Phone: 408 394-8702
Email: dperkins@snmpinfo.com
8. Acknowledgments
This document is a product of the Entity MIB Working Group.
9. References
9.1 Normative
[ALARM-MIB] Chisholm, S., Romascanu, D., "Alarm MIB",
draft-ietf-disman-alarm-mib-18.txt, February 2004
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Chisholm & Perkins Standards Track [Page 16]
Entity State MIB February 2004
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999.
[RFC2737] McCloghrie, K., Bierman, A., "Entity MIB (Version 2)",
December 1999.
[X.731] ITU Recommendation X.731, "Information Technology - Open
Systems Interconnection - System Management: State
Management Function", 1992
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,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002.
10. Full Copyright Statement
Copyright (C) The Internet Society (2004). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Chisholm & Perkins Standards Track [Page 17]
Entity State MIB February 2004
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be followed,
or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT
NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN
WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Chisholm & Perkins Standards Track [Page 18]
------_=_NextPart_001_01C3F48C.0D2D48FA
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2656.31">
<TITLE>draft-ietf-entmib-state-03.txt</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>Hi</FONT>
</P>
<P><FONT SIZE=3D2>Please post the following as an Internet =
Draft.</FONT>
</P>
<P><FONT SIZE=3D2>Thanks,</FONT>
</P>
<P><FONT SIZE=3D2>Sharon</FONT>
<BR><FONT SIZE=3D2>---------</FONT>
<BR><FONT SIZE=3D2>Entity MIB Working =
Group &=
nbsp; &=
nbsp; S. Chisholm</FONT>
<BR><FONT SIZE=3D2>Internet =
Draft &=
nbsp; &=
nbsp; =
Nortel Networks</FONT>
<BR><FONT SIZE=3D2>Document: =
draft-ietf-entmib-state-03.txt =
D. Perkins</FONT>
<BR><FONT SIZE=3D2>Category: Standards =
Track &=
nbsp; &=
nbsp; SNMPinfo</FONT>
<BR><FONT SIZE=3D2>Expiration Date: August =
2004 &n=
bsp; February =
2004</FONT>
</P>
<BR>
<P><FONT =
SIZE=3D2> &nb=
sp; &nb=
sp; Entity State MIB</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Status of this Memo</FONT>
</P>
<P><FONT SIZE=3D2> This document is an Internet-Draft and is in =
full conformance</FONT>
<BR><FONT SIZE=3D2> with all provisions of Section 10 of =
RFC2026.</FONT>
</P>
<P><FONT SIZE=3D2> Internet-Drafts are working documents of the =
Internet Engineering</FONT>
<BR><FONT SIZE=3D2> Task Force (IETF), its areas, and its working =
groups. Note that</FONT>
<BR><FONT SIZE=3D2> other groups may also distribute working =
documents as</FONT>
<BR><FONT SIZE=3D2> Internet-Drafts.</FONT>
</P>
<P><FONT SIZE=3D2> Internet-Drafts are draft documents valid for =
a maximum of six</FONT>
<BR><FONT SIZE=3D2> months and may be updated, replaced, or =
obsoleted by other</FONT>
<BR><FONT SIZE=3D2> documents at any time. It is =
inappropriate to use Internet-</FONT>
<BR><FONT SIZE=3D2> Drafts as reference material or to cite them =
other than as</FONT>
<BR><FONT SIZE=3D2> "work in progress."</FONT>
</P>
<BR>
<P><FONT SIZE=3D2> The list of current Internet-Drafts can be =
accessed at</FONT>
</P>
<P><FONT SIZE=3D2> <A =
HREF=3D"http://www.ietf.org/ietf/1id-abstracts.txt" =
TARGET=3D"_blank">http://www.ietf.org/ietf/1id-abstracts.txt</A></FONT>
</P>
<BR>
<P><FONT SIZE=3D2> The list of Internet-Draft Shadow Directories =
can be accessed at</FONT>
<BR><FONT SIZE=3D2> <A HREF=3D"http://www.ietf.org/shadow.html" =
TARGET=3D"_blank">http://www.ietf.org/shadow.html</A>.</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Abstract</FONT>
</P>
<P><FONT SIZE=3D2> This memo defines a portion of the Management =
Information Base (MIB)</FONT>
<BR><FONT SIZE=3D2> for use with network management protocols in =
the Internet community.</FONT>
<BR><FONT SIZE=3D2> In particular, it describes extensions to the =
Entity MIB to</FONT>
<BR><FONT SIZE=3D2> provide information about the state of =
physical entities.</FONT>
</P>
<P><FONT SIZE=3D2>Table of Contents</FONT>
</P>
<P><FONT SIZE=3D2> 1. The Internet-Standard Management =
Framework</FONT>
<BR><FONT SIZE=3D2> 2. Entity State</FONT>
<BR><FONT SIZE=3D2> 2.1. Hierarchical State =
Management</FONT>
<BR><FONT SIZE=3D2> 2.2. Entity Redundancy</FONT>
<BR><FONT SIZE=3D2> 3. Relationship to Other MIBs</FONT>
<BR><FONT SIZE=3D2> 3.1. Relation to Interfaces MIB</FONT>
<BR><FONT SIZE=3D2> 3.2. Relation to Alarm MIB</FONT>
<BR><FONT SIZE=3D2> 3.3. Relation to Bridge MIB</FONT>
<BR><FONT SIZE=3D2> 3.4. Relation to Host Resource =
MIB</FONT>
<BR><FONT SIZE=3D2> 4. Definitions</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Chisholm & =
Perkins Standards =
Track &=
nbsp; [Page 1]</FONT>
<BR><FONT =
SIZE=3D2>=0C =
=
Entity State =
MIB &nb=
sp; February 2004</FONT>
</P>
<BR>
<P><FONT SIZE=3D2> 5. Security Considerations</FONT>
<BR><FONT SIZE=3D2> 6. Intellectual Property</FONT>
<BR><FONT SIZE=3D2> 7. Authors' Addresses</FONT>
<BR><FONT SIZE=3D2> 8. Acknowledgements</FONT>
<BR><FONT SIZE=3D2> 9. References</FONT>
<BR><FONT SIZE=3D2>10. Full Copyright Statement</FONT>
</P>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<P><FONT SIZE=3D2>Chisholm & =
Perkins Standards =
Track &=
nbsp; [Page 2]</FONT>
<BR><FONT =
SIZE=3D2>=0C =
=
Entity State =
MIB &nb=
sp; February 2004</FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=3D2>1. The Internet-Standard Management Framework</FONT>
</P>
<P><FONT SIZE=3D2> For a detailed overview of the documents that =
describe the current</FONT>
<BR><FONT SIZE=3D2> Internet-Standard Management Framework, =
please refer to section 7 of</FONT>
<BR><FONT SIZE=3D2> RFC 3410 [RFC3410].</FONT>
</P>
<P><FONT SIZE=3D2> Managed objects are accessed via a virtual =
information store, termed</FONT>
<BR><FONT SIZE=3D2> the Management Information Base or MIB. =
MIB objects are generally</FONT>
<BR><FONT SIZE=3D2> accessed through the Simple Network =
Management Protocol (SNMP).</FONT>
<BR><FONT SIZE=3D2> Objects in the MIB are defined using the =
mechanisms defined in the</FONT>
<BR><FONT SIZE=3D2> Structure of Management Information =
(SMI). This memo specifies a MIB</FONT>
<BR><FONT SIZE=3D2> module that is compliant to the SMIv2, which =
is described in STD 58,</FONT>
<BR><FONT SIZE=3D2> RFC 2578 [RFC2578], STD 58, RFC 2579 =
[RFC2579] and STD 58, RFC 2580</FONT>
<BR><FONT SIZE=3D2> [RFC2580].</FONT>
</P>
<P><FONT SIZE=3D2>2. Entity State</FONT>
</P>
<P><FONT SIZE=3D2> The goal in adding state objects to the =
Entity MIB [RFC2737] is to</FONT>
<BR><FONT SIZE=3D2> define a useful subset of the possible =
state attributes that could</FONT>
<BR><FONT SIZE=3D2> be tracked for a given entity that both =
fit into the state models</FONT>
<BR><FONT SIZE=3D2> such as those used in the Interfaces =
MIB [RFC2863] as well as</FONT>
<BR><FONT SIZE=3D2> leverage existing well-deployed models. =
The entStateTable contains</FONT>
<BR><FONT SIZE=3D2> state objects that are a subset of the =
popular ISO/OSI states that</FONT>
<BR><FONT SIZE=3D2> are also defined in ITU's X.731 =
specification [X.731]. Objects are</FONT>
<BR><FONT SIZE=3D2> defined to capture administrative, =
operational and usage states. In</FONT>
<BR><FONT SIZE=3D2> addition there are further state =
objects defined to provide</FONT>
<BR><FONT SIZE=3D2> additional information for these three =
basic states.</FONT>
</P>
<P><FONT SIZE=3D2> Administrative state indicates =
permission to use or prohibition</FONT>
<BR><FONT SIZE=3D2> against using the entity and is imposed =
through the management</FONT>
<BR><FONT SIZE=3D2> services.</FONT>
</P>
<P><FONT SIZE=3D2> Operational state indicates whether or =
not the entity is physically</FONT>
<BR><FONT SIZE=3D2> installed and working. Note that unlike =
the ifOperStatus [RFC2863],</FONT>
<BR><FONT SIZE=3D2> this operational state is independent =
of the administrative state.</FONT>
</P>
<P><FONT SIZE=3D2> Usage state indicates whether or not the =
entity is in use at a</FONT>
<BR><FONT SIZE=3D2> specific instance, and if so, whether =
or not it currently has spare</FONT>
<BR><FONT SIZE=3D2> capacity to serve additional users. In =
the context of this MIB, the</FONT>
<BR><FONT SIZE=3D2> user is equivalent to an entity, so =
this term is substituted. This</FONT>
<BR><FONT SIZE=3D2> state refers to the ability of the =
entity to service other entities</FONT>
<BR><FONT SIZE=3D2> within its containment =
hierarchy.</FONT>
</P>
<P><FONT SIZE=3D2> Alarm state indicates whether or not =
there are any alarms active</FONT>
<BR><FONT SIZE=3D2> against the entity. In addition to =
those alarm status defined in</FONT>
<BR><FONT SIZE=3D2> X.731 [X.731], warning and =
indeterminate status are also defined to</FONT>
<BR><FONT SIZE=3D2> provide a more complete mapping to the =
Alarm MIB [Alarm-MIB].</FONT>
</P>
<P><FONT SIZE=3D2> Standby state indicates whether the =
entity is currently running as</FONT>
<BR><FONT SIZE=3D2> hot standby, cold standby or is =
currently providing service.</FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=3D2>Chisholm & =
Perkins Standards =
Track &=
nbsp; [Page 3]</FONT>
<BR><FONT =
SIZE=3D2>=0C =
=
Entity State =
MIB &nb=
sp; February 2004</FONT>
</P>
<BR>
<P><FONT SIZE=3D2> The terms state and status are used =
interchangeably in this memo.</FONT>
</P>
<P><FONT SIZE=3D2> The key words "MUST", =
"MUST NOT", "REQUIRED", "SHALL", =
"SHALL NOT",</FONT>
<BR><FONT SIZE=3D2> "SHOULD", "SHOULD =
NOT", "RECOMMENDED", "MAY", and =
"OPTIONAL" in this</FONT>
<BR><FONT SIZE=3D2> document are to be interpreted as =
described in RFC 2119 [RFC2119].</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>2.1 Hierarchical State Management</FONT>
</P>
<P><FONT SIZE=3D2> Physical entities exist within a =
containment hierarchy. Physical</FONT>
<BR><FONT SIZE=3D2> containment is defined by the =
entPhysicalContainedIn</FONT>
<BR><FONT SIZE=3D2> object[RFC2737]. This raises some =
interesting issues not addressed</FONT>
<BR><FONT SIZE=3D2> in existing work on state management =
[X.731].</FONT>
</P>
<P><FONT SIZE=3D2> There are two types of state for an =
entity:</FONT>
</P>
<P><FONT SIZE=3D2> 1) The state of the entity independent =
of the states of its parents</FONT>
<BR><FONT SIZE=3D2> and children in its containment hierarch=
y. This is often referred to</FONT>
<BR><FONT SIZE=3D2> as raw state.</FONT>
</P>
<P><FONT SIZE=3D2> 2) The state of the entity, as it may be =
influenced by the state of</FONT>
<BR><FONT SIZE=3D2> its parents and children. This is often =
referred to as computed</FONT>
<BR><FONT SIZE=3D2> state.</FONT>
</P>
<P><FONT SIZE=3D2> All state objects in this memo are raw =
state.</FONT>
</P>
<P><FONT SIZE=3D2>2.2 Entity Redundancy</FONT>
</P>
<P><FONT SIZE=3D2> While this memo is not attempting to =
address the entire problem</FONT>
<BR><FONT SIZE=3D2> space around redundancy, the =
entStateStandby object provides an</FONT>
<BR><FONT SIZE=3D2> important piece of state information =
for entities, which helps</FONT>
<BR><FONT SIZE=3D2> identify which pieces of redundant =
equipment are currently providing</FONT>
<BR><FONT SIZE=3D2> service, and which are waiting in =
either hot or cold standby mode.</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>3 Relation to other MIBs</FONT>
</P>
<P><FONT SIZE=3D2>3.1 Relationship to the Interfaces MIB</FONT>
</P>
<BR>
<P><FONT SIZE=3D2> The Interfaces MIB [RFC2863] defines the =
ifAdminStatus object, which</FONT>
<BR><FONT SIZE=3D2> has states of up, down and testing and =
the ifOperStatus object,</FONT>
<BR><FONT SIZE=3D2> which has states of up, down, testing, =
unknown, dormant, notPresent</FONT>
<BR><FONT SIZE=3D2> and lowerLayerDown.</FONT>
</P>
<P><FONT SIZE=3D2> An ifAdminStatus of 'up' is equivalent =
to setting the entStateAdmin</FONT>
<BR><FONT SIZE=3D2> object to 'unlocked'. An ifAdminStatus =
of 'down' is equivalent to</FONT>
<BR><FONT SIZE=3D2> setting the entStateAdmin object to =
either 'locked' or</FONT>
<BR><FONT SIZE=3D2> 'shuttingDown', depending on a systems =
interpretation of 'down'.</FONT>
</P>
<P><FONT SIZE=3D2> An ifOperStatus of 'up' is equivalent to =
an entStateOper value of</FONT>
<BR><FONT SIZE=3D2> 'enabled'. An ifOperStatus of 'down' =
due to operational failure is</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Chisholm & =
Perkins Standards =
Track &=
nbsp; [Page 4]</FONT>
<BR><FONT =
SIZE=3D2>=0C =
=
Entity State =
MIB &nb=
sp; February 2004</FONT>
</P>
<BR>
<P><FONT SIZE=3D2> equivalent to an entStateOper value of =
'disabled'. An ifOperStatus</FONT>
<BR><FONT SIZE=3D2> of 'down' due to being administratively =
disabled is equivalent to an</FONT>
<BR><FONT SIZE=3D2> entStateAdmin value of 'locked' and an =
entStateOper value of either</FONT>
<BR><FONT SIZE=3D2> 'enabled' or 'disabled' depending on =
whether there are any known</FONT>
<BR><FONT SIZE=3D2> issues that would prevent the entity =
from becoming operational when</FONT>
<BR><FONT SIZE=3D2> its entStateAdmin is set to =
'unlocked'. An ifOperStatus of</FONT>
<BR><FONT SIZE=3D2> 'unknown' is equivalent to an =
entStateOper value of 'unavailable'.</FONT>
<BR><FONT SIZE=3D2> The ifOperStatus values of 'testing' =
and 'dormant' are not</FONT>
<BR><FONT SIZE=3D2> explicitly supported by this MIB, but =
the state objects will be able</FONT>
<BR><FONT SIZE=3D2> to reflect other aspects of the =
entities administrative and</FONT>
<BR><FONT SIZE=3D2> operational state. The ifOperStatus =
values of 'notPresent' and</FONT>
<BR><FONT SIZE=3D2> 'lowerLayerDown' are in some ways =
computed states and so are</FONT>
<BR><FONT SIZE=3D2> therefore not supported in this MIB. =
They can though be computed by</FONT>
<BR><FONT SIZE=3D2> examining the states of entities within =
this objects containment</FONT>
<BR><FONT SIZE=3D2> hierarchy and other available related =
states.</FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=3D2>3.2 Relation to Alarm MIB</FONT>
</P>
<P><FONT SIZE=3D2> The entStateAlarm object indicates =
whether or not there are any</FONT>
<BR><FONT SIZE=3D2> active alarms against this entity. If =
there are active alarms, then</FONT>
<BR><FONT SIZE=3D2> the alarmActiveTable in the Alarm MIB =
[Alarm MIB] should be searched</FONT>
<BR><FONT SIZE=3D2> for alarmActiveResourceId that match =
this entPhysicalIndex.</FONT>
</P>
<P><FONT SIZE=3D2> Alternatively, if the alarmActiveTable =
is queried first and an</FONT>
<BR><FONT SIZE=3D2> active alarm with a value of =
alarmActiveResourceId that matches this</FONT>
<BR><FONT SIZE=3D2> entPhysicalIndex is found, then =
entStateAlarm can be used to quickly</FONT>
<BR><FONT SIZE=3D2> determine if there are additional =
active alarms against this</FONT>
<BR><FONT SIZE=3D2> physical entity.</FONT>
</P>
<P><FONT SIZE=3D2>3.3 Relation to Bridge MIB</FONT>
</P>
<P><FONT SIZE=3D2> For entities of physical type of 'port' =
that support the</FONT>
<BR><FONT SIZE=3D2> dot1dStpPortEnable object in the Bridge =
MIB [RFC1493], a value of</FONT>
<BR><FONT SIZE=3D2> 'enabled' is equivalent to setting the =
entStateAdmin object to</FONT>
<BR><FONT SIZE=3D2> 'unlocked'. Setting dot1dStpPortEnable =
to 'disabled' is equivalent</FONT>
<BR><FONT SIZE=3D2> to setting the entStateAdmin object to =
'locked'.</FONT>
</P>
<P><FONT SIZE=3D2>3.4 Relation to the Host Resources MIB</FONT>
</P>
<P><FONT SIZE=3D2> The hrDeviceStatus object in the Host =
Resources MIB [RFC2790]</FONT>
<BR><FONT SIZE=3D2> provides an operational state for =
devices. For entities that</FONT>
<BR><FONT SIZE=3D2> logically correspond to the concept of =
a device, a value of</FONT>
<BR><FONT SIZE=3D2> 'unknown' for hrDeviceStatus =
corresponds to an entStateOper value of</FONT>
<BR><FONT SIZE=3D2> 'unavailable'. A value of 'running' =
corresponds to an entStateOper</FONT>
<BR><FONT SIZE=3D2> value of 'enabled'. A value of =
'warning' also corresponds to an</FONT>
<BR><FONT SIZE=3D2> entStateOper value of 'enabled', but =
with appropriate bits set in</FONT>
<BR><FONT SIZE=3D2> the entStateAlarm object to indicate =
the alarms corresponding to the</FONT>
<BR><FONT SIZE=3D2> unusual error condition detected. A =
value of 'testing' or 'down' is</FONT>
<BR><FONT SIZE=3D2> equivalent to an entStateOper value of =
'disabled'.</FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=3D2>Chisholm & =
Perkins Standards =
Track &=
nbsp; [Page 5]</FONT>
<BR><FONT =
SIZE=3D2>=0C =
=
Entity State =
MIB &nb=
sp; February 2004</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>4. Definitions</FONT>
</P>
<P><FONT SIZE=3D2> ENTITY-STATE-MIB DEFINITIONS ::=3D =
BEGIN</FONT>
</P>
<P><FONT SIZE=3D2> IMPORTS</FONT>
<BR><FONT SIZE=3D2> =
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; FROM SNMPv2-SMI</FONT>
<BR><FONT SIZE=3D2> =
TEXTUAL-CONVENTION, DateAndTime</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; FROM SNMPv2-TC</FONT>
<BR><FONT SIZE=3D2> =
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; FROM SNMPv2-CONF</FONT>
<BR><FONT SIZE=3D2> =
entPhysicalIndex</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; FROM ENTITY-MIB;</FONT>
</P>
<P><FONT SIZE=3D2> entityStateMIB =
MODULE-IDENTITY</FONT>
<BR><FONT SIZE=3D2> =
LAST-UPDATED "200402150000Z"</FONT>
<BR><FONT SIZE=3D2> =
ORGANIZATION "IETF Entity MIB Working Group"</FONT>
<BR><FONT SIZE=3D2> =
CONTACT-INFO</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; " General Discussion: =
entmib@ietf.org</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; To Subscribe:</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; <A =
HREF=3D"http://www.ietf.org/mailman/listinfo/entmib" =
TARGET=3D"_blank">http://www.ietf.org/mailman/listinfo/entmib</A></FONT>=
</P>
<P><FONT =
SIZE=3D2> &nb=
sp; <A =
HREF=3D"http://www.ietf.org/html.charters/entmib-charter.html" =
TARGET=3D"_blank">http://www.ietf.org/html.charters/entmib-charter.html<=
/A></FONT>
</P>
<P><FONT =
SIZE=3D2> &nb=
sp; Sharon Chisholm</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; Nortel Networks</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; PO Box 3511 Station =
C</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; Ottawa, Ont. K1Y =
4H7</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; Canada</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; =
schishol@nortelnetworks.com</FONT>
</P>
<P><FONT =
SIZE=3D2> &nb=
sp; David T. Perkins</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; 548 Qualbrook Ct</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; San Jose, CA 95110</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; USA</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; Phone: 408 =
394-8702</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; =
dperkins@snmpinfo.com</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; "</FONT>
<BR><FONT SIZE=3D2> =
DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; "This MIB defines a state =
extension to the Entity MIB.</FONT>
</P>
<P><FONT SIZE=3D2> =
Copyright (C) The Internet Society =
2004. This version</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; of this MIB module is part of RFC =
yyyy; see the RFC</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; itself for full legal notices."</FONT>
<BR><FONT =
SIZE=3D2> =
-- RFC Ed.: replace yyyy with actual RFC number & remove</FONT>
<BR><FONT =
SIZE=3D2> =
-- this note</FONT>
<BR><FONT SIZE=3D2> =
REVISION "200402150000Z"</FONT>
<BR><FONT SIZE=3D2> =
DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; "Initial version, published as RFC YYYY."</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; -- RFC-Editor assigns yyyy</FONT>
<BR><FONT SIZE=3D2> =
::=3D { mib-2 XX } -- to be assigned by IANA</FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=3D2>Chisholm & =
Perkins Standards =
Track &=
nbsp; [Page 6]</FONT>
<BR><FONT =
SIZE=3D2>=0C =
=
Entity State =
MIB &nb=
sp; February 2004</FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=3D2> -- Textual conventions</FONT>
</P>
<BR>
<P><FONT SIZE=3D2> AdminState ::=3D =
TEXTUAL-CONVENTION</FONT>
<BR><FONT SIZE=3D2> =
STATUS current</FONT>
<BR><FONT SIZE=3D2> =
DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; " Represents the various possible administrative =
states.</FONT>
</P>
<P><FONT =
SIZE=3D2> &nb=
sp; A value of 'locked' means the resource is =
administratively</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; prohibited from use. A value of 'shuttingDown' means =
that</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; usage is administratively limited to current instances =
of</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; use. A value of 'unlocked' means the resource is =
not</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; administratively prohibited from use. A value of</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; 'unavailable' means that this resource is unable =
to</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; report administrative state."</FONT>
<BR><FONT SIZE=3D2> =
REFERENCE</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; "ITU Recommendation X.731, 'Information Technology - =
Open</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; Systems Interconnection - System =
Management: State</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; Management Function', =
1992"</FONT>
<BR><FONT SIZE=3D2> =
SYNTAX INTEGER</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; {</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; unavailable(1),</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; locked(2),</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; shuttingDown(3),</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; unlocked(4)</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; }</FONT>
</P>
<P><FONT SIZE=3D2> OperState ::=3D =
TEXTUAL-CONVENTION</FONT>
<BR><FONT SIZE=3D2> =
STATUS current</FONT>
<BR><FONT SIZE=3D2> =
DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; " Represents the possible values of operational states.</FONT>
</P>
<P><FONT =
SIZE=3D2> &nb=
sp; A value of 'disabled' means the resource is =
totally</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; inoperable. A value of 'enabled' means the =
resource</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; is partially or fully operable. A value of =
'testing'</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; means the resource is currently being tested</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; and cannot there fore report whether it is =
operational</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; or not. A value of 'unavailable' means that this</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; resource is unable to report operational state. =
"</FONT>
<BR><FONT SIZE=3D2> =
REFERENCE</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; "ITU Recommendation X.731, 'Information Technology - =
Open</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; Systems Interconnection - System =
Management: State</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; Management Function', =
1992"</FONT>
<BR><FONT SIZE=3D2> =
SYNTAX INTEGER</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; {</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; unavailable (1),</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; disabled(2),</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; enabled(3),</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; testing (4)</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; }</FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=3D2>Chisholm & Perkins &n=
bsp; Standards =
Track &=
nbsp; [Page 7]</FONT>
<BR><FONT =
SIZE=3D2>=0C =
=
Entity State =
MIB &nb=
sp; February 2004</FONT>
</P>
<BR>
<P><FONT SIZE=3D2> UsageState ::=3D =
TEXTUAL-CONVENTION</FONT>
<BR><FONT SIZE=3D2> =
STATUS current</FONT>
<BR><FONT SIZE=3D2> =
DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; " Represents the possible values of usage states.</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; A value of 'idle' means the resource is servicing =
no</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; users. A value of 'active' means the resource is</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; currently in use and it has sufficient spare =
capacity</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; to provide for additional users. A value of =
'busy'</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; means the resource is currently in use, but it</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; currently has no spare capacity to provide for</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; additional users. A value of 'unavailable' means</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; that this resource is unable to report usage =
state."</FONT>
<BR><FONT SIZE=3D2> =
REFERENCE</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; "ITU Recommendation X.731, 'Information Technology - =
Open</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; Systems Interconnection - System =
Management: State</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; Management Function', =
1992"</FONT>
<BR><FONT SIZE=3D2> =
SYNTAX INTEGER</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; {</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; unavailable (1),</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; idle(2),</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; active(3),</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; busy(4)</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; }</FONT>
</P>
<BR>
<P><FONT SIZE=3D2> AlarmStatus ::=3D =
TEXTUAL-CONVENTION</FONT>
<BR><FONT SIZE=3D2> =
STATUS current</FONT>
<BR><FONT SIZE=3D2> =
DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; "Represents the possible values of alarm status.</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; An Alarm [ALARM-MIB] is a persistent indication</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; of an error or warning condition.</FONT>
</P>
<P><FONT =
SIZE=3D2> &nb=
sp; When no bits of this attribute are set, then none</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; of the value of under repair is set, the resource is</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; currently being repaired, which depending on the</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; implementation, may make the other values in this bit</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; string unreliable.</FONT>
</P>
<P><FONT =
SIZE=3D2> &nb=
sp; When the value of 'critical' is set, one or more critical</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; alarms are active against the resource. When the value</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; of 'major' is set, one or more major alarms are active</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; against the resource. When the value of 'minor' is set,</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; one or more minor alarms are active against the resource.</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; When the value of 'warning' is set, one or more warning</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; alarms are active against the resource. When the value</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; of 'indeterminate' is set, one or more alarms whose of</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; perceived severity cannot be determined are active</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; against this resource.</FONT>
</P>
<P><FONT =
SIZE=3D2> &nb=
sp; When the value of 'alarmOutstanding' is set, one or more</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; alarms is active against the resource. The fault may</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; or may not be disabling. This bit provides a high-level</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Chisholm & =
Perkins Standards =
Track &=
nbsp; [Page 8]</FONT>
<BR><FONT =
SIZE=3D2>=0C =
=
Entity State =
MIB &nb=
sp; February 2004</FONT>
</P>
<BR>
<P><FONT =
SIZE=3D2> &nb=
sp; summary that can be used to determine whether or not</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; to examine the rest of the values. A value of</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; 'unavailable' means that this resource is unable to</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; report alarm state."</FONT>
<BR><FONT SIZE=3D2> =
REFERENCE</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; "ITU Recommendation X.731, 'Information Technology - =
Open</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; Systems Interconnection - System =
Management: State</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; Management Function', =
1992"</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; SYNTAX =
BITS</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; {</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; unavailable (0),</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; underRepair(1),</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; critical(2),</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; major(3),</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; minor(4),</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; alarmOutstanding(5),</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; -- The following are not defined in =
X.733</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; warning (6),</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; indeterminate (7)</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; &nb=
sp; }</FONT>
</P>
<BR>
<P><FONT SIZE=3D2> StandbyStatus =
::=3D TEXTUAL-CONVENTION</FONT>
<BR><FONT SIZE=3D2> =
STATUS current</FONT>
<BR><FONT SIZE=3D2> =
DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; " Represents the possible values of standby status.</FONT>
</P>
<P><FONT =
SIZE=3D2> &nb=
sp; A value of 'hotStandby' means the resource is =
not</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; providing service, but it will be immediately able =
to</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; take over the role of the resource to be =
backed-up,</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; without the need for initialization activity, and =
will</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; contain the same information as the resource to =
be</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; backed up. A value of 'coldStandy' means that =
the</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; resource is to back-up another resource, but will =
not</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; be immediately able to take over the role of a =
resource</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; to be backed up, and will require some =
initialization</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; activity. A value of 'providingService' means =
the</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; resource is providing service. A value of</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; 'unavailable' means that this resource is unable =
to</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; report standby state."</FONT>
<BR><FONT SIZE=3D2> =
REFERENCE</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; "ITU Recommendation X.731, 'Information Technology - =
Open</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; Systems Interconnection - System =
Management: State</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; Management Function', =
1992"</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; SYNTAX =
INTEGER</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; {</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; unavailable (1),</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; hotStandby(2),</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; coldStandby(3),</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; providingService(4)</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; }</FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=3D2>Chisholm & =
Perkins Standards =
Track &=
nbsp; [Page 9]</FONT>
<BR><FONT =
SIZE=3D2>=0C =
=
Entity State =
MIB &nb=
sp; February 2004</FONT>
</P>
<BR>
<P><FONT SIZE=3D2> -- Entity State =
Objects</FONT>
</P>
<P><FONT SIZE=3D2> entStateObjects OBJECT =
IDENTIFIER ::=3D { entityStateMIB 1 }</FONT>
</P>
<P><FONT SIZE=3D2> entStateTable =
OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2> =
SYNTAX SEQUENCE OF EntStateEntry</FONT>
<BR><FONT SIZE=3D2> MAX-ACCESS =
not-accessible</FONT>
<BR><FONT SIZE=3D2> =
STATUS current</FONT>
<BR><FONT SIZE=3D2> DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2> "A =
table of information about state/status of entities.</FONT>
<BR><FONT =
SIZE=3D2> =
This is a sparse augment of the entPhysicalTable. Entries</FONT>
<BR><FONT =
SIZE=3D2> =
appear in this table for values of</FONT>
<BR><FONT =
SIZE=3D2> =
entPhysicalClass [RFC2737] that in this implementation</FONT>
<BR><FONT =
SIZE=3D2> =
are able to report any of the state or status stored in</FONT>
<BR><FONT =
SIZE=3D2> =
this table.</FONT>
<BR><FONT =
SIZE=3D2> =
"</FONT>
<BR><FONT SIZE=3D2> ::=3D { =
entStateObjects 1 }</FONT>
</P>
<BR>
<P><FONT SIZE=3D2> entStateEntry =
OBJECT-TYPE</FONT>
<BR><FONT =
SIZE=3D2> =
SYNTAX EntStateEntry</FONT>
<BR><FONT =
SIZE=3D2> =
MAX-ACCESS not-accessible</FONT>
<BR><FONT =
SIZE=3D2> =
STATUS current</FONT>
<BR><FONT =
SIZE=3D2> =
DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; "State information about this physical =
entity."</FONT>
<BR><FONT =
SIZE=3D2> =
INDEX { entPhysicalIndex }</FONT>
<BR><FONT =
SIZE=3D2> ::=3D { =
entStateTable 1 }</FONT>
</P>
<P><FONT SIZE=3D2> EntStateEntry =
::=3D SEQUENCE {</FONT>
<BR><FONT =
SIZE=3D2> =
entStateLastChanged DateAndTime,</FONT>
<BR><FONT =
SIZE=3D2> =
entStateAdmin AdminState,</FONT>
<BR><FONT =
SIZE=3D2> =
entStateOper =
OperState,</FONT>
<BR><FONT =
SIZE=3D2> =
entStateUsage UsageState,</FONT>
<BR><FONT =
SIZE=3D2> =
entStateAlarm AlarmStatus,</FONT>
<BR><FONT =
SIZE=3D2> =
entStateStandby StandbyStatus</FONT>
<BR><FONT =
SIZE=3D2> =
}</FONT>
</P>
<P><FONT SIZE=3D2> entStateLastChanged =
OBJECT-TYPE</FONT>
<BR><FONT SIZE=3D2> =
SYNTAX DateAndTime</FONT>
<BR><FONT SIZE=3D2> MAX-ACCESS =
read-only</FONT>
<BR><FONT SIZE=3D2> =
STATUS current</FONT>
<BR><FONT SIZE=3D2> DESCRIPTION</FONT>
<BR><FONT SIZE=3D2> "The =
value of this object is the date and</FONT>
<BR><FONT SIZE=3D2> =
time when the value of any of entStateAdmin,</FONT>
<BR><FONT SIZE=3D2> =
entStateOper, entStateUsage, entStateAlarm,</FONT>
<BR><FONT SIZE=3D2> or =
entStateStandby changed for this entity.</FONT>
</P>
<P><FONT SIZE=3D2> If there =
has been no change since</FONT>
<BR><FONT SIZE=3D2> the last =
re-initialization of the local system,</FONT>
<BR><FONT SIZE=3D2> this =
object contains the date and time of</FONT>
<BR><FONT SIZE=3D2> local =
system initialization. If there has been</FONT>
<BR><FONT SIZE=3D2> no change =
since the entity was added to the</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Chisholm & =
Perkins Standards =
Track &=
nbsp; [Page 10]</FONT>
<BR><FONT SIZE=3D2>=0C &n=
bsp; &n=
bsp; Entity State =
MIB &nb=
sp; February 2004</FONT>
</P>
<BR>
<P><FONT SIZE=3D2> local =
system, this object contains the date and</FONT>
<BR><FONT SIZE=3D2> time of =
the insertion"</FONT>
<BR><FONT SIZE=3D2> ::=3D { entStateEntry =
1 }</FONT>
</P>
<P><FONT SIZE=3D2> entStateAdmin OBJECT-TYPE</FONT>
<BR><FONT =
SIZE=3D2> =
SYNTAX AdminState</FONT>
<BR><FONT =
SIZE=3D2> =
MAX-ACCESS read-write</FONT>
<BR><FONT =
SIZE=3D2> =
STATUS current</FONT>
<BR><FONT =
SIZE=3D2> =
DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; "The administrative state for this =
entity.</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; Setting this object to 'notSupported' will =
result</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; in an 'inconsistentValue' error. For =
entities that</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; do not support administrative state, all =
set</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; operations will result in an =
'inconsistentValue'</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; error</FONT>
</P>
<P><FONT =
SIZE=3D2> &nb=
sp; Some physical entities exhibit only a =
subset of the</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; remaining administrative state values. Some =
entities</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; cannot be locked, and hence this object =
exhibits only</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; the 'unlocked' state. Other entities can =
not be shutdown</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; gracefully, and hence this object does not =
exhibit the</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; 'shuttingDown' state. A value of =
'inconsistentValue'</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; will be returned if attempts are made to =
set this</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; object to values not supported by its =
administrative</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; model."</FONT>
<BR><FONT =
SIZE=3D2> ::=3D { =
entStateEntry 2 }</FONT>
</P>
<P><FONT SIZE=3D2> entStateOper OBJECT-TYPE</FONT>
<BR><FONT =
SIZE=3D2> =
SYNTAX OperState</FONT>
<BR><FONT =
SIZE=3D2> =
MAX-ACCESS read-only</FONT>
<BR><FONT =
SIZE=3D2> =
STATUS current</FONT>
<BR><FONT =
SIZE=3D2> =
DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; "The operational state for this entity.</FONT>
</P>
<P><FONT =
SIZE=3D2> &nb=
sp; Note that unlike the state model used within =
the</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; Interfaces MIB [RFC2863], this object does not =
follow</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; the administrative state. An administrative state =
of</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; down does not predict an operational state</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; of disabled.</FONT>
</P>
<P><FONT =
SIZE=3D2> &nb=
sp; A value of 'disabled' means that an entity is =
totally</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; inoperable and unable to provide service both to =
entities</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; within its containment hierarchy, or to other =
receivers</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; of its service as defined in ways outside the =
scope of</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; this MIB.</FONT>
</P>
<P><FONT =
SIZE=3D2> &nb=
sp; A value of 'enabled' means that an entity is =
fully or</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; partially operable and able to provide service =
both to</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; entities within its containment hierarchy, or to =
other</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; receivers of its service as defined in ways =
outside the</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; scope of this MIB.</FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=3D2>Chisholm & =
Perkins Standards =
Track &=
nbsp; [Page 11]</FONT>
<BR><FONT =
SIZE=3D2>=0C =
=
Entity State =
MIB &nb=
sp; February 2004</FONT>
</P>
<BR>
<P><FONT =
SIZE=3D2> &nb=
sp; Note that some implementations may not be able =
to</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; accurately report entStateOper while the</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; entStateAdmin object has a value other than =
'unlocked'.</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; In these cases, this object MUST have a =
value</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; of 'unavailable'."</FONT>
<BR><FONT =
SIZE=3D2> ::=3D { =
entStateEntry 3 }</FONT>
</P>
<P><FONT SIZE=3D2> entStateUsage OBJECT-TYPE</FONT>
<BR><FONT =
SIZE=3D2> =
SYNTAX UsageState</FONT>
<BR><FONT =
SIZE=3D2> =
MAX-ACCESS read-only</FONT>
<BR><FONT =
SIZE=3D2> =
STATUS current</FONT>
<BR><FONT =
SIZE=3D2> =
DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; "The usage state for this entity.</FONT>
</P>
<P><FONT =
SIZE=3D2> &nb=
sp; Note that in the context of a physical entity, =
this</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; object refers to an entity's ability to service =
more</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; physical entities in a containment hierarchy. A =
value</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; of 'idle' means this entity is able to contain =
other</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; entities but that no other entity is =
currently</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; contained within this entity.</FONT>
</P>
<P><FONT =
SIZE=3D2> &nb=
sp; A value of 'active' means that at least one =
entity is</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; contained within this entity, but that it could =
handle</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; more. A value of 'busy' means that the entity is =
unable</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; to handle any additional entities being contained =
in it.</FONT>
</P>
<P><FONT =
SIZE=3D2> &nb=
sp; Some entities will exhibit only a subset of =
the</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; usage state values. Entities that are unable to =
ever</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; service any entities within a containment =
hierarchy will</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; always have a usage state of 'busy'. Some =
entities will</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; only ever be able to support one entity within =
its</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; containment hierarchy and will therefore only =
exhibit</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; values of 'idle' and 'busy'."</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; ::=3D { entStateEntry 4 }</FONT>
</P>
<P><FONT SIZE=3D2> entStateAlarm OBJECT-TYPE</FONT>
<BR><FONT =
SIZE=3D2> =
SYNTAX AlarmStatus</FONT>
<BR><FONT =
SIZE=3D2> =
MAX-ACCESS read-only</FONT>
<BR><FONT =
SIZE=3D2> =
STATUS current</FONT>
<BR><FONT SIZE=3D2>  =
; DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; "The alarm status for this entity. It does =
not include</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; the alarms raised on child components within =
its</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; containment hierarchy.</FONT>
</P>
<P><FONT =
SIZE=3D2> &nb=
sp; Note that this differs from 'indeterminate' =
which</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; means that that alarm state is supported and =
there</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; are alarms against this entity, but the severity =
of</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; some of the alarms is not known.</FONT>
</P>
<P><FONT =
SIZE=3D2> &nb=
sp; If no bits are set, then this entity supports =
reporting</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; of alarms, but there are currently no active =
alarms</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; against this entity.</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Chisholm & =
Perkins Standards =
Track &=
nbsp; [Page 12]</FONT>
<BR><FONT =
SIZE=3D2>=0C =
=
Entity State =
MIB &nb=
sp; February 2004</FONT>
</P>
<BR>
<P><FONT =
SIZE=3D2> &nb=
sp; "</FONT>
<BR><FONT =
SIZE=3D2> ::=3D { =
entStateEntry 5 }</FONT>
</P>
<P><FONT SIZE=3D2> entStateStandby OBJECT-TYPE</FONT>
<BR><FONT =
SIZE=3D2> SYNTAX =
StandbyStatus</FONT>
<BR><FONT =
SIZE=3D2> =
MAX-ACCESS read-only</FONT>
<BR><FONT =
SIZE=3D2> STATUS =
current</FONT>
<BR><FONT =
SIZE=3D2> =
DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; "The standby status for this entity.</FONT>
</P>
<P><FONT =
SIZE=3D2> &nb=
sp; Some entities will exhibit only a subset of =
the</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; remaining standby state values. If this =
entity</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; cannot operate in a standby role, the value of =
this</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; object will always be =
'providingService'."</FONT>
<BR><FONT SIZE=3D2> ::=3D { entStateEntry 6 =
}</FONT>
</P>
<P><FONT SIZE=3D2> -- Notifications</FONT>
<BR><FONT SIZE=3D2> entStateNotifications OBJECT =
IDENTIFIER ::=3D { entityStateMIB 0 }</FONT>
</P>
<P><FONT SIZE=3D2> entStateOperEnabled =
NOTIFICATION-TYPE</FONT>
<BR><FONT SIZE=3D2> OBJECTS { =
entStateAdmin,</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; entStateAlarm</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; }</FONT>
<BR><FONT SIZE=3D2> =
STATUS =
current</FONT>
<BR><FONT SIZE=3D2> DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; "An entStateOperEnabled Notification signifies =
that the</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; SNMP entity, acting in an agent role, has =
detected that</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; the entStateOper object for one of its entities =
has left</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; the 'disabled' state and transitioned into the =
'enabled'</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; state.</FONT>
</P>
<P><FONT =
SIZE=3D2> &nb=
sp; The entity this notification refers can be =
identified by</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; extracting the entPhysicalIndex from one of =
the</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; variable bindings. The entStateAdmin and =
entStateAlarm</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; varbinds may be examined to find out =
additional</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; information on the administrative state at the =
time of</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; the operation state change as well to find out =
whether</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; there were any known alarms against the entity at =
that</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; time that may explain why the physical entity has =
become</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; operationally disabled."</FONT>
<BR><FONT SIZE=3D2> ::=3D { =
entStateNotifications 1 }</FONT>
</P>
<P><FONT SIZE=3D2> entStateOperDisabled =
NOTIFICATION-TYPE</FONT>
<BR><FONT SIZE=3D2> OBJECTS { =
entStateAdmin,</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; entStateAlarm }</FONT>
<BR><FONT SIZE=3D2> =
STATUS =
current</FONT>
<BR><FONT SIZE=3D2> DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; "An entStateOperDisabled Notification signifies =
that the</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; SNMP entity, acting in an agent role, has =
detected that</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; the entStateOper object for one of its entities =
has left</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; the 'enabled' state and transitioned into =
the</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; 'disabled' state.</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Chisholm & =
Perkins Standards =
Track &=
nbsp; [Page 13]</FONT>
<BR><FONT =
SIZE=3D2>=0C =
=
Entity State =
MIB &nb=
sp; February 2004</FONT>
</P>
<BR>
<BR>
<P><FONT =
SIZE=3D2> &nb=
sp; The entity this notification refers can be =
identified by</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; extracting the entPhysicalIndex from one of =
the</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; variable bindings. The entStateAdmin and =
entStateAlarm</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; varbinds may be examined to find out =
additional</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; information on the administrative state at the =
time of</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; the operation state change as well to find out =
whether</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; there were any known alarms against the entity at =
that</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; time that may have affect on the physical =
entity's</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; ability to stay operationally =
enabled."</FONT>
<BR><FONT SIZE=3D2> ::=3D { =
entStateNotifications 2 }</FONT>
</P>
<P><FONT SIZE=3D2> -- Conformance and Compliance</FONT>
</P>
<P><FONT SIZE=3D2> entStateConformance OBJECT IDENTIFIER =
::=3D { entityStateMIB 3 }</FONT>
</P>
<P><FONT SIZE=3D2> entStateCompliances OBJECT =
IDENTIFIER</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; ::=3D { =
entStateConformance 1 }</FONT>
</P>
<P><FONT SIZE=3D2> entStateCompliance =
MODULE-COMPLIANCE</FONT>
<BR><FONT SIZE=3D2> =
STATUS current</FONT>
<BR><FONT SIZE=3D2> =
DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; "The compliance statement for systems supporting</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; the Entity State MIB."</FONT>
<BR><FONT SIZE=3D2> =
MODULE -- this module</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; MANDATORY-GROUPS {</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; entStateGroup</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; }</FONT>
<BR><FONT SIZE=3D2> =
GROUP =
entStateNotificationsGroup</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; "This group is optional."</FONT>
<BR><FONT SIZE=3D2> =
OBJECT entStateAdmin</FONT>
<BR><FONT =
SIZE=3D2> =
MIN-ACCESS read-only</FONT>
<BR><FONT =
SIZE=3D2> =
DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; "Write access is not required."</FONT>
<BR><FONT SIZE=3D2> ::=3D { =
entStateCompliances 1 }</FONT>
</P>
<P><FONT SIZE=3D2> entStateGroups OBJECT IDENTIFIER ::=3D { =
entStateConformance 2 }</FONT>
</P>
<P><FONT SIZE=3D2> entStateGroup OBJECT-GROUP</FONT>
<BR><FONT SIZE=3D2> OBJECTS {</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; entStateLastChanged,</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; entStateAdmin,</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; entStateOper,</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; entStateUsage,</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; entStateAlarm,</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; entStateStandby</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; }</FONT>
<BR><FONT SIZE=3D2> =
STATUS current</FONT>
<BR><FONT SIZE=3D2> =
DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; "Standard Entity State group."</FONT>
<BR><FONT SIZE=3D2> ::=3D { =
entStateGroups 1}</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Chisholm & =
Perkins Standards =
Track &=
nbsp; [Page 14]</FONT>
<BR><FONT =
SIZE=3D2>=0C =
=
Entity State =
MIB &nb=
sp; February 2004</FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=3D2> entStateNotificationsGroup =
NOTIFICATION-GROUP</FONT>
<BR><FONT SIZE=3D2> NOTIFICATIONS =
{</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; entStateOperEnabled,</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; entStateOperDisabled</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; }</FONT>
<BR><FONT SIZE=3D2> =
STATUS current</FONT>
<BR><FONT SIZE=3D2> =
DESCRIPTION</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; "Standard Entity State Notification group."</FONT>
<BR><FONT SIZE=3D2> ::=3D { =
entStateGroups 2}</FONT>
</P>
<P><FONT SIZE=3D2> END</FONT>
</P>
<P><FONT SIZE=3D2>5. Security Considerations</FONT>
</P>
<P><FONT SIZE=3D2> There is one management object defined =
in this MIB that has a</FONT>
<BR><FONT SIZE=3D2> MAX-ACCESS clause of read-write. The =
object may be considered</FONT>
<BR><FONT SIZE=3D2> sensitive or vulnerable in some network =
environments. The support</FONT>
<BR><FONT SIZE=3D2> for SET operations in a non-secure =
environment without proper</FONT>
<BR><FONT SIZE=3D2> protection can have a negative effect =
on network operations.</FONT>
</P>
<P><FONT SIZE=3D2> The following object is defined with a =
MAX-ACCESS clause of</FONT>
<BR><FONT SIZE=3D2> read-write: entStateAdmin.</FONT>
</P>
<P><FONT SIZE=3D2> SNMP versions prior to SNMPv3 did not =
include adequate security.</FONT>
<BR><FONT SIZE=3D2> Even if the network itself is secure =
(for example by using IPSec),</FONT>
<BR><FONT SIZE=3D2> even then, there is no control as to =
who on the secure network is</FONT>
<BR><FONT SIZE=3D2> allowed to access and GET/SET =
(read/change/create/delete) the</FONT>
<BR><FONT SIZE=3D2> objects in this MIB module.</FONT>
</P>
<P><FONT SIZE=3D2> It is RECOMMENDED that implementers =
consider the security features</FONT>
<BR><FONT SIZE=3D2> as provided by the SNMPv3 framework =
(see [RFC3410], section 8),</FONT>
<BR><FONT SIZE=3D2> including full support for the SNMPv3 =
cryptographic mechanisms (for</FONT>
<BR><FONT SIZE=3D2> authentication and privacy).</FONT>
</P>
<P><FONT SIZE=3D2> Further, deployment of SNMP versions =
prior to SNMPv3 is NOT</FONT>
<BR><FONT SIZE=3D2> RECOMMENDED. Instead, it is =
RECOMMENDED to deploy SNMPv3 and to</FONT>
<BR><FONT SIZE=3D2> enable cryptographic security. It =
is then a customer/operator</FONT>
<BR><FONT SIZE=3D2> responsibility to ensure that the SNMP =
entity giving access to an</FONT>
<BR><FONT SIZE=3D2> instance of this MIB module is properly =
configured to give access to</FONT>
<BR><FONT SIZE=3D2> the objects only to those principals =
(entities) that have legitimate</FONT>
<BR><FONT SIZE=3D2> rights to indeed GET or SET =
(change/create/delete) them.</FONT>
</P>
<P><FONT SIZE=3D2> Note that setting the entStateAdmin to =
'locked' or 'shuttingDown'</FONT>
<BR><FONT SIZE=3D2> can cause disruption of services =
ranging from those running on a</FONT>
<BR><FONT SIZE=3D2> port to those on an entire device, =
depending on the type of entity.</FONT>
<BR><FONT SIZE=3D2> Access to this object should be =
properly protected.</FONT>
</P>
<P><FONT SIZE=3D2> Access to the objects defined in this =
MIB allows one to figure out</FONT>
<BR><FONT SIZE=3D2> what the active and standby resources =
in a network are. This</FONT>
<BR><FONT SIZE=3D2> information can be used to optimize =
attacks on networks so even</FONT>
<BR><FONT SIZE=3D2> read-only access to this MIB should be =
properly protected.</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Chisholm & =
Perkins Standards =
Track &=
nbsp; [Page 15]</FONT>
<BR><FONT =
SIZE=3D2>=0C =
=
Entity State =
MIB &nb=
sp; February 2004</FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=3D2>6. Intellectual Property</FONT>
</P>
<P><FONT SIZE=3D2> The IETF takes no position regarding the =
validity or scope of any</FONT>
<BR><FONT SIZE=3D2> intellectual property or other rights =
that might be claimed to </FONT>
<BR><FONT SIZE=3D2> pertain to the implementation or use of =
the technology described in</FONT>
<BR><FONT SIZE=3D2> this document or the extent to which =
any license under such rights</FONT>
<BR><FONT SIZE=3D2> might or might not be available; =
neither does it represent that it</FONT>
<BR><FONT SIZE=3D2> has made any effort to identify any =
such rights. Information on the</FONT>
<BR><FONT SIZE=3D2> IETF's procedures with respect to =
rights in standards-track and</FONT>
<BR><FONT SIZE=3D2> standards-related documentation can be =
found in BCP-11. Copies of</FONT>
<BR><FONT SIZE=3D2> claims of rights made available for =
publication and any assurances</FONT>
<BR><FONT SIZE=3D2> of licenses to be made available, or =
the result of an attempt made</FONT>
<BR><FONT SIZE=3D2> to obtain a general license or =
permission for the use of such</FONT>
<BR><FONT SIZE=3D2> proprietary rights by implementors or =
users of this specification</FONT>
<BR><FONT SIZE=3D2> can be obtained from the IETF =
Secretariat.</FONT>
</P>
<P><FONT SIZE=3D2> The IETF invites any interested party to =
bring to its attention any</FONT>
<BR><FONT SIZE=3D2> copyrights, patents or patent =
applications, or other proprietary</FONT>
<BR><FONT SIZE=3D2> rights which may cover technology that =
may be required to practice</FONT>
<BR><FONT SIZE=3D2> this standard. Please address the =
information to the IETF Executive</FONT>
<BR><FONT SIZE=3D2> Director.</FONT>
</P>
<P><FONT SIZE=3D2>7. Authors' Addresses</FONT>
</P>
<P><FONT SIZE=3D2> Sharon Chisholm</FONT>
<BR><FONT SIZE=3D2> Nortel Networks</FONT>
<BR><FONT SIZE=3D2> PO Box 3511, Station C</FONT>
<BR><FONT SIZE=3D2> Ottawa, Ontario, K1Y 4H7</FONT>
<BR><FONT SIZE=3D2> Canada</FONT>
<BR><FONT SIZE=3D2> Email: schishol@nortelnetworks.com</FONT>
</P>
<P><FONT SIZE=3D2> David T. Perkins</FONT>
<BR><FONT SIZE=3D2> 548 Qualbrook Ct</FONT>
<BR><FONT SIZE=3D2> San Jose, CA 95110</FONT>
<BR><FONT SIZE=3D2> USA</FONT>
<BR><FONT SIZE=3D2> Phone: 408 394-8702</FONT>
<BR><FONT SIZE=3D2> Email: dperkins@snmpinfo.com</FONT>
</P>
<P><FONT SIZE=3D2>8. Acknowledgments</FONT>
</P>
<P><FONT SIZE=3D2>This document is a product of the Entity MIB Working =
Group.</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>9. References</FONT>
</P>
<P><FONT SIZE=3D2>9.1 Normative</FONT>
</P>
<P><FONT SIZE=3D2> [ALARM-MIB] Chisholm, S., Romascanu, D., =
"Alarm MIB",</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; draft-ietf-disman-alarm-mib-18.txt, February =
2004</FONT>
</P>
<P><FONT SIZE=3D2> [RFC2119] Bradner, S., "Key =
words for use in RFCs to Indicate</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Chisholm & =
Perkins Standards =
Track &=
nbsp; [Page 16]</FONT>
<BR><FONT =
SIZE=3D2>=0C =
=
Entity State =
MIB &nb=
sp; February 2004</FONT>
</P>
<BR>
<P><FONT =
SIZE=3D2> &nb=
sp; Requirement Levels", BCP 14, RFC 2119, March =
1997.</FONT>
</P>
<BR>
<P><FONT SIZE=3D2> [RFC2578] McCloghrie, K., Perkins, D., =
Schoenwaelder, J., Case, J.,</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; Rose, M. and S. Waldbusser, "Structure of Management</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; Information Version 2 (SMIv2)", STD 58, RFC 2578, April</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; 1999.</FONT>
</P>
<P><FONT SIZE=3D2> [RFC2579] McCloghrie, K., Perkins, D., =
Schoenwaelder, J., Case, J.,</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; Rose, M. and S. Waldbusser, "Textual Conventions for</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; SMIv2", STD 58, RFC 2579, April 1999.</FONT>
</P>
<P><FONT SIZE=3D2> [RFC2580] McCloghrie, K., Perkins, D., =
Schoenwaelder, J., Case, J.,</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; Rose, M. and S. Waldbusser, "Conformance Statements for</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; SMIv2", STD 58, RFC 2580, April 1999.</FONT>
</P>
<P><FONT SIZE=3D2> [RFC2737] McCloghrie, K., Bierman, A., =
"Entity MIB (Version 2)",</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; December 1999.</FONT>
</P>
<P><FONT SIZE=3D2> [X.731] ITU Recommendation X.731, =
"Information Technology - Open</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; Systems Interconnection - System Management: State</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; Management Function", 1992</FONT>
</P>
<P><FONT SIZE=3D2>8.2 Informative References</FONT>
</P>
<P><FONT SIZE=3D2> [RFC1493] Decker, E., Langille, P., =
Rijsinghani, A., McCloghrie, K.,</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; "Definitions of Managed Objects for Bridges", RFC =
1493,</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; July 1993</FONT>
</P>
<P><FONT SIZE=3D2> [RFC2790] Waldbusser, S., Grillo, P., =
"Host Resources MIB",</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; RFC 2790, March 2000</FONT>
</P>
<P><FONT SIZE=3D2> [RFC2863] McCloghrie, K., Kastenholz, =
F., "The Interfaces Group</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; MIB using SMIv2", RFC2863, June 2000</FONT>
</P>
<P><FONT SIZE=3D2> [RFC3410] Case, J., Mundy, R., Partain, =
D. and B. Stewart,</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; "Introduction and Applicability Statements for =
Internet-</FONT>
<BR><FONT =
SIZE=3D2> &nb=
sp; Standard Management Framework", RFC 3410, December =
2002.</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>10. Full Copyright Statement</FONT>
</P>
<P><FONT SIZE=3D2> Copyright (C) The Internet Society (2004). All =
Rights Reserved.</FONT>
</P>
<P><FONT SIZE=3D2> This document and translations of it may be =
copied and furnished to</FONT>
<BR><FONT SIZE=3D2> others, and derivative works that comment on =
or otherwise explain it</FONT>
<BR><FONT SIZE=3D2> or assist in its implementation may be =
prepared, copied, published</FONT>
<BR><FONT SIZE=3D2> and distributed, in whole or in part, without =
restriction of any kind,</FONT>
<BR><FONT SIZE=3D2> provided that the above copyright notice and =
this paragraph are</FONT>
<BR><FONT SIZE=3D2> included on all such copies and derivative =
works. However, this</FONT>
<BR><FONT SIZE=3D2> document itself may not be modified in any =
way, such as by removing</FONT>
<BR><FONT SIZE=3D2> the copyright notice or references to the =
Internet Society or other</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Chisholm & =
Perkins Standards =
Track &=
nbsp; [Page 17]</FONT>
<BR><FONT =
SIZE=3D2>=0C =
=
Entity State =
MIB &nb=
sp; February 2004</FONT>
</P>
<BR>
<P><FONT SIZE=3D2> Internet organizations, except as needed for =
the purpose of</FONT>
<BR><FONT SIZE=3D2> developing Internet standards in which case =
the procedures for</FONT>
<BR><FONT SIZE=3D2> copyrights defined in the Internet Standards =
process must be followed,</FONT>
<BR><FONT SIZE=3D2> or as required to translate it into languages =
other than English.</FONT>
</P>
<P><FONT SIZE=3D2> The limited permissions granted above are =
perpetual and will not be</FONT>
<BR><FONT SIZE=3D2> revoked by the Internet Society or its =
successors or assigns.</FONT>
</P>
<P><FONT SIZE=3D2> This document and the information contained =
herein is provided on an</FONT>
<BR><FONT SIZE=3D2> "AS IS" basis and THE INTERNET =
SOCIETY AND THE INTERNET ENGINEERING</FONT>
<BR><FONT SIZE=3D2> TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS =
OR IMPLIED, INCLUDING BUT</FONT>
<BR><FONT SIZE=3D2> NOT LIMITED TO ANY WARRANTY THAT THE USE OF =
THE INFORMATION HEREIN</FONT>
<BR><FONT SIZE=3D2> WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED =
WARRANTIES OF</FONT>
<BR><FONT SIZE=3D2> MERCHANTABILITY OR FITNESS FOR A PARTICULAR =
PURPOSE.</FONT>
</P>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<P><FONT SIZE=3D2>Chisholm & =
Perkins Standards =
Track &=
nbsp; [Page 18]</FONT>
<BR><FONT SIZE=3D2>=0C</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C3F48C.0D2D48FA--