JayG30
Contributor
- Joined
- Jun 26, 2013
- Messages
- 158
Hello,
Looking to see if anyone else has seen this or has an input on where to look. I have a TrippLite SU6000RT4UHVPM with the TrippLite SNMP webcard in it.
In the UPS settings I set:
Driver: "Various ups 3 (various) SNMP - RFC 1628 (snmp-ups)"
Port: "IP or Hostname of UPS"
Just defining these two settings appeared to work. Issuing upsc tripplite seems to report back everything you would expect!
For hours this worked fine. Than all of a sudden, with no real explanation I can come up with, I get emails about COMMBAD - tripplite (I should note two identical emails actually, think that is a bug in freenas). Also see on the CLI something like this;
After a few minutes it is reconnected! Issuing the upsc tripplite command works no problem.
I thought perhaps it needed some more parameters in ups.conf to make it work reliably so I added;
to auxiliary parameters. However the same issue keeps coming up.
It seems to me like something is preventing NUT from connecting to the UPS. My gut is saying this might not be caused by FreeNAS and the UPS is becoming inaccessible perhaps due to other traffic hitting the SNMP card. Or perhaps something in my network is limiting its packets. Or perhaps it really is something caused by NUT or FreeNAS.
Anyone have any insight, opinions, ideas?
Looking to see if anyone else has seen this or has an input on where to look. I have a TrippLite SU6000RT4UHVPM with the TrippLite SNMP webcard in it.
In the UPS settings I set:
Driver: "Various ups 3 (various) SNMP - RFC 1628 (snmp-ups)"
Port: "IP or Hostname of UPS"
Just defining these two settings appeared to work. Issuing upsc tripplite seems to report back everything you would expect!
Code:
[root@freenas] /usr/local/libexec/nut# upsc tripplite battery.charge: 100.00 battery.runtime: 4020.00 battery.temperature: 19.00 battery.voltage: 219.00 device.mfr: TRIPPLITE device.model: SU6000RT4UHVPM device.type: ups driver.name: snmp-ups driver.parameter.pollinterval: 2 driver.parameter.port: 192.168.0.24 driver.version: 2.7.2 driver.version.data: ietf MIB 1.4 driver.version.internal: 0.72 input.bypass.frequency: 60.00 input.bypass.phases: 1.00 input.bypass.voltage: 212.00 input.frequency: 60.00 input.phases: 1.00 input.transfer.high: 300.00 input.transfer.low: 100.00 input.voltage: 211.00 input.voltage.nominal: 220.00 output.current: 0.20 output.frequency: 60.00 output.phases: 1.00 output.realpower: 423.00 output.voltage: 220.00 ups.beeper.status: enabled ups.firmware: 06 ups.firmware.aux: 12.06.0064 ups.load: 80.00 ups.mfr: TRIPPLITE ups.model: SU6000RT4UHVPM ups.status: OL
For hours this worked fine. Than all of a sudden, with no real explanation I can come up with, I get emails about COMMBAD - tripplite (I should note two identical emails actually, think that is a bug in freenas). Also see on the CLI something like this;
Code:
Error: Connection failure: Connection refused
Broadcast Message from root@freenas
(no tty) at 11:51 EDT...
Communications with UPS tripplite lost
After a few minutes it is reconnected! Issuing the upsc tripplite command works no problem.
I thought perhaps it needed some more parameters in ups.conf to make it work reliably so I added;
Code:
pollfreq = 30 snmp_version = v2c community = tripplite
to auxiliary parameters. However the same issue keeps coming up.
It seems to me like something is preventing NUT from connecting to the UPS. My gut is saying this might not be caused by FreeNAS and the UPS is becoming inaccessible perhaps due to other traffic hitting the SNMP card. Or perhaps something in my network is limiting its packets. Or perhaps it really is something caused by NUT or FreeNAS.
Anyone have any insight, opinions, ideas?
