How would you like to have the desired counters?
Say, you would receive power data for a defined timeslot and we have
to watch for the counters in that same timeslot? Or a constant
reporting of the data on the network device?
Yes, we need to match the traffic counters with the power values we
measure over the same time interval. We do not need the counters live
though, it's no problem if we get them after the measurement is completed.
So far, we worked with counters collected every 5 minutes (the SNMP
default as far as I know). The frequency of the counter data does not
matter much, but the finer-grained the better for us. If you are already
collecting this data somehow, it is most likely enough for our needs.
--
Romain
> Regards, Urs
>
> *Von: *Romain Jacob
jacobr@ethz.ch
> *Datum: *Freitag, 21. Juni 2024 um 16:47
> *An: *Müller Urs (IT-PTR-CEN1-SL4)
urs.bf.mueller@sbb.ch
> *Cc: *Vanbever Laurent
lvanbever@ethz.ch, swinog@lists.swinog.ch
>
swinog@lists.swinog.ch
> *Betreff: *Re: AW: [swinog] Research project on Sustainable Networking
>
> Dear Urs,
>
> Let me keep the list on to reply to some questions, as you are not the
> first to ask:
>
> * Most routers we are interested in have multiple power supply. Our
> strategy is to use one measurement unit per PSU. That demands
> extra hardware, but we wouldn't want to have two PSU connected to
> the same power meter anyway as this would create a potential
> single point of failure.
> * Network connectivity for the Pi is required but *does work behind
> a firewall*. The only requirement is that the Pi must be able to
> connect to the Internet.
>
> Thanks again to those who already reached out!
>
> Best,
> --
> Romain
>
> On 21/06/2024 16:24, Mueller Urs SBB CFF FFS wrote:
>
> Hello Romain
>
> Could you please go into more detail concerning the phrase:
>
> /the Pi needs to be connected to a publicly reachable network via
> RJ45/
>
> Does this mean, you want to be able to remote to this pi? Or does
> the pi only <send> data and it would be ok to have it behind a
> firewall?
>
> How about router with dual power supply?
>
> You may also contact me off list for more informations, perhaps we
> may share such data.
>
> Kind regards, Urs
>
> SBB AG
>
> Poststrasse 6, 3072 Ostermundigen
>
> urs.bf.mueller@sbb.ch
mailto:urs.bf.mueller@sbb.ch / www.sbb.ch
>
http://www.sbb.ch/
>
> *Von: *Romain Jacob via swinog
swinog@lists.swinog.ch
>
mailto:swinog@lists.swinog.ch
> *Datum: *Donnerstag, 20. Juni 2024 um 17:00
> *An: *swinog@lists.swinog.ch
swinog@lists.swinog.ch
>
mailto:swinog@lists.swinog.ch
> *Cc: *Vanbever Laurent
lvanbever@ethz.ch mailto:lvanbever@ethz.ch
> *Betreff: *[swinog] Research project on Sustainable Networking
>
> Dear all,
>
> My name is Romain; I’m a researcher at ETH Zürich working with
> Laurent Vanbever. I have led projects on sustainable networking
> for about 2+ years now.
>
> One important challenge the academic community currently faces is
> the lack of quality data for the energy a router or switch
> consumes. To address this, we work on fine-grained power modeling
> of network devices, and we need data to validate their accuracy
> “in the wild.” To facilitate that, we worked to realize the vision
> of “RIPE Atlas for power data” I pitched at last winter’s RIPE
> meeting
https://ripe87.ripe.net/archives/video/1143/. And I’m
> happy to say that we are ready to start distributing measurement
> units!
>
> Concretely, we are looking for people willing to
>
> 1. Install measurement units in series of each PSU of routers and
> switches. The measurement unit is an MCP39F511N
>
https://www.microchip.com/en-us/development-tool/ADM00706
> power meter combined with a Raspberry Pi for management and
> data collection:
>
> We will provide the appropriate cabling. To control the unit, the
> Pi needs to be connected to a publicly reachable network via RJ45
> (WiFi connectivity is technically possible as well, but requires
> additional setup)
>
> 2. Share device-specific data with us, including at minima
>
> 1. Packet and/or byte counters for the active device interfaces.
> 2. Types and numbers of transceivers plugged in.
>
> and optionally
>
> 3. PSU-internal measurements
> 4. Operating system version
> 5. Fan speeds
> 6. CPU load
> 7. Average room temperature conditions
>
> 3. Let the measurement run for at least one week.
> 4. Send us back the measurement units (we provide pre-labeled
> packaging for that).
>
> In return, we can only offer our sincere gratitude and the
> guarantee that your effort will contribute to the progress of
> science! I know it s not much, but I hope that’s worth something :-)
>
> ➡️ If you are interested, please let me know by replying to this
> email. Thank you in advance!
>
> Note: We want to publish the collected data (in an anonymized
> way), but that is *optional*. If you are willing to contribute but
> your organization opposes the data sharing, we won’t publish it,
> and we will sign NDAs if necessary.
>
> Thank you again for reading! Looking forward to hearing from 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 G81
> 8092 Zurich
> +41 7 68 16 88 22
>
> --
>
> *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 G81
> 8092 Zurich
> +41 7 68 16 88 22
>
--
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 G81
8092 Zurich
+41 7 68 16 88 22