search for: xppc

...1.4.1.935 It says: snmpwalk: Timeout (msgGlobalData header type A2: s/b 30) But snmpget of a certain parameter works fine and we are currently able to monitor it through Zabbix's snmp: snmpget -v 1 -c public 10.200.254.39 .1.3.6.1.4.1.935.1.1.1.4.1.1 Output shows the correct value of status: XPPC-MIB::upsBaseOutputStatus.0 = INTEGER: onLine(2) If it is possible for you, could you please run it from your pc in "mode 2" that doesn't require direct access to device (mib file is attached)? Thanks in advance, Ishi On Mon, Feb 10, 2014 at 8:56 PM, Charles Lepple <clepple...

...file.am +++ b/drivers/Makefile.am @@ -199,8 +199,7 @@ mge_shut_LDADD = $(LDADD) # SNMP snmp_ups_SOURCES = snmp-ups.c apc-mib.c baytech-mib.c compaq-mib.c eaton-mib.c \ ietf-mib.c mge-mib.c netvision-mib.c powerware-mib.c raritan-pdu-mib.c \ - bestpower-mib.c cyberpower-mib.c delta_ups-mib.c \ - xppc-mib.c + bestpower-mib.c cyberpower-mib.c delta_ups-mib.c xppc-mib.c huawei-mib.c snmp_ups_LDADD = $(LDADD_DRIVERS) $(LIBNETSNMP_LIBS) # NEON XML/HTTP @@ -264,7 +263,7 @@ dist_noinst_HEADERS = apc-mib.h apc-hid.h baytech-mib.h bcmxcp.h \ delta_ups-mib.h nutdrv_qx.h nutdrv_qx_bestups.h nutdrv_q...

...1 clear is that's it not a completed effort... at all > but, still IIRC, it should have produced at least a bit more Hi Arnaud, I may not have been specific enough in my description. The crash that Jason saw is with the version of snmp-ups that is currently in Git - including the new 'xppc' MIB, but the NULL pointer in question is also in 'delta_ups'. Given that mib2nut[i]->oid_auto_check is only used for the "classic" OID check, I think we can just add a special case to check for NULL, and continue the loop if oid_auto_check has not been provided. > @Ja...

...: checking MIB cyberpower 0.018764 match_sysoid: comparing .1.3.6.1.4.1.476.1.42 with .1.3.6.1.4.1.3808 0.018773 match_sysoid: checking MIB delta_ups 0.018783 match_sysoid: comparing .1.3.6.1.4.1.476.1.42 with .1.3.6.1.4.1.2254.2.4 0.018792 match_sysoid: checking MIB xppc 0.018802 match_sysoid: comparing .1.3.6.1.4.1.476.1.42 with .1.3.6.1.4.1.935 0.018811 match_sysoid: checking MIB huawei 0.018821 match_sysoid: comparing .1.3.6.1.4.1.476.1.42 with .1.3.6.1.4.1.8072.3.2.10 0.018830 match_sysoid: checking MIB ietf 0.018839 matc...

2014-02-25 12:58 GMT+01:00 Charles Lepple <clepple at gmail.com>: > On Feb 24, 2014, at 11:48 PM, Jason R Begley wrote: > > > 0.073855 load_mib2nut: trying classic method with 'delta_ups' mib > > 0.073878 Entering nut_snmp_get_str() > > 0.073899 nut_snmp_get((null)) > > 0.073918 nut_snmp_walk((null)) > > Arnaud, > >

...s, upsBaseOutputStatus, upsSmartOutputLoad - is all we need. And maybe traps, to know when UPS goes on battery, online etc. > As I wrote earlier, snmpget commands are working fine "snmpget -v 1 -c public 10.200.254.39 .1.3.6.1.4.1.935.1.1.1.4.1.1" returning correct results: > > XPPC-MIB::upsBaseOutputStatus.0 = INTEGER: onLine(2) > > I would like to take this opportunity to make sure that gen-snmp-subdriver is working, so can you please run the following commands: snmpget -v 1 -c public -On 10.200.254.39 .1.3.6.1.4.1.935.1.1.1.1.1.1 1.3.6.1.4.1.935.1.1.1.4.1.1 1.3....

