And here comes nut into play, running on another system and offering a uniform network approach for EVERY UPS.īut for this, a network client on the router is needed.Īll my servers/nas/workstation connect to my NUT server and when we get a power outage they all shutdown (Different times for each) base on my configs. This protocol is of course not supported by MT, as if APC is the only "real" UPS manufacturer. the blazer protocol is used by a lot of manufacturers (Ablerex, ActivePower, ARTronic, ATEK, some Belkins, Borri, Cover, Dynamix, Effekta, Ever, Fenton, GE Digital Energy, Gtec, Infosec, Ippon, Kolff, Krauler, Maxxtro, Microline, Mustek, Plexus, Powerex, Powerguard, PowerWalker, Soyntec, Sven, some Sweex, Sysgration, Tecnoware, Trust, Unitek, some Upsonic and a lot of others). No one said to implement nut on the having a network attached UPS starts with the false assumption that you have one.Īnd while supporting the APC protocol is nice, most of the UPSes out there are not APC compatible.Į.g. The possibility to connect to another system running the nut daemon to interrogate the UPS status and take decisions based on that data. But you are right, nut may offer also snmp services through the nut-snmpagent wrapper.Īgain, it is about the nut client. I had put this in discussion some time time ago:īut it seems that everyone understands to implement the NUT server, not the client.
0 Comments
Leave a Reply. |