search for: sysoid

Is there a way to DRY this up a bit? named_scope :has_valid_sysoid, lambda{|sysoid| (sysoid.nil?) ? {:conditions => ["nodesysoid IS NOT NULL AND nodelabel LIKE ''%-to-%''"], :include => [:ipinterface, :alarm]} : {:conditions => ["nodesysoid IS NOT NULL AND nodelabel LIKE ''%-to-%'' AND nodesysoid = ? &quo...

Hello. Just wanted to report this sysOID to you. The UPSC output is below. Network UPS Tools - Generic SNMP UPS driver 0.70 (2.7.1) kill: No such process No matching MIB found for sysOID '.1.3.6.1.4.1.318.1.3.2.11'! Please report it to NUT developers, with an 'upsc' output for your device. Going back to the classic MIB d...

...or a great FOSS project. Also, thank you for reading my question. I have a CyberPower OR1500LCDRTXL2U with an RMCARD205. There are a handful of devices plugged into the UPS. I received a message today saying to send upsc output to NUT developers after this message: "No matching MIB found for sysOID '.1.3.6.1.4.1.3808.1.1.1'" root at delta:/etc/nut# systemctl status nut-driver.service Feb 15 17:47:52 delta upsdrvctl[519]: No matching MIB found for sysOID '.1.3.6.1.4.1.3808.1.1.1'! Feb 15 17:47:52 delta upsdrvctl[519]: Please report it to NUT developers, with an 'upsc...

...NET-SNMP-EXTEND-MIB): At line 0 in (none) Cannot find module (UCD-DLMOD-MIB): At line 0 in (none) Cannot find module (SNMP-NOTIFICATION-MIB): At line 0 in (none) Cannot find module (SNMPv2-TM): At line 0 in (none) Cannot find module (NET-SNMP-VACM-MIB): At line 0 in (none) No matching MIB found for sysOID '.1.3.6.1.4.1.232.165.3'! Please report it to NUT developers, with the 'mib' paramater for your devices Detected R5500 XR on host 192.168.24.101 (mib: cpqpower 1.0) [r5500] snmp_ups_walk: data stale for ups.realpower [r5500] snmp_ups_walk: data stale for input.voltage [r5500] snmp_...

Hi, I'm thinking about adding support for PDU (Power Distribution Unit) devices from Digipower [1] and Aviosys [2] to NUT via the SNMP interface. The specific devices I have in mind are the following: Digipower AMz-1623/SW-08-1 Aviosys IP Power 925x (both are 8-port PDUs which are SNMP capable via an ethernet interface) Does anybody have other DigiPower or Aviosys devices and if so

...PS driver: entering upsdrv_initups() 0.000513 SNMP UPS driver: entering nut_snmp_init(snmp-ups) 0.015262 Setting SNMP retries to 5 0.015280 Setting SNMP timeout to 1 second(s) 0.015344 SNMP UPS driver: entering load_mib2nut(auto) 0.015355 trying the new match_sysoid() method 0.018505 OID value: .1.3.6.1.4.1.476.1.42 0.018522 match_sysoid: device sysOID value = .1.3.6.1.4.1.476.1.42 0.018529 match_sysoid: checking MIB apcc 0.018533 match_sysoid: checking MIB mge 0.018540 match_sysoid: comparing .1.3.6.1.4.1.476.1.42 with...

...Starting the driver with command *snmp-ups -a trippliteups -D * is failing with the following output: Network UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5) 0.000000 debug level is '1' 0.000215 SNMP UPS driver : entering upsdrv_initups() 0.020982 trying the new match_sysoid() method 0.026416 match_sysoid: device sysOID value = .1.3.6.1.4.1.935 0.026425 match_sysoid: checking MIB apcc 0.026431 match_sysoid: checking MIB mge 0.026435 match_sysoid: comparing .1.3.6.1.4.1.935 with .1.3.6.1.4.1.705.1 0.026439 match_sysoid: checking MIB ne...

...2.7.1-signed-54-g348cd84) 0.000000 debug level is '2' 0.000353 SNMP UPS driver : entering upsdrv_initups() 0.000363 SNMP UPS driver : entering nut_snmp_init(snmp-ups) 0.023970 SNMP UPS driver : entering load_mib2nut(auto) 0.024013 trying the new match_sysoid() method 0.027661 match_sysoid: device sysOID value = .1.3.6.1.4.1.850.1 0.027683 match_sysoid: checking MIB apcc 0.027694 match_sysoid: checking MIB mge 0.027703 match_sysoid: comparing .1.3.6.1.4.1.850.1 with .1.3.6.1.4.1.705.1 0.027711 match_sysoid: check...