...0.060391 nut_snmp_get(.1.3.6.1.4.1.2254.2.4.1.2.0) 0.060396 nut_snmp_walk(.1.3.6.1.4.1.2254.2.4.1.2.0) 0.060401 nut_snmp_walk: max. iteration = 1 0.060409 load_mib2nut: testOID provided and doesn't match MIB 'delta_ups'! 0.060415 load_mib2nut: trying classic method with 'xppc' mib 0.060420 su_find_info: "ups.model" found 0.060426 Testing ups.model using OID .1.3.6.1.4.1.935.1.1.1.1.1.1.0 0.060431 Entering nut_snmp_get_str() 0.060436 nut_snmp_get(.1.3.6.1.4.1.935.1.1.1.1.1.1.0) 0.060441 nut_snmp_walk(.1.3.6.1.4.1.935.1.1.1.1.1.1.0) 0.06044...

...254.26 command output shows the UPS status as shown below:) battery.charge: 100.00 device.mfr: Tripp Lite / Phoenixtec device.model: Intelligent device.type: ups driver.name: snmp-ups driver.parameter.pollinterval: 2 driver.parameter.port: 10.200.254.39 driver.version: 2.7.1.5 driver.version.data: xppc MIB 0.2 driver.version.internal: 0.71 input.voltage: 213.30 output.frequency: 50.00 output.voltage: 230.80 ups.load: 7.00 ups.mfr: Tripp Lite / Phoenixtec ups.model: Intelligent ups.status: OL ups.temperature: 28.00 Thanks so much for your help, it's great to know that with your and the team...

...53277 load_mib2nut: trying classic method with 'bestpower' mib 84.160268 load_mib2nut: trying classic method with 'cyberpower' mib 90.167252 load_mib2nut: trying classic method with 'delta_ups' mib 90.167275 load_mib2nut: trying classic method with 'xppc' mib 90.167281 load_mib2nut: trying classic method with 'ietf' mib 96.174289 No supported device detected You may want to take a look output with higher debug level: http://pastebin.com/GEcxkjv7 Both of them use snmpv3 with SHA1 and DES What could it be wrong? Thanks in...

