draft-ietf-entmib-state-04.txt   draft-ietf-entmib-state-05.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-04.txt D. Perkins Document: draft-ietf-entmib-state-05.txt D. Perkins
Category: Standards Track SNMPinfo Category: Standards Track SNMPinfo
Expiration Date: January 2005 July 2004 Expiration Date: March 2005 September 2004
Entity State MIB Entity State MIB
Status of this Memo Status of this Memo
By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed, or
will be disclosed, and any of which I become aware will be disclosed,
in accordance with RFC 3668.
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
other groups may also distribute working documents as other groups may also distribute working documents as
Internet-Drafts. Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other months and may be updated, replaced, or obsoleted by other
skipping to change at page 1, line 48 skipping to change at page 2, line 4
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 physical entities. provide information about the state of physical entities.
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. Entity Redundancy 2.2. Entity Redundancy
2.3. Physical Entity Users 2.3. Physical Entity Users
Entity State MIB September 2004
2.4. Physical Class Behaviour 2.4. Physical Class Behaviour
3. Relationship to Other MIBs 3. Relationship to Other MIBs
3.1. Relation to Interfaces MIB 3.1. Relation to Interfaces MIB
3.2. Relation to Alarm MIB 3.2. Relation to Alarm MIB
3.3. Relation to Bridge MIB 3.3. Relation to Bridge MIB
3.4. Relation to Host Resource MIB 3.4. Relation to Host Resource MIB
4. Textual Conventions 4. Textual Conventions
5. Definitions 5. Definitions
6. Security Considerations 6. Security Considerations
7. Intellectual Property 7. Intellectual Property
8. Authors' Addresses 8. Authors' Addresses
9. Acknowledgements 9. Acknowledgements
10. References 10. References
11. Full Copyright Statement 11. Full Copyright Statement
Entity State MIB September 2004
1. The Internet-Standard Management Framework 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
skipping to change at page 4, line 5 skipping to change at page 4, line 5
within its containment hierarchy. 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.
Entity State MIB September 2004
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. Physical Physical entities exist within a containment hierarchy. Physical
containment is defined by the entPhysicalContainedIn containment is defined by the entPhysicalContainedIn
skipping to change at page 5, line 5 skipping to change at page 5, line 5
2. Anywhere in physical hierarchy 2. Anywhere in physical hierarchy
3. As defined by a means outside the scope of this MIB. This could 3. As defined by a means outside the scope of this MIB. This could
include logical interfaces that could run on a port, software that include logical interfaces that could run on a port, software that
could run on a module, etc. could run on a module, etc.
Administrative, operational, alarm and standby state use all three Administrative, operational, alarm and standby state use all three
definitions of 'user'. Usage state only supports the concept of definitions of 'user'. Usage state only supports the concept of
direct containment to simplify implementations of this object. direct containment to simplify implementations of this object.
Entity State MIB September 2004
2.4 Physical Class Behaviour 2.4 Physical Class Behaviour
This MIB makes no effort to standardize on the behaviours and This MIB makes no effort to standardize on the behaviours and
characteristics of the various physical classes [RFC2737], but characteristics of the various physical classes [RFC2737], but
rather how this information is reported. In looking at real-world rather how this information is reported. In looking at real-world
products, items within the same physical class vary substantially. products, items within the same physical class vary substantially.
The MIB has therefore provided guidance on how to support objects The MIB has therefore provided guidance on how to support objects
where a particular instance of a physical class can not support part where a particular instance of a physical class can not support part
or all of a particular state. or all of a particular state.
skipping to change at page 5, line 37 skipping to change at page 5, line 39
'shuttingDown', depending on a systems interpretation of 'down'. 'shuttingDown', depending on a systems interpretation of 'down'.
An ifOperStatus of 'up' is equivalent to an entStateOper value of An ifOperStatus of 'up' is equivalent to an entStateOper value of
'enabled'. An ifOperStatus of 'down' due to operational failure is 'enabled'. An ifOperStatus of 'down' due to operational failure is
equivalent to an entStateOper value of 'disabled'. An ifOperStatus equivalent to an entStateOper value of 'disabled'. An ifOperStatus
of 'down' due to being administratively disabled is equivalent to an of 'down' due to being administratively disabled is equivalent to an
entStateAdmin value of 'locked' and an entStateOper value of either entStateAdmin value of 'locked' and an entStateOper value of either
'enabled' or 'disabled' depending on whether there are any known 'enabled' or 'disabled' depending on whether there are any known
issues that would prevent the entity from becoming operational when issues that would prevent the entity from becoming operational when
its entStateAdmin is set to 'unlocked'. An ifOperStatus of its entStateAdmin is set to 'unlocked'. An ifOperStatus of
'unknown' is equivalent to an entStateOper value of 'unavailable'. 'unknown' is equivalent to an entStateOper value of 'unknown'. The
The ifOperStatus values of 'testing' and 'dormant' are not ifOperStatus values of 'testing' and 'dormant' are not explicitly
explicitly supported by this MIB, but the state objects will be able supported by this MIB, but the state objects will be able to reflect
to reflect other aspects of the entities administrative and other aspects of the entities administrative and operational state.
operational state. The ifOperStatus values of 'notPresent' and The ifOperStatus values of 'notPresent' and 'lowerLayerDown' are in
'lowerLayerDown' are in some ways computed states and so are some ways computed states and so are therefore not supported in this
therefore not supported in this MIB. They can though be computed by MIB. They can though be computed by examining the states of entities
examining the states of entities within this objects containment within this objects containment hierarchy and other available
hierarchy and other available related states. related states.
3.2 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.
Entity State MIB September 2004
Alternatively, if the alarmActiveTable is queried first and an Alternatively, if the alarmActiveTable is queried first and an
active alarm with a value of alarmActiveResourceId that matches this active alarm with a value of alarmActiveResourceId that matches this
entPhysicalIndex is found, then entStateAlarm can be used to quickly entPhysicalIndex is found, then entStateAlarm can be used to quickly
determine if there are additional active alarms against this determine if there are additional active alarms against this
physical entity. physical entity.
3.3 Relation to Bridge MIB 3.3 Relation to Bridge MIB
For entities of physical type of 'port' that support the For entities of physical type of 'port' that support the
dot1dStpPortEnable object in the Bridge MIB [RFC1493], a value of dot1dStpPortEnable object in the Bridge MIB [RFC1493], a value of
'enabled' is equivalent to setting the entStateAdmin object to 'enabled' is equivalent to setting the entStateAdmin object to
'unlocked'. Setting dot1dStpPortEnable to 'disabled' is equivalent 'unlocked'. Setting dot1dStpPortEnable to 'disabled' is equivalent
to setting the entStateAdmin object to 'locked'. to setting the entStateAdmin object to 'locked'.
3.4 Relation to the Host Resources MIB 3.4 Relation to the Host Resources MIB
The hrDeviceStatus object in the Host Resources MIB [RFC2790] The hrDeviceStatus object in the Host Resources MIB [RFC2790]
provides an operational state for devices. For entities that provides an operational state for devices. For entities that
logically correspond to the concept of a device, a value of logically correspond to the concept of a device, a value of
'unknown' for hrDeviceStatus corresponds to an entStateOper value of 'unknown' for hrDeviceStatus corresponds to an entStateOper value of
'unavailable'. A value of 'running' corresponds to an entStateOper 'unknown'. A value of 'running' corresponds to an entStateOper value
value of 'enabled'. A value of 'warning' also corresponds to an of 'enabled'. A value of 'warning' also corresponds to an
entStateOper value of 'enabled', but with appropriate bits set in entStateOper value of 'enabled', but with appropriate bits set in
the entStateAlarm object to indicate the alarms corresponding to the the entStateAlarm object to indicate the alarms corresponding to the
unusual error condition detected. A value of 'testing' or 'down' is unusual error condition detected. A value of 'testing' or 'down' is
equivalent to an entStateOper value of 'disabled'. equivalent to an entStateOper value of 'disabled'.
4. Textual Conventions 4. Textual Conventions
ENTITY-STATE-TC DEFINITIONS ::= BEGIN ENTITY-STATE-TC DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
skipping to change at page 7, line 4 skipping to change at page 7, line 4
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
Entity State MIB September 2004
David T. Perkins David T. Perkins
548 Qualbrook Ct 548 Qualbrook Ct
San Jose, CA 95110 San Jose, CA 95110
USA USA
Phone: 408 394-8702 Phone: 408 394-8702
dperkins@snmpinfo.com" dperkins@snmpinfo.com"
DESCRIPTION DESCRIPTION
"This MIB defines a state textual conventions. "This MIB defines a state textual conventions.
Copyright (C) The Internet Society 2004. This version Copyright (C) The Internet Society 2004. 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 "200407190000Z" REVISION "200407190000Z"
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
AdminState ::= TEXTUAL-CONVENTION EntityAdminState ::= 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. A value of administratively prohibited from use. A value of
'unavailable' means that this resource is unable to 'unknown' means that this resource is unable to
report administrative state." report administrative state."
REFERENCE
"ITU Recommendation X.731, 'Information Technology - Open
Systems Interconnection - System Management: State
Management Function', 1992"
SYNTAX INTEGER SYNTAX INTEGER
{ {
unavailable(1), unknown(1),
locked(2), locked(2),
shuttingDown(3), shuttingDown(3),
unlocked(4) unlocked(4)
} }
OperState ::= TEXTUAL-CONVENTION EntityOperState ::= 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. A value of 'testing' is partially or fully operable. A value of 'testing'
means the resource is currently being tested means the resource is currently being tested
and cannot there fore report whether it is operational and cannot there fore report whether it is operational
or not. A value of 'unavailable' means that this or not. A value of 'unknown' means that this
resource is unable to report operational state. " resource is unable to report operational state. "
REFERENCE
"ITU Recommendation X.731, 'Information Technology - Open Entity State MIB September 2004
Systems Interconnection - System Management: State
Management Function', 1992"
SYNTAX INTEGER SYNTAX INTEGER
{ {
unavailable (1), unknown (1),
disabled(2), disabled(2),
enabled(3), enabled(3),
testing (4) testing (4)
} }
UsageState ::= TEXTUAL-CONVENTION EntityUsageState ::= 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 A value of 'idle' means the resource is servicing no
users. A value of 'active' means the resource is users. A value of 'active' means the resource is
currently in use and it has sufficient spare capacity currently in use and it has sufficient spare capacity
to provide for additional users. A value of 'busy' to provide for additional users. A value of 'busy'
means the resource is currently in use, but it means the resource is currently in use, but it
currently has no spare capacity to provide for currently has no spare capacity to provide for
additional users. A value of 'unavailable' means additional users. A value of 'unknown' means
that this resource is unable to report usage state." 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 SYNTAX INTEGER
{ {
unavailable (1), unknown (1),
idle(2), idle(2),
active(3), active(3),
busy(4) busy(4)
} }
AlarmStatus ::= TEXTUAL-CONVENTION EntityAlarmStatus ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Represents the possible values of alarm status. "Represents the possible values of alarm status.
An Alarm [ALARM-MIB] is a persistent indication An Alarm [ALARM-MIB] is a persistent indication
of an error or warning condition. of an error or warning condition.
When no bits of this attribute are set, then none When no bits of this attribute are set, then none
of the value of under repair is set, the resource is of the value of under repair is set, the resource is
currently being repaired, which depending on the currently being repaired, which depending on the
implementation, may make the other values in this bit implementation, may make the other values in this bit
skipping to change at page 9, line 17 skipping to change at page 9, line 5
alarms are active against the resource. When the value alarms are active against the resource. When the value
of 'major' is set, one or more major alarms are active of 'major' is set, one or more major alarms are active
against the resource. When the value of 'minor' is set, against the resource. When the value of 'minor' is set,
one or more minor alarms are active against the resource. one or more minor alarms are active against the resource.
When the value of 'warning' is set, one or more warning When the value of 'warning' is set, one or more warning
alarms are active against the resource. When the value alarms are active against the resource. When the value
of 'indeterminate' is set, one or more alarms whose of of 'indeterminate' is set, one or more alarms whose of
perceived severity cannot be determined are active perceived severity cannot be determined are active
against this resource. against this resource.
A value of 'unavailable' means that this resource is Entity State MIB September 2004
A value of 'unknown' means that this resource is
unable to report alarm state." unable to report alarm state."
REFERENCE
"ITU Recommendation X.731, 'Information Technology - Open
Systems Interconnection - System Management: State
Management Function', 1992"
SYNTAX BITS SYNTAX BITS
{ {
unavailable (0), unknown (0),
underRepair(1), underRepair(1),
critical(2), critical(2),
major(3), major(3),
minor(4), minor(4),
-- The following are not defined in X.733 -- The following are not defined in X.733
warning (5), warning (5),
indeterminate (6) indeterminate (6)
} }
StandbyStatus ::= TEXTUAL-CONVENTION EntityStandbyStatus ::= 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 A value of 'hotStandby' means the resource is not
providing service, but it will be immediately able to providing service, but it will be immediately able to
take over the role of the resource to be backed-up, take over the role of the resource to be backed-up,
without the need for initialization activity, and will without the need for initialization activity, and will
contain the same information as the resource to be contain the same information as the resource to be
backed up. A value of 'coldStandy' means that the backed up. A value of 'coldStandy' means that the
resource is to back-up another resource, but will not resource is to back-up another resource, but will not
be immediately able to take over the role of a resource be immediately able to take over the role of a resource
to be backed up, and will require some initialization to be backed up, and will require some initialization
activity. A value of 'providingService' means the activity. A value of 'providingService' means the
resource is providing service. A value of resource is providing service. A value of
'unavailable' means that this resource is unable to 'unknown' means that this resource is unable to
report standby state." report standby state."
REFERENCE
"ITU Recommendation X.731, 'Information Technology - Open
Systems Interconnection - System Management: State
Management Function', 1992"
SYNTAX INTEGER SYNTAX INTEGER
{ {
unavailable (1), unknown (1),
hotStandby(2), hotStandby(2),
coldStandby(3), coldStandby(3),
providingService(4) providingService(4)
} }
END END
5. Definitions 5. 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
Entity State MIB September 2004
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
AdminState, OperState, UsageState, AlarmStatus, StandbyStatus EntityAdminState, EntityOperState, EntityUsageState,
EntityAlarmStatus, EntityStandbyStatus
FROM ENTITY-STATE-TC; FROM ENTITY-STATE-TC;
entityStateMIB MODULE-IDENTITY entityStateMIB MODULE-IDENTITY
LAST-UPDATED "200407190000Z" LAST-UPDATED "200407190000Z"
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
skipping to change at page 11, line 22 skipping to change at page 11, line 5
REVISION "200407190000Z" REVISION "200407190000Z"
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
-- Entity State Objects -- Entity State Objects
entStateObjects OBJECT IDENTIFIER ::= { entityStateMIB 1 } entStateObjects OBJECT IDENTIFIER ::= { entityStateMIB 1 }
Entity State MIB September 2004
entStateTable OBJECT-TYPE entStateTable OBJECT-TYPE
SYNTAX SEQUENCE OF EntStateEntry SYNTAX SEQUENCE OF EntStateEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of information about state/status of entities. "A table of information about state/status of entities.
This is a sparse augment of the entPhysicalTable. Entries This is a sparse augment of the entPhysicalTable. Entries
appear in this table for values of appear in this table for values of
entPhysicalClass [RFC2737] that in this implementation entPhysicalClass [RFC2737] that in this implementation
are able to report any of the state or status stored in are able to report any of the state or status stored in
skipping to change at page 11, line 47 skipping to change at page 11, line 32
SYNTAX EntStateEntry SYNTAX EntStateEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"State information about this physical entity." "State information about this physical entity."
INDEX { entPhysicalIndex } INDEX { entPhysicalIndex }
::= { entStateTable 1 } ::= { entStateTable 1 }
EntStateEntry ::= SEQUENCE { EntStateEntry ::= SEQUENCE {
entStateLastChanged DateAndTime, entStateLastChanged DateAndTime,
entStateAdmin AdminState, entStateAdmin EntityAdminState,
entStateOper OperState, entStateOper EntityOperState,
entStateUsage UsageState, entStateUsage EntityUsageState,
entStateAlarm AlarmStatus, entStateAlarm EntityAlarmStatus,
entStateStandby StandbyStatus entStateStandby EntityStandbyStatus
} }
entStateLastChanged OBJECT-TYPE entStateLastChanged OBJECT-TYPE
SYNTAX DateAndTime SYNTAX DateAndTime
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object is the date and "The value of this object is the date and
time when the value of any of entStateAdmin, time when the value of any of entStateAdmin,
entStateOper, entStateUsage, entStateAlarm, entStateOper, entStateUsage, entStateAlarm,
or entStateStandby changed for this entity. or entStateStandby changed for this entity.
skipping to change at page 12, line 23 skipping to change at page 12, line 5
If there has been no change since If there has been no change since
the last re-initialization of the local system, the last re-initialization of the local system,
this object contains the date and time of this object contains the date and time of
local system initialization. If there has been local system initialization. If there has been
no change since the entity was added to the no change since the entity was added to the
local system, this object contains the date and local system, this object contains the date and
time of the insertion" time of the insertion"
::= { entStateEntry 1 } ::= { entStateEntry 1 }
Entity State MIB September 2004
entStateAdmin OBJECT-TYPE entStateAdmin OBJECT-TYPE
SYNTAX AdminState SYNTAX EntityAdminState
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object refers to an entities administrative "This object refers to an entities administrative
permission to service both other entities within permission to service both other entities within
its containment hierarchy as well other users of its containment hierarchy as well other users of
its services defined by means outside the scope its services defined by means outside the scope
of this MIB. of this MIB.
The administrative state for this entity. The administrative state for this entity.
skipping to change at page 12, line 53 skipping to change at page 12, line 37
cannot be locked, and hence this object exhibits only cannot be locked, and hence this object exhibits only
the 'unlocked' state. Other entities can not be shutdown the 'unlocked' state. Other entities can not be shutdown
gracefully, and hence this object does not exhibit the gracefully, and hence this object does not exhibit the
'shuttingDown' state. A value of 'inconsistentValue' 'shuttingDown' state. A value of 'inconsistentValue'
will be returned if attempts are made to set this will be returned if attempts are made to set this
object to values not supported by its administrative object to values not supported by its administrative
model." model."
::= { entStateEntry 2 } ::= { entStateEntry 2 }
entStateOper OBJECT-TYPE entStateOper OBJECT-TYPE
SYNTAX OperState SYNTAX EntityOperState
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.
Note that unlike the state model used within the Note that unlike the state model used within the
Interfaces MIB [RFC2863], this object does not follow Interfaces MIB [RFC2863], this object does not follow
the administrative state. An administrative state of the administrative state. An administrative state of
down does not predict an operational state down does not predict an operational state
of disabled. of disabled.
A value of 'disabled' means that an entity is totally A value of 'disabled' means that an entity is totally
inoperable and unable to provide service both to entities inoperable and unable to provide service both to entities
within its containment hierarchy, or to other receivers within its containment hierarchy, or to other receivers
of its service as defined in ways outside the scope of of its service as defined in ways outside the scope of
this MIB. this MIB.
A value of 'enabled' means that an entity is fully or A value of 'enabled' means that an entity is fully or
partially operable and able to provide service both to partially operable and able to provide service both to
entities within its containment hierarchy, or to other entities within its containment hierarchy, or to other
Entity State MIB September 2004
receivers of its service as defined in ways outside the receivers of its service as defined in ways outside the
scope of this MIB. scope of this MIB.
Note that some implementations may not be able to Note that some implementations may not be able to
accurately report entStateOper while the accurately report entStateOper while the
entStateAdmin object has a value other than 'unlocked'. entStateAdmin object has a value other than 'unlocked'.
In these cases, this object MUST have a value In these cases, this object MUST have a value
of 'unavailable'." of 'unknown'."
::= { entStateEntry 3 } ::= { entStateEntry 3 }
entStateUsage OBJECT-TYPE entStateUsage OBJECT-TYPE
SYNTAX UsageState SYNTAX EntityUsageState
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.
This object refers to an entity's ability to service more This object refers to an entity's ability to service more
physical entities in a containment hierarchy. A value physical entities in a containment hierarchy. A value
of 'idle' means this entity is able to contain other of 'idle' means this entity is able to contain other
entities but that no other entity is currently entities but that no other entity is currently
contained within this entity. contained within this entity.
skipping to change at page 14, line 9 skipping to change at page 13, line 45
Some entities will exhibit only a subset of the Some entities will exhibit only a subset of the
usage state values. Entities that are unable to ever usage state values. Entities that are unable to ever
service any entities within a containment hierarchy will service any entities within a containment hierarchy will
always have a usage state of 'busy'. Some entities will always have a usage state of 'busy'. Some entities will
only ever be able to support one entity within its only ever be able to support one entity within its
containment hierarchy and will therefore only exhibit containment hierarchy and will therefore only exhibit
values of 'idle' and 'busy'." values of 'idle' and 'busy'."
::= { entStateEntry 4 } ::= { entStateEntry 4 }
entStateAlarm OBJECT-TYPE entStateAlarm OBJECT-TYPE
SYNTAX AlarmStatus SYNTAX EntityAlarmStatus
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 alarms raised on child components within its the alarms raised on child components within its
containment hierarchy. containment hierarchy.
Note that this differs from 'indeterminate' which Note that this differs from 'indeterminate' which
means that that alarm state is supported and there means that that alarm state is supported and there
are alarms against this entity, but the severity of are alarms against this entity, but the severity of
some of the alarms is not known. some of the alarms is not known.
If no bits are set, then this entity supports reporting If no bits are set, then this entity supports reporting
Entity State MIB September 2004
of alarms, but there are currently no active alarms of alarms, but there are currently no active alarms
against this entity. against this entity.
" "
::= { entStateEntry 5 } ::= { entStateEntry 5 }
entStateStandby OBJECT-TYPE entStateStandby OBJECT-TYPE
SYNTAX StandbyStatus SYNTAX EntityStandbyStatus
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.
Some entities will exhibit only a subset of the Some entities will exhibit only a subset of the
remaining standby state values. If this entity remaining standby state values. If this entity
cannot operate in a standby role, the value of this cannot operate in a standby role, the value of this
object will always be 'providingService'." object will always be 'providingService'."
::= { entStateEntry 6 } ::= { entStateEntry 6 }
skipping to change at page 15, line 24 skipping to change at page 15, line 4
::= { entStateNotifications 1 } ::= { entStateNotifications 1 }
entStateOperDisabled NOTIFICATION-TYPE entStateOperDisabled NOTIFICATION-TYPE
OBJECTS { entStateAdmin, OBJECTS { entStateAdmin,
entStateAlarm } entStateAlarm }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entStateOperDisabled Notification signifies that the "An entStateOperDisabled Notification signifies that the
SNMP entity, acting in an agent role, has detected that SNMP entity, acting in an agent role, has detected that
the entStateOper object for one of its entities has left the entStateOper object for one of its entities has left
Entity State MIB September 2004
the 'enabled' state and transitioned into the the 'enabled' state and transitioned into the
'disabled' state. 'disabled' state.
The entity this notification refers can be identified by 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. The entStateAdmin and entStateAlarm variable bindings. The entStateAdmin and entStateAlarm
varbinds may be examined to find out additional varbinds may be examined to find out additional
information on the administrative state at the time of information on the administrative state at the time of
the operation state change as well to find out whether the operation state change as well to find out whether
there were any known alarms against the entity at that there were any known alarms against the entity at that
time that may have affect on the physical entity's time that may have affect on the physical entity's
ability to stay operationally enabled." ability to stay operationally enabled."
::= { entStateNotifications 2 } ::= { entStateNotifications 2 }
-- Conformance and Compliance -- Conformance and Compliance
entStateConformance OBJECT IDENTIFIER ::= { entityStateMIB 3 } entStateConformance OBJECT IDENTIFIER ::= { entityStateMIB 2 }
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
skipping to change at page 16, line 23 skipping to change at page 16, line 4
OBJECTS { OBJECTS {
entStateLastChanged, entStateLastChanged,
entStateAdmin, entStateAdmin,
entStateOper, entStateOper,
entStateUsage, entStateUsage,
entStateAlarm, entStateAlarm,
entStateStandby entStateStandby
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
Entity State MIB September 2004
"Standard Entity State group." "Standard Entity State group."
::= { entStateGroups 1} ::= { entStateGroups 1}
entStateNotificationsGroup NOTIFICATION-GROUP entStateNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
entStateOperEnabled, entStateOperEnabled,
entStateOperDisabled entStateOperDisabled
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 17, line 23 skipping to change at page 17, line 5
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.
Note that setting the entStateAdmin to 'locked' or 'shuttingDown' Note that setting the entStateAdmin to 'locked' or 'shuttingDown'
can cause disruption of services ranging from those running on a can cause disruption of services ranging from those running on a
port to those on an entire device, depending on the type of entity. port to those on an entire device, depending on the type of entity.
Access to this object should be properly protected. Access to this object should be properly protected.
Entity State MIB September 2004
Access to the objects defined in this MIB allows one to figure out Access to the objects defined in this MIB allows one to figure out
what the active and standby resources in a network are. This what the active and standby resources in a network are. This
information can be used to optimize attacks on networks so even information can be used to optimize attacks on networks so even
read-only access to this MIB should be properly protected. read-only access to this MIB should be properly protected.
7. Intellectual Property 7. Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
skipping to change at page 18, line 20 skipping to change at page 18, line 5
USA USA
Phone: 408 394-8702 Phone: 408 394-8702
Email: dperkins@snmpinfo.com Email: dperkins@snmpinfo.com
9. Acknowledgments 9. Acknowledgments
This document is a product of the Entity MIB Working Group. This document is a product of the Entity MIB Working Group.
10. References 10. References
10.1 Normative Entity State MIB September 2004
[ALARM-MIB] Chisholm, S., Romascanu, D., "Alarm MIB", 10.1 Normative
draft-ietf-disman-alarm-mib-18.txt, February 2004
[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.,
Rose, M. and S. Waldbusser, "Textual Conventions for Rose, M. and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
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
Systems Interconnection - System Management: State
Management Function", 1992
10.2 Informative References 10.2 Informative References
[RFC1493] Decker, E., Langille, P., Rijsinghani, A., McCloghrie, K., [RFC1493] Decker, E., Langille, P., Rijsinghani, A., McCloghrie, K.,
"Definitions of Managed Objects for Bridges", RFC 1493, "Definitions of Managed Objects for Bridges", RFC 1493,
July 1993 July 1993
[RFC2790] Waldbusser, S., Grillo, P., "Host Resources MIB", [RFC2790] Waldbusser, S., Grillo, P., "Host Resources MIB",
RFC 2790, March 2000 RFC 2790, March 2000
[RFC2863] McCloghrie, K., Kastenholz, F., "The Interfaces Group [RFC2863] McCloghrie, K., Kastenholz, F., "The Interfaces Group
MIB using SMIv2", RFC2863, June 2000 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.
skipping to change at page 19, line 14 skipping to change at page 18, line 44
[RFC2790] Waldbusser, S., Grillo, P., "Host Resources MIB", [RFC2790] Waldbusser, S., Grillo, P., "Host Resources MIB",
RFC 2790, March 2000 RFC 2790, March 2000
[RFC2863] McCloghrie, K., Kastenholz, F., "The Interfaces Group [RFC2863] McCloghrie, K., Kastenholz, F., "The Interfaces Group
MIB using SMIv2", RFC2863, June 2000 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.
11. Full Copyright Statement [RFC3877] Chisholm, S., Romascanu, D., "Alarm Management Information
Base (MIB)", RFC 3877, September 2004
Copyright (C) The Internet Society (2004). All Rights Reserved. [X.731] ITU Recommendation X.731, "Information Technology - Open
Systems Interconnection - System Management: State
Management Function", 1992
This document and translations of it may be copied and furnished to 11. Full Copyright Statement
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
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 Copyright (C) The Internet Society (2004). This document is subject
revoked by the Internet Society or its successors or assigns. to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights."
This document and the information contained herein is provided on an Entity State MIB September 2004
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT "This document and the information contained herein are provided on
NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. INTERNET ENGINEERING TASK FORCE DISCLAIM 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."
 End of changes. 

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