We use Cisco

in the file /etc/nav/ipdevpoll.conf I have

# 1 minute statistics [job_1minstats] interval = 1m plugins = statsystem statmulticast statsensors

I must add poe ?

Le 11.09.20 à 10:59, Morten Brekkevold a écrit :

They do not. PoE power usage data is collected ever 60 seconds (in the 1minstats ipdevpoll job) - however, it requires proper support for the POWER-ETHERNET-MIB in your device, specifically the `pethMainPseConsumptionPower` object.

What vendor is your device from?

Hi,

here's the debug trace

2020-09-14 13:22:32,245 [DEBUG plugins.statsystem.statsystem] [1minstats ca-bi-02.epfl.ch] Got poe data {OID('.2'): {'pethMainPsePower': 1825, 'pethMainPseOperStatus': 1, 'pethMainPseConsumptionPower': 147, 0: OID('.2')}, OID('.5'): {'pethMainPsePower': 1825, 'pethMainPseOperStatus': 1, 'pethMainPseConsumptionPower': 53, 0: OID('.5')}, OID('.6'): {'pethMainPsePower': 1825, 'pethMainPseOperStatus': 1, 'pethMainPseConsumptionPower': 40, 0: OID('.6')}, OID('.7'): {'pethMainPsePower': 1825, 'pethMainPseOperStatus': 1, 'pethMainPseConsumptionPower': 51, 0: OID('.7')}}

Le 11.09.20 à 14:03, Morten Brekkevold a écrit :

On Fri, 11 Sep 2020 11:38:03 +0200 Biselx Nicolas nicolas.biselx@epfl.ch wrote:

...

# 1 minute statistics [job_1minstats] interval = 1m plugins = statsystem statmulticast statsensors

I must add poe ?

No, the data is collected by the statsystem plugin, which is already in your plugin list.

As far as I know, this should work just fine on Cisco, but it wouldn't be unheard of that the implementation varies between different Cisco platforms.

By adding the following line to NAV's `logging.conf`, you can make the statsystem plugin debug log the PoE data it collects (among other things) for dispatch to Graphite:

nav.ipdevpoll.plugins.statsystem = DEBUG

Either restart ipdevpoll, or run a manual `1minstats` job against your affected devices using the `ipdevpoll -J 1minstats -n [AFFECTED-DEVICE]` command line. What do the logs say about PoE?

With your help, I finally found the problem.

I added a blacklist.conf file in /etc/carbon/ and by default the graphs starting with this are deleted:

.. ^. .$

I've put in a comment #.. and everything works fine.

I am sorry for the inconvenience. Many thanks for the development of NAV

Regards, Nicolas

Le 15.09.20 à 08:21, Morten Brekkevold a écrit :

On Mon, 14 Sep 2020 13:29:27 +0200 Biselx Nicolas nicolas.biselx@epfl.ch wrote:

...

Hi,

here's the debug trace

[snip]

...

{ OID(".2"): { "pethMainPsePower": 1825, "pethMainPseOperStatus": 1, "pethMainPseConsumptionPower": 147, 0: OID(".2"), }, OID(".5"): { "pethMainPsePower": 1825, "pethMainPseOperStatus": 1, "pethMainPseConsumptionPower": 53, 0: OID(".5"), }, OID(".6"): { "pethMainPsePower": 1825, "pethMainPseOperStatus": 1, "pethMainPseConsumptionPower": 40, 0: OID(".6"), }, OID(".7"): { "pethMainPsePower": 1825, "pethMainPseOperStatus": 1, "pethMainPseConsumptionPower": 51, 0: OID(".7"), }, }

ipdevpoll does apparently pull real power data for 4 separate PoE groups here, so the problem must either be with getting the data stored in Graphite, or retrieved from Graphite.

I would attempt to use Graphite directly to render the contents of the expression `nav.devices.ca-bi-02_epfl_ch.system.power.*`, to confirm there is real power data stored there.

Furthermore, I would use the network tab of the browser's web developer tools to confirm that the NAV web ui is actually fetching the render data from said Graphite path, and getting a proper response with data in it.