-
Hello, I have some CyberPower CDU's model 41101. I have had some success using SNMP to collect data from them, the outlet names and notes will populate, but I can not get any load data or outlet on/off status from them. I have tried several OID's that will supply the data in question, and I can snmpget from the openDCIM host computers command line and collect the data also. I have added "POLL" and "OPTIN" tags to the devices. I believe I have the cron jobs for the scripts correct now (I got my env sensors working). I have not tried switches yet, thats next..... I am relatively new to SNMP stuff and openDCIM, and pretty rusty on linux, but I got this far..... Any thoughts? only thing I can think of for the status is that it responds 1 for on and 2 for off, instead of a binary 0 or 1. not sure what openDCIM expects to see or how it would know what to expect if that output is not standard..... Oh this also sounds something like this issue #1464 , so I ran the SQL query suggested in that thread and the results look ok to me: I see that user apparently gave up. I am a little more stubborn.....any help very much appreciated. |
Beta Was this translation helpful? Give feedback.
Replies: 15 comments 25 replies
-
Hi, |
Beta Was this translation helpful? Give feedback.
-
The biggest thing jumping out at me is that you do not have the community string set on the device. Also, the Tag should be Poll. Not sure if POLL will work. I just enabled one of mine:
|
Beta Was this translation helpful? Give feedback.
-
Look closer and you will see a difference between the OID it is trying to walk and the one you are using on the command line.
Scott
…________________________________
From: ArumBlack ***@***.***>
Sent: Thursday, June 27, 2024 9:58 AM
To: opendcim/openDCIM ***@***.***>
Cc: Subscribed ***@***.***>
Subject: Re: [opendcim/openDCIM] CDU not pulling load info or outlet status (Discussion #1542)
HMM. so typing the command from crontab that executes the script directly into the command line I get "could not perform walk" for a number of the OID's.
trying to walk those oids directly from the command line succeeds??? is this a permissions issue? It always seems like every problem I have in Linux comes down to a permissions issue :)
2024-06-27.08_55_43-Window.png (view on web)<https://github.com/opendcim/openDCIM/assets/120606523/9966606f-8768-436d-8f7f-bb02e3d42f54>
—
Reply to this email directly, view it on GitHub<#1542 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAMTY657NCSAQMLK52FLBSDZJQLCDAVCNFSM6AAAAABJURLTGGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TQOJUG43TC>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
on outlet count = control your oid with snmpwalk or snmpget, result number of outlet (24) |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
hi, 1 - Walk through SNMP manually using tools like snmpwalk to see if you can retrieve information from the specified OID ... |
Beta Was this translation helpful? Give feedback.
-
Yeah I have seen that before. Snmp walk will succeed and sometimes you
don't notice that the OID that it used is not the same one as you're using.
As you saw, sometimes they're a little longer and you need to use the more
specific one.
…On Tue, Jul 2, 2024, 2:42 p.m. ArumBlack ***@***.***> wrote:
I have this working now.the key was the difference between snmpwalk, and
snmp get. and the confusion was the error on the script stating it could
not perform walk....so I was using OID's that worked with snmp walk, and
wondering why they fail. I had to go 1 level deeper to get it to work so
firmware really needed .1.3.6.1.4.1.3808.1.1.3.1.3.0, not
.1.3.6.1.4.1.3808.1.1.3.1.3. same for load.
—
Reply to this email directly, view it on GitHub
<#1542 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAH3N665VCA3YQBC6QDWWH3ZKLRBVAVCNFSM6AAAAABJURLTGGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TSMZZGY4TO>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Is someone here with knowledge for Rittal CMC3 MIB? |
Beta Was this translation helpful? Give feedback.
-
Good morning sometimes the mib files are available in the admin interface of the devices for download otherwise on the manufacturer's website. If not found, then use software to explore the mibs, there are several free software like "oid view" if you have an export file with the oid addresses listed and the values in table form, make a new post on this subject to answer and I'll take a quick look and see if I can help |
Beta Was this translation helpful? Give feedback.
-
Firmware Version: Outlet Count: Outlet State: Outlet Name: Outlet Description: Phase 1 Power Watt: Phase 2 Power Watt: Phase 3 Power Watt: Humidity Value: Temperature Value: Go.. |
Beta Was this translation helpful? Give feedback.
-
I just tried another Version, which does not work but the mib looks much more compact
|
Beta Was this translation helpful? Give feedback.
-
@samilliken
The Rittal MIB is displaying 33 variables per outlet.
Integer representation would be at 1.3.6.1.4.1.2606.7.4.2.2.1.11.2.X+7 (for State).
Writing this, I notice how hard it even is to grasp and describe the Rittal logic. |
Beta Was this translation helpful? Give feedback.
-
Nope, if the OIDs are not consecutive, we do not support it.
Scott
…________________________________
From: LFrank2021 ***@***.***>
Sent: Monday, July 8, 2024 5:06 AM
To: opendcim/openDCIM ***@***.***>
Cc: Scott Milliken ***@***.***>; Comment ***@***.***>
Subject: Re: [opendcim/openDCIM] CDU not pulling load info or outlet status (Discussion #1542)
I just tried another Version, which does not work but the mib looks much more compact
Firmware Version: 1.3.6.1.4.1.2606.7.4.1.2.1.11.1
Outlet Name:
Outlet Description: 1.3.6.1.4.1.2606.7.4.2.3.1.4.44.2
Outlet Count:
Outlet State: 1.3.6.1.4.1.2606.7.4.2.4.1.5.5.2 (11: On, 10: Off)
Phase 1 Power Watt: 1.3.6.1.4.1.2606.7.4.2.2.1.11.2.56
Phase 2 Power Watt: 1.3.6.1.4.1.2606.7.4.2.2.1.11.2.99
Phase 3 Power Watt: 1.3.6.1.4.1.2606.7.4.2.2.1.11.2.142
But it seems, the 'jump' in numbers is not supported by OpenDCIM.
SNMPv2-SMI::enterprises.2606.7.4.2.3.1.4.44.2.157 = STRING: "C13"
SNMPv2-SMI::enterprises.2606.7.4.2.3.1.4.44.2.190 = STRING: "C13"
SNMPv2-SMI::enterprises.2606.7.4.2.3.1.4.44.2.223 = STRING: "C13"
SNMPv2-SMI::enterprises.2606.7.4.2.3.1.4.44.2.256 = STRING: "C13"
SNMPv2-SMI::enterprises.2606.7.4.2.3.1.4.44.2.289 = STRING: "C13"
SNMPv2-SMI::enterprises.2606.7.4.2.3.1.4.44.2.322 = STRING: "C13"
SNMPv2-SMI::enterprises.2606.7.4.2.3.1.4.44.2.355 = STRING: "C13"
SNMPv2-SMI::enterprises.2606.7.4.2.3.1.4.44.2.388 = STRING: "C13"
SNMPv2-SMI::enterprises.2606.7.4.2.3.1.4.44.2.421 = STRING: "C19"
SNMPv2-SMI::enterprises.2606.7.4.2.3.1.4.44.2.454 = STRING: "C19"
SNMPv2-SMI::enterprises.2606.7.4.2.3.1.4.44.2.487 = STRING: "C13"
SNMPv2-SMI::enterprises.2606.7.4.2.3.1.4.44.2.520 = STRING: "C13"
SNMPv2-SMI::enterprises.2606.7.4.2.3.1.4.44.2.553 = STRING: "C13"
SNMPv2-SMI::enterprises.2606.7.4.2.3.1.4.44.2.586 = STRING: "C13"
SNMPv2-SMI::enterprises.2606.7.4.2.3.1.4.44.2.619 = STRING: "C13"
SNMPv2-SMI::enterprises.2606.7.4.2.3.1.4.44.2.652 = STRING: "C13"
SNMPv2-SMI::enterprises.2606.7.4.2.3.1.4.44.2.685 = STRING: "C13"
SNMPv2-SMI::enterprises.2606.7.4.2.3.1.4.44.2.718 = STRING: "C13"
SNMPv2-SMI::enterprises.2606.7.4.2.3.1.4.44.2.751 = STRING: "C19"
SNMPv2-SMI::enterprises.2606.7.4.2.3.1.4.44.2.784 = STRING: "C19"
SNMPv2-SMI::enterprises.2606.7.4.2.3.1.4.44.2.817 = STRING: "C13"
SNMPv2-SMI::enterprises.2606.7.4.2.3.1.4.44.2.850 = STRING: "C13"
SNMPv2-SMI::enterprises.2606.7.4.2.3.1.4.44.2.883 = STRING: "C13"
SNMPv2-SMI::enterprises.2606.7.4.2.3.1.4.44.2.916 = STRING: "C13"
SNMPv2-SMI::enterprises.2606.7.4.2.3.1.4.44.2.949 = STRING: "C13"
SNMPv2-SMI::enterprises.2606.7.4.2.3.1.4.44.2.982 = STRING: "C13"
SNMPv2-SMI::enterprises.2606.7.4.2.3.1.4.44.2.1015 = STRING: "C13"
SNMPv2-SMI::enterprises.2606.7.4.2.3.1.4.44.2.1048 = STRING: "C13"
SNMPv2-SMI::enterprises.2606.7.4.2.3.1.4.44.2.1081 = STRING: "C19"
SNMPv2-SMI::enterprises.2606.7.4.2.3.1.4.44.2.1114 = STRING: "C19"
SNMPv2-SMI::enterprises.2606.7.4.2.4.1.5.5.2.162 = INTEGER: 11
SNMPv2-SMI::enterprises.2606.7.4.2.4.1.5.5.2.195 = INTEGER: 10
SNMPv2-SMI::enterprises.2606.7.4.2.4.1.5.5.2.228 = INTEGER: 11
SNMPv2-SMI::enterprises.2606.7.4.2.4.1.5.5.2.261 = INTEGER: 11
SNMPv2-SMI::enterprises.2606.7.4.2.4.1.5.5.2.294 = INTEGER: 11
SNMPv2-SMI::enterprises.2606.7.4.2.4.1.5.5.2.327 = INTEGER: 11
SNMPv2-SMI::enterprises.2606.7.4.2.4.1.5.5.2.360 = INTEGER: 11
SNMPv2-SMI::enterprises.2606.7.4.2.4.1.5.5.2.393 = INTEGER: 11
SNMPv2-SMI::enterprises.2606.7.4.2.4.1.5.5.2.426 = INTEGER: 11
SNMPv2-SMI::enterprises.2606.7.4.2.4.1.5.5.2.459 = INTEGER: 11
SNMPv2-SMI::enterprises.2606.7.4.2.4.1.5.5.2.492 = INTEGER: 11
SNMPv2-SMI::enterprises.2606.7.4.2.4.1.5.5.2.525 = INTEGER: 11
SNMPv2-SMI::enterprises.2606.7.4.2.4.1.5.5.2.558 = INTEGER: 11
SNMPv2-SMI::enterprises.2606.7.4.2.4.1.5.5.2.591 = INTEGER: 11
SNMPv2-SMI::enterprises.2606.7.4.2.4.1.5.5.2.624 = INTEGER: 11
SNMPv2-SMI::enterprises.2606.7.4.2.4.1.5.5.2.657 = INTEGER: 11
SNMPv2-SMI::enterprises.2606.7.4.2.4.1.5.5.2.690 = INTEGER: 11
SNMPv2-SMI::enterprises.2606.7.4.2.4.1.5.5.2.723 = INTEGER: 11
SNMPv2-SMI::enterprises.2606.7.4.2.4.1.5.5.2.756 = INTEGER: 11
SNMPv2-SMI::enterprises.2606.7.4.2.4.1.5.5.2.789 = INTEGER: 11
SNMPv2-SMI::enterprises.2606.7.4.2.4.1.5.5.2.822 = INTEGER: 11
SNMPv2-SMI::enterprises.2606.7.4.2.4.1.5.5.2.855 = INTEGER: 11
—
Reply to this email directly, view it on GitHub<#1542 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAMTY6ZLAJGZ25GWHOW7N7TZLJJC3AVCNFSM6AAAAABJURLTGGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TSOBVGE2DE>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
We've discussed situations like this and in order to support them we'd have to implement major database changes to allow you to tie specific OID to a port and we haven't had the time to do that. This would apply to switches as well that have the port numbers all jumbled around. |
Beta Was this translation helpful? Give feedback.
on outlet count = control your oid with snmpwalk or snmpget, result number of outlet (24)
on outlet state oid = 1.3.6.1.4.1.3808.1.1.6.6.1.4.1.5 your picture snmpwalk is ok
on template management > edit device template add 1 on outlet state (on)
on edit configuration >reporting Switches = OptOut
Go and joy