draft-ietf-entmib-state-06.txt   draft-ietf-entmib-state-07.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-06.txt D. Perkins Document: draft-ietf-entmib-state-07.txt D. Perkins
Category: Standards Track SNMPinfo Category: Standards Track SNMPinfo
Expiration Date: June 2005 December 2004 Expiration Date: July 2005 January 2005
Entity State MIB Entity State MIB
Status of this Memo Status of this Memo
By submitting this Internet-Draft, I certify that any applicable By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed, or 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, will be disclosed, and any of which I become aware will be disclosed,
in accordance with RFC 3668. in accordance with RFC 3668.
skipping to change at page 2, line 14 skipping to change at page 2, line 14
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. IANA Considerations
9. Acknowledgements 9. Authors' Addresses
10. References 10. Acknowledgements
11. Full Copyright Statement 11. References
12. Full Copyright Statement
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).
skipping to change at page 3, line 50 skipping to change at page 3, line 50
Usage state indicates whether or not the entity is in use at a Usage state indicates whether or not the entity is in use at a
specific instance, and if so, whether or not it currently has spare specific instance, and if so, whether or not it currently has spare
capacity to serve additional users. In the context of this MIB, the capacity to serve additional users. In the context of this MIB, the
usage state refers to the ability of an entity to service other usage state refers to the ability of an entity to service other
entities within its containment hierarchy. entities within its containment hierarchy.
Alarm state indicates whether or not there are any alarms active Alarm state indicates whether or not there are any alarms active
against the entity. In addition to those alarm states defined in against the entity. In addition to those alarm states 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 [RFC3877].
Standby state indicates whether the entity is currently running as Standby state indicates whether the entity is currently running as
hot standby, cold standby or is currently providing service. hot standby, cold standby or is currently providing service.
The terms state and status are used interchangeably in this memo. The terms state and status are used interchangeably in this memo.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
skipping to change at page 5, line 52 skipping to change at page 5, line 52
some ways computed states and so are therefore not supported in this some ways computed states and so are therefore not supported in this
MIB. They can though be computed by examining the states of entities MIB. They can though be computed by examining the states of entities
within this objects containment hierarchy and other available within this objects containment 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 rows whose alarmActiveResourceId matches this entPhysicalIndex.
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 with a different
physical entity. severity against this 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
skipping to change at page 6, line 41 skipping to change at page 6, line 41
4. Textual Conventions 4. Textual Conventions
ENTITY-STATE-TC-MIB DEFINITIONS ::= BEGIN ENTITY-STATE-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC; TEXTUAL-CONVENTION FROM SNMPv2-TC;
entityStateTc MODULE-IDENTITY entityStateTc MODULE-IDENTITY
LAST-UPDATED "200407190000Z" LAST-UPDATED "200501230000Z"
ORGANIZATION "IETF Entity MIB Working Group" ORGANIZATION "IETF Entity MIB Working Group"
CONTACT-INFO CONTACT-INFO
"General Discussion: entmib@ietf.org "General Discussion: entmib@ietf.org
To Subscribe: To Subscribe:
http://www.ietf.org/mailman/listinfo/entmib http://www.ietf.org/mailman/listinfo/entmib
http://www.ietf.org/html.charters/entmib-charter.html http://www.ietf.org/html.charters/entmib-charter.html
Sharon Chisholm Sharon Chisholm
Nortel Networks Nortel Networks
PO Box 3511 Station C PO Box 3511 Station C
Ottawa, Ont. K1Y 4H7 Ottawa, Ont. K1Y 4H7
Canada Canada
schishol@nortelnetworks.com schishol@nortelnetworks.com
Chisholm & Perkins Standards Track
2005
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 state textual conventions. "This MIB defines state textual conventions.
Copyright (C) The Internet Society 2004. This version Copyright (C) The Internet Society 2005. 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 "200501230000Z"
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
EntityAdminState ::= TEXTUAL-CONVENTION EntityAdminState ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" Represents the various possible administrative states. " Represents the various possible administrative states.
skipping to change at page 8, line 36 skipping to change at page 8, line 36
unknown (1), unknown (1),
idle (2), idle (2),
active (3), active (3),
busy (4) busy (4)
} }
EntityAlarmStatus ::= 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 [RFC3877] 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 no active When no bits of this attribute are set, then no active
alarms are known against this entity and it is not under alarms are known against this entity and it is not under
repair. repair.
When the 'value of underRepair' is set, the resource is When the 'value of underRepair' 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
string not meaningful. string not meaningful.
skipping to change at page 10, line 17 skipping to change at page 10, line 17
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
EntityAdminState, EntityOperState, EntityUsageState, EntityAdminState, EntityOperState, EntityUsageState,
EntityAlarmStatus, EntityStandbyStatus EntityAlarmStatus, EntityStandbyStatus
FROM ENTITY-STATE-TC-MIB; FROM ENTITY-STATE-TC-MIB;
entityStateMIB MODULE-IDENTITY entityStateMIB MODULE-IDENTITY
LAST-UPDATED "200407190000Z" LAST-UPDATED "200501230000Z"
ORGANIZATION "IETF Entity MIB Working Group" ORGANIZATION "IETF Entity MIB Working Group"
CONTACT-INFO CONTACT-INFO
" General Discussion: entmib@ietf.org " General Discussion: entmib@ietf.org
To Subscribe: To Subscribe:
http://www.ietf.org/mailman/listinfo/entmib http://www.ietf.org/mailman/listinfo/entmib
http://www.ietf.org/html.charters/entmib-charter.html http://www.ietf.org/html.charters/entmib-charter.html
Sharon Chisholm Sharon Chisholm
Nortel Networks Nortel Networks
skipping to change at page 10, line 43 skipping to change at page 10, line 43
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 extension to the Entity MIB. "This MIB defines a state extension to the Entity MIB.
Copyright (C) The Internet Society 2004. This version Copyright (C) The Internet Society 2005. 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 "200501230000Z"
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 }
entStateTable OBJECT-TYPE entStateTable OBJECT-TYPE
SYNTAX SEQUENCE OF EntStateEntry SYNTAX SEQUENCE OF EntStateEntry
skipping to change at page 16, line 29 skipping to change at page 16, line 29
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Standard Entity State Notification group." "Standard Entity State Notification group."
::= { entStateGroups 2} ::= { entStateGroups 2}
END END
6. Security Considerations 6. Security Considerations
There is one management object defined in this MIB that has a There is one management object - entStateAdmin - defined in this MIB
MAX-ACCESS clause of read-write. The object may be considered that has a MAX-ACCESS clause of read-write. The object may be
sensitive or vulnerable in some network environments. The support considered sensitive or vulnerable in some network environments.
for SET operations in a non-secure environment without proper The support for SET operations in a non-secure environment without
protection can have a negative effect on network operations. proper protection can have a negative effect on network operations.
The following object is defined with a MAX-ACCESS clause of Note that setting the entStateAdmin to 'locked' or 'shuttingDown'
read-write: entStateAdmin. 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.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec), 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 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 allowed to access and GET/SET (read/change/create/delete) the
objects in this MIB module. objects in this MIB module.
It is RECOMMENDED that implementers consider the security features It is RECOMMENDED that implementers consider the security features
as provided by the SNMPv3 framework (see [RFC3410], section 8), as provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (entities) that have legitimate the objects only to those principals (entities) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
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.
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
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of standards-related documentation can be found in BCP-11. Copies of
skipping to change at page 17, line 39 skipping to change at page 17, line 36
to obtain a general license or permission for the use of such to obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification proprietary rights by implementors or users of this specification
can be obtained from the IETF Secretariat. can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
8. Authors' Addresses 8. IANA Considerations
This draft requires no action on the part of IANA other than the
allocation of the MIB OID from which to root this MIB. This section
should be removed prior to publication as and RFC.
9. Authors' Addresses
Sharon Chisholm Sharon Chisholm
Nortel Networks Nortel Networks
PO Box 3511, Station C PO Box 3511, Station C
Ottawa, Ontario, K1Y 4H7 Ottawa, Ontario, K1Y 4H7
Canada Canada
Email: schishol@nortelnetworks.com Email: schishol@nortelnetworks.com
David T. Perkins David T. Perkins
548 Qualbrook Ct 548 Qualbrook Ct
San Jose, CA 95110 San Jose, CA 95110
USA USA
Phone: 408 394-8702 Phone: 408 394-8702
Email: dperkins@snmpinfo.com Email: dperkins@snmpinfo.com
9. Acknowledgments 10. 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 11. References
10.1 Normative 11.1 Normative
[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. [Note to RFC Editor: If later version of
RFC2727 is available at time of publication, please update this
references]
10.2 Informative References 11.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
skipping to change at page 19, line 6 skipping to change at page 19, line 12
"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.
[RFC3877] Chisholm, S., Romascanu, D., "Alarm Management Information [RFC3877] Chisholm, S., Romascanu, D., "Alarm Management Information
Base (MIB)", RFC 3877, September 2004 Base (MIB)", RFC 3877, September 2004
[X.731] ITU Recommendation X.731, "Information Technology - Open [X.731] ITU Recommendation X.731, "Information Technology - Open
Systems Interconnection - System Management: State Systems Interconnection - System Management: State
Management Function", 1992 Management Function", 1992
11. Full Copyright Statement 12. Full Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights." except as set forth therein, the authors retain all their rights."
"This document and the information contained herein are provided on "This document and the information contained herein are provided on
an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE
INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." 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/