RE: [Entmib] FW: [psg.com #332] AutoReply: More Standby State/Sta tus Issues
"Sharon Chisholm" <schishol@nortelnetworks.com> Sun, 15 February 2004 20:09 UTC
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22108 for <entmib-archive@lists.ietf.org>; Sun, 15 Feb 2004 15:09:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AsSZZ-0002Jb-G2; Sun, 15 Feb 2004 15:09:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AsSZK-0002GF-G4 for entmib@optimus.ietf.org; Sun, 15 Feb 2004 15:08:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22041 for <entmib@ietf.org>; Sun, 15 Feb 2004 15:08:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AsSZH-0007An-00 for entmib@ietf.org; Sun, 15 Feb 2004 15:08:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AsSYK-00077q-00 for entmib@ietf.org; Sun, 15 Feb 2004 15:07:45 -0500
Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by ietf-mx with esmtp (Exim 4.12) id 1AsSY3-00075A-00 for entmib@ietf.org; Sun, 15 Feb 2004 15:07:27 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69]) by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i1FK6un04614 for <entmib@ietf.org>; Sun, 15 Feb 2004 15:06:56 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19) id <1FNH8YN7>; Sun, 15 Feb 2004 15:06:57 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A2A7283@zcard0ka.ca.nortel.com>
From: Sharon Chisholm <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] FW: [psg.com #332] AutoReply: More Standby State/Sta tus Issues
Date: Sun, 15 Feb 2004 15:06:56 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-BeenThere: entmib@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/entmib>, <mailto:entmib-request@ietf.org?subject=unsubscribe>
List-Id: IETF Entity MIB WG <entmib.ietf.org>
List-Post: <mailto:entmib@ietf.org>
List-Help: <mailto:entmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/entmib>, <mailto:entmib-request@ietf.org?subject=subscribe>
The following is the proposed resolution to entstate-332. The issue will be considered closed pending the proposed edit being done. In the description to entStateStandby replace " If this entity cannot operate in a standby role, the value of this object will always be 'providingService'." Sharon -----Original Message----- From: Chisholm, Sharon [CAR:0S00:EXCH] Sent: Sunday, February 15, 2004 3:03 PM To: 'entmib@ietf.org' Subject: RE: [Entmib] FW: [psg.com #332] AutoReply: More Standby State/Status Issues Hi I'm going to object to my own proposed resolution. In going back though the issues list I note that adding an enumeration to support load sharing was already discussed by the working group and was tracked as issue #74. The decision was not the include it since ... "It seems that 'loadSharing' would be more of a specialization of 'providingSerice' than a peer concept. I propose not including it in this list. The question of adding another option to provide this sort of information was briefly discussed in the Vienna meeting and it was felt that our intention was to not provide a full set of objects to support redundancy. I propose we do not add this object at this time." Sharon -----Original Message----- From: Chisholm, Sharon [CAR:0S00:EXCH] Sent: Sunday, February 15, 2004 2:11 PM To: entmib@ietf.org Subject: [Entmib] FW: [psg.com #332] AutoReply: More Standby State/Status Issues The following is the proposed resolution to entstate-332. The issue will be considered closed pending the proposed edit being done. [Note that this text may be affected by the resolution of other issues] In the description of StandybyStatus add " A value 'providingSharedService' means the entity is providing service that is summed with the service provided by other entities." And add the following enumeration: " providingSharedService (5) " In the description to entStateStandby replace " If this entity cannot operate in a standby role, the value of this object will always be 'providingService'." Sharon -----Original Message----- From: rt+entity-state@rt.psg.com [mailto:rt+entity-state@rt.psg.com] Sent: Friday, February 13, 2004 12:13 PM To: Chisholm, Sharon [CAR:0S00:EXCH] Subject: [psg.com #332] AutoReply: More Standby State/Status Issues <clip> ------------------------------------------------------------------------- David T. Perkins [dperkins@dsperkins.com] ""Standby status" items should be renamed to "standby state" to be consistent with the other naming of other items in the MIB module. (Items are "state" when value is an enumerated int, and "status" when the value is a bit string.) There is one important value missing from the enums for standby. It is the one that means that the service output is combined with other entities. This is commonly found with power supplies where the output is "summed". Section 2.2 is incorrect. It implies that by reading the value of entStandbyStatus for all entities, then entities can be classified as redundant (or protected). This is not true. Say that there are two entities that are identical and provide a "protected" service. At any time, only one is providing service, and the other is standing by protecting the other. A "protection switch" causes the roles to change (that is the one providing service will switch to standing by, and the one standing by will start to providing service). In general, this MIB module does not provide enough information to determine 1) which entities are protected, 2) the relationship between the entities that are protected and the entities providing protection. " David T. Perkins [dperkins@dsperkins.com] "Here is a replacement for TC StandbyStatus: StandbyState ::= TEXTUAL- CONVENTION STATUS current DESCRIPTION " Represents the possible values of standby state. The value 'notAvailable(1)' means that no information is available on the standby state for the entity. The value 'hotStandby(2)' means the entity is not providing service, and will be immediately able to start providing service for the entity being backed up without the need for initialization activity, and will contain the same information as the entity being backed up. The value 'coldStandy(3)' means the entity is not providing service, and will be able to start providing service for an entity (possibly one from a set) being backed up, and will require some initialization activity. The value 'providingService(4)' means the entity is providing service. The value 'providingSharedService(5)' means the entity is providing service that is summed with the service provided by other entities." REFERENCE "ITU Recommendation X.731, 'Information Technology - Open Systems Interconnection - System Management: State Management Function', 1992" SYNTAX INTEGER { notAvailable(1), hotStandby(2), coldStandby(3), providingService(4), providingSharedService (5) } And a replacement for entStateStandby: entStateStandby OBJECT-TYPE SYNTAX StandbyStatus MAX-ACCESS read-only STATUS current DESCRIPTION "The standby state for this entity. A value of 'notAvailable' means that this entity is unable to determine standby state. Some entities will exhibit only a subset of the remaining standby state values. If this entity cannot operate in a standby role, then the value with always be 'providingService'." ::= { entStateEntry 6 } " _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib
- RE: [Entmib] FW: [psg.com #332] AutoReply: More S… Sharon Chisholm
- RE: [Entmib] FW: [psg.com #332] AutoReply: More S… Sharon Chisholm