search for: nosuchnam

Hi, I just installed NUT to monitor 4 UPS, all APC, all with Network card APC 9617. NUT have problem to access the following SNMP OID on all the UPSes: Detected Smart-UPS 3000 XL on host apc4.cs.ait.ac.th (mib: apcc 1.1) [apc4] nut_snmp_get: .1.3.6.1.4.1.318.1.1.1.9.2.2.1.2.1: Error in packet: (noSuchName) There is no such variable name in this MIB. [apc4] nut_snmp_get: .1.3.6.1.4.1.318.1.1.1.9.2.3.1.3.1.1.1: Error in packet: (noSuchName) There is no such variable name in this MIB. [apc4] nut_snmp_get: .1.3.6.1.4.1.318.1.1.1.9.2.3.1.3.1.1.2: Error in packet: (noSuchName) There is no such variable n...

...e whole package? * Starting UPS drivers... Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - Generic SNMP UPS driver 0.44 (2.4.1) Detected GXT2-2000RT120 on host upswallleft (mib: ietf 1.3) [upswallleft] nut_snmp_get: 1.3.6.1.2.1.33.1.4.4.1.4.0: Error in packet: (noSuchName) There is no such variable name in this MIB. [upswallleft] nut_snmp_get: 1.3.6.1.2.1.33.1.7.4: Error in packet: (noSuchName) There is no such variable name in this MIB. [upswallleft] nut_snmp_get: 1.3.6.1.2.1.33.1.2.6.0: Error in packet: (noSuchName) There is no such variable name in this MIB. [...

...2.2 Network UPS Tools - Multi-MIBS SNMP UPS driver 0.421 (2.2.2) Warning: This is an experimental driver. Some features may not function correctly. Detected GXT2-2000RT120 on host upswallleft (mib: ietf 1.2) [upswallleft] nut_snmp_get: 1.3.6.1.2.1.33.1.4.4.1.4.0: Error in packet: (noSuchName) There is no such variable name in this MIB. [upswallleft] nut_snmp_get: 1.3.6.1.2.1.33.1.2.6.0: Error in packet: (noSuchName) There is no such variable name in this MIB. [upswallleft] nut_snmp_get: 1.3.6.1.2.1.33.1.4.4.1.2.0: Error in packet: (noSuchName) There is no such variable name in this...

...el. Since I didn't want to install a Windows box to run Powerwares software I now went nut(s) ;-) So far things look pretty good, snmp-ups talks to both ups using the pw mib. Though I get these messages, when I start the driver: [ups2] nut_snmp_get: 1.3.6.1.4.1.534.1.4.4.1.3: Error in packet: (noSuchName) There is no such variable name in this MIB. [ups2] nut_snmp_get: 1.3.6.1.4.1.534.1.3.4.1.4.1: Error in packet: (noSuchName) There is no such variable name in this MIB. [ups2] nut_snmp_get: 1.3.6.1.4.1.534.1.3.4.1.4.2: Error in packet: (noSuchName) There is no such variable name in this MIB. [ups2...

...el. Since I didn't want to install a Windows box to run Powerwares software I now went nut(s) ;-) So far things look pretty good, snmp-ups talks to both ups using the pw mib. Though I get these messages, when I start the driver: [ups2] nut_snmp_get: 1.3.6.1.4.1.534.1.4.4.1.3: Error in packet: (noSuchName) There is no such variable name in this MIB. [ups2] nut_snmp_get: 1.3.6.1.4.1.534.1.3.4.1.4.1: Error in packet: (noSuchName) There is no such variable name in this MIB. [ups2] nut_snmp_get: 1.3.6.1.4.1.534.1.3.4.1.4.2: Error in packet: (noSuchName) There is no such variable name in this MIB. [ups2...

...utput: # /usr/local/etc/rc.d/nut start Network UPS Tools - UPS driver controller 2.0.5 Network UPS Tools - Multi-MIBS SNMP UPS driver 0.41 (2.0.5) Warning: This is an experimental driver. Some features may not function correctly. [ups1] nut_snmp_get: .1.3.6.1.2.1.33.1.1.2.0: Error in packet: (noSuchName) There is no such variable name in this MIB. ietf MIB wasn't found on ups1 Driver failed to start (exit status=1) Do any of you know if it is possible to use the 66102 card with the snmp driver at all, or do I have to buy the old card to get it working? Any help is appreciated. :) -- La...

...ups -x mibs=pw -x community=publicstring upsname Network UPS Tools - Multi-MIBS SNMP UPS driver 0.41 (2.1.0) Warning: This is an experimental driver. Some features may not function correctly. detected Powerware 9170 on host upsname [(null)] nut_snmp_get: .1.3.6.1.2.1.33.1.2.4.0: Error in packet: (noSuchName) There is no such variable name in this MIB. [(null)] nut_snmp_get: .1.3.6.1.4.1.534.1.6.1.0: Error in packet: (noSuchName) There is no such variable name in this MIB. pkdick:~/nut/bin# Commenting out references to those MIBs in pwmib.h (in the pw_mib structure) seems to make everything work, alt...

...et() 0.111643 su_find_infoval: found OB (value: 1) 0.111652 => value: 1 0.111659 getting data: ups.status (.1.3.6.1.4.1.232.165.3.7.4.0) 0.111666 su_ups_get: ups.status .1.3.6.1.4.1.232.165.3.7.4.0 0.116669 [R3000-T] nut_snmp_get: .1.3.6.1.4.1.232.165.3.7.4.0: (noSuchName) There is no such variable name in this MIB. 0.116695 => Failed 0.116719 getting data: ups.type (.1.3.6.1.4.1.232.165.3.4.5.0) 0.116726 su_ups_get: ups.type .1.3.6.1.4.1.232.165.3.4.5.0 0.120919 su_find_infoval: found normal (value: 3) 0.120943 entering su_set...

Thanks to Olli, I can now talk to my PW9125 via SNMP: > upsc cscfups001@localhost ambient.temperature: 031.0 battery.charge: 090.0 battery.runtime: 2640.0 battery.voltage: 055.5 driver.name: snmp-ups driver.parameter.mibs: pw driver.parameter.port: cscfups001.cs.uwaterloo.ca driver.version: 2.1.0 driver.version.internal: 0.41 input.frequency: 060.0 input.voltage: 120.0 output.current: 020.0

...MP GET to retrieve info from the agent, but under wine the OID in the package is sometimes wrong. wine: GetRequest E:762.2.5.2.1.25.0 E:762.2.5.2.1.11.0 windows: GetRequest E:762.2.5.2.1.25.1 E:762.2.5.2.1.11.1 The last digit in the OID is actually an index number, so the agent returns "noSuchName" to the wine manager. Wine use a 0 at the end, regardless of what the index number should be. Any GetNext-requests is working ok. So, if anyone could give a hint to solutions, please do. mvh Johan Johansen University of Tromso, Norway.

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 -