I have an APC 9210 PDU in my rack. It's connected to the network and is configurable by web access. I'd like to control it in combination with my ups. Unfortunately I cannot get NUT to recognise this PDU. Here's my ups.conf section: [apc] driver = snmp-ups port = 192.168.10.21 mibs = auto community = public snmp_version = v1 running upsdrvctl gives this: $ sudo /sbin/upsdrvctl start apc Network UPS Tools - UPS driver controller 2.6.5 Network UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5) No matching MIB found for sysOID '.1.3.6.1.4.1.318.1.3.4.5'! Please report it to NUT developers, with an 'upsc' output for your device. Going back to the classic MIB detection method. No supported device detected Driver failed to start (exit status=1) $ What's the upsc output that the developers want? I have a MIB file supplied from APC, but is there a way I can give this to upsd to use? Cheers, -- Graeme Hilton
On 26 March 2013 16:19, Graeme Hilton <graeme.hilton at fishter.org.uk> wrote:> I have an APC 9210 PDU in my rack. It's connected to the network and > is configurable by web access.<snip> Sorry, I need to correct my last mail. It's not an APC 9210 it's an APC 7920. -- Graeme Hilton
On Mar 26, 2013, at 12:19 PM, Graeme Hilton wrote:> What's the upsc output that the developers want? > I have a MIB file supplied from APC, but is there a way I can give > this to upsd to use?The process isn't automatic yet: http://buildbot.networkupstools.org/~buildbot/cayenne/docs/reb1f01ed6f0e3844d00876b748287976b7c2478a-343/website/output/docs/developer-guide.chunked/ar01s04.html#snmp-subdrivers We have a script to generate a stub SNMP driver, but it requires a bit of work to merge that back into the existing driver. The author of the snmp-ups driver doesn't have a lot of free time at the moment, but if you follow those directions and post results to the list (either this one, or nut-upsdev), I'll see what I can do. -- Charles Lepple clepple at gmail