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

"Thomas D. Nadeau" <tnadeau@lucidvision.com> Mon, 17 February 2014 12:45 UTC

References: <88A474D1-677D-4BA0-8399-0429A095AE45@lucidvision.com> <001801cf2bbc$3b43f870$b1cbe950$@prantl.name> <9904FB1B0159DA42B0B887B7FA8119CA2E41B63A@AZ-FFEXMB04.global.avaya.com> <20140217091027.GA96287@elstar.local>
Mime-Version: 1.0 (1.0)
In-Reply-To: <20140217091027.GA96287@elstar.local>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-Id: <DF8E18A1-292A-4913-A126-AC5487A81B9F@lucidvision.com>
From: "Thomas D. Nadeau" <tnadeau@lucidvision.com>
Date: Mon, 17 Feb 2014 07:45:23 -0500
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Archived-At: http://mailarchive.ietf.org/arch/msg/eman/R-vOXAh6Pji1cUinjOVFcKtRCaY
Cc: eman mailing list <eman@ietf.org>
Subject: Re: [eman] Read-Only or Read-Write EMAN MIBs
Precedence: list

> On Feb 17, 2014, at 4:10 AM, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
> 
>> 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.

	This is generally speaking, the normal mode of operation though right?  Maybe the approach here is to go through and make sure all of the conformance statements conditionally require the read-write objects at least read-only?

	Also, it would be good to hear from folks about how many actual read-write implementations exist, as well as read-write deployments. I forgot to include that in my original note last week.

	--Tom



> 
> /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/>
>

[eman] Read-Only or Read-Write EMAN MIBs Thomas Nadeau
Re: [eman] Read-Only or Read-Write EMAN MIBs Romascanu, Dan (Dan)
Re: [eman] Read-Only or Read-Write EMAN MIBs Juergen Schoenwaelder
Re: [eman] Read-Only or Read-Write EMAN MIBs Romascanu, Dan (Dan)
Re: [eman] Read-Only or Read-Write EMAN MIBs Juergen Schoenwaelder
Re: [eman] Read-Only or Read-Write EMAN MIBs Thomas Nadeau
Re: [eman] Read-Only or Read-Write EMAN MIBs Thomas Nadeau
Re: [eman] Read-Only or Read-Write EMAN MIBs Juergen Schoenwaelder
Re: [eman] Read-Only or Read-Write EMAN MIBs Thomas Nadeau
Re: [eman] Read-Only or Read-Write EMAN MIBs Bruce Nordman
Re: [eman] Read-Only or Read-Write EMAN MIBs Mouli Chandramouli (moulchan)
Re: [eman] Read-Only or Read-Write EMAN MIBs David Prantl
Re: [eman] Read-Only or Read-Write EMAN MIBs Romascanu, Dan (Dan)
Re: [eman] Read-Only or Read-Write EMAN MIBs Juergen Schoenwaelder
Re: [eman] Read-Only or Read-Write EMAN MIBs Romascanu, Dan (Dan)
Re: [eman] Read-Only or Read-Write EMAN MIBs Thomas D. Nadeau
Re: [eman] Read-Only or Read-Write EMAN MIBs John Parello (jparello)