IETF Logo Mail Archive

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

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Mon, 17 February 2014 09:00 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 036EA1A0394 for <eman@ietfa.amsl.com>; Mon, 17 Feb 2014 01:00:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.148
X-Spam-Level:
X-Spam-Status: No, score=-3.148 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 Si5OpQWIjtm5 for <eman@ietfa.amsl.com>; Mon, 17 Feb 2014 01:00:42 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id B843E1A02C3 for <eman@ietf.org>; Mon, 17 Feb 2014 01:00:41 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFANbOAVPGmAcV/2dsb2JhbABZgmUhOFe/M4EaFnSCJQEBAQEDAQEBDyg0FwQCAQgNBAQBAQsUCQcnCxQJCAIEARIIGodjAQyfNKwIEwSOGTc4BoMegRQEnxuLNIMtgio
X-IronPort-AV: E=Sophos;i="4.95,859,1384318800"; d="scan'208";a="43196340"
Received: from unknown (HELO co300216-co-erhwest-exch.avaya.com) ([198.152.7.21]) by de307622-de-outbound.net.avaya.com with ESMTP; 17 Feb 2014 04:00:37 -0500
Received: from unknown (HELO AZ-FFEXHC04.global.avaya.com) ([135.64.58.14]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/AES128-SHA; 17 Feb 2014 03:48:58 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC04.global.avaya.com ([135.64.58.14]) with mapi id 14.03.0174.001; Mon, 17 Feb 2014 10:00:35 +0100
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: David Prantl <david@prantl.name>, 'Thomas Nadeau' <tnadeau@lucidvision.com>, 'eman mailing list' <eman@ietf.org>
Thread-Topic: [eman] Read-Only or Read-Write EMAN MIBs
Thread-Index: AQHC6u7uBAKsxvXaYoAFJCbQSShBjJrRolswgAAD1SA=
Date: Mon, 17 Feb 2014 09:00:34 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA2E41B63A@AZ-FFEXMB04.global.avaya.com>
References: <88A474D1-677D-4BA0-8399-0429A095AE45@lucidvision.com> <001801cf2bbc$3b43f870$b1cbe950$@prantl.name>
In-Reply-To: <001801cf2bbc$3b43f870$b1cbe950$@prantl.name>
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/njNJNFY-B11bXLapcd0wDJZ1eMk
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 09:00:44 -0000

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? 

Thanks and Regards,

Dan



> -----Original Message-----
> From: eman [mailto:eman-bounces@ietf.org] On Behalf Of David Prantl
> Sent: Monday, February 17, 2014 10:43 AM
> To: 'Thomas Nadeau'; 'eman mailing list'
> Subject: Re: [eman] Read-Only or Read-Write EMAN MIBs
> 
> Hi,
> 
> Currently the Cisco Energywise Manager/Joulex Energy Manager only has
> been used with read-only implementations of the EMAN-MIB.
> 
> Thanks
> Mouli
> 
> 
> -----Original Message-----
> From: eman [mailto:eman-bounces@ietf.org] On Behalf Of Thomas Nadeau
> Sent: Dienstag, 11. Februar 2014 17:03
> To: eman mailing list
> Subject: [eman] Read-Only or Read-Write EMAN MIBs
> 
> 
> 	EMAN WG:
> 
> 	The EMAN WG currently has three MIBs that are WG drafts:
> 
> 	draft-ietf-eman-battery-mib-11
> 	draft-ietf-eman-energy-aware-mib-14
> 	draft-ietf-eman-energy-monitoring-mib-08
> 
> 	At present Benoit as AD, the Ops Directorate and MIB Doctors are
> preparing a statement to WGs that strongly recommends against MIBs with
> writable objects unless the working group has a strong consensus to do so.
> The current *draft* of the statement is listed here for your information:
> 
> The OPS area recommends the use of NETCONF/YANG standards for
> configuration.
> IETF working groups are therefore encouraged to use the NETCONF/YANG
> standards for configuration, specifically in new charters. SNMP MIB modules
> modifying persistent configuration state should only be produced by working
> groups in cases of clear utility and overwhelming consensus to use SNMP
> write operations for configuration.
> 
> 	In an effort to head off any potential snafus during the IESG review
> of the three EMAN MIBs, I want to poll the WG for consensus on whether or
> not to make the current list of WG documents read-write or read-only. If
> there is not strong consensus to leave them read-write, Nevil and I will
> instruct the editors to edit the documents to remove writable objects.
> 
> 	Please post comments on this matter by Friday, February 14, 2014 at
> 9AM EDT.
> 
> 
> 	Tom
> 	EMAN WG Co-Chair
> 
> 
> 
> 
> _______________________________________________
> eman mailing list
> eman@ietf.org
> https://www.ietf.org/mailman/listinfo/eman

v2.23.0 | Report a Bug | By Email