How many votes does it take for an idea to be accepted?

Hi @Aleksey, there is no solid threshold defined, bu the highest voted ideas should be taken first as soon as they’re clear and as we have the ability to take them.

Here are the translated data from your walk.

INMATICS-MIB::generalRfc1628AlarmBatteryBad.0 = INTEGER: no(0)
INMATICS-MIB::generalRfc1628AlarmOnBattery.0 = INTEGER: no(0)
INMATICS-MIB::generalRfc1628AlarmLowBattery.0 = INTEGER: no(0)
INMATICS-MIB::generalRfc1628AlarmDepletedBattery.0 = INTEGER: no(0)
INMATICS-MIB::generalRfc1628AlarmTempBad.0 = INTEGER: no(0)
INMATICS-MIB::generalRfc1628AlarmInputBad.0 = INTEGER: notSupported(2)
INMATICS-MIB::generalRfc1628AlarmOutputBad.0 = INTEGER: no(0)
INMATICS-MIB::generalRfc1628AlarmOutputOverload.0 = INTEGER: no(0)
INMATICS-MIB::generalRfc1628AlarmOnBypass.0 = INTEGER: no(0)
INMATICS-MIB::generalRfc1628AlarmBypassBad.0 = INTEGER: notSupported(2)
INMATICS-MIB::generalRfc1628AlarmOutputOffAsRequested.0 = INTEGER: notSupported(2)
INMATICS-MIB::generalRfc1628AlarmUpsOffAsRequested.0 = INTEGER: notSupported(2)
INMATICS-MIB::generalRfc1628AlarmChargerFailed.0 = INTEGER: no(0)
INMATICS-MIB::generalRfc1628AlarmUpsOutputOff.0 = INTEGER: notSupported(2)
INMATICS-MIB::generalRfc1628AlarmUpsSystemOff.0 = INTEGER: no(0)
INMATICS-MIB::generalRfc1628AlarmFanFailure.0 = INTEGER: notSupported(2)
INMATICS-MIB::generalRfc1628AlarmFuseFailure.0 = INTEGER: notSupported(2)
INMATICS-MIB::generalRfc1628AlarmGeneralFault.0 = INTEGER: no(0)
INMATICS-MIB::generalRfc1628AlarmDiagnosticTestFailed.0 = INTEGER: no(0)
INMATICS-MIB::generalRfc1628AlarmCommunicationsLost.0 = INTEGER: no(0)
INMATICS-MIB::generalRfc1628AlarmAwaitingPower.0 = INTEGER: notSupported(2)
INMATICS-MIB::generalRfc1628AlarmShutdownPending.0 = INTEGER: notSupported(2)
INMATICS-MIB::generalRfc1628AlarmShutdownImminent.0 = INTEGER: notSupported(2)
INMATICS-MIB::generalRfc1628AlarmTestInProgress.0 = INTEGER: no(0)
INMATICS-MIB::megatecStateRectifierRotationError.0 = INTEGER: no(0)
INMATICS-MIB::megatecStateLowBatteryShutdown.0 = INTEGER: no(0)
INMATICS-MIB::megatecStateLowBattery1.0 = INTEGER: no(0)
INMATICS-MIB::megatecStateOnBattery.0 = INTEGER: no(0)
INMATICS-MIB::megatecStateCharge.0 = INTEGER: float(0)
INMATICS-MIB::megatecStateRectifierOperating.0 = INTEGER: no(0)
INMATICS-MIB::megatecStateBypassFrequencyFail.0 = INTEGER: no(0)
INMATICS-MIB::megatecStateManualBypassBreaker.0 = INTEGER: open(0)
INMATICS-MIB::megatecStateBypassAC.0 = INTEGER: abnormal(0)
INMATICS-MIB::megatecStateStaticSwitchMode.0 = INTEGER: bypass(0)
INMATICS-MIB::megatecStateInverterOperating.0 = INTEGER: no(0)
INMATICS-MIB::megatecStateEmergencyStop.0 = INTEGER: no(0)
INMATICS-MIB::megatecStateHighDCShutdown.0 = INTEGER: no(0)
INMATICS-MIB::megatecStateManualBypassBreakerOnShutdown.0 = INTEGER: no(0)
INMATICS-MIB::megatecStateOverLoadShutdown.0 = INTEGER: no(0)
INMATICS-MIB::megatecStateInverterOutputFailShutdown.0 = INTEGER: no(0)
INMATICS-MIB::megatecStateOverTemperatureShutdown.0 = INTEGER: no(0)
INMATICS-MIB::megatecStateShortCircuitShutdown.0 = INTEGER: no(0)
INMATICS-MIB::megatecStateUtilityFail.0 = INTEGER: no(0)
INMATICS-MIB::megatecStateLowBattery2.0 = INTEGER: no(0)
INMATICS-MIB::megatecStateBypassBoostBuckActive.0 = INTEGER: no(0)
INMATICS-MIB::megatecStateUPSFailed.0 = INTEGER: no(0)
INMATICS-MIB::megatecStateTestInProgress.0 = INTEGER: no(0)
INMATICS-MIB::megatecStateShutdownActive.0 = INTEGER: no(0)
INMATICS-MIB::cmsiiiModulesInPhases.0 = INTEGER: 0
INMATICS-MIB::cmsiiiModulesOutPhases.0 = INTEGER: triple(3)
INMATICS-MIB::cmsiiiBatteryVoltPos.0 = INTEGER: 0 0.1 V DC
INMATICS-MIB::cmsiiiBatteryVoltNeg.0 = INTEGER: 0 0.1 V DC
INMATICS-MIB::cmsiiiBatteryCurrPos.0 = INTEGER: 0 0.1 A
INMATICS-MIB::cmsiiiBatteryCurrNeg.0 = INTEGER: 0 0.1 A
INMATICS-MIB::upsEnvSensorCounts.0 = INTEGER: 1
INMATICS-MIB::upsEnvSensorTemperature.1 = INTEGER: 2006 0.01 degrees Centigrade
INMATICS-MIB::upsEnvSensorHumidity.1 = INTEGER: 33 percent
INMATICS-MIB::upsAlarmEnvSensorTemperatureHigh.0 = INTEGER: no(0)
INMATICS-MIB::upsAlarmEnvSensorTemperatureLow.0 = INTEGER: no(0)
INMATICS-MIB::upsAlarmEnvSensorHumidityHigh.0 = INTEGER: no(0)
INMATICS-MIB::upsIOinputCounts.0 = INTEGER: 0