...able Cab ID: 0 P1: snmp-ups.exe P2: 0.0.0.0 P3: 5317277b P4: libnetsnmp-30.dll P5: 0.0.0.0 P6: 4f9128b9 P7: c0000005 P8: 000053e1 P9: P10: C:\Program Files (x86)\NUT\bin>snmp-ups.exe -a ups Network UPS Tools - Generic SNMP UPS driver 0.70 (Windows-v2.6.5-5-7-g72f380c) No matching MIB found for sysOID '.1.3.6.1.4.1.8072.3.2.10'! Please report it to NUT developers, with an 'upsc' output for your device. Going back to the classic MIB detection method. => Same error and entry in eventlog Any idea how to fix this and get the things work? Greeting Tobias -------------- next part...

...592 Update 4, with a NUT version of SDS5-2-2015Q1branch-5579-15061. I then attempted to connect my desktop via SNMP. My desktop is running Arch Linux, with a NUT version of 2.7.3. I seem to be able to connect to the NAS, but snmp-ups errors out with the following message: No matching MIB found for sysOID '.1.3.6.1.4.1.8072.3.2.10'! 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 Here is the output of upsc on the NAS: battery.charge: 100 battery.charge.low: 10 battery.charge.warn...

...t of postponed patch, with rationales. If you feel some of this should not wait for 2.8.0, tell me back. postponed - 8-10 (pyperl / snmp...) => need tree / deps handling revamp + [PATCH] "oops, forgot that I changed where nut-usbinfo.pl is to be run from!" - 11 => need advanced sysOID matching (is_subtree may not be enough, a linked list of sysOID may be needed... need more investigation) - 12 => not needed (static are refreshed and settable!). Need confirmation from Greg. - 19 => status "DYING" needs discussion - 28 => non standard vars (https://alioth.debian...

...2.7.1-signed-54-g348cd84) 0.000000 debug level is '2' 0.002156 SNMP UPS driver : entering upsdrv_initups() 0.002169 SNMP UPS driver : entering nut_snmp_init(snmp-ups) 0.025430 SNMP UPS driver : entering load_mib2nut(auto) 0.025464 trying the new match_sysoid() method 0.028413 match_sysoid: device sysOID value = .1.3.6.1.4.1.850.1 0.028449 match_sysoid: checking MIB apcc 0.028474 match_sysoid: checking MIB mge 0.028497 match_sysoid: comparing .1.3.6.1.4.1.850.1 with .1.3.6.1.4.1.705.1 0.028519 match_sysoid: check...

...;Hey all, > > I recently got an RMCARD205 for my Cyber UPS.... > >if I use no MIBS line in the config file, I get this: > > >> 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.3808.1.1.1'! >> Please report it to NUT developers, with an 'upsc' output for your >device. >> Going back to the classic MIB detection method. >> Detected PR1500LCDRTXL2Ua on host 192.168.125.10 (mib: cyberpower >0.1) >> Network UPS Tools...

