On Jan 14, 2010, at 2:25 AM, [email protected] wrote:
Quoting Charles Lepple <[email protected]>:
On Jan 13, 2010, at 8:55 PM, Philip Tait wrote:
On 01/13/2010 03:29 PM, Charles Lepple wrote:
On Tue, Jan 12, 2010 at 4:29 PM, Philip Tait <[email protected]
> wrote:
After configuring (details below), I get:
# upsdrvctl start
Network UPS Tools - UPS driver controller 2.2.0-
Network UPS Tools - Multi-MIBS SNMP UPS driver 0.42 (2.2.0-)
Warning: This is an experimental driver.
Some features may not function correctly.
Unknown mibs value: auto
This should be a permitted option, even in 2.2.0. Is there a chance
that some control characters got copied into the configuration
file?
Thanks for the response.
I did an 'od -cx' on the file, and saw no non-printing characters.
Sorry, I should have looked harder - that error message was fixed
between 2.2.0 and the latest version.
Using 'mbrowse', I explored the MIB, and found that this particular
model (AP341/342) has everything under .1.3.6.1.4.1.476
(iso.org.dod.internet.private.enterprises.emerson), which, from
looking
at the source for 2.4.1, seems to be not supported. I think newer
Liebert models use a more standard arrangement, under 'ietf'.
Seems like I will have to develop my own custom solution... (or
buy a
newer network card!)
OK - let us know if you would like any help with generating a new
MIB-to-NUT mapping.
That sounds like a better idea - how do I get started?
Arjen has a good point - it may be possible to upgrade the firmware on
the card.
If not, we might want to switch to the nut-devel list. It would be
good to post a few details on that list about your development machine
(OS version, etc.) so we can suggest what tools to install.
_______________________________________________
Nut-upsuser mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