In addition to temperature and humidity, what other metrics/status seem relevant to you?

Hello,

I successfully use the capabilities of the 'hardware::ups::standard::rfc1628::snmp::plugin' plugin in the 'battery-status', 'input-lines', 'output-lines', 'alarms' modes
All these modes work with PSU Sputnik.
The only thing missing now is a separate 'environment' mode.
That’s why I suggested making a separate plugin for PSU Sputnik and adding this mode there

In the new plugin 'hardware::sensors::inmatics::psusputnik::snmp::plugin' you can add the modes 'battery-status', 'input-lines', 'output-lines', 'alarms', which will be a link to 'hardware::ups::standard::rfc1628::snmp::plugin'. And I can check it.

Ok thanks!

Hi @Aleksey,

Something is not clear to me about Sputnik’s category: is it a power supply unit (PSU) or an uninterruptible power supply (UPS)?

You are saying it’s a PSU but the OIDs from your walk and MIB and the fact it can be monitored by the standard UPS connector makes it appear more like a UPS.

Would it be wrong to categorize it as UPS?

Hello, @omercier 

You can remove the "psu" characters from the name if they confuse you. "Sputnik" is a universal UPS management and monitoring card. Similar to NMC APC. But this card supports different communication protocols with the UPS and can be used in different UPSs: APC, Powerware, Impuls, and so on.
The SNMP stack inside Sputnik cards is implemented through support for rfc1628 and an additional proprietary MIB with environmental parameters, which I wrote about earlier in this topic.

Hi @Aleksey,

The new pack has been released yesterday: https://docs.centreon.com/pp/integrations/plugin-packs/procedures/hardware-ups-inmatics-sputnik-snmp/

Thank you. We'll test it.

Thanks a lot. It works