Difference between revisions of "Uninterruptable Power Supply"

From SME Server
Jump to navigationJump to search
Line 3: Line 3:
  
 
====Standard configuration====
 
====Standard configuration====
If using USB just enable nut
+
If using USB just enable nut  
 
  config setprop nut status enabled
 
  config setprop nut status enabled
 +
config setprop nut Model newhidups (default)
 +
config setprop nut Device /var/lib/ups/hiddev0 (default/USB)
  
If using a serial port you have to set a Model and Device
+
Not all UPS's are supported by USB or the newhidups driver, refer to the link below
Find your model here http://www.networkupstools.org/compat/stable.html <br />
+
eg. config setprop nut Model bcmxcp_usb is for some Powerware units on USB
 +
or config setprop nut Model genericups is for other Powerware units that only work on serial
 +
 
 +
Find your Model here http://www.networkupstools.org/compat/stable.html <br />
 
Type is only used if your model is genericups <br />
 
Type is only used if your model is genericups <br />
  

Revision as of 12:53, 11 June 2007

Nut UPS – Uninterruptable Power Supply

The primary goal of the Network UPS Tools (NUT) project is to provide reliable monitoring of UPS hardware and ensure safe shutdowns of the systems which are connected.

Standard configuration

If using USB just enable nut

config setprop nut status enabled
config setprop nut Model newhidups (default)
config setprop nut Device /var/lib/ups/hiddev0 (default/USB)

Not all UPS's are supported by USB or the newhidups driver, refer to the link below eg. config setprop nut Model bcmxcp_usb is for some Powerware units on USB or config setprop nut Model genericups is for other Powerware units that only work on serial

Find your Model here http://www.networkupstools.org/compat/stable.html
Type is only used if your model is genericups

config setprop nut Model apcsmart 
config setprop nut Device /dev/ttyS0
config setprop nut Type 7
config setprop nut status enabled 

check

config show nut

apply changes and restart server

signal-event post-upgrade ; signal-event reboot 

alternatively

expand-template /etc/sysconfig/ups
expand-template /etc/ups/ups.conf
expand-template /etc/ups/upssched.conf
expand-template /etc/ups/upsmon.conf
expand-template /etc/ups/upsd.users
expand-template /etc/ups/upsd.conf
/etc/rc7.d/S15nut restart

confirm server is communicating with UPS

upsc UPS@localhost

Emails are sent to admin whenever a UPS event occurs

Configuring as a slave

where 192.168.33.11 is your UPS master, the computer that will communicate with the UPS The hostname of the server may also work.

set configuration values

config setprop nut SlaveUPS UPS@192.168.33.11
config setprop nut Master no

apply changes and restart server

signal-event post-upgrade ; signal-event reboot 

confirm server is communicating with master

upsc UPS@192.168.33.11

Conecting multiple UPS's

to be added http://bugs.contribs.org/show_bug.cgi?id=629