Re: [OPSAWG] [IVY] side meeting #119: Power Metrics: concrete usage example
Simon Leinen <simon.leinen@switch.ch> Tue, 26 March 2024 14:00 UTC
Return-Path: <simon.leinen@switch.ch>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58FB0C14F616; Tue, 26 Mar 2024 07:00:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=switch.ch
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id woiP-uuOZ5sX; Tue, 26 Mar 2024 07:00:31 -0700 (PDT)
Received: from mx4.switch.ch (mx4.switch.ch [85.235.88.35]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E23EC14F699; Tue, 26 Mar 2024 07:00:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=switch.ch; l=1601; s=selector1; t=1711461631; h=from:to:cc:subject:in-reply-to:references:date: message-id:mime-version; bh=wAmzjWyK5nf4/n8YQIVbRpOT2tU+kd1mPp+JJEubZ14=; b=C8MUcc+ELJnDM4O4adkmzo5dPw8l2nSocIR1yoNMaENkC9JE5cF8Tyb2 9C4hdpMVepLwEhDUNn+tO/Y+kUJknC7R7NTtlZwD9Y3ErcGWud5aE/3Hm qAIPE/puJO8HKry1bMOrp4gGA2saSPpmfSCz3MHuiY+MLEvg+K6eZI7kd T0vAdPRwwTFe4S3pTcrXzk/FK/Dc9kLlFthmOBWVLsUBgp5Y5V7wMa3sb fJ9migKdMFhhEkgjx5qRQTFl2qXGBx9uyUGcdTgFq0ktIuFB1yDTigoKJ kJUaSuhofBy3ONRdSucADPKQQZRmbx6uuPyL0rVZntpMMyE1ilCt4ZbMY Q==;
X-IronPort-MAIL-FROM: simon.leinen@switch.ch
X-IronPort-AV: E=Sophos;i="6.07,156,1708383600"; d="scan'208";a="7504313"
Received: from unknown (HELO SWH-S04-EXC2.swd.switch.ch) ([172.16.60.12]) by mx4int.switch.ch with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 26 Mar 2024 15:00:28 +0100
Received: from macsl (172.16.60.33) by SWH-S04-EXC2.swd.switch.ch (172.16.60.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.32; Tue, 26 Mar 2024 15:00:27 +0100
From: Simon Leinen <simon.leinen@switch.ch>
To: "Jan Lindblad (jlindbla)" <jlindbla=40cisco.com@dmarc.ietf.org>
CC: Carlos Pignataro <cpignata@gmail.com>, "Marisol Palmero Amador (mpalmero)" <mpalmero=40cisco.com@dmarc.ietf.org>, opsawg@ietf.org, e-impact@ietf.org, inventory-yang@ietf.org, Alexander Clemm <alex@clemm.org>, "Alberto Rodriguez-Natal (natal)" <natal@cisco.com>, Ron Bonica <rbonica@juniper.net>, Mahesh Jethanandani <mjethanandani@gmail.com>, "Ali Rezaki (Nokia)" <ali.rezaki@nokia.com>, "Suresh Krishnan (sureshk)" <sureshk@cisco.com>, Jari Arkko <jari.arkko@gmail.com>
In-Reply-To: <B949745F-B8AC-4BCB-ADF8-3AC669F2F326@cisco.com> (Jan Lindblad's message of "Tue, 26 Mar 2024 09:46:48 +0000")
References: <DM4PR11MB52778685A92225856D21BB16C5282@DM4PR11MB5277.namprd11.prod.outlook.com> <CACe62Mnii4FMwkYAtvDHPEriy_BmEx4MtLtte1s1KKxFShJHZg@mail.gmail.com> <B949745F-B8AC-4BCB-ADF8-3AC669F2F326@cisco.com>
User-Agent: Gnus/5.13 (Gnus v5.13)
Date: Tue, 26 Mar 2024 15:00:27 +0100
Message-ID: <lzv859ks90.fsf@switch.ch>
MIME-Version: 1.0
Content-Type: text/plain
X-Originating-IP: [172.16.60.33]
X-ClientProxiedBy: SWH-S06-EXC4.swd.switch.ch (172.16.60.18) To SWH-S04-EXC2.swd.switch.ch (172.16.60.12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/W7vHFIlqxGL1HI82KQeD2uElcfM>
Subject: Re: [OPSAWG] [IVY] side meeting #119: Power Metrics: concrete usage example
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Mar 2024 14:00:36 -0000
Jan Lindblad (jlindbla) writes: > There are a number of us IETF participants, from a rather long list of > equipment providers as well as operators, that are working on solving > very concrete and current issues with respect to energy management in > network equipment. For example, we have noted that most devices can > report their energy and/or power usage, but they all do that in > different ways and with different precision. We see a real need to > standardize this, in order to realize use cases many operators are > asking for, somewhat urgently. As an operator, I can second this. We are adding continuous and consistent power consumption monitoring across our fleet of routers. Most of them expose their overall energy consumption (as well as that of some components) via the wonderful ENTITY-MIB/ENTITY-SENSOR-MIB or close vendor-specific cousins of those. But (even within one vendor) the representation of these sensors varies widely, which makes it complicated to (a) locate the relevant/best sensors and (b) deal with the different representations - some devices have separate volt/ampere sensors, others have watts, some measure performance into the PSU, some out of, some both. Not to mention funny bugs, e.g. claiming the power sensor is in "dBm" units where the values clearly indicate Watts (280 dBm aren't really plausible :-). It's painful and already cost me a lot of time, which leads me to suspect that router power consumption is not widely monitored in the industry (I could be wrong though, maybe people use other methods). -- Simnon.
- [OPSAWG] side meeting #119: Power Metrics: concre… Marisol Palmero Amador (mpalmero)
- Re: [OPSAWG] side meeting #119: Power Metrics: co… Alexander Clemm
- Re: [OPSAWG] side meeting #119: Power Metrics: co… Carlos Pignataro
- Re: [OPSAWG] side meeting #119: Power Metrics: co… Rob Wilton (rwilton)
- Re: [OPSAWG] side meeting #119: Power Metrics: co… Marisol Palmero Amador (mpalmero)
- Re: [OPSAWG] side meeting #119: Power Metrics: co… Carlos Pignataro
- Re: [OPSAWG] side meeting #119: Power Metrics: co… Suresh Krishnan (sureshk)
- Re: [OPSAWG] side meeting #119: Power Metrics: co… Michael Richardson
- Re: [OPSAWG] side meeting #119: Power Metrics: co… Rob Wilton (rwilton)
- Re: [OPSAWG] side meeting #119: Power Metrics: co… Rob Wilton (rwilton)
- Re: [OPSAWG] [IVY] side meeting #119: Power Metri… Michael Richardson
- Re: [OPSAWG] side meeting #119: Power Metrics: co… Carlos Pignataro
- Re: [OPSAWG] side meeting #119: Power Metrics: co… Rob Wilton (rwilton)
- Re: [OPSAWG] [IVY] side meeting #119: Power Metri… Jan Lindblad (jlindbla)
- Re: [OPSAWG] side meeting #119: Power Metrics: co… Carlos Pignataro
- Re: [OPSAWG] [IVY] side meeting #119: Power Metri… Simon Leinen
- Re: [OPSAWG] side meeting #119: Power Metrics: co… Carlos Pignataro
- Re: [OPSAWG] [IVY] side meeting #119: Power Metri… Carlos Pignataro
- Re: [OPSAWG] [E-impact] side meeting #119: Power … Suresh Krishnan
- Re: [OPSAWG] side meeting #119: Power Metrics: co… Jari Arkko