Nut upsuser - Nov 2011 - Nexenta: "load_mib2nut: using pw mib" package / config / or firewall problem?

G'day

I'm currently using NUT on Debian squeeze box in the same subnet with an IBM
3000 HV (branded Eaton 5125 with Web/SNMP card),  now I wanted to get our
storage appliance running NexentaStor 3.1 set up to be using NUT too. Nexenta-
Stor is an OpenSolaris / illumos-based appliance OS currently using
NUT packages
from ubuntu hardy.

My question here is whether I'm running into a
- network configuration (Firewall) problem?
- config error?
- problem in the package?

NUT version:  2.4.1
Packages installed: snmp, nut, nut-snmp
OS: SunOS 5.11 NexentaOS_134f (NexentaStor 3.1.1)

I have set up the IBM in ups.conf as follows
[ibm3000_1]
 driver = snmp-ups
 port = <ip-of-ups>
 mibs = pw
 pollfreq = 30
 community = public
 snmp_version = v1
 desc = "Rack 1: main network ups"

When I startt NUT, dmesg spits out, before SMF turns nut into maintenance:
Nov  7 13:36:05 museion upsd[18640]: [ID 702911 daemon.error] Can't
connect to UPS [ibm3000_1] (snmp-ups-ibm3000_1): No such file or
directory

When launching snmp-ups driver directly using I get
root at nexenta1:/# /lib/nut/snmp-ups -D -a ibm3000_1
Network UPS Tools - Generic SNMP UPS driver 0.44 (2.4.1)
debug level is '1'
SNMP UPS driver : entering upsdrv_initups()
load_mib2nut: using pw mib
pw MIB wasn't found on <ip-of-ups>

Network: The UPS is in another subnet. Our network guy has opened port 161 betwe
en the 2 boxes, and I can also do a 'snmpget' from nexenta
and fetch some data with an OID of the UPS. i.e.:
root at nexenta1:/# snmpget -v1 -c public <ip-of-ups> 
.1.3.6.1.4.1.534.1.6.1.0
SNMPv2-SMI::enterprises.534.1.6.1.0 = INTEGER: 35 (which is the battery temp)

If anyone could point me in the right direction, how to debug further,
I'd be grateful.

Best regards
Mathieu

Hi Mathieu,

2011/11/7 Mathieu Simon <mathieu.sim at gmail.com>
> G'day
>
> I'm currently using NUT on Debian squeeze box in the same subnet with
an
> IBM
> 3000 HV (branded Eaton 5125 with Web/SNMP card),  now I wanted to get our
> storage appliance running NexentaStor 3.1 set up to be using NUT too.
> Nexenta-
> Stor is an OpenSolaris / illumos-based appliance OS currently using
> NUT packages
> from ubuntu hardy.
>
> My question here is whether I'm running into a
> - network configuration (Firewall) problem?
> - config error?
> - problem in the package?
>
> NUT version:  2.4.1
> Packages installed: snmp, nut, nut-snmp
> OS: SunOS 5.11 NexentaOS_134f (NexentaStor 3.1.1)
>
> I have set up the IBM in ups.conf as follows
> [ibm3000_1]
>  driver = snmp-ups
>  port = <ip-of-ups>
>  mibs = pw
>  pollfreq = 30
>  community = public
>  snmp_version = v1
>  desc = "Rack 1: main network ups"
>
> When I startt NUT, dmesg spits out, before SMF turns nut into maintenance:
> Nov  7 13:36:05 museion upsd[18640]: [ID 702911 daemon.error] Can't
> connect to UPS [ibm3000_1] (snmp-ups-ibm3000_1): No such file or
> directory
>
> When launching snmp-ups driver directly using I get
> root at nexenta1:/# /lib/nut/snmp-ups -D -a ibm3000_1
> Network UPS Tools - Generic SNMP UPS driver 0.44 (2.4.1)
> debug level is '1'
> SNMP UPS driver : entering upsdrv_initups()
> load_mib2nut: using pw mib
> pw MIB wasn't found on <ip-of-ups>
>
> Network: The UPS is in another subnet. Our network guy has opened port 161
> betwe
> en the 2 boxes, and I can also do a 'snmpget' from nexenta
> and fetch some data with an OID of the UPS. i.e.:
> root at nexenta1:/# snmpget -v1 -c public <ip-of-ups>
>  .1.3.6.1.4.1.534.1.6.1.0
> SNMPv2-SMI::enterprises.534.1.6.1.0 = INTEGER: 35 (which is the battery
> temp)
>
> If anyone could point me in the right direction, how to debug further,
> I'd be grateful.
>
first of all, IBM support in NUT is still on my (Eaton) TODO list...

I've (very) quickly looked at it, and should be able to provide something
quickly.
That said:
- the sysOID is buggy (fix scheduled) and pointing wrongly the MGE MIB
(iso.3.6.1.4.1.705.1), which is not implemented on this device.

Moreover, the NUT version you're using is using a simple "try and
fail"
test, that tries to match against ".1.3.6.1.4.1.534.1".
And this OID is also not available:
$ snmpget -v1 -c public <ip-of-ups> .1.3.6.1.4.1.534.1
Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: iso.3.6.1.4.1.534.1

I'll check all this when I have a bit more time, and will update you as
soon as possible.

cheers,
Arnaud
-- 
Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20111108/bff87318/attachment.html>