Re: [Entmib] FW: [ #309] AutoReply: Operational State Names and Concepts

"David T. Perkins" <> Thu, 12 February 2004 22:15 UTC

Received: from ( []) by (8.9.1a/8.9.1a) with ESMTP id RAA19334 for <>; Thu, 12 Feb 2004 17:15:30 -0500 (EST)
Received: from localhost.localdomain ([] by with esmtp (Exim 4.20) id 1ArP6s-00045s-JC; Thu, 12 Feb 2004 17:15:02 -0500
Received: from ([] by with esmtp (Exim 4.20) id 1ArP6N-0003ut-OM for; Thu, 12 Feb 2004 17:14:31 -0500
Received: from ietf-mx ( []) by (8.9.1a/8.9.1a) with ESMTP id RAA19297 for <>; Thu, 12 Feb 2004 17:14:28 -0500 (EST)
Received: from ietf-mx ([]) by ietf-mx with esmtp (Exim 4.12) id 1ArP6J-0003Gn-00 for; Thu, 12 Feb 2004 17:14:27 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1ArP5Q-0003CA-00 for; Thu, 12 Feb 2004 17:13:33 -0500
Received: from ([]) by ietf-mx with esmtp (Exim 4.12) id 1ArP4s-00037E-00 for; Thu, 12 Feb 2004 17:12:58 -0500
Received: from ( []) by (8.11.6/8.11.6) with ESMTP id i1CMCs332011; Thu, 12 Feb 2004 14:12:55 -0800
Message-Id: <>
X-Sender: dperkins@
X-Mailer: QUALCOMM Windows Eudora Version
Date: Thu, 12 Feb 2004 14:12:49 -0800
To: Sharon Chisholm <>,
From: "David T. Perkins" <>
Subject: Re: [Entmib] FW: [ #309] AutoReply: Operational State Names and Concepts
In-Reply-To: <>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <>, <>
List-Id: IETF Entity MIB WG <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>


implementing this object to match the semantics of X.731 will be difficult
(if not impossible) if the hardware was not designed this way. And
for some hardware (such as a power supplys) it may not be economically
feasible to implement. (On a power supply, it may "disabled" by
disconnecting the input power. If so, you cannot determine if
it is working (that is, delivering output power within it's
rated range) unless you supply input power. You could fake the
oper state value by saving the last value of oper state when admin
state was "unlocked" and returning it while the admin state is "locked".)

Because of this issue, I believe that a new value needs to be added,
such as "disabledDue2Admin". Also, the other values for object
IF-MIB::ifOperStatus should be added. These values are:
      testing(3),   -- in some test mode
      unknown(4),   -- status can not be determined
                              -- for some reason.
      notPresent(6),    -- some component is missing
      lowerLayerDown(7) -- down due to state of
                                  -- lower-layer interface(s)
But "lowerLayerDown" which be renamed to "containedNotEnabled".

Secondly, I would name the terms "up" and "down" instead of
"enabled" and "disabled", since enabled/disabled seem to be
admin status and not operational state!

Thirdly, the relationship between values of contained entities
needs to be defined. (Object IF-MIB::ifOperStatus supports this.)    

At 02:17 PM 2/11/2004 -0500, Sharon Chisholm wrote:
>The following is the proposed resolution to entstate-309. The issue will be
>considered closed pending the proposed edit being done.
>Add the following text to entStateOper 
>"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
>-----Original Message-----
>From: entity-state [] 
>Sent: Tuesday, January 13, 2004 2:57 AM
>To: Chisholm, Sharon [CAR:0S00:EXCH]
>Subject: [ #309] AutoReply: Operational State Names and Concepts
>Keith McCloghrie []
>"'enabled' and 'disabled' to me imply that an admin state, i.e., if
>>   I saw an operState of 'disabled', or a entStateOperDisabled
>>   I'd look for the knob by which I could issue the enable command to
>>   it again.
>>   for most things, I believe you have to turn them on to see if they
>>   if they don't work, you can turn them off again, and label
>them "inoperable",
>>   but what that means is that they were inoperable the last time they
>>   turned on, and it doesn't necessarily mean they are still
>inoperable, e.g.,
>>   if something was inoperable the last time it was turned on and has
>>   been repaired, but not yet turned on again, is it still
>inoperable ??
>>   That is, neither 'disabled' nor 'inoperable' is the right term for
>> operState.
/david t. perkins 

Entmib mailing list