Rittal CMCIII discovered as LCP?

Hi,

originally I wanted to find out why LibreNMS is showing temperature values for a CMCIII device, but no descriptions of the values also showing under .1.3.6.1.4.1.2606.7.4.2.2.1.10. So I started with the discovery process.

rittal-cmc OS Detection:

sysObjectID:
- .1.3.6.1.4.1.2606.4

Let’s try this:

$ snmpwalk -v2c -c public hostname .1.3.6.1.4.1.2606.4
iso.3.6.1.4.1.2606.4 = No Such Object available on this agent at this OID

Nope, isn’t CMC according to LibreNMS … but it’s a CMCIII. Let’s try the one from includes/definitions/rittal-lcp.yaml:

sysObjectID:
- .1.3.6.1.4.1.2606.7


$ snmpwalk -v2c -c public hostname .1.3.6.1.4.1.2606.7
iso.3.6.1.4.1.2606.7.1.1.0 = Gauge32: 1

This seems to work, snmpwalk is listing all the temperatures which are showing up in the graphs but without their names. Now my question is what to do next.

  • Fix the detection bug?
    rittal-lcp is clearly using the RITTAL-CMC-III-MIB while rittal-cmc is using RITTAL-CMC-TC-MIB which seems to be CMCII?
  • Add a new os, like rittal-cmc-iii to not break other stuff?

Once this is fixed the original bug with missing sensor names can be fixed I guess …

What do you think?

You have to check sysObjectID. What does the device return ?

snmpwalk -v2c -c public hostname .1.3.6.1.2.1.1.2

This block below means : Retrieve sysObjectID and compare the value. If this is a match, identification is done. The fact that .1.3.6.1.4.1.2606.4 returns a value (or not) is completely ignored here, no snmpget is done on .1.3.6.1.4.1.2606.4.

sysObjectID:
- .1.3.6.1.4.1.2606.4

Working on it:

Thanks @nightcore500! Really looking good on my CMC now :slight_smile:
Looks like it killed the (sort of) support for .1.3.6.1.4.1.2606.7 (Rittal PDUs) but I’ll look into it over the next days to get this working again.

@eimann
The device support only concerns the PU devices at the moment because i had no possibility to test the rest of the devices for functionality. Please check with “snmpget -v2c -c .1.3.6.1.2.1.1.1.0” which value you get. Only the front part before SN is interesting. Then add this value in the file “includes/definitions/rittal-cmc-iii-pu.yaml” under “sysDescr_regex:”.
Probably:

  • ‘/^Rittal PDU/’
    or
  • ‘/^Rittal CMC III PDU/’

Afterwards the sensors should be read out. Please report if they are correct and complete.

diff --git a/includes/definitions/rittal-cmc-iii-pu.yaml b/includes/definitions/rittal-cmc-iii-pu.yaml
index 9cf2005a1…8c24f811c 100644
— a/includes/definitions/rittal-cmc-iii-pu.yaml
+++ b/includes/definitions/rittal-cmc-iii-pu.yaml
@@ -17,3 +17,5 @@ discovery:
sysDescr_regex:
- ‘/^Rittal CMC III PU/’
- ‘/^Rittal CMC III PU Compact/’

  •        - '/^Rittal Rittal PDU/'
    
  •        - '/^Rittal PDU/'
    

7955.210 with firmware 5.15.50 reports “Rittal Rittal PDU”
7979.215 with firmware 7.17.30 report “Rittal PDU”

So far detected sensors are looking good. I’ll wait until tomorrow and see if the values are good too.

This looks fine:

Unfortunately this website only allows one attachement per message.

But those values seem to be broken:

Seems to be the same sensor several times, looks like power grid frequency:

L1 Power seems to be roughly multiplied by 3, Power active is way too high