FW: [psg.com #73] AutoReply: AlatrmStatusTC - notSupported versus indeterminate

"Sharon Chisholm" <[email protected]>
Newsgroups gmane.ietf.entmib
Message-ID <[email protected]>
Hi

Proposed Resolution for ent-state-73:

In the description of entStateAlarm replace"

      "The alarm status for this entity. It does not include
       the severity of alarms raised on child components."

With
      "The alarm status for this entity. It does not include
       the severity of alarms raised on child components.

       A value of 'notSupported' means the entity does not
       support the alarm status object. 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."

Sharon

-----Original Message-----
From: entity-state [mailto:[email protected]] 
Sent: Monday, July 14, 2003 12:58 PM
To: Chisholm, Sharon [CAR:0S00:EXCH]
Subject: [psg.com #73] AutoReply: AlatrmStatusTC - notSupported versus
indeterminate
<clip>
-------------------------------------------------------------------------
Romascanu, Dan (Dan) [[email protected]]

"A3) AlarmStatusTC - what does setting notSupported(0) bit mean? Is not 
this same as indeterminate(7)?"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.