> > According to mge-mib.c (NUT 2.6.2) LB condition > > is gained from variable .1.3.6.1.4.1.705.1.5.14.0 (i.e. > > upsmgBatteryLowBattery.0). > > > > The test device of me does not set this variable to yes(1) > > even if runtime drops below the preconfigured limit. > > I complained about this at Schneider Electric. > > They replied that low battery status is indicated by > > .1.3.6.1.4.1.705.1.5.14.0 (upsmgBatteryLowCondition.0).
Original mail: | When "upsmgConfigLowBatteryTime" is SET to 9999 and current | "upsmgBatteryRemainingTime" is below 9999 second, | "upsmgBatteryLowCondition" will have value 1, when UPS will be on battery | => NOT "upsmgBatteryLowBattery", which is linked with | "upsmgBatteryLowBatteryLevel" (i suppose, not tested) | | Now, for IETF MIB, "upsBatteryStatus" goes to value 3 when | "upsmgBatteryLowCondition" goes to value 1 > copy/paste error: you probably meant 1.3.6.1.4.1.705.1.5.16.0 Sure. You are absolutely right. :) I missed the number. > That said, I've added and committed the above OID with the standard lowbatt > mapping (1 = LB, 2 = <not LB>) > Can you please test the trunk, r3318? Thanks. I'll do in a week or so. Unfortunately at this moment I'm quite busy. Regards Gabor -- E-mail = m-mail * c-mail ^ 2 _______________________________________________ Nut-upsdev mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
