[E-impact] Re: Digging into the source of SNMP data

Romain Jacob <jacobr@ethz.ch> Tue, 12 November 2024 23:04 UTC

Return-Path: <jacobr@ethz.ch>
X-Original-To: e-impact@ietfa.amsl.com
Delivered-To: e-impact@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 571DFC1840D1; Tue, 12 Nov 2024 15:04:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.904
X-Spam-Level:
X-Spam-Status: No, score=-1.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 6nM6jxQs_lXf; Tue, 12 Nov 2024 15:04:27 -0800 (PST)
Received: from mailg210.ethz.ch (mailg210.ethz.ch [IPv6:2001:67c:10ec:5606::21]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AE8CC14F6EA; Tue, 12 Nov 2024 15:04:26 -0800 (PST)
Received: from mailm113.d.ethz.ch (2001:67c:10ec:5602::25) by mailg210.ethz.ch (2001:67c:10ec:5606::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.39; Wed, 13 Nov 2024 00:04:12 +0100
Received: from [192.168.1.27] (31.10.155.204) by mailm113.d.ethz.ch (2001:67c:10ec:5602::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.39; Wed, 13 Nov 2024 00:04:23 +0100
Message-ID: <2ed84f28-6a24-44e8-98eb-655a335c1263@ethz.ch>
Date: Wed, 13 Nov 2024 00:05:09 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: emile.stephan@orange.com, Toerless Eckert <tte@cs.fau.de>
References: <1de6f145-3686-4320-8776-32f67d6affc9@ethz.ch> <Zyztq4Yz5o12L9lI@faui48e.informatik.uni-erlangen.de> <feab0b455c0b484e9e5fa8b5a9bb38fb@orange.com>
From: Romain Jacob <jacobr@ethz.ch>
Content-Language: en-US
In-Reply-To: <feab0b455c0b484e9e5fa8b5a9bb38fb@orange.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms000706020707080005010504"
X-Originating-IP: [31.10.155.204]
X-ClientProxiedBy: mailm216.d.ethz.ch (2001:67c:10ec:5603::30) To mailm113.d.ethz.ch (2001:67c:10ec:5602::25)
Message-ID-Hash: QQTPGRBENAGUQ5E4MCB6WAGIQPJF276E
X-Message-ID-Hash: QQTPGRBENAGUQ5E4MCB6WAGIQPJF276E
X-MailFrom: jacobr@ethz.ch
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "green@ietf.org" <green@ietf.org>, "e-impact@ietf.org" <e-impact@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [E-impact] Re: Digging into the source of SNMP data
List-Id: Environmental impacts of the Internet <e-impact.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/e-impact/NqirQsoRrH5sfm-EPfSzWqXVIls>
List-Archive: <https://mailarchive.ietf.org/arch/browse/e-impact>
List-Help: <mailto:e-impact-request@ietf.org?subject=help>
List-Owner: <mailto:e-impact-owner@ietf.org>
List-Post: <mailto:e-impact@ietf.org>
List-Subscribe: <mailto:e-impact-join@ietf.org>
List-Unsubscribe: <mailto:e-impact-leave@ietf.org>

Hi everyone,

I got replies that make me wonder if my second email was correctly 
received. Trying to resend...

> Which router product/model are you using , and which MIB OIDs are you using ?

In that particular case, that's a Cisco 8201-32FH. I am not entirely 
sure about the exact MIB since I'm not collecting the data myself. Simon 
Leinen, from SWITCH, put this together (Many thanks again, Simon!).

AFAIU, the relevant MIB entries can be read from this file [1].

Cheers, -- Romain

[1] 
https://github.com/sleinen/snmp-session/blob/master/test/get-cisco-power-usage.pl 


On 08/11/2024 11:53, emile.stephan@orange.com wrote:
> Hi Romain
>
> Many thanks for providing such input. This issues can generate a lot of exchange. So imo to avoid many clarification question, it should be great that you share more information on the platform you are using (MIB specs, platform...).
>
> Best regards
> Emile
>
>
> -----Original Message-----
> From: Toerless Eckert<tte@cs.fau.de>  
> Sent: jeudi 7 novembre 2024 17:41
> To: Romain Jacob<jacobr@ethz.ch>
> Cc:e-impact@ietf.org;green@ietf.org
> Subject: [E-impact] Re: Digging into the source of SNMP data
>
> --------------------------------------------------------------------------------------------------------------
> CAUTION : This email originated outside the company. Do not click on any links or open attachments unless you are expecting them from the sender.
>
> ATTENTION : Cet e-mail provient de l'extérieur de l'entreprise. Ne cliquez pas sur les liens ou n'ouvrez pas les pièces jointes à moins de connaitre l'expéditeur.
> --------------------------------------------------------------------------------------------------------------
>
> I wonder if questions like this might now be more appropriate to thegreen@ietf.org  WG mailing list given how that one seems to be mostly around instrumenting routers with such measurement options. Cc'ed.
>
> Which router product/model are you using , and which MIB OIDs are you using ?
>
> I remember from the past routers with separate environmental support hardware, so i would not want to exclude that there may be different sources of truth.
>
> Cheers
>      Toerless
>
> On Thu, Nov 07, 2024 at 05:29:25PM +0100, Romain Jacob wrote:
>> Hello everyone,
>>
>> I have access to power data collected via SNMP. The numbers do not
>> match the sensor data that I can get manually from the router with
>> commands like `sh env all` or similar, which makes me wonder where the
>> power data that I get from SNMP comes from, or how it is preprocessed before it is piped to SNMP.
>>
>> If some of you have any clues or pointers, I'd be very interested :-)
>>
>> Thanks,
>>
>> --
>> Romain JACOB
>> Postdoctoral Researcher
>> ETH Zurich
>> Networked Systems Group (NSG)
>> Lead: Prof. Laurent Vanbever
>> www.romainjacob.net  <https://www.romainjacob.net/>  @RJacobPartner
>> <https://twitter.com/RJacobPartner>
>> @jacobr@discuss.systems<https://discuss.systems/@jacobr>  
>> Gloriastrasse 35, ETZ G84
>> 8092 Zurich
>> +41 7 68 16 88 22
>
>
>> --
>> E-impact mailing list --e-impact@ietf.org  To unsubscribe send an
>> email toe-impact-leave@ietf.org
>
> --
> ---
> tte@cs.fau.de
>
> --
> E-impact mailing list --e-impact@ietf.org  To unsubscribe send an email toe-impact-leave@ietf.org
> ____________________________________________________________________________________________________________
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
-- 
Romain JACOB
Postdoctoral Researcher
ETH Zurich
Networked Systems Group (NSG)
Lead: Prof. Laurent Vanbever
www.romainjacob.net <https://www.romainjacob.net/>
@RJacobPartner <https://twitter.com/RJacobPartner>
@jacobr@discuss.systems <https://discuss.systems/@jacobr>
Gloriastrasse 35, ETZ G84
8092 Zurich
+41 7 68 16 88 22