Re: [eman] Read-Only or Read-Write EMAN MIBs

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Mon, 17 February 2014 10:05 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: eman@ietfa.amsl.com
Delivered-To: eman@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C66E51A0453 for <eman@ietfa.amsl.com>; Mon, 17 Feb 2014 02:05:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level:
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i_O8E8WVYVF5 for <eman@ietfa.amsl.com>; Mon, 17 Feb 2014 02:05:55 -0800 (PST)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 5558C1A03C9 for <eman@ietf.org>; Mon, 17 Feb 2014 02:05:55 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgILAGHeAVOHCzIm/2dsb2JhbABWA4JlIThXqAqXKoEcFnSCJQEBAQEDEig0CwwCAgIBCA0BAgEEAQEBChQJBxsXFAkIAgQODRqHYwGfP6wLFwSOFTchEAcGC4MTgRQEmV6FPYs0gy2CKg
X-IronPort-AV: E=Sophos;i="4.95,859,1384318800"; d="scan'208";a="49813473"
Received: from unknown (HELO p-us1-erheast-smtpauth.us1.avaya.com) ([135.11.50.38]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 17 Feb 2014 05:05:52 -0500
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by p-us1-erheast-out.us1.avaya.com with ESMTP/TLS/AES128-SHA; 17 Feb 2014 04:53:00 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.03.0174.001; Mon, 17 Feb 2014 05:05:50 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Thread-Topic: [eman] Read-Only or Read-Write EMAN MIBs
Thread-Index: AQHC6u7uBAKsxvXaYoAFJCbQSShBjJrRolswgAAD1SD///NggIAAH+ZA
Date: Mon, 17 Feb 2014 10:05:50 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA2E41B759@AZ-FFEXMB04.global.avaya.com>
References: <88A474D1-677D-4BA0-8399-0429A095AE45@lucidvision.com> <001801cf2bbc$3b43f870$b1cbe950$@prantl.name> <9904FB1B0159DA42B0B887B7FA8119CA2E41B63A@AZ-FFEXMB04.global.avaya.com> <20140217091027.GA96287@elstar.local>
In-Reply-To: <20140217091027.GA96287@elstar.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.64.58.46]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/eman/fc9mrxuAQDNmAdFT72ni_zV8Zqo
Cc: 'eman mailing list' <eman@ietf.org>
Subject: Re: [eman] Read-Only or Read-Write EMAN MIBs
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman/>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 10:05:58 -0000

Yes, this looks like a good strategy. 

Regards,

Dan


> -----Original Message-----
> From: Juergen Schoenwaelder [mailto:j.schoenwaelder@jacobs-
> university.de]
> Sent: Monday, February 17, 2014 11:10 AM
> To: Romascanu, Dan (Dan)
> Cc: David Prantl; 'Thomas Nadeau'; 'eman mailing list'
> Subject: Re: [eman] Read-Only or Read-Write EMAN MIBs
> 
> On Mon, Feb 17, 2014 at 09:00:34AM +0000, Romascanu, Dan (Dan) wrote:
> > Hi David,
> >
> > I have a question about the read-only implementation of draft-ietf-eman-
> battery-mib . There are six writeable objects in the MIB module
> batteryAlarmLowCharge, batteryAlarmLowVoltage,
> batteryAlarmLowCapacity, batteryAlarmHighCycleCount,
> batteryAlarmHighTemperature, batteryAlarmLowTemperature which set
> thresholds for notifications. In a read-only implementation how are these
> objects set - using CLI instead and then the MIB objects are used to display
> the values set by CLI? Or you do not do notifications at all?
> >
> 
> The batteryCompliance seems to allow both options. You are not required to
> implement batteryAlarmThresholdsGroup. If you choose to do so, you are
> not required to implement the objects read-write. Of course, if you support
> threshold notifications and implement read-only, the parameters must be
> set via some other mechanism.
> 
> It may make sense to make the threshold objects conditionally mandatory to
> implement (at least read-only) if the batteryNotificationsGroup is
> implemented so that management applications can see the thresholds
> generating the notifications.
> 
> /js
> 
> --
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>