...c SNMP UPS driver 0.68 (2.6.5) 0.000000 debug level is '2' 0.000327 SNMP UPS driver : entering upsdrv_initups() 0.000341 SNMP UPS driver : entering nut_snmp_init(snmp-ups) 0.056112 SNMP UPS driver : entering load_mib2nut(auto) 0.056126 trying the new match_sysoid() method 1.119440 match_sysoid: device sysOID value = .1.3.6.1.4.1.318 1.119456 match_sysoid: checking MIB apcc 1.119469 match_sysoid: checking MIB mge 1.119474 match_sysoid: comparing .1.3.6.1.4.1.318 with .1.3.6.1.4.1.705.1 1.119481 match_sysoid: checking MIB ne...

...ces are UPS, PDU, server power supplies and solar controllers, as supported by the Network UPS Tools (NUT) project. NUT is the major free software for dealing with such devices: http://www.networkupstools.org/ NUT has some internal automation that allows to extract these information (USB IDs, SNMP sysOIDs, IPMI PSU,...) from the drivers (so no declaration redundancy), in order to generate support files (udev, upower, ...) or tools such as the NUT scanner: http://www.networkupstools.org/docs/man/nut-scanner.html So, would you be interested in working with me on this topic? How can we proceed? Which...

Hey, I'm scheduling a 2.6.2 release for max. September 15. The content will be lighter than first expected with 2.8.0 (see below). This includes the current trunk plus: - merge the nut-scanner branch, - some snmp-ups improvements (sysOID matching for init stage) and some more MIBs, - a first complete version of the nut-ipmipsu driver, - the new jNut Java binding, - preliminary support of systemd integration. So if you have any patch that should be in 2.6.2, raise your hand... The following are postponed to 2.8.0: - the configurat...

I did a bunch of work on this today. It should be all set to go. This patch is to add support for the Cyberpower RMCARD snmp cards. I basically copied the driver for bestpower, changed the name and updated the mib map. I have this running on two separate systems (two separate ups's) and it looks good. The only thing I could not figure out was updating the Makefile.am (my aclocal/libtools

Hello, I have an NETYS RT 1/1 UPS, which is not fully supported. Starting snmp driver displays: [root at kvm1 ~]# snmp-ups -a local Network UPS Tools - Generic SNMP UPS driver 0.66 (2.6.4) Duplicate driver instance detected! Terminating other driver! No matching MIB found for sysOID '.1.3.6.1.4.1.2254.2.4'! Please report it to NUT developers, with an 'upsc' output for your device. Going back to the classic MIB detection method. Detected NETYS RT 1/1 UPS on host 192.168.14.10 (mib: ietf 1.4) [local] unhandled ASN 0x5 received from 1.3.6.1.2.1.33.1.2.3.0 [local]...

Hello, I have an NETYS RT 1/1 UPS, which is not fully supported. Starting snmp driver displays: [root at kvm1 ~]# snmp-ups -a local Network UPS Tools - Generic SNMP UPS driver 0.66 (2.6.4) Duplicate driver instance detected! Terminating other driver! No matching MIB found for sysOID '.1.3.6.1.4.1.2254.2.4'! Please report it to NUT developers, with an 'upsc' output for your device. Going back to the classic MIB detection method. Detected NETYS RT 1/1 UPS on host 192.168.14.10 (mib: ietf 1.4) [local] unhandled ASN 0x5 received from 1.3.6.1.2.1.33.1.2.3.0 [local]...

...: SETINFO driver.parameter.port "10.9.40.196" 0.000043 debug level is '7' 0.000490 SNMP UPS driver : entering upsdrv_initups() 0.000501 SNMP UPS driver : entering nut_snmp_init(snmp-ups) 0.001679 SNMP UPS driver : entering load_mib2nut(auto) 0.001691 trying the new match_sysoid() method 0.001696 Entering nut_snmp_get_str() 0.001706 nut_snmp_get(.1.3.6.1.2.1.1.2.0) 6.008128 Can't get sysOID value 6.008150 load_mib2nut: trying classic method with 'apcc' mib 6.008157 Entering nut_snmp_get_str() 6.008169 nut_snmp_get(.1.3.6.1.4.1.318.1.1.1.1.1.1.0) 12...