...er will result in this error: `Unable to connect to CIFS host, will retry in 60 seconds' After three retries, CUPS will disable the printer. Using 3.0.22 does not cause this error and print jobs are transmitted normally. However, when using 3.0.23c I can connect to the printer smbclient //xppc/printer and print a text file to it using smb:\> print filename with no error other than missing the CR/LF at EOL. Additional Info: --------------- I have also been experiencing a problem printing from an XP Home Laptop to a Samba 3.0.23c server set up as Standalone/Share level yet other XP...

...soid: checking MIB cyberpower 0.027836 match_sysoid: comparing .1.3.6.1.4.1.850.1 with .1.3.6.1.4.1.3808 0.027841 match_sysoid: checking MIB delta_ups 0.027847 match_sysoid: comparing .1.3.6.1.4.1.850.1 with .1.3.6.1.4.1.2254.2.4 0.027853 match_sysoid: checking MIB xppc 0.027859 match_sysoid: comparing .1.3.6.1.4.1.850.1 with .1.3.6.1.4.1.935 0.027864 match_sysoid: checking MIB ietf 0.027872 match_sysoid: comparing .1.3.6.1.4.1.850.1 with .1.3.6.1.2.1.33 0.027878 No matching MIB found for sysOID '.1.3.6.1.4.1.850.1'! Pleas...

...soid: checking MIB cyberpower 0.028969 match_sysoid: comparing .1.3.6.1.4.1.850.1 with .1.3.6.1.4.1.3808 0.028988 match_sysoid: checking MIB delta_ups 0.029010 match_sysoid: comparing .1.3.6.1.4.1.850.1 with .1.3.6.1.4.1.2254.2.4 0.029030 match_sysoid: checking MIB xppc 0.029052 match_sysoid: comparing .1.3.6.1.4.1.850.1 with .1.3.6.1.4.1.935 0.029073 match_sysoid: checking MIB ietf 0.029095 match_sysoid: comparing .1.3.6.1.4.1.850.1 with .1.3.6.1.2.1.33 0.029115 No matching MIB found for sysOID '.1.3.6.1.4.1.850.1'! Pleas...

...utStatus, upsSmartOutputLoad - is all we need. And maybe traps, > to know when UPS goes on battery, online etc. > As I wrote earlier, snmpget commands are working fine "snmpget -v 1 -c > public 10.200.254.39 .1.3.6.1.4.1.935.1.1.1.4.1.1" returning correct > results: > > XPPC-MIB::upsBaseOutputStatus.0 = INTEGER: onLine(2) > > > > I would like to take this opportunity to make sure that gen-snmp-subdriver > is working, so can you please run the following commands: > > snmpget -v 1 -c public -On 10.200.254.39 > .1.3.6.1.4.1.935.1.1.1.1.1.1 1.3.6.1...

...ted effort... at all >> but, still IIRC, it should have produced at least a bit more > > Hi Arnaud, > > I may not have been specific enough in my description. > > The crash that Jason saw is with the version of snmp-ups that is > currently in Git - including the new 'xppc' MIB, but the NULL pointer > in question is also in 'delta_ups'. > > Given that mib2nut[i]->oid_auto_check is only used for the "classic" > OID check, I think we can just add a special case to check for NULL, > and continue the loop if oid_auto_check has n...

On Feb 24, 2014, at 6:57 PM, Jason R Begley wrote: > Segmentation fault That's not good. If you crank up the debug level past 2, does it provide any more detail about where it crashed? (We'd only need the last few lines, if they are different.) I don't know how Arch Linux does debug symbols, so the dmesg output doesn't pinpoint which function in libc got bad data. Can you run

On Feb 10, 2014, at 1:16 AM, ??? ????? wrote: > Thanks for you reply. Concerning the subscribtion list, I have earlier filled in the fields and sent request to subscribe to this list, but still haven't got an answer. I added you manually, but check your spam folder just in case it ended up there. > Yes, I do have a MIB file that was on CD that came with the UPS, attached it to this

...ll -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -o snmp-ups snmp-ups.o apc-mib.o baytech-mib.o compaq-mib.o eaton-mib.o ietf-mib.o mge-mib.o netvision-mib.o powerware-mib.o raritan-pdu-mib.o bestpower-mib.o cyberpower-mib.o delta_ups-mib.o xppc-mib.o huawei-mib.o eaton-ats16-mib.o apc-ats-mib.o raritan-px2-mib.o eaton-ats30-mib.o apc-pdu-mib.o main.o dstate.o -Wl,-z -Wl,relro -Wl,-z -Wl,now ../common/.libs/libcommon.a ../common/.libs/libparseconf.a -L/usr/lib64 -lnetsnmp -lpthread nutdrv_qx-nutdrv_qx.o: In function `ippon_command'...

On Feb 24, 2014, at 10:29 PM, Jason R Begley wrote: > Thanks for the quick response Charles! I may not have gotten the correct output from the snmpwalk, let me know if the attachment is usable. Thanks! Sorry, it's basically all comments. Do you have the stdout from the subdriver script? Also, how is the MIB file installed? > New data added, here is the gdb output: > Reading

...soid: checking MIB cyberpower 0.029305 match_sysoid: comparing .1.3.6.1.4.1.850.1 with .1.3.6.1.4.1.3808 0.029325 match_sysoid: checking MIB delta_ups 0.029347 match_sysoid: comparing .1.3.6.1.4.1.850.1 with .1.3.6.1.4.1.2254.2.4 0.029367 match_sysoid: checking MIB xppc 0.029389 match_sysoid: comparing .1.3.6.1.4.1.850.1 with .1.3.6.1.4.1.935 0.029408 match_sysoid: checking MIB ietf 0.029430 match_sysoid: comparing .1.3.6.1.4.1.850.1 with .1.3.6.1.2.1.33 0.029450 No matching MIB found for sysOID '.1.3.6.1.4.1.850.1'! Pleas...

Hi, Nut-upsusers, I am having problem configuring NUT to work with Tripplite UPS through SNMP. There is a Tripplite SmartOnline SU10KRT3/1X and attempts to monitor it using NUT though SNMP are failing... OS: Enterprise Linux 6, Nut version: 2.6.5. ups.conf is configured: [trippliteups] driver = snmp-ups port = 10.200.254.39 desc = "ProductionServer"