enLogic PDUs 2.0

Help
1

Hi.

I thought this is less of a Device Request, but more an open discussion about the 2.0 series of enLogic PDUs.

With the new 2.0 firmware, enLogic rolled a new MIB (ENLOGIC-PDU2-MIB), but with the same base sysObjectID as the previous series firmware, .1.3.6.1.4.1.38446.1

Of course, the object IDs for the basic variables (hardware, serial number and version) changed.

I’m willing to contribute in order to have support for enLogic PDU 2.0.

But I’m hesitating on how to do it, as the current enlogic-pdu model PDU is for the 1.x series.

Do you think it’s a good idea to create a enlogic-pdu-v2 model matching the value of ENLOGIC-PDU2-MIB::pduNamePlateFirmwareVersion.1 (starts with “2.0”) ?

If we agree on something, I can start working on it and then continue the discussion in an actual pull request.

The only issue is I don’t have any enLogic 1.0 PDU on hand, to test it doesn’t breaks the previous series.

Thanks.

2

Hi.

Quick update, I started working on it and so far so good.

Strangely, the sensor part didn’t changed from the 1.0 branch, only the " pduNamePlate" part changed (where model, serial number etc… are given)

So the content in includes/discovery/sensors/(current|power|pre-cache|state|voltage)/enlogic-pdu2.inc.php files is only a big sed of includes/discovery/sensors/(current|power|pre-cache|state|voltage)/enlogic-pdu.inc.php

I still have some tests/polish to do, when it’ll be functional, I’ll create a PR so we can discuss the technical side.

Thanks

3

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.