Trying to Monitor Eltek devices

We have some Eltek devices with working SNMP on our network and we have managed to bring the hosts into CheckMK but whenever we try and run the service discovery it comes back with nothing to monitor.

I can see that CheckMK comes with Eltek checks standard but I am unable to locate those anywhere besides the plugin list within CheckMK.

What am I missing in order to start monitoring this information

Are you sure the SNMP daemon is properly configured on your Eltek device? Try running a snmpbulkwalk to see which OIDs you get in return. Normally some standard SNMP checks, like SNMP Uptime should be discovered. If even these don’t appear, then there’s definitely something wrong with your SNMP configuration

As addition to @simon-mueller, Eltek devices are existing in many different variants.

1.3.6.1.4.1.12148.9 → eltekDistributedPlantV9 - last version i found
1.3.6.1.4.1.12148.8 → eltekDistributed
1.3.6.1.4.1.12148.7 → eltekPlant

→ all the Eltek Device Types

		         Aeongold branch will be 1
		         AL175 branch will be 2
		         AL6000 branch will be 3
		         Internal used branch will be 4
		         Internal used branch will be 5
		         OEM Smartpack branch will be 6
		         ELTEK Common branch will be 7 (SmartPack, MCU, AEON w/WebPower sw V2.x)
		         ELTEK Distributed branch will be 8 (SmartPack w/WebPower sw V3.x)
		         ELTEK Distributed V2 branch will be 9 (SmartPack w/WebPower sw V4.0)
		         ELTEK Distributed V3 branch will be 9 (SmartPack w/WebPower sw V4.1)
		         ELTEK Distributed V4 branch will be 9 (SmartPack w/WebPower sw V4.1, V4.2, V4.3, V4.5 and compack V1.0, V1.01, V1.02, V1.03)
		         ELTEK Distributed V5 branch will be 9 (SmartPack w/WebPower sw V4.1, V4.2, V4.3, V4.5, V4.6)
		         ELTEK Distributed V6 branch will be 9 (SmartPack2 sw V1.1, V1.2, V1.3)
		         ELTEK Distributed V7 branch will be 9 (SmartPack w/WebPower sw V4.1, V4.2, V4.3, V4.5, V4.6, V4.7 and compack V1.04, V1.05)
		         ELTEK Distributed V8 branch will be 9 (SmartPack w/WebPower sw V4.9, V4.10, ComPack V1.04, V1.05, Smartpack2 V1.1, V1.2)
		         ELTEK Distributed V9 branch will be 9 (SmartPack w/WebPower sw V4.11)
		         ELTEK eNexus MIB branch will be 10 (SmartPack2 V2.x, SmartPack S V2.x and Compack V2.x)
		         ELTEK Brasil office will have branch 11
		         ELTEK BMS-EM MIB will have branch 12
		         ELTEK TELMEX MIB will have branch 13

The eltekDistributedPlantV9 MIB is used by the CheckMK checks.
Here only the following data is used.

Subbranch 2.2 - systemOperationalStatus
Subbranch 1.17 - ioUnits → Temperature
Subbranch 3 - Battery → Battery, Breakers, Phase & Temperature

We have our old monitoring system that is working via SNMP on all of our Eltek devices and can pull the data we’re looking for.

I think it is the same with your old monitoring system as it is with CMK. You can define need checks if you know what data you need to fetch.
The only problem with CMK can be that it is not enough to have a MIB file like some other monitoring tools do it. You need to define a check. I had one customer with some Eltek devices not supported by CMK out of the box and it was possible to add the needed checks for this devices.

Where/how would we be able to add the needed checks for these?

Hello everyone,

we also use a lot of Eltek (now Delta) power supplies. Mainly the Smartpack S and R series. There are lots of values ​​that are interesting. I am currently putting together an overview of important OIDS. We are looking for a developer who will then write the checks. Alternatively, I could also imagine a community project.

The devices are used a lot in the ISP area, I’m surprised there’s nothing official yet.

Michael

Sometimes the next two weeks i have access to the system with my custom made Eltek device checks.
I will have a look at the checks and if they are good enough for public :smiley:

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.