Difference between revisions of "Uninterruptable Power Supply"

From SME Server
Jump to navigationJump to search
m (added comment re operational until critical battery state reached)
m (add language bar)
Line 1: Line 1:
 +
{{Languages}}
 +
 
===Nut UPS – Uninterruptable Power Supply===
 
===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.  
 
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.  

Revision as of 13:25, 2 May 2008


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.

The default configuration of NUT, will keep your connected systems operational until a critical battery state is reached (ie battery is nearing exhaustion) and then power down your server/equipment in a controlled fashion. See http://www.networkupstools.org/


Default Configuration

Most USB UPS devices will work with the default settings. If using a USB device just enable nut as follows.

config setprop nut status enabled
signal-event post-upgrade
signal-event reboot

If your USB UPS does not work properly OR you have a serial device then follow the optional instructions below.

Optional Configuration Options

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
Note: "Type" is only used if your model is genericups
Caution: ALWAYS use the cable supplied with the UPS. Standard serial cables won't work with a serial UPS and have even been known to cause damage to the UPS.


These are basic example settings. Replace the properties with the appropriate settings for your UPS.

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/*
/etc/rc7.d/S38nut start

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


Aditional Information

There are template fragments in /etc/e-smith/templates/etc/ups that control the config files located in /etc/ups. The default settings should be OK for most situations.

For information on configuration parameters

man ups.conf
man upsd.conf
man upsd.users
man upsmon.conf
man upssched.conf

For general information

man upsd
man nutupsdrv